From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] possible way to have the secstore on the cpu server
Date: Sat, 15 Jun 2002 11:32:40 -0400 [thread overview]
Message-ID: <7a71a76889be64fd5e79917ef8faafdc@plan9.bell-labs.com> (raw)
What I was, and still am worried about, is accidentally letting
the secstore files be read. The only thing that protects against
a dictionary attack now is the service cutting you off for 5 minutes
or so after a small number of failed attempts. Accidents are
too easy in an environment that has varied and changing services
like a cpu server. It's quite likely that some typo will make
the secstore files readable to a bad guy for some window. Anyone
that can read them can mount a dictionary attack, all you need
guess is the user's password. What's in the secstore files
is a uses' crown jewels, so to speak.
next reply other threads:[~2002-06-15 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 15:32 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 11:51 presotto
2002-06-17 10:25 nigel
2002-06-15 15:34 presotto
2002-06-15 14:02 nigel
2002-06-14 16:42 Russ Cox
2002-06-14 8:26 nigel
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=7a71a76889be64fd5e79917ef8faafdc@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.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).