George Adams wrote:
1) Why isn't everyone using stronger public/private key pairs? Nobody
who seems to offer SSL certs (Verisign, Thawte, GoDaddy, Comodo) tells
their customers to generate 2048-bit keys with OpenSSL. Obviously
they're not worried - why not?
It's really up to you to determine the lifetime of the need to secure
the data.
ie. if your developing an E-Commerce site then you'll want higher
security, otherwise if the data is going to obsolete in a couple of
years then you don't need something that big.
There are some documents from NIST that are trying to spell outline what
are appropriate lifetimes for certain key sizes.
http://csrc.nist.gov/publications/nistpubs/800-57/SP800-57-Part1.pdf
http://csrc.nist.gov/publications/drafts/800-78-1/draft-SP_800-78-1-070306.pdf
From page 66 -they're saying up till 2010 1024bit keys should be used.
"If information is initially signed in 2009 and needs to remain secure
for a maximum of
ten years (i.e., from 2009 to 2019), a 1024 bit RSA key would not
provide sufficient
protection between 2011 and 2019 and, therefore, it is not recommended
that 1024-bit
RSA be used in this case. "
2) Related to that, should I be worried that I'm generating a
public/private keypair for my Apache2/mod_ssl server that's only
1024-bits? Do I even have the OPTION of having a larger/stronger key,
or am I going to hit some weird compatibility problems with modern-day
browsers?
I think all CA's will only sign a request with a key size smaller than
it's own key size. Most CA's should be at least 2048 if not higher.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]