The native SCTP implementation assumes that the given byte buffer ( buffer
address + position ) is memory aligned. It re-uses the buffer for handling
notifications from the SCTP Stack ( as well as for reading data off the socket
). This can result in a SIBGUS on sparc(v9) if the address is not 4
On 22/03/2014 08:13, Chris Hegarty wrote:
The native SCTP implementation assumes that the given byte buffer ( buffer
address + position ) is memory aligned. It re-uses the buffer for handling
notifications from the SCTP Stack ( as well as for reading data off the socket
). This can result in a
On 22 Mar 2014, at 08:19, Alan Bateman wrote:
> On 22/03/2014 08:13, Chris Hegarty wrote:
>> The native SCTP implementation assumes that the given byte buffer ( buffer
>> address + position ) is memory aligned. It re-uses the buffer for handling
>> notifications from the SCTP Stack ( as well a
On Mar 21, 11:48pm, mh...@mhcomputing.net (Matthew Hall) wrote:
-- Subject: Re: Review Request of JDK Enhancement Proposal: DTLS
| The following bug and source code [1] are present in OpenSSL:
|
| http://rt.openssl.org/Ticket/Display.html?id=1929
This link is not public. Can you post a summary?
Sorry about the hiccup. Supposedly the bug will work if you get in with user
guest PW guest.
As for non Windows, I don't know a lot of Windows programmers, only malware
analysts. So we'd need to ask somebody in Sun's porting group I think. Or if
somebody has a contact at Microsoft.
Matthew.
--
On Mar 22, 9:39am, mh...@mhcomputing.net (Matthew Hall) wrote:
-- Subject: Re: Review Request of JDK Enhancement Proposal: DTLS
| Sorry about the hiccup. Supposedly the bug will work if you get in with user
guest PW guest.
Thanks.
christos
