Perhaps the issuer's certificate expired? (Assuming it's not a
self-signed cert.)
On Sep 8, 2004, at 5:53 PM, Edward Chan wrote:
It says 2005, and my system clock is fine. But it seems to expire
after 30
days.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Beh
That is what I meant, thank you!
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Dr. Stephen Henson
>Sent: Wednesday, September 08, 2004 4:36 PM
>To: [EMAIL PROTECTED]
>Subject: Re: setting CA certificate expiration to more than 30 days
>through conf file
Hmm, I am not sure if I explained my dilemma correctly. Let me jump onto
CLI, maybe it will make more sense that way:
#create a new CA cert
openssl req -x509 -newkey rsa -keyout ca_key.pam -keyform PEM -out
ca_cert.pem -outform PEM -config
#create a new server cert
openssl req -newkey rsa -keyou
Hi
You should try a 8-bit microcontroller driven implementation.
However, even on these plataforms (e. g. 8051), the addressing overhead plus
the tables is smaller than the overhead of a function call plus the function
itself. That note applies both for the S-Tables, Inv-S-Tables and the XTime
f
It says 2005, and my system clock is fine. But it seems to expire after 30
days.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Joseph Bruni
> Sent: Wednesday, September 08, 2004 3:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Certificate expired
On Wed, Sep 08, 2004, IB wrote:
> I'd like to create an own CA certificate that will last for more than 30
> days.
> I tried to add the default_days attribute into [ req ] section but this
> attribute
> never gets applied. However, if I set "-days" through a CLI (command line)
> everything
> work
The default_days in the REQ section doesn't do anything since a
certificate request doesn't expire. The default_days is used in the CA
section when making a certificate from a request.
On Sep 8, 2004, at 5:29 PM, IB wrote:
I'd like to create an own CA certificate that will last for more than
30
On Wed, Sep 08, 2004, Joseph Bruni wrote:
> The text database used by the openssl ca command can only allow one
> certificate per subject. If you need to issue another certificate with
> the exact same subject, revoke the previous certificate first, even if
> the earlier certificate has expired
I'd like to create an own CA certificate that will last for more than 30
days.
I tried to add the default_days attribute into [ req ] section but this
attribute
never gets applied. However, if I set "-days" through a CLI (command line)
everything
work fine.
Any thoughts? hints?
___
The text database used by the openssl ca command can only allow one
certificate per subject. If you need to issue another certificate with
the exact same subject, revoke the previous certificate first, even if
the earlier certificate has expired.
On Sep 7, 2004, at 3:03 PM, Areg Alimian wrote:
Use the "openssl x509 -dates" option to view the actual dates in the
certificate.
Also check your system clock.
On Sep 7, 2004, at 5:09 PM, Edward Chan wrote:
Hi there,
I had created a certificate to test with using OpenSSL. It is
supposed to expire in Aug. 2005. I have been using it for the p
Hi,
I'm coming with a strange phenomenon about which I didn't find any
answer on the Net (using keywords like garbage, IE, openssl).
I've ben using X509 certificates for couple of years but that was for
VPN softwares.
These are not less stricts than browsers but this phenomenon didn't seem
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 07 September 2004 19:53, Joe DeBattista wrote:
> Hi,
>I sent a query last week about removing a passphrase from an Apache
> server I have set up with openssl-0.9.7d and compiled with the gcc
> compiler. I thought I'd provide a little mor
13 matches
Mail list logo
