Re: triple algorithms

On Thu, 28 Feb 2008 12:52:47 +0100
Ertugrul Söylemez <es@xxxxxxxx> wrote:

Now history has shown that finding weaknesses in modern asymmetric
ciphers usually does not eliminate their security completely, but
merely weakens it by a factor, which is practically unimportant to
most people. I would even consider MD5 still secure enough for most
applications. I wouldn't recommend it for new ones, though, just as I
wouldn't recommend 1024 bits moduli, even though they're still
relatively secure.

Typo, sorry. It should be "modern symmetric" in the first line.


Regards,
Ertugrul.


--
http://ertes.de/

.

Relevant Pages

  • Re: Minimum & Maximum for username/password
    ... > I would recommend not setting a default min/max length for ... Firstly if these logins are going into a db, ... So what you do is you get the login and password, and MD5 the password ...
    (comp.lang.java)
  • Re: Minimum & Maximum for username/password
    ... > I would recommend not setting a default min/max length for ... Firstly if these logins are going into a db, ... So what you do is you get the login and password, and MD5 the password ...
    (comp.lang.java.programmer)
  • Re: Minimum & Maximum for username/password
    ... > I would recommend not setting a default min/max length for ... Firstly if these logins are going into a db, ... So what you do is you get the login and password, and MD5 the password ...
    (comp.lang.java.help)
  • Re: Crypto Mini-FAQ
    ... There are lots of low-security apps for which MD5 is fine. ... but SHA1 is also fine for those. ... and recommend gradually swapping ... >are those who think that AES is at the edge because it doesn't ...
    (sci.crypt)