RE: [Full-disclosure] Comparing Algorithms On The List OfHard-to-brut-force?

2005-11-01 Thread Aditya Deshmukh
> views? Only on 2 of them > -- > AES I would put my money on this one because this is a std. does all the encryption very fast and can be extended as per the security requirments: you want more security than 128 bit you can have 192, you want more you can go to virtually any number AES2

Re: [Full-disclosure] Comparing Algorithms On The List OfHard-to-brut-force?

2005-11-01 Thread Bipin Gautam
On 11/1/05, Brandon Enright <[EMAIL PROTECTED]> wrote: > Brute forcing an algorithm suggests that you are not attacking a weakness or > known flaw in the algorithm but rather just running through the keyspace > trying to recover the plaintext. In that case, whichever allows you to use > the most b

Re: [Full-disclosure] Comparing Algorithms On The List OfHard-to-brut-force?

2005-11-01 Thread James Longstreet
On Nov 1, 2005, at 12:11 PM, Brandon Enright wrote: IIRC, there aren't any good known attacks against Blowfish, AES, or Twofish so the *RIGHT* algorithm is whatever works best for your application. Depending on the situation, there may be a feasible cache-timing attack on software impleme

Re: [Full-disclosure] Comparing Algorithms On The List OfHard-to-brut-force?

2005-11-01 Thread Andrew Farmer
On 01 Nov 05, at 10:11, Brandon Enright wrote: Brute forcing an algorithm suggests that you are not attacking a weakness or known flaw in the algorithm but rather just running through the keyspace trying to recover the plaintext. In that case, whichever allows you to use the most bits is w

RE: [Full-disclosure] Comparing Algorithms On The List OfHard-to-brut-force?

2005-11-01 Thread Brandon Enright
Brute forcing an algorithm suggests that you are not attacking a weakness or known flaw in the algorithm but rather just running through the keyspace trying to recover the plaintext. In that case, whichever allows you to use the most bits is what you want. IIRC, there aren't any good known attack