Bonjour,
Le 17/08/2012 09:33, kiran Palli a écrit :
Hi,
I generated an rsa 2048 key-pair with these commands:
openssl.exe genrsa -F4 -out key.pem 2048
openssl.exe rsa -text -in key.pem key.txt
Now I lost the key.pem file and also lost the key.txt in its original
format.
That's sad. 2
On 8/17/2012 11:46 AM, Erwann Abalea wrote:
Bonjour,
Le 17/08/2012 09:33, kiran Palli a écrit :
Hi,
I generated an rsa 2048 key-pair with these commands:
openssl.exe genrsa -F4 -out key.pem 2048
openssl.exe rsa -text -in key.pem key.txt
Now I lost the key.pem file and also lost the
I see. I've digged a little bit more in the built-in engines and found out
that this is the way some of them are implemented. I guess there's no way
to to the same for ECDSA_METHOD tough, since there's no finish function
pointer on that...
By the way, I took a look at the gost engine, which uses
I want to make sure I don't potentially report openssl bugs that someone else
has already reported. Is there a database of open openssl bugs that I
haven't seen the link to, somewhere?
Thanks,
Cassie
__
OpenSSL Project
On Fri, Aug 17, 2012, Cassie Helms wrote:
I want to make sure I don't potentially report openssl bugs that someone else
has already reported. Is there a database of open openssl bugs that I
haven't seen the link to, somewhere?
See:
http://www.openssl.org/support/faq.html#BUILD16
and
On Fri, Aug 17, 2012, Felipe Blauth wrote:
I see. I've digged a little bit more in the built-in engines and found out
that this is the way some of them are implemented. I guess there's no way
to to the same for ECDSA_METHOD tough, since there's no finish function
pointer on that...
There
Hello,
I am trying to create a shared library of openssl (1.0.1c) with the
following configuration:
./Configure --cross-compile-prefix=i686-unknown-linux-gnu-
--prefix=$HOME/toolchains/{i686-unknown-linux-gnu} shared linux-elf
compiler version:
i686-unknown-linux-gnu-gcc (GCC) 4.2.4
The
For EAP-FAST key derivation, I need to know the key block size. With
OpenSSL 1.0.0 I used effectively following function to figure this out
after having completed TLS handshake:
int get_block_size(SSL *ssl)
{
const EVP_CIPHER *c = ssl-enc_read_ctx-cipher;
const EVP_MD *h =
Hi folks,
I'm looking to compile fips and openssl with gdb symbols. So far both
compilations are unhappy with
make CFLAGS=-g
after doing my typical config stuff.
I noticed there are some debug options for fips/Configure, if you look really
hard in the Configure file...I think these typically
Actually, my real question was, where can I see a list of bugs that are
already reported for openssl, so I can anticipate certain openssl
functions failing? I wish I could contribute more to the source by
reporting bugs, but I have so many of my own already...and would like
to be able to see
I'm seeing odd failures in the MD4/MD4_Init functions and I can't
debug them with gdb because I can't see what the source is doing.
Maybe I should add that I've verified that FIPS_mode is turned on right before
my failing MD4 calls (think OpenSSLDie()), and I didn't do anything special
to
On Fri, Aug 17, 2012, Cassie Helms wrote:
I'm seeing odd failures in the MD4/MD4_Init functions and I can't
debug them with gdb because I can't see what the source is doing.
Maybe I should add that I've verified that FIPS_mode is turned on right before
my failing MD4 calls (think
Maybe I should add that I've verified that FIPS_mode is turned on right before
my failing MD4 calls (think OpenSSLDie()), and I didn't do anything special
to compile or turn on the MD4 algorithm.could that be where I'm missing a
step?
Ah yes, now I see that what I am trying to do is
2012/8/17 Dr. Stephen Henson st...@openssl.org
On Fri, Aug 17, 2012, Felipe Blauth wrote:
I see. I've digged a little bit more in the built-in engines and found
out
that this is the way some of them are implemented. I guess there's no way
to to the same for ECDSA_METHOD tough, since
On Fri, Aug 17, 2012, Cassie Helms wrote:
Maybe I should add that I've verified that FIPS_mode is turned on right
before
my failing MD4 calls (think OpenSSLDie()), and I didn't do anything special
to compile or turn on the MD4 algorithm.could that be where I'm missing
a
step?
On Fri, Aug 17, 2012, Eric Fowler wrote:
Must a client free the pointer returned from OBJ_nid2obj() ? I assume
the pointer references data in some internal table and is not
free()'d.
But I want to be sure ... man page is no help on this.
An application doesn't have to no. However it is
From: owner-openssl-us...@openssl.org On Behalf Of CharlesTSR
Sent: Tuesday, 14 August, 2012 17:12
You've already followed-up with some, but a few more points:
I am porting an existing Windows-based TCP/IP server
(receive-only, not a Web server) to OpenSSL.
The way it works with TCP/IP
17 matches
Mail list logo
