Hi,
After a long pause of silence let me bring up the EBCDIC topic again.
In May, I posted the patches for EBCDIC machines which were supposed
to work on Siemens' BS2000 machines (and were prepared to run on other
EBCDIC based platforms, mainly IBM's).
In the file ebcdic.c, however, I had left t
> While waiting for these details to be worked out, I had to get going on my
> application, and the quick hack I did was just what you propose, with the
> minor difference of using type "void *". It worked well enough to keep me
> going, but on reflection I'm convinced it would lead to a more uni
Damien Miller <[EMAIL PROTECTED]> wrote:
> I want to add the facility to pass user data to password callback
> functions. e.g.
>
> RSA *PEM_read_bio_RSAPrivateKey(BIO *bp, RSA **x, pem_password_cb *cb)
>
> becomes
>
> RSA *PEM_read_bio_RSAPrivateKey(BIO *bp, RSA **x, pem_password_cb *cb, char
*u
> What you propose would make libcrypto require libssl as well
> ...
> there are other ways to access the PEM routines apart from the SSL**
> functions. You don't always have a SSL_CTX to relate to.
Okay, makes sense to me. Then there is no coupling with SSL_CTX to
exploit, and "void *" is good
Erik Johannisson <[EMAIL PROTECTED]> wrote:
> in ex_data.c,line 190:
> m->free_func(obj,ptr,ad,i,m->argl,m->argp);
>
> in crypto.h, line 174, the free_func is defined as:
> void (*free_func)
> (/*char *obj,char *item,int index,long argl,char *argp*/);
>
> So the actual call is made with to man
OpenSSL Project wrote:
> AVAILABLE PATCHES
> o OCSP ([EMAIL PROTECTED])
Tom Titchener is no longer with CertCo, and CertCo are no longer
contributing patches (for export-control reasons). Tom's OCSP patches
were for 0.9.2b. Has anyone patched the OCSP patches to bring them up
to date for
On Mon, 26 Jul 1999, Dan Razzell wrote:
> Damien Miller <[EMAIL PROTECTED]> wrote:
>
> > I want to add the facility to pass user data to password callback
> > functions. e.g.
NB the changes have already been added to the CVS repository.
> It's good to see this question raised again!
>
> I ha
Is there any effort to incorporate a change that would allow the use
of the BSAFE toolkit in conjunction with the OPENSSL code. I have
looked at Gordon Chaffee's patches. They fix SSLeay 0.9.0b to
run with BSAFE. However, his patch will not work with the
latest OPENSSL code.
Why would one wan
I am trying to understand the NO_STDIO flag. I would like
to build with it defined. However, if I do that, bio.h
does not compile properly:
Looking at the following piece of code from bio.h,
If I define NO_STDIO, then NO_FP_API gets defined.
However, WIN16 and _WINDLL are not defined so I stil
Hi.
Is there a method i can assign encryption arithmetic?
thans a lot.
leo
__
»¶ÓʹÓýðÁêÈÈÏßÃâ·Ñµç×ÓÓʼþϵͳhttp://www.990.net
__
in ex_data.c,line 190:
m->free_func(obj,ptr,ad,i,m->argl,m->argp);
in crypto.h, line 174, the free_func is defined as:
void (*free_func)
(/*char *obj,char *item,int index,long argl,char *argp*/);
So the actual call is made with to many paramteters.
think that you should remove the ad pointer
"Dr Stephen Henson (by way of Goetz Babin-Ebell )" wrote:
>
> Ulf Moeller wrote:
> >
> > >Was I assuming too much when I assumed that OpenSSL would be a useful
> > >framework for implementing cryptosystems not currently used by SSL or
> > >TLS?
> >
> > It depends on what you want to do. I have fo
>> >> I suppose I ought to start thinking about submitting diffs back to the
>> >> project, huh?
>> >
>> >Yes, please do so via openssl-dev list. But please
>> >consider the following: (a) code needs to be somehow
>> >stable since probably no other developer has a Mac
>
>I do:-) But my CodeWarrior
13 matches
Mail list logo
