On Mon, Aug 10, 2015 at 5:10 AM, Mark Kettenis wrote:
> Jan Engelhardt schreef op 2015-08-10 10:29:
>
>> On Monday 2015-08-10 02:38, Brent Cook wrote:
On Aug 9, 2015, at 10:07 AM, Jan Engelhardt wrote:
> We have released LibreSSL 2.2.2, which will be arriving in the
> Libre
This matches the current myproposal.h ordering with
chacha20-poly1305's promotion (and referenced in various release
notes). Please correct if I've misunderstood or misformatted. Thanks.
Index: usr.bin/ssh/ssh_config.5
===
RCS file: /
> ludovic coues schreef op 2015-08-10 23:29:
> > 2015-08-10 22:56 GMT+02:00 Martin Pieuchot :
> >> On 30/07/15(Thu) 12:18, Ludovic Coues wrote:
> >>> Right now, an USB_REQUEST ioctl will fail with an EBADF error if done
> >>> on a device opened as read-only. With this patch, the ioctl will fail
> >
Michael Reed wrote:
> I only have a very loose idea of what gets accepted or not when the tree
> is "locked", so apologies if this should have been sent at a different
> time.
patches are always welcome. they just get overlooked sometimes. :)
> Index: worm.c
>
ludovic coues schreef op 2015-08-10 23:29:
2015-08-10 22:56 GMT+02:00 Martin Pieuchot :
On 30/07/15(Thu) 12:18, Ludovic Coues wrote:
Right now, an USB_REQUEST ioctl will fail with an EBADF error if done
on a device opened as read-only. With this patch, the ioctl will fail
only if the USB_REQUES
2015-08-10 22:56 GMT+02:00 Martin Pieuchot :
> On 30/07/15(Thu) 12:18, Ludovic Coues wrote:
>> Right now, an USB_REQUEST ioctl will fail with an EBADF error if done
>> on a device opened as read-only. With this patch, the ioctl will fail
>> only if the USB_REQUEST is a write request.
>
> Do you nee
Convert two rt->rt_refcnt-- to rtfree(rt). In both cases the entry
is returned from rtrequest1(RTM_ADD, ...) and wont be freed because
it currently *is* in the table.
Ok?
Index: net/route.c
===
RCS file: /cvs/src/sys/net/route.c,v
r
On 30/07/15(Thu) 12:18, Ludovic Coues wrote:
> Right now, an USB_REQUEST ioctl will fail with an EBADF error if done
> on a device opened as read-only. With this patch, the ioctl will fail
> only if the USB_REQUEST is a write request.
Do you need this to be able to use your usbdevs-like tool as a
Since this backward compat' is here we can now assume that applications
have been updated to not set the IN6_IFF_DEPRECATED. At least our base
is clean and I doubt any port still do that.
Ok?
Index: netinet6/in6.c
===
RCS file: /cvs
In general these messages do not help. Here we have two cases of
messages, either logged at LOG_INFO or LOG_ERR.
In the first case a proper error code is returned via ioctl(2), so
the userland application knows it has done something incorrect.
The second case correspond to a ENOMEM error, which
Hi,
I figure that the text which this diff removes wasn't of much use
besides stating the obvious, as the meaning of list items in the
ENVIRONMENT section seems pretty consistent across the man pages.
Regards,
Michael
Index: src/usr.sbin/vipw/vipw.8
=
Hi tech@,
I only have a very loose idea of what gets accepted or not when the tree
is "locked", so apologies if this should have been sent at a different
time.
If I launch worm(6) with an invalid argument, my terminal flashes once
before the strtonum error message is shown. I assume this is beca
Hi,
while trying to build a newer xserver 1.17 on loongson, I got the
folloing ld crash.
Apparently this is already using -fPIC so I don't know how to make
space for local GOT entries.
Making all in modesetting
/bin/sh ../../../../libtool --tag=CC--mode=link gcc -std=gnu99
-DHAVE_DIX_CONF
decleration -> declaration
Index: relayd.conf.5
===
RCS file: /cvs/src/usr.sbin/relayd/relayd.conf.5,v
retrieving revision 1.164
diff -u -p -r1.164 relayd.conf.5
--- relayd.conf.5 24 Jul 2015 15:25:08 - 1.164
+++ rela
> It feels wasteful to develop a seemingly comprehensive and modular code
> scanner which will inherently find heaps of bugs, and then not release
> it or allow others to work with it.
Sam, since you think throwing opinions out there is valuable
Let me give me yours.
I think you should talk priv
> I am also of the opinion that if somebody/a method can discover bugs,
> they should report them. And if they can't, that method should be
> disclosed to allow others to continue their work.
And my opinion is that Sam should back his opinions with lots of
money.
On 2015/08/10 11:54, sam wrote:
> I am also of the opinion that if somebody/a method can discover bugs,
> they should report them. And if they can't, that method should be
> disclosed to allow others to continue their work.
So you think others "should" do work for you, right? Whether that work is
On Fri, 7 Aug 2015 22:49:50 +0200
shun.obsd.t...@dropcut.net wrote:
> Hi Maxime,
> Hi Sam,
>
> I have been following this thread (and others) for some time.
>
> On Fri, Aug 07, 2015 at 09:55:21PM +0200, Maxime Villard wrote:
> > Well, I guess I'll have to admit that I find your attitude extremel
I'm sorry, I misread you. I wasn't trying to make fun of you or
disregard your work.
Thanks for reporting this (among other bugs).
I am also of the opinion that if somebody/a method can discover bugs,
they should report them. And if they can't, that method should be
disclosed to allow others to
Jan Engelhardt schreef op 2015-08-10 10:29:
On Monday 2015-08-10 02:38, Brent Cook wrote:
On Aug 9, 2015, at 10:07 AM, Jan Engelhardt wrote:
We have released LibreSSL 2.2.2, which will be arriving in the
LibreSSL directory of your local OpenBSD mirror soon.
The .pc files in libressl-2.2.2 u
On Monday 2015-08-10 02:38, Brent Cook wrote:
>> On Aug 9, 2015, at 10:07 AM, Jan Engelhardt wrote:
>>
>>> We have released LibreSSL 2.2.2, which will be arriving in the
>>> LibreSSL directory of your local OpenBSD mirror soon.
>>
>> The .pc files in libressl-2.2.2 upset the package mechanisms
21 matches
Mail list logo
