From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] crypto question
Date: Wed, 13 Apr 2005 05:44:37 +0200 [thread overview]
Message-ID: <035d01c53fdb$1e46c7b0$9efb7d50@kilgore> (raw)
In-Reply-To: <Pine.BSI.4.61.0504121735440.5044@malasada.lava.net>
> If this is the case, should this be switched now that export restrictions
> have eased?
'spose so. i quite liked the CBC tho. guess it hints what the NSA
could bust, rather than J. Random Idiot.
--
MGRS 31U DQ 52572 12604
next prev parent reply other threads:[~2005-04-13 3:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 22:54 Tim Newsham
2005-04-12 23:10 ` boyd, rounin
2005-04-13 0:18 ` Martin Harriss
2005-04-13 3:36 ` Tim Newsham
2005-04-13 3:44 ` boyd, rounin [this message]
2005-04-13 15:52 ` Bruce Ellis
2005-04-13 18:45 ` Tim Newsham
2005-04-13 19:23 ` Devon H. O'Dell
2005-04-13 22:01 ` Karl Magdsick
2005-04-13 22:05 ` Devon H. O'Dell
2005-04-13 22:16 ` Bruce Ellis
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='035d01c53fdb$1e46c7b0$9efb7d50@kilgore' \
--to=boyd@insultant.net \
--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).