Hi Dave
thanks a lot for the explanation. That makes a lot clearer to me. I added
some code to read out possible errors and there is none on the write
method. However there is a strange one on read:
error code pubkey: 537297017 in bio_lib.c line 297.
error data:
error string: error:20068079:BIO
Hi,
I went on reading about this error and figured out that the socket bio
does not support the BIO_gets method. Is it possible that
PEM_read_bio_RSA_PUBKEY uses BIO_gets internally and is therefore not
really compatible with a socket bio?
In order to verify that I created a buffer BIO
Is it possible that PEM_read_bio_RSA_PUBKEY uses BIO_gets internally
Sometimes the best answer to that sort of question -- sadly, perhaps, but
true nonetheless -- is to look at the source code. Not so hard to read as I
had at first supposed.
Charles
-Original Message-
From:
I am using OpenSSL version : openssl-1.0.0j in our production.
I am facing a strange problem where the SSL connection simply hangs
during initial handshake when requested from our office IP address.
When I run the same command from another IP address it works fine.
From office IP (Unsuccessful
I did that already and saw already that BIO_gets is called. I just left
the question open since I don't understand the reason behind this. It
forces me to use a buffer BIO that I only need for that one read. But I
agree that this is a workaround that is doable
Is it possible that
Amit amit.uttam@... writes:
Hello,
Looking at *crypto/sha/asm/sha1-x86_64.pl*, there is a measurement that
states 5.3 cycles / byte when computing the sha1.
How was this measurement obtained? I tried using linux perf tools and
got close to this figure but I am not sure if I am
Is there any tutorial or other documentation on how to use the openssl
asn1 parsing C functions? That is, not the command line.
The man pages are empty. I found that the asn1parse command line
utility works, but the asn1pars.c code is completely uncommented. It
will be a chore to reverse
Is there a C-callable function that an application may call to determine the
version of the OpenSSL library with which it is linked?
Thanks,
Charles
__
OpenSSL Project http://www.openssl.org
Is there a C-callable function that an application may call to determine the
version of the OpenSSL library with which it is linked?
See the SSLeay() and SSLeay_version() functions, depending on whether you
wish to retrieve a long containing the version, or a textual string.
Hope this helps,
Never mind. Found it:
http://www.openssl.org/docs/crypto/SSLeay_version.html
Hard to search for. Google SSL version and you get a lot of irrelevant
hits.
Charles
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Charles Mills
On Tue, Sep 04, 2012, Ken Goldman wrote:
Use case: I have to parse a non-standard X.509 certificate that
openssl cannot handle at a higher level. I think I have to parse at
a low level and pull out the data I need.
Is this the OAEP certificate issue? It should be possible to retrieve
From: owner-openssl-us...@openssl.org On Behalf Of Carolin Latze
Sent: Tuesday, 04 September, 2012 08:03
I went on reading about this error and figured out that the socket bio
does not support the BIO_gets method. Is it possible that
PEM_read_bio_RSA_PUBKEY uses BIO_gets internally and is
12 matches
Mail list logo
