The idea of avoiding something less popular, is that if someone gets your
encrypted data, they could look through the algorithm and find a hole and
break it without you knowing. However, choosing Serpent is not a choice of
security through obscurity. Serpent is as open as AES, and in this day
Hi
I just wanted to jump in and say that I'm personally a fan of Serpent. I
like to use something that's a little less popular, but still open. It is
similar in strength (IMHO), but there will be more people trying to break
AES than Serpent. For example, I've read the XSL attack that can
On Sat, Mar 1, 2008 at 10:43 AM, Florian Philipp
[EMAIL PROTECTED] wrote:
On Fri, 2008-02-29 at 22:31 -0500, Mansour Moufid wrote:
On Fri, Feb 29, 2008 at 9:37 PM, Steffen Schulz [EMAIL PROTECTED] wrote:
snip
While I've been following this thread, I noticed this advert at the
top of my
I just wanted to jump in and say that I'm personally a fan of Serpent. I
like to use something that's a little less popular, but still open. It is
similar in strength (IMHO), but there will be more people trying to break
AES than Serpent. For example, I've read the XSL attack that can weaken
I benchmakerked them also about two years ago. At that time anibus encryption, xtc and lrw modes didnt exist in the kernel. I concentrated on 256 bits for AES, Serpant and Twofish. I dont recall the exact numbers, but this is the order from slowest (and also most secure) to fastest:
1. Serpent
2.
On Fri, Feb 29, 2008 at 9:37 PM, Steffen Schulz [EMAIL PROTECTED] wrote:
128bit are considered secure for the next several years.
On that subject, the CSEC (Communications Security Establishment
Canada) publishes an updated summary of safe key cryptoperiods for
different algorithms [1] which I
Do you think keysize is more important than choosing a cipher which
made it further in the AES-contest and therefore using Anubis with
320bit would be a better choice than AES or Twofish with 256bit?
I think a 256 bit cipher has 2^256 combinations or
On Thu, Feb 28, 2008 at 1:29 PM, Florian Philipp
[EMAIL PROTECTED] wrote:
One last question for everyone who has read this rather long mail (thank
you, btw): What exactly is benbi in aes-lrw-benbi:sha256 and what should
I choose for XTS? The kernel description states plain but essiv and