From: Eric Grosse <ehg@lucent.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gnupg or pgp for plan9?
Date: Tue, 28 Mar 2006 08:59:48 -0500 [thread overview]
Message-ID: <e48da9739b8fbb3706a3be21ffc54583@plan9.bell-labs.com> (raw)
In-Reply-To: <105ff5a0df2c594ec826765600ec7d49@quintile.net>
auth/aescbc already includes anti-tampering checks,
based on SHA1 which is better than MD5.
But aescbc was never intended to last this long; it was a
temporary measure until NIST settled on a common mode of
operation, presumably CTR rather than CBC. It's not clear
yet if mode (or the hash function) is settled.
Also, aescbc was intended mainly for secstore. We wanted
something small enough to audit. For exchange with others,
or even yourself on other systems, I agree that PGP or S/MIME
is the way to go.
Eric
next prev parent reply other threads:[~2006-03-28 13:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 4:30 Fernan Bolando
2006-03-27 6:50 ` geoff
2006-03-27 7:25 ` Steve Simon
2006-03-27 9:18 ` Fernan Bolando
2006-03-27 13:10 ` Lluís Batlle
2006-03-27 17:26 ` Fernan Bolando
2006-03-28 0:38 ` Anthony Sorace
2006-03-28 13:59 ` Eric Grosse [this message]
2006-03-28 0:48 erik quanstrom
2006-03-28 14:59 ` Anthony Sorace
2006-03-28 15:23 ` Bruce Ellis
2006-03-28 15:57 ` Gabriel Diaz
2006-03-28 17:29 ` Charles Forsyth
2006-03-28 17:47 ` Gabriel Diaz
2006-03-29 0:27 ` Fernan Bolando
2006-03-29 2:49 ` geoff
2006-03-29 7:29 ` geoff
2006-03-29 2:07 ` Paul Lalonde
2006-03-29 3:17 ` quanstro
2006-03-29 3:56 ` Paul Lalonde
2006-03-29 9:09 ` Taj Khattra
2006-03-29 16:02 ` uriel
2006-03-29 22:03 ` Taj Khattra
2006-03-29 1:13 erik quanstrom
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=e48da9739b8fbb3706a3be21ffc54583@plan9.bell-labs.com \
--to=ehg@lucent.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).