From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hmm, secstore KFS?
Date: Sat, 12 Oct 2002 18:47:58 +0100 [thread overview]
Message-ID: <c33edc8b453189d1b86424332685110d@caldo.demon.co.uk> (raw)
>>Btw, one thing that's always confused me about secstore; can't one
>>mount a dictionary attack against data that's transmitted across the
>>network from the secstore? Granted, that's harder, since the attacker
>>would have to snif it and couldn't simply pursue it at his or her
>>leasure, but still possible, or no?
the connection itself is separately encrypted, with digests.
next reply other threads:[~2002-10-12 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 17:47 Charles Forsyth [this message]
2002-10-12 17:49 ` Dan Cross
2002-10-12 20:30 Eric Grosse
2002-10-12 21:10 ` Dan Cross
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=c33edc8b453189d1b86424332685110d@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).