From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] crypto question
Date: Thu, 14 Apr 2005 08:16:22 +1000 [thread overview]
Message-ID: <775b8d1905041315163be4315c@mail.gmail.com> (raw)
In-Reply-To: <20050413220530.GD13046@smp500.sitetronics.com>
Anyone thought off a computationally feasable attack that
disproves the"unsuitable for anything but authentication"
claim? Check out the protocol, the time frame, what
is exchanged and how it is subsequently used.
brucee
prev parent reply other threads:[~2005-04-13 22:16 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
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 [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=775b8d1905041315163be4315c@mail.gmail.com \
--to=bruce.ellis@gmail.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).