On 09/13/2017 09:31 AM, Michael Richardson wrote:
Robert Moskowitz wrote:
> The devices never test out the lifetime of their certs. That is up to
Exactly...
(Do you think about the MacGyver/StarTrek/A-Team/Leverage/MissionImpossible
plot line that goes along with each engineering decisio
> Le 13 sept. 2017 à 17:08, Michael Wojcik a
> écrit :
>
>> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
>> Of Michael Richardson
>> Sent: Wednesday, September 13, 2017 09:32
>>
>> I suspect that the value: literal value 1231235959Z will simply come to
>> mean "
On 09/13/2017 09:39 AM, Salz, Rich via openssl-users wrote:
An X509v3 certificate has “notBefore” and “notAfter” fields. If either of
those is not present, then it is not an X509v3 certificate. The time marked by
those fields is the validity period.
If you want “never expires” X509v3 certi
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Michael Richardson
> Sent: Wednesday, September 13, 2017 09:32
>
> I suspect that the value: literal value 1231235959Z will simply come to
> mean "the end of time", even after the year 10,000. It has a well known
>
An X509v3 certificate has “notBefore” and “notAfter” fields. If either of
those is not present, then it is not an X509v3 certificate. The time marked by
those fields is the validity period.
If you want “never expires” X509v3 certificates, the best you can do it put a
very large value in the n
Robert Moskowitz wrote:
> The devices never test out the lifetime of their certs. That is up to
Exactly...
(Do you think about the MacGyver/StarTrek/A-Team/Leverage/MissionImpossible
plot line that goes along with each engineering decision?...)
> validating servers. And the iDevID is no
Hello!
Thanks for the response.
I was thinking of setting the duration fo the certificate to infinite,
i.e. the Validity period set to infinite.
Because in the information I have, the only possibility is to set the duration
(in days) with the command, but the command doesn't allow to put othe
