create it.
We have told our business partner to fix the problem (and they have approached Chilkat) ... in the meantime I wrote some C to fix it locally (and I'm not a developer).
Peter
Beat Jucker <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 01, 2005 at 12:19:11PM +0100, Pe
Try using the asn1parser (an option with openssl). If this doesn't complete without an error then you may have a problem with the way your originator is producing ASN.1 (we did here and I had to solve it by producing a bit of code to act as a 'filter' to correct the problem!).
PeterBeat Jucker <
thing. Just wondering, enquiring minds etc ;-)
Once again many thanks.
Peter
"Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote:
On Sun, Mar 06, 2005, Peter Cope wrote:> > I'm using openssl 0.9.7e on Unix (The example output below is from Windows> version of openssl [a
nd until I have
proof it isn't.
Peter
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dr. Stephen Henson
Sent: 06 March 2005 01:13
To: openssl-users@openssl.org
Subject: Re: Re(2): Decryption Problem
On Fri, Mar 04, 2005, Peter Cope wrote:
>
856 prim: cont [ 0 ]
The block beyond 370 is not ASN.1 (which I understand is OK, according to S/MIME).
Peter
"Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote:
On Fri, Mar 04, 2005, Peter Cope wrote:> Firstly I've searched the FAQ's and Google'd and not
, and is followed by a binary chunk of some 60k in size (this isn't itself structured .. unlike the des3-ede3-cbc produced by default by openssl). I've tried detaching this data to see if anything can make sense of it, but no.
Anyone got any ideas, I'm assuming I'm missing a point somewhere!
Peter Cope
