You mean you're not testing *all* of the real code. That's
fine, you can't
debug everythign at once.
if you haven't tested your final production binary then you
haven't tested
anything at all.
You: Two plus two is five.
Me: Are you crazy? Two plus two is not five.
You: If you don't
on the other hand it may be a known plaintext attack.
what are you guys smoking?
-dean
This argument has already been refuted in the posts you are replying to.
Such an attack would require the algorithm to not meet its specific design
security objectives. In other words, you are arguing
Hi there,
Can you please unsubscribe anyone who posts on this subject again.
The participants should long ago have taken this debate off list.
It's degenerated into a discussion without any value whatsoever.
Kind regards
-paul
Lutz Jaenicke wrote:
OpenSSL CVS Repository
http://cvs.openssl.org/
Server: cvs.openssl.org Name: Lutz Jaenicke
Root: /v/openssl/cvs Email: [EMAIL PROTECTED]
Module:
on the other hand it may be a known plaintext attack.
Using those words in this context makes it sound that you not only don't
understand what is being discussed right here and now, but also that you
don't understand the term you just used. Are you sure you understood,
e.g., Ted Tso's
2 issues with RSA_set_method(3) man page:
1. the function prototypes for RSA sign and verify functions in
RSA_set_method(3) man page do not match reality
- crypto/rsa/rsa.h lists them as:
int (*rsa_sign)(int type,
const unsigned char *m, unsigned int m_length,
Hi,
I am using fipsld to create 32 bit (using -m32) statically linked shared
object library from fips capable openssl on SOLARIS 9 SPARC. But fipsld
hangs at link step (when creating shared object lib).I guess this is a bug
in fipsld script or openssl?
To reproduce the problem please
Hello,
I can get encoding of an ANSI X9.62 ECDSA public key
from previously generated EC_KEY using function i2d_EC_PUBKEY.
Is where way to get Ec_params encoding of an ANSI X9.62
from EC_KEY?
I did not found function for this purpose.
Best regards
Mark
Mark Shnaider | Software engineer
On Monday 19 May 2008 15:27:24 dean gaudet wrote:
Note that you should always build with no-asm if you're doing this kind
of debug analysis. The assembly optimisations are likely to operate at
granularities and in ways that valgrind could easily complain about. I
don't know that this is
On Tue, May 20, 2008 at 12:09 AM, Bodo Moeller [EMAIL PROTECTED] wrote:
On Mon, May 19, 2008 at 11:57 PM, Richard Stoughton [EMAIL PROTECTED] wrote:
- do not mix the PID into the internal entropy pool, and
The OpenSSL PRNG uses the PID twice:
Once it is used as part of the intitial seeding
On Tue, 20 May 2008, Richard Salz wrote:
on the other hand it may be a known plaintext attack.
Using those words in this context makes it sound that you not only don't
understand what is being discussed right here and now, but also that you
don't understand the term you just used. Are
11 matches
Mail list logo
