On 19/03/15(Thu) 14:11, Martin Pieuchot wrote:
> When a host want to send packets to a destination whose Ethernet address
> that has not been resolved yet, it puts such packet on a mbuf queue.
>
> Right now this queue, linked to the corresponding ARP data structure, is
> hand rolled. I wrote the
On Thu, Mar 19, 2015 at 03:58:16PM +0100, Stefan Sperling wrote:
>
> Perhaps the following diff would make everyone happy again?
Thanks Stefan, it looks good for me.
>
> Index: mbstowcs.3
> ===
> RCS file: /cvs/src/lib/libc/locale/
Hi all,
I think that in /usr/src/sys/dev/pci/pcidevs these 3 records
product INTEL E5V2_ERR_20x0be3 E5 v2 Error
product INTEL E5V2_ERR_30x0be6 E5 v2 Error
product INTEL E5V2_ERR_40x0be7 E5 v2 Error
should be
product INTEL E5V2_ERR_20x0eb3 E5 v2 Error
product
On Thu, 19 Mar 2015, John Merriam wrote:
> On Thu, 19 Mar 2015, Ted Unangst wrote:
>
> > Ted Unangst wrote:
> > > Patches are now available to fix a variety of issues in libcrypto and
> > > libssl.
> > > 5.5 patch:
> > > http://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/024_openssl.patch.sig
On Thu, 19 Mar 2015, Ted Unangst wrote:
> Ted Unangst wrote:
> > Patches are now available to fix a variety of issues in libcrypto and
> > libssl.
> > 5.5 patch:
> > http://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/024_openssl.patch.sig
>
> And I boned the instructions again.
> cd /us
We have released LibreSSL 2.1.6, which will be arriving in the
LibreSSL directory of your local OpenBSD mirror soon.
This release primarily addresses a number of security issues in
coordination with the OpenSSL project.
Fixes for the following issues are integrated into LibreSSL 2.1.6:
*
On Wed, 18 Mar 2015 15:35:55 -0600, "Todd C. Miller" wrote:
> Trivial conversion to strtonum().
Apparently too trivial. STRTOI advances the pointer passed to it
which is broken by this diff.
- todd
Reads ok to me (for what that's worth).
jmc
Original Message
From: Stefan Sperling
Sent: Thursday, 19 March 2015 14:59
To: Kaspars Bankovskis
Cc: tech@openbsd.org
Subject: Re: Rewording mbstowcs(3), wcrtomb(3) and wcstombs(3)
On Thu, Mar 19, 2015 at 03:59:44PM +0200, Kaspars Bankovskis wrote:
On Thu, Mar 19, 2015 at 03:59:44PM +0200, Kaspars Bankovskis wrote:
> On Thu, Mar 19, 2015 at 01:36:45PM +0001, Jason McIntyre wrote:
> > On Thu, Mar 19, 2015 at 03:32:52PM +0200, Kaspars Bankovskis wrote:
> > > Is that really accurate to say that elements are stored in a pointer?
> > >
> >
> > n
Ted Unangst wrote:
> Patches are now available to fix a variety of issues in libcrypto and libssl.
> 5.5 patch:
> http://ftp.openbsd.org/pub/OpenBSD/patches/5.5/common/024_openssl.patch.sig
And I boned the instructions again.
cd /usr/src/lib/libcrypto/crypto
should be
cd /usr/src/l
Patches are now available to fix a variety of issues in libcrypto and libssl.
For 5.6 and the forthcoming 5.7 release:
CVE-2015-0209 - Use After Free following d2i_ECPrivatekey error
CVE-2015-0286 - Segmentation fault in ASN1_TYPE_cmp
CVE-2015-0287 - ASN.1 structure reuse memory corruption
CVE-201
On Thu, 19 Mar 2015 13:36:45 +0001
Jason McIntyre wrote:
> On Thu, Mar 19, 2015 at 03:32:52PM +0200, Kaspars Bankovskis wrote:
> > Is that really accurate to say that elements are stored in a pointer?
> >
>
> no idea. it's why i asked stsp to look it over.
> jmc
I looked up the Linux and FreeB
On Thu, Mar 19, 2015 at 01:36:45PM +0001, Jason McIntyre wrote:
> On Thu, Mar 19, 2015 at 03:32:52PM +0200, Kaspars Bankovskis wrote:
> > Is that really accurate to say that elements are stored in a pointer?
> >
>
> no idea. it's why i asked stsp to look it over.
> jmc
It's just that the previou
On Thu, Mar 19, 2015 at 03:32:52PM +0200, Kaspars Bankovskis wrote:
> Is that really accurate to say that elements are stored in a pointer?
>
no idea. it's why i asked stsp to look it over.
jmc
>
> On Thu, Mar 19, 2015 at 12:41:48PM +0001, Jason McIntyre wrote:
> > On Wed, Mar 18, 2015 at 03:32
Is that really accurate to say that elements are stored in a pointer?
On Thu, Mar 19, 2015 at 12:41:48PM +0001, Jason McIntyre wrote:
> On Wed, Mar 18, 2015 at 03:32:40PM -0400, Andre Smagin wrote:
> > Hello.
> >
> > mbstowcs(3), wcrtomb(3) and wcstombs(3) use a bit awkward wording -
> > "the fi
When a host want to send packets to a destination whose Ethernet address
that has not been resolved yet, it puts such packet on a mbuf queue.
Right now this queue, linked to the corresponding ARP data structure, is
hand rolled. I wrote the diff below during s2k15 to make use of the
mq_enqueue(9)
On Wed, Mar 18, 2015 at 03:32:40PM -0400, Andre Smagin wrote:
> Hello.
>
> mbstowcs(3), wcrtomb(3) and wcstombs(3) use a bit awkward wording -
> "the first at most", and repeat "array pointed to by blah" from the
> previous sentence.
>
> Perhaps something similar to this diff would make them easi
Timo Trinks wrote:
> Hi!
>
> At the time of writing (Thu Mar 19 11:00:12 UTC 2015) the recently
> published patch for libXfont (19_libxfont.patch.sig) for OpenBSD 5.6
> includes a typo [1]:
>
> --- /tmp/019_libxfont.patch.sig Thu Mar 19 12:03:47 2015
> +++ /tmp/019_libxfont.patch.sig_fixed
18 matches
Mail list logo
