On Sat, 16 Jan 2010 11:58:03 -0600
Steven Stern wrote:
> Because I have a hard time remembering how to generate self-signed
> certs, I set the expiration date for 5 years the last time I had to
> create them.
>
There is a Fedora package for gnomint, a GUI which makes it easy to set
yourself up
On Sat, 2010-01-16 at 11:58 -0600, Steven Stern wrote:
> Because I have a hard time remembering how to generate self-signed
> certs, I set the expiration date for 5 years the last time I had to
> create them.
I'm not sure that I see a good reason for setting an expiry date, at
all.
It'd probably
On Sat, Jan 16, 2010 at 17:59:32 +0100,
Vadkan Jozsef wrote:
> what does a self-signed outdated ssl cert worth? [https]
>
> could it be tricked [https] in a way, that the end user will not
> recognize? [e.g. he already accepted the cert one time, and the browser
> would warn
On 01/16/2010 11:21 AM, Craig White wrote:
> On Sat, 2010-01-16 at 17:59 +0100, Vadkan Jozsef wrote:
>> what does a self-signed outdated ssl cert worth? [https]
>>
>> could it be tricked [https] in a way, that the end user will not
>> recognize? [e.g. he already accepted
On Sat, 2010-01-16 at 17:59 +0100, Vadkan Jozsef wrote:
> what does a self-signed outdated ssl cert worth? [https]
>
> could it be tricked [https] in a way, that the end user will not
> recognize? [e.g. he already accepted the cert one time, and the browser
> would warn her, if it
what does a self-signed outdated ssl cert worth? [https]
could it be tricked [https] in a way, that the end user will not
recognize? [e.g. he already accepted the cert one time, and the browser
would warn her, if it been ""attacked""?]
..I mean does an outdated self-signed
