Michael Stephan wrote:
Hallo, I try to verify an ECDSA signature, which is by definition given
as the concatenation of 2 octet-streams (BIGNUM r and BIGNUM s), the
base64 encoded version is:
449afHAqHfJZmkET0a0hYVpaj+n1bbe4eTmHRAQsA+Zsl/px3AWzb5fWGjRzWWtz
(This is part of an xmldsig-ecdsa
Hon Hwang wrote:
Hi all,
I am attempting to understand how to create ASN.1 data structure in
OpenSSL.
First off, a simple ASN.1 structure that I want to create as the
starting point.
VersionInfo := SEQUENCE {
major INTEGER,
minor INTEGER
}
From looking through the posts in this mailing
Hi,
the block size is always the same as the key length in AES (and the most block
ciphers, I think). You are using 128-AES - 128 bits key == 16 bytes block size
(q.e.d).
Good luck,
Sebastian
Eric S. Eberhard wrote:
Kyle,
Thank you ... I thought I was missing something (actually the
Hello,
the block size is always the same as the key length in AES (and the most
block
ciphers, I think). You are using 128-AES - 128 bits key == 16 bytes block
size
(q.e.d).
Not exactly:
AES128: block_size: 16 bytes, key_size: 16 bytes
AES192: block_size: 16 bytes, key_size: 24 bytes
Hi,Like to clarify one point, am I right to say the peer (client) we are referring to here is the browser? I'm using Firefox 2 Beta 1 which I know has ECC support. Ihad performeda test at tls.secg.org to verify this.Another point I'm puzzled is that the openssl ciphersuites shown only
Hi
I'm using BIO in
async mode. When writing or reading data with SSL_write or SSL_read, in some
parts of the code, after receive some data
I use EVPs
functions.In some cases, due key problems, my EVP_DecryptFinalEx fails and
call
EVPerr(EVP_F_EVP_DECRYPTFINAL_EX,EVP_R_BAD_DECRYPT);
On Wed, Oct 18, 2006 at 11:35:13AM +0200, Marek Marcola wrote:
Hello,
the block size is always the same as the key length in AES (and the most
block
ciphers, I think). You are using 128-AES - 128 bits key == 16 bytes block
size
(q.e.d).
Not exactly:
AES128: block_size: 16
Hello,
On Wed, Oct 18, 2006 at 11:35:13AM +0200, Marek Marcola wrote:
Hello,
the block size is always the same as the key length in AES (and the most
block
ciphers, I think). You are using 128-AES - 128 bits key == 16 bytes
block size
(q.e.d).
Not exactly:
AES128:
I have the following error when installing PostgreSQL in Windows XP SP2:
http://lbarzi.galeon.com
Unload I complete SP2 of Windows XP and volvi to install and follows he himself error.-- Jorge A. Barzola Rosadio[Lima - Perú]Comparte lo que sabes, aprende lo que no sepas
Marc Girod [EMAIL PROTECTED] writes:
Indeed, it does. With your path, I can build.
I'll try to see what exactly affects.
I wasn't yet able to find the exact cause of my error on Solaris...
I switched to HP-UX, where I built a shared lib version of zlib,
and failed to produce one of openssl.
I
This problem was raised on this mailing list many times, but the clear solution
(in my opinion) was not given. From OpenSSL FAQ: ...an SSL connection may not
concurrently be used by multiple threads... This means that I can't have 2
threads, one reading and one writing at the same time from the
Title: SSL_read()
Hello,
I have a single threaded application where a SSL_read() is returning a return code of 0. The openSSL doc suggests that this is due to a socket shutdown by the peer. Upon this error, is there anything that I can do to recover the connection and/or data or do I just
Hi, can anyone tell me how to fix the leading zero in BIGNUM. I have the
following code:
unsigned char pkinit_1024_dhprime[128] = {
0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
0xC9, 0x0F, 0xDA, 0xA2, 0x21, 0x68, 0xC2, 0x34,
0xC4, 0xC6, 0x62, 0x8B, 0x80, 0xDC, 0x1C, 0xD1,
0x29,
13 matches
Mail list logo
