I am looking for a tool which can dump out ASN.1 data. I think this will
throw some light. Any inputs.
On Wed, Jan 22, 2014 at 2:27 PM, Mithun Kumar mithunsi...@gmail.com wrote:
I think below error is caused by corrupt data received by the client. Is
my observation correct. Any idea how
I think below error is caused by corrupt data received by the client. Is my
observation correct. Any idea how figure out where things are going wrong.
error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag
error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error
Dave,
Thanks for your response. Please find the response for your queries below.
1. Yes, we are trying to upgrade it. But before that we are trying it in
our testbeds and all possible options for the fix.
2. The errno is 104 and it is Connection reset by peer
3. Can you help
I'm no expert, but doesn't connection reset by peer mean that the other side
of the connection is hanging up? So maybe the error is with whatever you are
talking to? Andrew
On Wed, Jan 22, 2014 at 11:24:07AM +, Thirumal, Karthikeyan wrote:
Dave,
Thanks for your response. Please find the
On 01/06/2014 10:34 PM, Alan Cabrera wrote:
I should have obtained the DER form using i2d_RSA_PUBKEY(). Also,
passing buf to the method should have warned me that the pointer was
being modified. I have no idea why it gets modified and what it points
to after the call.
So now I do
From: owner-openssl-us...@openssl.org On Behalf Of andrew cooke
Sent: Wednesday, January 22, 2014 06:49
I'm no expert, but doesn't connection reset by peer mean that the other
side
of the connection is hanging up? So maybe the error is with whatever you
are
talking to? Andrew
Originally
It is certainly *invalid* data received by the client. *corrupt* normally
means
that correct data was sent, or at least created, and something changed it on
the way to the receiver, either accidentally (such as line noise or gamma
rays) or
deliberately (by an attacker). Nowadays uncorrected
Those links (and the man pages in the latest release tarball, which they
should
and do match) are different for me as they should be. *Some* of the setup
code
is the same for both directions, and mostly the same for other algorithms
also -
the main point of EVP_ is to use different
On 21 January 2014 23:51, HelenH Zhang helen...@yahoo.com wrote:
Thank you, Matt for your quick reply.
I have additional questions: I looked both links below:
https://www.openssl.org/docs/crypto/EVP_PKEY_encrypt.html
https://www.openssl.org/docs/crypto/EVP_PKEY_decrypt.html
One for
On 22 January 2014 22:40, Dave Thompson dthomp...@prinpay.com wrote:
The general public-key sign and verify processes are:
S1. compute hash of data (or for CMS, hash of data-hash plus some other
bits)
S2. generate signature for hash S1 using private key (RSA, DSA, or ECDSA)
S3. send
10 matches
Mail list logo