From: Sam <test532@codingninjas.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] double algorithm question E3E-2A1
Date: Sat, 1 Aug 2009 23:56:02 -0400 [thread overview]
Message-ID: <200908012356.03807.test532@codingninjas.org> (raw)
In-Reply-To: <cf657bae0908011857y4ec8ad03v8796d82c60998c49@mail.gmail.com>
Hi Roscoe,
Thanks for your suggestion. I have heard this vaguely elsewhere in the past.
Perhaps that is what I will do now that you bring it up again.
By the way, your mail got through each time. I get that spam message too when
posting. I believe what happens is that when the mailing list server sends our
message to each address that is subscribed, only one person who is subscribed
has some problem that triggers that message from their address. Thus your mail
gets to everyone but that one person. I don't know about you, but every time I
post I also get a subscribe request confirmation for some yahoo group for
danish cats as well, lol.
Thanks again,
Sam
> Getting past spam filter, attempt 4. If this doesn't work I'm giving up.
>
>
> FWIW I wouldn't forget about Serpent, which came 2nd in the AES
> selection process. From Practical Cryptography, by Niels Ferguson and
> Bruce Schneier:
> "If you are paranoid about the security of your data, and speed is
> not important, then you should choose Seprent. During the AES process,
> every serious cryptographer agreed that Serpent was the most secure
> (or most conservative) of the submissions"
>
> -- Roscoe
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
prev parent reply other threads:[~2009-08-02 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 1:49 [dm-crypt] double algorithm question E3E-2A1 Roscoe
2009-08-02 1:57 ` Roscoe
2009-08-02 3:56 ` Sam [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908012356.03807.test532@codingninjas.org \
--to=test532@codingninjas.org \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox