Theo de Raadt wrote:
> sensiblehue wrote:
>
> > On Thu, Jun 11, 2020 at 03:08:01PM +0200, Marc Espie wrote:
> > > On Thu, Jun 11, 2020 at 04:37:34AM +, sensiblehue wrote:
> > > > Hello,
> > > > I was wondering why OpenBSD doesn't have a `__p
sensiblehue wrote:
> On Thu, Jun 11, 2020 at 03:08:01PM +0200, Marc Espie wrote:
> > On Thu, Jun 11, 2020 at 04:37:34AM +, sensiblehue wrote:
> > > Hello,
> > > I was wondering why OpenBSD doesn't have a `__printflike' macro in
> > > ? FreeBSD, NetBSD, and DragonflyBSD have it and it's also
Because we don't.
sensiblehue wrote:
> Hello,
> I was wondering why OpenBSD doesn't have a `__printflike' macro in
> ? FreeBSD, NetBSD, and DragonflyBSD have it and it's also
> available from libbsd on Linux.
> Personally I think it's cleaner and just as portable if not more
> portable, because
i386 showed the correct amount of memory *it could use*.
man Chan wrote:
> Thanks. I tried to use amd64 which show the correct memory size.
> Is there a way to use i386 to show the correct size of memory ? The bios
> shows 8G memory. Did I miss something to make it ?
> Clarence
>
>
I was halfway there.
That's an old bug.
Philip Guenther wrote:
> On Sat, Jun 6, 2020 at 5:08 PM Zé Loff wrote:
>
> > On Sat, Jun 06, 2020 at 03:51:58PM -0700, Jordan Geoghegan wrote:
> > > I'm working on a simple awk snippet to convert the IP range data listed
> > in
> > > the Extended
east merely unveil â./â as
> âcwâ;
> make any specified cafile/capath including shortcut resolution as ârâ
> (perhaps with the shell âxâ) so that at worst, current directory files
> could be overwritten, but not read?
>
> On Wed, Jun 3, 2020 at 10:39 AM Theo d
You really don't get it.
+ unveil_list = calloc(2 * argc, sizeof(char*));
Imagine argc is 1.
+ for (i = 2 * argc - 2; i >= 0; i -= 2) {
+ if (unveil_list[i]) {
+ if
. It only took 2 or 3 days to figure out what it was doing
> and change
> it. I left in the fprintf()s to so that I could amuse you.
>
> I’m kinda surprised that you didn’t go straight for the “submit a diff.
> Anything you
> submit will just be rejected anyway!”
>
>
Thank you for the laugh.
Luke Small wrote:
> I think I'm done tinkering. try these out in ftp folder. I left in some
> fprintf(ttyout,...) in main.c
> to show what is being unveiled. It resolves shortcuts in SSL_CAFILE
> and SSL_PATH variables.
> It leaves in place the functionality of the
Kevin Chadwick wrote:
> On 2020-06-01 11:20, Stuart Henderson wrote:
> > We went through this earlier when unveil was added to nc. The way capath
> > directories are often populated in the real world is not compatible with
> > unveil, you would need to resolve all files in capath, recursively
Stuart Henderson wrote:
> On 2020-05-29, Christopher Turkel wrote:
> > On Friday, May 29, 2020, Stuart Henderson wrote:
> >
> >> On 2020/05/29 08:30, Luke Small wrote:
> >> > You mention a lot of files that need to be read, but a program like
> >> pkg_add can make it the
> >> > _pkgfetch (57)
you are wasting everyone's time if you don't write a diff, which you've
tested.
Luke Small wrote:
> You mention a lot of files that need to be read, but a program like pkg_add
> can make it the _pkgfetch (57) user which has no directory and I’m guessing
> not in interactive mode. At the very
So you have one of these
ipw(4) - Intel PRO/Wireless 2100 IEEE 802.11b wireless network device
iwi(4) - Intel PRO/Wireless 2200BG/2225BG/2915ABG IEEE 802.11a/b/g wireless
network device
iwm(4) - Intel 7000/8000/9000 IEEE 802.11a/ac/b/g/n wireless network devices
iwn(4) - Intel WiFi Link and
A few tools have options like -s, but it is a problem.
I'm also frustrated by this solution, and working on a better method.
Pierre Emeriaud wrote:
> What is the current canonical way to tweak source address selection?
>
> I have a bgp multi-homed router, and while answers do use the correct
And by the way, if it is *just routing* -- in the kernel -- then
neither Meltdown NOR MDS are involved in what you perceive as
performance problems, since those only happen upon *context switch
to/from userland*.
As I was saying... we don't want to provide these knobs for people who
cannot make
Absolutely no interest at all.
Not interested in the source code complexity (it is worse than you
think), nor do we believe people's ability to make correct decisions
in regards to complicated security issues.
dhcpd, you say...
Elias Carter wrote:
> Would there be any interest in having a
Otto Moerbeek wrote:
> I run
>
> nice /usr/libexec/reorder_kernel &
>
> And my landisk is usable from the start.
I don't even tweak my landisk. These machines are 30% the
performance of the OP's complaint.
I don't see any reason to change the way it works.
An important note:
If you do any of that and subsequently encounter a problem, you must
1. Assume you created that problem for yourself
2. Not file a bug report
3. Not complain to others on OpenBSD mailing lists.
If that is an acceptable tradeoff, go ahead, make a mess.
Philippe wrote:
> On
You are on your own.
You knew that would be the answer. Be happy about it.
Dawid Czeluśniak wrote:
> Hi OpenBSD community,
>
> First of all, thank you for 6.7 release.
>
> I am a huge fan of minimal and custom installations
> as I mostly use OpenBSD to host simple HTTP servers.
> I
No.
Because what you say isn't true at all. That's limiting spin.
Chris Bennett wrote:
> I keep seeing people not getting the idea that OpenBSD has more of a
> philosophy of users needing to put out their own special efforts at
> learning, vs. other OS's.
>
> Do you think that mentioning
Bars Bars wrote:
> Thank you much.
>
> Do you mean i should not do syspatch if a modified kernel sources?
syspatches can deliver replacements for kernel .o files
So if you have changed a .h or .c file, the syspatches are not
going to work correctly.
Once you use source-code methods, you
Andre S wrote:
> The sha256 checksum data of the install67.img file is missing in the
> snapshot.
Fixed.
Andras Farkas wrote:
> Not sure whether to post this on misc@ or tech@, so trying misc@ first:
>
> Why isn't src included on OpenBSD, perhaps as an install fileset?
Because then we'd need to adjust the disk-layout expectations on every
architecture, and consider and match a variety of build
I've misinterpreted the situation.
Previous to 6.7, and probably in most other operating systems, this
was limited to 65535 / 100 or 644.
But now the range is extended. Wait about 3 days, upgrade, etc.
Theo de Raadt wrote:
> We supply source code, so this took under 60 seconds to f
We supply source code, so this took under 60 seconds to find:
SO_RCVTIMEO is in uipc_socket.c
memcpy(, mtod(m, struct timeval *), sizeof tv);
if (!timerisvalid())
return (EINVAL);
nsecs =
Aaron Mason wrote:
> On Fri, May 15, 2020 at 3:39 AM Nick Holland
> wrote:
> >
> > On 2020-05-14 11:08, i...@aulix.com wrote:
> >
> > I actually had Adaptec give me a firmware update with a time bomb in
> > it, and didn't bother to tell me that after X days, it would brick my
> > adapter and
Nick Holland wrote:
> On 2020-05-14 11:08, i...@aulix.com wrote:
> >> If that binary code was on a ROM, would it be less malicious?
> >
> > Cannot more recent and up to date binary code be more malicious than
> > old one in the ROM?
>
> This has nothing to do with OpenBSD. That can be true
i...@aulix.com wrote:
> > If that binary code was on a ROM, would it be less malicious?
>
> Cannot more recent and up to date binary code be more malicious than old one
> in the ROM?
Our firmwares do not replace code on ROM, since the hardware in question
HAS NO ROM.
Janne Johansson wrote:
> Den tors 14 maj 2020 kl 06:27 skrev Mogens Jensen <
> mogens-jen...@protonmail.com>:
>
> > Normally I would just assume that fetched files are verified, but maybe
> > in the case with fw_update, the rationale is that firmware files are
> > binary blobs so we can't know
The firmwares are packages, and are signed with the
/etc/signify/openbsd-XX-fs.pub key.
There is no risk.
Mogens Jensen wrote:
> I was just trying out the fw_update program on OpenBSD 6.5, deleting/
> installing all the firmware and was wondering if fw_update will verify
> the files before
Kevin Chadwick wrote:
> The unveil man page is perfectly correct and it is not hard to test it's
> behaviour.
>
> I just wonder if it may aid unveil adoption in languages other than C, if it
> explicitly mentioned that exec is not required on a dir to allow reading the
> files within, e.g. if
Theo de Raadt wrote:
>
>
> Stuart Henderson wrote:
>
> > On 2020-05-07, Marko Cupać wrote:
> > > Hi,
> > >
> > > why not change default constraint server in ntpd.conf from current
> > > https://google.com to something more neutral /
Stuart Henderson wrote:
> On 2020-05-07, Marko Cupać wrote:
> > Hi,
> >
> > why not change default constraint server in ntpd.conf from current
> > https://google.com to something more neutral / reputable?
> >
> > If https://www.openbsd.org does not want to be involved, perhaps
> >
d. moreover ldp address message structure is nothing about the
> configuration at all.
>
> чт, 7 мая 2020 г., 21:29 Theo de Raadt :
>
> Sergey wrote:
>
> > ok theo, you are very user friendly as always.
> > you may be think that users should sol
Sergey wrote:
> ok theo, you are very user friendly as always.
> you may be think that users should solve their issues themself and would be
> nice if
> they will post their effort here for you, very fair.
You want the people on misc@ to decide for you if code from 2018 might
work better than
urpose. And i asked if it expected behavior or not?
> it was my effort to analyze the issue on my setup.
>
> чт, 7 мая 2020 г., 18:12 Theo de Raadt :
>
> Sergey wrote:
>
> > Hi.
> >
> > Im using the pretty old release 5.5 on openbsd box acting
> > as M
Sergey wrote:
> Hi.
>
> Im using the pretty old release 5.5 on openbsd box acting
> as MPLS PE router with many domains, and i noticed that
> ldpd sends huge ldp address message including all interfaces
> in every rdomains.
> Looking at the -current sources it seems there is the same behavior,
pfctl has an ruleset optimizer built in, which handles most of that.
So, it is best if you write rules in a way that makes sense.
Lars Bonnesen wrote:
> Is it no longer important to group block/pass in/out for speed optimization?
>
> I see many "modern" pf.conf where everything is mixed more
Adam Thompson wrote:
> AFAICT, GNU RCS (v5.9.4, ca. 2015, examined) creates a temp file,
> unlinks the target file, then renames the temp file. I beleve this
> guarantees(-ish, modulo "special" filesystems including NFS and
> FreeBSD's directory-SUID behaviour) that resulting file ownership =
>
I think it would be worthwhile describing the multi-user mode of operation of
> RCS in
> the manual, as it's currently completely absent/omitted. Patch coming soon,
> maybe
> tomorrow if I can make time.
>
> -Adam
>
> On Apr. 29, 2020 21:28, Theo de Raadt wrote:
>
athom...@athompso.net wrote:
> Heh, good point. Didn't even occur to me because as it happens, I am
> running as root and would like to not change the ownership.-Adam
> On Apr. 29, 2020 13:32, Anders Andersson wrote:
>
> On Wed, Apr 29, 2020 at 7:46 PM Adam Thompson
> wrote:
> >
> >
f.holop wrote:
> would it be possible to regenerate the latest snapshots
> (amd64, cdn.openbsd.org)? some of the archives show
> checksum errors...
No.
Builds are continual, but the mirrors can temporarily de-sync
and have a partial.
That's what is going on, nothing more.
Amelia A Lewis wrote:
> So, and I recognize that the answer might reasonably be "go read more
> code and figure it out yourself," a question for Theo and others if you
> have a moment: why couldn't an arch expand past sixteen? It seems, both
> from the math calculating struct size (which may
Strahil Nikolov wrote:
> On April 25, 2020 4:09:53 AM GMT+03:00, Theo de Raadt
> wrote:
> >Allan Streib wrote:
> >
> >> Theo de Raadt writes:
> >>
> >> > OpenBSD has apparently become popular amongst people who can't
> >think
&g
Allan Streib wrote:
> Theo de Raadt writes:
>
> > OpenBSD has apparently become popular amongst people who can't think
> > and connect "real world constraints" and "reality" with "no alternative
> > decision was possible". This is very
Allan Streib wrote:
> Theo de Raadt writes:
>
> > Allan Streib wrote:
> >
> >> Seems like one of those numbers that was chosen long ago, when disks
> >> had orders of magnitude less storage capacity they have now, and 16
> >> parti
Allan Streib wrote:
> Seems like one of those numbers that was chosen long ago, when disks
> had orders of magnitude less storage capacity they have now, and 16
> partitions really would have been more than enough.
the word "chosen" makes it seem like such an arbitrary decision.
As currently
Lars,
Your email didn't contain a diff.
Is there a reason for that?
I'm wondering whether it is because it is too difficult for you,
or maybe it is too difficult for everyone, or maybe you are simply
talking out of your ass by trying to assign work to other people
because that is your nature?
Todd C. Miller wrote:
> On Wed, 22 Apr 2020 21:21:28 -0600, "Todd C. Miller" wrote:
>
> > That's fine with me. Those interfaces appeared in SunOS 4.0 according
> > to tzcode (which is where we got them from). They did *not* originate
> > in NetBSD. I've verified that they were present in
You need to stop making this mailing list just about you.
STFU.
wrote:
> "Martin Schröder" wrote:
> > Am Do., 23. Apr. 2020 um 21:31 Uhr schrieb :
> >> No problem. Would it be too crude a suggestion that we go back to the
> >> content now...?
> >
> > You didn't provide any patch.
>
> That
You made it all up.
wrote:
> theo wrote:
> > That is a rewriting of history.
>
> It's history the way meknows it. Mecertainly predates some of it.
>
> > The disklabel format predates the PC.
>
> Indeed. Mewasn't sure where and when exactly it appeared, so meleft that
> bit out. But medid
That is a rewriting of history.
The disklabel format predates the PC.
It came from the the ancient attempt to handle things in CSRG's
4.3reno/4.4 work on the hp300. It was probably a rewrite of the
native HPUX disk format.
This was then put on all the other architectures, as a unified
view of
Groot wrote:
> I've tried and failed to create more than 16
> partitions on OpenBSD. First of all I don't
> understand the difference between the operations
> performed by fdisk and disklabel. Is it that
> OpenBSD sees partitions differently? First we
> create an OpenBSD partition with fdisk
William Ahern wrote:
> On Tue, Apr 21, 2020 at 02:01:10PM +0200, Otto Moerbeek wrote:
> > On Tue, Apr 21, 2020 at 10:51:54AM +, Roderick wrote:
> >
> > >
> > > Acording to the man page: "timegm() is a deprecated interface that
> > > converts [...]"
> > >
> > > O.K., deprecated. And what
Looks broken.
Mihai Popescu wrote:
> Hi,
>
> It's clear OpenBSD is moving to sndioctl. I used it, but I got some
> "strange" behaviour.
> Watching youtube in chromium, tried this:
>
> $ sndioctl output.level=1
> default: can't open control device
>
> After closing / restarting chromium, and
You don't know your place.
wrote:
> Morning Theo,
>
> theo wrote:
> > Alexandre Ratchov wrote:
> >> Hi,
> >>
> >> mixerctl is still the appropriate tool here, sndioctl is not inteded
> >> to be run as root.
> >>
> >> usbhidaction runs as root, given /dev/uhidN permissions, it's clearly
> >>
wrote:
> > usbhidaction runs as root, given /dev/uhidN permissions, it's clearly
> > not intended to run "high level" user commands.
>
> The keys, however frivolous memight find them, are clearly to apply to
> the output belonging to the terminal that the kbd is attached to.
You are welcome to
Alexandre Ratchov wrote:
> On Tue, Apr 21, 2020 at 03:15:58AM +0200, Erling Westenvik wrote:
> > > >
> > > > I'm a bit confused now... so why the previous usbhidaction configuration
> > > > (which was aligned to the manpage suggestions and worked flawlessly for
> > > > years) doesn't work
Raul Miller wrote:
> On Sat, Apr 18, 2020 at 12:25 PM Aham Brahmasmi
> wrote:
> > The examples and Theo's reply helped in understanding the nuance. It
> > might seem logical and common sense on further thought, as Janne has
> > pointed out. But at least in my case, it was not immediately
considering a job scheduled like
> >
> > ~ ~ * * * somecommand
> >
> > I'm assuming, provided that the cron daemon is not restarted, this would
> > run the job at a single random point in each 24h period, right? A
> > *different* point in time, each 24 period
Yes.
But that problem already existed with the minutes field being >close to
the moment cron was restarted.
Only difference is now you don't know the minute.
Andreas Kusalananda Kähäri wrote:
> Thanks for the ~ crontab(5) feature!
>
> Question: If the cron daemon is restarted (e.g. via
Nothing you are saying has any relevance to the use of OpenBSD.
The chatter is useless.
Stop it.
zap wrote:
>
>
> I think theo is about the same as Linus in how foul he can get...
>
> but on the other hand, he at least doesn't wreck his software with
> pointless things like redhat's crap,
What does this have to do with OpenBSD?
zap wrote:
>
>
>
> On 04/14/2020 04:22 PM, Theo de Raadt wrote:
> > What the hell does this have to do with OpenBSD?
> >
> >
> Probably it has nothing to do with OpenBSD, since they are no longer
> talking about
What do thsi have to with OpenBSD?
zap wrote:
> Well just to correct myself, seeming libre. It isn't actually that much
> more libre than OpenBSD.
>
>
> On 04/14/2020 05:54 PM, zap wrote:
> >
> > On 04/14/2020 04:22 PM, Theo de Raadt wrote:
> >>
What does this have to do with OpenBSD?
Steve Litt wrote:
> On Tue, 14 Apr 2020 22:38:00 +0300
> Consus wrote:
>
> > On Tue, Apr 14, 2020 at 03:12:18PM -0400, Raul Miller wrote:
> > > last I checked, systemd was not modular, was poorly documented,
> > > exhibited incompatibilities with
What does this have to do with OpenBSD?
Raul Miller wrote:
> On Tue, Apr 14, 2020 at 1:37 PM Consus wrote:
> > On Tue, Apr 14, 2020 at 05:10:14PM +0200, Oddmund G. wrote:
> > > I know all this, Ottavio. I have been using GNU+Linux since 1994 after
> > > several years with Ultrix/VMS/OpenVMS
What the hell does this have to do with OpenBSD?
i...@aulix.com wrote:
> There are IMHO a few of good systemD free Linux distros:
> Devuan - Debian without systemD
> Parabola - Arch without systemD
>
> Alpine unfortunately lacks verification of checksums of earlier installed
> files.
>
>
Patrick Harper wrote:
> I mean that all Chromium releases are made available for OpenBSD-stable
> (excluding the previous release at any given time, as with all existing port
> maintenance).
So you want constant Chromium updates in -stable.
Who's going to do that?
Are you going to do it?
Elias M. Mariani wrote:
> Actually, I was just checking the ports-changes mailing-list, and the
> sync between Iridium and Chromium made me ask this.
Step right up, step right up, there's room for volunteers
Raymond, David wrote:
> That said, I am a bit nervous about OpenBSD's lags in
> keeping up with browser security fixes.
It isn't that simple.
They don't ship security fixes standalone. Instead, they ship a mix of
new changes *and* fixes. Lots of new unrelated changes, and only a few
security
I am succesfully relinking kernels on a landisk with 128MB of ram.
I think this conversation is ridiculous:
If a machine is too small, then it is too small. Do I have to paypal
a $0.05 to some users?
Nick Holland wrote:
>
>
>
> On 2020-04-10 10:10, Stefan Sperling wrote:
> > On Fri, Apr
Because either string could be shorter than len.
strncasecmp() and strncasecmp_l() compare at most len characters.
^^^
"NUL-terminated string" is firmly explaining to people that in C,
a string is only a string if it ends in a NUL. There's
Claus Assmann wrote:
> > Qualsys chose to call that remote, at a stretch. Either way, it does not
> > change
>
> It seems to be similar to "if you visit a compromised website"...
Which is not remote, either.
> Anyway, it doesn't seem to be productive to argue terminology etc,
> hence: sorry
Daniel Jakots wrote:
> On Tue, 07 Apr 2020 19:05:31 + (UTC), Chris Ross
> wrote:
>
> > Hello all. I am running a OpenBSD 6.6 that I installed late last
> > year. I was recently trying to make sure I'd updated my smtpd to
> > 6.6.4, based on earlier security announcement. As I'm running
Well, that definately looks like the filesystem blowing up.
Installing bsd.rd 100% |**| 8560 KB00:00
Installing base67.tgz66% |* | 113 MB
00:17 ETAftp: Reading from file: Input/output error
gzip: stdin: Input/output error
tar: End
There is a problem with some of the mirrors. It is being looked into.
rgc wrote:
> misc@
>
> was trying to sysupgrade to latest snapshot but got this
>
> rgc:/home/rgc:94$ doas sysupgrade -kn
> Fetching from http://ftp.jaist.ac.jp/pub/OpenBSD/snapshots/macppc/
> SHA256.sig 100%
>
Cord wrote:
> You are free to believe or not to believe, but you are not free to insult me.
> Is that clear ?
Or what.. you'll throw your tinfoil hat at them?
Martin,
I think you misread what is below.
Since you won't file a complete bug report with all details, you are on
your own. Good luck!
Martin wrote:
> Still can't find a solution. I'm suspect backup battery.
>
> ‐‐‐ Original Message ‐‐‐
> On Sunday, March 22, 2020 9:12 PM, Otto
Ingo Schwarze wrote:
> Hi Jeffrey,
>
> Jeffrey Walton wrote on Wed, Mar 18, 2020 at 11:55:53AM -0400:
>
> > I assumed OpenBSD and NetBSD were collaborating and shared code and
> > docs in some places.
>
> To a limited extent, that is true.
To a limited extent, it is true that birds and fish
Jeffrey Walton wrote:
> On Wed, Mar 18, 2020 at 4:26 AM Stuart Henderson wrote:
> >
> > On 2020-03-18, Jeffrey Walton wrote:
> > > According to https://man.openbsd.org/NetBSD-8.1/security.7#FORTIFY_SOURCE
> > > OpenBSD implements glibc bounds checking on certain functions. I am
> > > trying to
Anthony Campbell wrote:
> On 09 Mar 2020, Otto Moerbeek wrote:
> > On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote:
> >
> > > On 07 Mar 2020, Amit Kulkarni wrote:
> > > [snip]
> > >
> > > >
> > > > will do as you suggest.
> > > >
> > > > Thanks
> > > >
> > > >
> > >
> >
Todd C. Miller wrote:
> On Thu, 05 Mar 2020 16:07:48 +0100, Thomas de Grivel wrote:
>
> > Actually I see the same problem on 6.6-stable :
> > including readline/readline.h produces warnings.
> >
> > Any -Werror hope some day ?
>
> You still haven't bothered to include:
>
> 1) the compiler you
shankarapailoor . wrote:
> I was looking at the pledge policy for the tset binary and I was wondering
> why wpath is necessary. I removed the group from the pledge and did some
> basic tests with the utility and there was no error. Removing any of the
> other groups produces an error so they
Peter N. M. Hansteen wrote:
> On Sat, Feb 29, 2020 at 03:36:02PM +, Ottavio Caruso wrote:
>
> > It's also a pity the the faq are not available in a single html or pdf
> > format. This would be handy for those who, like me, are studying for
> > the BSD Specialist certification. Having a
Vincenzo Nicosia wrote:
> On Mon, Mar 02, 2020 at 01:30:02AM +0100, Ingo Schwarze wrote:
>
> [cut]
>
> >
> > Besides, the FAQ only applies to -stable and not to -current, so
> > installing it on a -current system would be badly misleading.
> > And we certainly don't want the release(8)
Matthias wrote:
> Just curious why you never check the return value of the close(2) system
> call for errors.
It never fails in a way that matters.
The program must be properly written for the fd to be alive, so EBADF
doesn't occur.
EINTR doesn't occur, and if it did, nowhere is it cleanly
Theo de Raadt wrote:
> Andre Smagin wrote:
>
> > Hello.
> >
> > While prototyping something in C, I made a mistake with
> > pre-processor macros, which I narrowed down to this:
> >
> > int
> > main()
> > {
> > char *test
Andre Smagin wrote:
> Hello.
>
> While prototyping something in C, I made a mistake with
> pre-processor macros, which I narrowed down to this:
>
> int
> main()
> {
> char *test[10][2097152] = { { 0 } };
> }
>
> Running it results in
> $ ./a.out
> Segmentation fault
Jonathan Schleifer wrote:
> Fair enough - I can understand you don't want to give any guarantees for
> snapshots.
>
> I guess it's fair to assume that snapshots are only built from full commits
> and not partial commits? In this case then, I guess I should be fine.
The snapshot promise does
You are asking questions beyond the promises we make about snapshots.
Sorry, no answer to your question. Sorry if you think that is unfair.
Jonathan Schleifer wrote:
> Hi!
>
> I'm wondering: If I upgrade to snapshots/sparc64/base66.tgz that is listed on
> ftp as
> base66.tgz
I think you are using the old boot method, which boots bsd from
msdos. The new method has a bootblock, which loads bsd from the
filesystem.
Meaning you didn't read the notes, and your setenv's are wrong.
Lars Noodén wrote:
> I've tried downloading bsd.rd for octeon for both 6.6 and
whistlez...@riseup.net wrote:
> On Thu, Feb 06, 2020 at 10:35:17AM -0700, Theo de Raadt wrote:
> > Kevin Chadwick wrote:
> >
> > > I am considering replacing all chroot use with unveil in my processes
> > > even where
> > > no filesystem acce
Cannot reproduce this issue, and the MAKEDEV script in question
has had only minor unrelated changes.
Something is messed up on your system, and you can diagnose this
better yourself.
Jan Stary wrote:
> With the latest two upgrades (this week and the last),
> the daily security complains about
Kevin Chadwick wrote:
> I am considering replacing all chroot use with unveil in my processes even
> where
> no filesystem access is required.
I am discouraging this.
unveil is a complicated mechanism, and we may still discover a bug in
it.
Almost all the chroot in the tree are to empty
wpa_supplicant is definately a lower-class citizen, sorry.
I increasingly wonder why this stuff matters; transit costs are so much
lower than the period when eduroam was setup, and their reliance on 802.11x
is super wierd in a world where, for the most part
- entire cities have open wifi in
I am considering backtracking on the pressure towards just doing "dns",
and opening up "inet" also, because the other pledges are pretty tight.
We are trying to protect the program, not the network.
Stuart Henderson wrote:
> On 2020-01-21, Dieter Rauschenberger wrote:
> > Hi misc,
> >
> > on
The diff is clearly a layer violation, trying to interpret and dance
for an event which happens after less terminates.
What comes next, someone wanting ANSI control characters to be parsed
and evaluated to avoid screen damage?
Richard Ulmer wrote:
> Hi,
> when using a $PS1, which has more than
Your example is vaguely inprecise enough that I cannot reproduce the
failure. If I could, I would ktrace it.
dig is supposed to use SOCK_DNS, and then not bother doing additional
stuff.
105 is setsockopt. We would investigate if the setsockopt being done
is required, or if it can be removed.
Raymond, David wrote:
> The POSIX SSIZE_MAX is something like 2^15 -1.
I doubt that, you better backtrack a couple of steps.
Raw physical memory is not exported at all, not even to root.
That is not going to change.
Johannes Krottmayer wrote:
> On 10.01.20 at 17:26, Theo de Raadt wrote:
> > We won't help you because we oppose the lack of a security barrier
> > in such designs.
>
> Detaile
501 - 600 of 2950 matches
Mail list logo
