.org [owner-openssl-...@openssl.org] on
> behalf of Ben Laurie [b...@links.org]
> Sent: Monday, March 11, 2013 14:16
> To: openssl-dev@openssl.org
> Subject: Re: Question on encryption algorithms brittleness
>
> On 11 March 2013 11:09, Ido Regev wrote:
> > Hi,
> >
256-bit.
Good luck.
From: owner-openssl-...@openssl.org [owner-openssl-...@openssl.org] on behalf
of Ben Laurie [b...@links.org]
Sent: Monday, March 11, 2013 14:16
To: openssl-dev@openssl.org
Subject: Re: Question on encryption algorithms brittleness
On 11 March 2
Find an unhappy employee and offer them a couple-hundred thousand Euro for
their password.
The question/requirement as stated is unanswerable, and certainly not by the
well-meaning volunteers who frequent this list.
/r$
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
_
On Behalf Of Jason Gerfen
> Sent: Wednesday, March 06, 2013 4:29 PM
> To: openssl-dev@openssl.org
> Subject: Re: Question on encryption algorithms brittleness
>
>
>
> NIST has more details. http://csrc.nist.gov/publications/PubsFIPS.html See
> FIPS 200 (Minimum guidelines), FIPS
safe answer is "go hire an expert".
PG
From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org] On
Behalf Of Ido Regev
Sent: Monday, March 11, 2013 7:09 AM
To: openssl-dev@openssl.org
Subject: RE: Question on encryption algorithms brittleness
Hi,
I hav
l-dev@openssl.org
Subject: Re: Question on encryption algorithms brittleness
NIST has more details. http://csrc.nist.gov/publications/PubsFIPS.html See FIPS
200 (Minimum guidelines), FIPS 198--1 (HMAC), FIPS 197 (AES, symmetric
algorithms) & FIPS 185 (PKI escrow)
On Wed, Mar 6, 2013 at 7:15
This site would be a good place to start:
http://www.keylength.com/
Matt
On 6 March 2013 13:56, Ido Regev wrote:
> We have a requirement from one of our customers regarding the encryption
> algorithms – "Make use of published public encryption algorithms that are
> considered to be practicall
