On Sun, 17 Jan 1999, Ben Laurie wrote:
> I'm being driven slowly mad by the number of files that have to be in
> the CVS tree but also get modified by code. Most of them I can deal
> with
I assume/hope that you'll do the "foo.in --> foo" kind of transform.
> In general, Makefile.ssl is
> linked
Nelson Alves da Silva Filho wrote:
>
> I think I have found I minor bug in the apps\pkcs8.c. An error occurs whenever it is
>used with the "-topk8" and "-inform DER" parameters together. I think the -topk8 does
>not take care of the -inform parameter and always assumes a PEM input format.
>
>
Andrew Griffin wrote:
>
>
> I have a similar problem and would be willing to send you the private
> key file in question if your still prepared to have a go at converting
> it. The file was generated using Oracles genreq tool of which I know
> little!
>
Well I'll have a look at a sample if you
>The reference count is upped in X509_get_pubkey() so it is just
>decremented by X509_free() and EVP_PKEY_free() actually frees it up.
>
>If I recall this behaviour was first added in OpenSSL 0.9.2.
>
>Steve.
You are absolutly right Steve!
I am currently using SSLeay 0.9.1a.
I intend to switch to
What is a good suggestion for an algorithm in SSL that I can use that
doesn't have the patent problems here in the US? I am writing the
software for both client and server, so I can be quite flexible here.
Actually, I just got everything done today and had a successful
connection just a few minute
Richard Levitte - VMS Whacker wrote:
>
> ben> I'm being driven slowly mad by the number of files that have to be in
> ben> the CVS tree but also get modified by code. Most of them I can deal
> ben> with, but one I need some feedback on.
>
> ben> In general, Makefile.ssl is to Makefile (why???),
Jun-ichiro itojun Hagino wrote:
>
> Hello this is Jun-ichiro (Itoh) Hagino of KAME project.
> RFC2144 says that, CAST128 must be performed only 12 rounds if
> key length <= 80bits. The following patch should fix the behavior.
> Assembly language versions needs som
ben> I'm being driven slowly mad by the number of files that have to be in
ben> the CVS tree but also get modified by code. Most of them I can deal
ben> with, but one I need some feedback on.
ben> In general, Makefile.ssl is to Makefile (why???),
I'm guessing at EAY's intensions here, but I've n
I'm being driven slowly mad by the number of files that have to be in
the CVS tree but also get modified by code. Most of them I can deal
with, but one I need some feedback on. In general, Makefile.ssl is
linked to Makefile (why???), and dependencies tacked on to the end of
Makefile.ssl. This need
[EMAIL PROTECTED] wrote:
>
> On my webserver, one of the server variables contains the base64 encoded
> certificate.
> I would like to read this certificate in to a X509*.
> What is the best way to do this?
>
> The certificate bit stream is without the headers used in the PEM decoding
> (BEGIN C
Rene G. Eberhard wrote:
>
> OpenSSL 0.9.5-dev 09 Aug 1999
>
> Consider the following: Sign a PKCS#10 with apps/x509.c
>
> openssl x509 -CAserial serial.txt -CAkey RSA_1024_NONE.key.pem
> -CA RSA_RSA_1024_NONE.cert.pem -in req.pem -req
>
> In this case need_rand can be set to zero.
Nicolas Roumiantzeff wrote:
>
> >What you normally do is this...
> >EVP_PKEY *key;
> >/* X509 *cert from somewhere */
> >key = X509_get_pubkey(x509);
> >/* various operations */
> >X509_free(x509);
> >EVP_PKEY_free(key);
>
> In my case:
> After "X509_free(x509);" the "key" pointer is freed.
> So
Steve,
Keith Johnston wrote:
>
> Does anyone know of a tool to convert a PKCS8 RSA private key to the
PEM
> or DER format
> that OpenSSL uses?
And you responded
Yes I do.
Its in my personal library source and isn't yet in the main tree: yet
another thing on my list of 'things to do'. What kind
On my webserver, one of the server variables contains the base64 encoded
certificate.
I would like to read this certificate in to a X509*.
What is the best way to do this?
The certificate bit stream is without the headers used in the PEM decoding
(BEGIN CERTIFICATE..) so I can not use the PEM
>What you normally do is this...
>EVP_PKEY *key;
>/* X509 *cert from somewhere */
>key = X509_get_pubkey(x509);
>/* various operations */
>X509_free(x509);
>EVP_PKEY_free(key);
In my case:
After "X509_free(x509);" the "key" pointer is freed.
So "EVP_PKEY_free(key);" would crash.
Am I missing som
15 matches
Mail list logo