lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTilacFvDL7NDUGud9KKzTVmzbrpe3P9cK38coBeZ@mail.gmail.com>
Date: Thu, 22 Jul 2010 17:41:35 -0700
From: Ryan Castellucci <ryan.castellucci@...il.com>
To: Dimitry Andric <dimitry@...ric.com>
Cc: full-disclosure@...ts.grok.org.uk, Daniel Sichel <daniels@...derosatel.com>
Subject: Re: Expired certificate

On Fri, Jul 16, 2010 at 11:06 AM, Dimitry Andric <dimitry@...ric.com> wrote:
> On 2010-07-16 19:15, Larry Seltzer wrote:
>> Certificates have expiration dates so that the verification that happens
>> at the time the cert is acquired can have some "freshness."
>
> That is definitely not the only reason.  The longer a certificate (or
> actually, any 'secret key') is being used, the larger the probability
> that it will be compromised, either by an opponent brute-forcing it, or
> by good ole' human error.

Except that there's nothing that makes you change out the private key
when the cert expires.  As far as I've seen, the cert vendors will just let
you renew your certificate for the same private key.

-- 
Ryan Castellucci http://ryanc.org/

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ