Come on, having me preparing bootable CF card image for a gizmo I'm not
familiar with is unrealistic. Don't you have anything you can compile
10-lines C code and some assembler to add to?
Well you mentioned tests on x86 in your paper, I thought you
do have some minimal test setup ready for
I am testing a Java 1.6.x SSL client against Apache httpd 2.2.21
compiled against OpenSSL 1.0.1 beta 1.
The Java client refuses to connect to the server, complaining about
unsupported type_15 extension.
Network traffic capture shows the server responding to an
uninteresting TLS 1.0 ClientHello
[ivan.ris...@gmail.com - Wed Jan 18 14:07:52 2012]:
I am testing a Java 1.6.x SSL client against Apache httpd 2.2.21
compiled against OpenSSL 1.0.1 beta 1.
The Java client refuses to connect to the server, complaining about
unsupported type_15 extension.
This is caused by a bug in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL Security Advisory [18 Jan 2011]
===
DTLS DoS attack (CVE-2012-0050)
A flaw in the fix to CVE-2011-4108 can be exploited in a denial of
service attack. Only DTLS
No. For following reason. Originally idea was to attempt to gather OS
noise. I mean entropy would come from interrupts, interaction with say
DMA, etc. Therefore no explicit attempts to perform the experiment
outside OS were made. Besides it would be impossible for me to set it
up in most cases
Looks like it is still there in 1.0.0g
Again, it's an alignment issue of function pointers put into an array
processed by the C-runtime normally used for doing things like global
constructors.
Its in crypto/perlasm/x86_64-xlate.pl:558
Currently:
$v.= READONLY DWORD;
Should be:
