what's going on ...?
Regards
-- Beat
On Thu, Jun 16, 2005 at 02:58:24PM +0200, Beat Jucker wrote:
When I try to decode a particular smime message I'll get error
ASN1_get_object:too long. First I thought there's something
wrong with ASN.1 syntax but than I found a major difference
in openssl base64
When I try to decode a particular smime message I'll get error
ASN1_get_object:too long. First I thought there's something
wrong with ASN.1 syntax but than I found a major difference
in openssl base64 decoding compared to other base64 tools.
Given attached PEM file with all other base64 tools
On Wed, Jun 01, 2005 at 12:19:11PM +0100, Peter Cope wrote:
Try using the asn1parser (an option with openssl).
no problem: asn1parse tells me
0:d=0 hl=2 l=inf cons: SEQUENCE
2:d=1 hl=2 l= 9 prim: OBJECT:pkcs7-envelopedData
...
When I parse the encoded
I have an intermediate SMIME decrypting problem. I'm using following
commandline interface (little bit outdated openssl 0.9.6b @ HPUX-B.11.11):
cat email | openssl smime -decrypt -inkey mykey -recip mycert
This works usually without problems. But Emails from one particular
address I can
On Wed, Jun 01, 2005 at 12:19:11PM +0100, Peter Cope wrote:
Try using the asn1parser (an option with openssl).
no problem: asn1parse tells me
0:d=0 hl=2 l=inf cons: SEQUENCE
2:d=1 hl=2 l= 9 prim: OBJECT:pkcs7-envelopedData
...
But I'm realy confused because
The same result with openssl-0.9.6k. Any idea why this error happens?
regards
-- Beat
On Wed, Mar 03, 2004 at 11:32:58PM +0100, Beat Jucker wrote:
I received an encrypted SMIME message. Within a script I decode and
verify the message. With one particular message decoding was no problem
smime custom services
(based on Unix) but the partners will implement theire services on PCs.
I would be interested in any informations you got so I can forward it.
Thank you and best regards
Beat Jucker
I have generated a certificate to use as a CA root certificate. All I
want to do is export it as pkcs12 _without_ the private key so it can be
installed as a trusted certificate by the end user.
I thought this would do it. Using OpenSSL 0.9.5a
openssl pkcs12 -export -nokeys
