RE: ASN1_OBJECT to ascii?

1999-07-07 Thread Salz, Rich
>Or do an "evil hack". ... I can't believe you wrote that in a public forum. :) __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated

Re: ASN1_OBJECT to ascii?

1999-07-07 Thread Dr Stephen Henson
Salz, Rich wrote: > > >> I have an ASN1_OBJECT, which in this case is an OID. > >> How do I get a string out, like "1.2.4.122334.69" ? > > > >i2t_ASN1_OBJECT() ? > > No because that gives preference to a user-friendly name, which > of course isn't guaranteed to be unique. > > The answer appears

RE: ASN1_OBJECT to ascii?

1999-07-07 Thread Salz, Rich
>> I have an ASN1_OBJECT, which in this case is an OID. >> How do I get a string out, like "1.2.4.122334.69" ? > >i2t_ASN1_OBJECT() ? No because that gives preference to a user-friendly name, which of course isn't guaranteed to be unique. The answer appears to be that I will have to clone the "i

Re: SSL_ERROR_*

1999-07-07 Thread Juan Pablo Rojas Jimenez
Thank you very much for your help. Juanpa. begin:vcard n:Rojas Jimenez;Juan Pablo x-mozilla-html:FALSE org:Faculad de Informática;DDpto. de Lenguajes y Sistemas Infotmáticos. adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Laboratorio de Teleinformática x-mozilla-cpt:;-3

Re: subscribe + compile openssl met VC1.52

1999-07-07 Thread Ulf Möller
> - Will openssl in the future properly handle 16-bit compiler > support? Or is it simply considered too old. If you write it, it will. Otherwise probably not. None of the current developers have access to 16 bit compilers, but if you get it to compile and pass the tests in 16 bit mode, we'll

Re: bn_m.c

1999-07-07 Thread Ulf Moeller
> What's the function of the bn_m.c module? It apparently was some experimental code by Eric Young, and should have deleted. __ OpenSSL Project http://www.openssl.org Development Mailing List

Re: SSL_ERROR_*

1999-07-07 Thread Bodo Moeller
On Wed, Jul 07, 1999 at 10:26:18AM +0200, Juan Pablo Rojas Jimenez wrote: > Bodo Moeller wrote: >> When discussing the semantics of SSL_read etc., SSL_pending should >> also be mentioned, I guess, although I currently can't think of any >> scenario where you'd really *need* it. SSL_pending tells

Re: SSL_ERROR_*

1999-07-07 Thread Bodo Moeller
On Wed, Jul 07, 1999 at 10:24:22AM +0200, Juan Pablo Rojas Jimenez wrote: > Bodo Moeller wrote: >>> SSL_ERROR_WANT_WRITE >>> SSL_ERROR_WANT_READ >> These can happen only with non-blocking I/O (or with BIO pairs, which >> will be available in OpenSSL 0.9.4). It means that the program has to >> r

Re: (autoconf cometh?!)

1999-07-07 Thread Ben Laurie
William M. Perry wrote: > I'll see what I can do towards the end of the week. The biggest pain in > the %!@%%! will be configuring any of the definitions of MD2_CHAR/MD2_LONG > stuff. That doesn't seem like something that you can detect in autoconf. Aren't they for performance? You could always

Re: SSL_ERROR_*

1999-07-07 Thread Juan Pablo Rojas Jimenez
Bodo Moeller wrote: > On Tue, Jul 06, 1999 at 01:50:31PM +0200, Bodo Moeller wrote: > > On Tue, Jul 06, 1999 at 11:16:50AM +0200, Juan Pablo Rojas Jimenez wrote: > > >> Could anyone tell me what's the exact meaning of the possible errors > >> returned in a SSL_read/write call. > > > [...] > >

Re: SSL_ERROR_*

1999-07-07 Thread Juan Pablo Rojas Jimenez
Bodo Moeller wrote: > On Tue, Jul 06, 1999 at 11:16:50AM +0200, Juan Pablo Rojas Jimenez wrote: > > > Could anyone tell me what's the exact meaning of the possible errors > > returned in a SSL_read/write call. > > Note that those errors are not returned by > SSL_{accept,connect,read,write}, b