Re: (whatever)

On Sun, 07 Nov 1999 12:10:35 +0100, "Rene G. Eberhard" wrote: > Cewl Mail. > Can you please describe your problem a bit more detailed =)? > > BTW: It is not allowed to have more than one CN. It is - see X.500 et al - but do you mean perhaps that OpenSSL can't handle entering them? Cheers, Chr

Re: DN formats

On Mon, 08 Nov 1999 10:09:36 +1100, "Ramsay, Ron" wrote: > You say below that the type information is lost under RFC 2253, as if it is > preservered under RFC 1779. It is not. The discussion in RFC 2253 applies to > *all* LDAP DNs - it's a consequence of the string representation. It is > therefor

Added feature to memory debugging routines

[ My employer, Celo Communications, has kindly allowed me to let this added feature get out to this list to be included i OpenSSL ] I'm currently using the memory debugging routines from crypto/mem.c. They show really nicely who allocated what (if used as intended). However, there are times wh

Re: DN formats

On Fri, 05 Nov 1999 19:22:12 GMT, Dr Stephen Henson wrote: > Chris Ridd wrote: > > > > On Fri, 05 Nov 1999 13:06:42 GMT, Dr Stephen Henson wrote: > > > Chris Ridd wrote: > > Treating it as 8859-1 is just plain wrong, and would penalise vendors > > who bothered implementing the standards correctly

problems with i2d_PKCS7

Hello, I need to transform a PKCS7* to a char* or similar, and I've done this: unsigned char **msg_aux; msg_aux=(unsigned char **) malloc (8194); /*enough size...*/ i=i2d_PKCS7(p7,msg_aux); I've got a segmentation fault. Could anybody help me? ___

Re: problems with i2d_PKCS7

Try something like: unsigned char **msg_aux; *msg_aux=(unsigned char *) malloc (8194); /*enough size...*/ i=i2d_PKCS7(p7,&msg_aux); Or, if you do want to know the size before allocating: unsigned char **msg_aux; int sz; sz = i2d_PKCS7(p7,NULL); *msg_aux=(unsigned char *) malloc (sz); /*eno

Re: problems with i2d_PKCS7

Ooops! Remove '&' from i=i2d_PKCS7(p7,&msg_aux), i.e. i=i2d_PKCS7(p7,msg_aux)... (The problem is just to get the pointers right.) Patrik Patrik Carlsson wrote: > Try something like: > > unsigned char **msg_aux; > > *msg_aux=(unsigned char *) malloc (8194); /*enough size...*/ > i=i2d_PKCS7(p

Re: Creating own Certificate Authority.

Many thanks, I now have my client application speaking to my Apache server and exchanging the certificates correctly. However, I am now trying to get the server to authenticate the client certificate. I understand that I can use an RCL file, but do not know how to get all the required certificat

Re: DN formats

Chris Ridd <[EMAIL PROTECTED]> writes: >I read Peter Guttmann's screed on X.509 and char sets last night - >interesting, though he does fall into the trap of discussing all the myriad >of drafts, and forgetting that these are just drafts. The standards >themselves are less ambiguous. The reason

Re: X509 reference counts

Hi, On Tue, 9 Nov 1999, Dr Stephen Henson wrote: > Yes horrible isn't it? > > I've also noticed wildly inconsistent behaviour. When you call something > like XXX_get_YYY() you might get something which will last only as long > as the parent and it shouldn't be freed at all or something which wi

peer did not return a certificate

Help! I am trying to get an Apache Server with OpenSSL to validate a client certificate. I have created a client application which succussfully validates the server certificate but cannot get the server to sucessfully validate a client certificate when SSLVerifyClient is set to require. I used

Re: problems with i2d_PKCS7

Ignacio Gil wrote: > > Hello, > I need to transform a PKCS7* to a char* or similar, and I've done this: > > unsigned char **msg_aux; > msg_aux=(unsigned char **) malloc (8194); /*enough size...*/ > i=i2d_PKCS7(p7,msg_aux); > > I've got a segmentation fault. > Could anybody help me? The co

Re: problems with i2d_PKCS7

You don't need p. Patrik Dr Stephen Henson wrote: > Ignacio Gil wrote: > > > > Hello, > > I need to transform a PKCS7* to a char* or similar, and I've done this: > > > > unsigned char **msg_aux; > > msg_aux=(unsigned char **) malloc (8194); /*enough size...*/ > > i=i2d_PKCS7(p7,msg_aux); >

Re: Looking for easy routines from Perl to Digitally Sign data within a URL

"Bill Mann" <[EMAIL PROTECTED]> writes: > Hi, > I wish to sign some data within a URL to generate the following URL: > > www.xyz.com/token=value1?,signature=392839283928932893 > > > Is there any Perl Modules available that hook into the underlying SSL stuff. Take a look at the smime stuff

Re: problems with i2d_PKCS7

Patrik Carlsson wrote: > > You don't need p. > > Patrik > You do need p... see below. > Dr Stephen Henson wrote: > > > The correct way is this... > > > > int len; > > unsigned char *buf, *p; > > > > len = i2d_PKCS7(p7, NULL); > > buf = malloc(len); > > p = buf; > > i2d_PKCS7(p7, &p); > > Wh

Re: problems with i2d_PKCS7

Yep, you're right. Thanks for the information. Patrik Dr Stephen Henson wrote: > Patrik Carlsson wrote: > > > > You don't need p. > > > > Patrik > > > > You do need p... see below. > > > Dr Stephen Henson wrote: > > > > > The correct way is this... > > > > > > int len; > > > unsigned char *buf

Re: X509 reference counts

Geoff Thorpe wrote: > > Hi, > > On Tue, 9 Nov 1999, Dr Stephen Henson wrote: > > > Yes horrible isn't it? > > > > I've also noticed wildly inconsistent behaviour. When you call something > > like XXX_get_YYY() you might get something which will last only as long > > as the parent and it shouldn

RE: X509 reference counts

When you speak of breaking existing applications, I guess you mean applications based on the s_server code (or those that use sockets). As someone who has written code based on BIOs and not sockets, I am somewhat concerned that BIO reference counts are broken. Apparently I cannot make my code robu