From: Tim Newsham <newsham@lava.net>
To: Bruce Ellis <bruce.ellis@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] crypto question
Date: Wed, 13 Apr 2005 08:45:45 -1000 [thread overview]
Message-ID: <Pine.BSI.4.61.0504130842300.5044@malasada.lava.net> (raw)
In-Reply-To: <775b8d19050413085223e10893@mail.gmail.com>
> I think it's a mute point. "unsuitable for anything
> but authentication" is fair, but it is suitable for p9sk1.
>
> If you really wanta try a man-in-the-middle attack you'll
> need more resources than the user is willing to wait for.
>
> If you are just snooping you won't learn anything to
> compromise the authenticated session or shared key.
>
> Correct me if I'm wrong.
If it is "suitable for authentication" then there's no problem.
I have definitely not figured out a way to abuse the weaknesses
to break the authentication. My concern is that weaknesses like
this often provide an avenue for an attack and my failure to come
up with one is definitely not a proof that one doesn't exist.
Why use a weak form of chaining that offers an attacker some
extra leverage when stronger forms exist, are well known and
widely examined?
> brucee
Tim Newsham
http://www.lava.net/~newsham/
next prev parent reply other threads:[~2005-04-13 18:45 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 [this message]
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=Pine.BSI.4.61.0504130842300.5044@malasada.lava.net \
--to=newsham@lava.net \
--cc=9fans@cse.psu.edu \
--cc=bruce.ellis@gmail.com \
/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).