From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how do you usually deal with new users and secstore?
Date: Sun, 7 Sep 2003 12:38:32 -0600 [thread overview]
Message-ID: <7c0c961ff3835850b345e0aa09ce2209@plan9.ucalgary.ca> (raw)
In-Reply-To: <3F5B7841.9000705@lucent.com>
> I create a secstore account immediately for new users and set
> their p9sk1 password to a string with, say, 80 bits of entropy
> so brute-force attack on sniffed challenge/response packets is
> infeasible. When creating the initial secstore factotum file,
> I encourage the new user to install an RSA key as well, for
> ssh to remote systems without having to type any more passwords.
such a huge password would be impossible to use in our environment,
where we don't have any other means of proving who a user is -- people
logging in with drawterm can't be expected to remember an 80-character
string, especially a random one...
am I missing something? i can't see how one can get access to
secstore without first having done a p9sk1 authentication..
on a different topic -- what is the syntax for an rsa key? i'm
currently using a secstore entry (on a per-user, per-machine basis)
for remote ssh connections similar to:
key proto=pass server=some.machone service=ssh user=andrey ...
andrey
next prev parent reply other threads:[~2003-09-07 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 17:20 mirtchov
2003-09-07 18:26 ` Eric Grosse
2003-09-07 18:38 ` mirtchov [this message]
2003-09-07 19:07 ` Eric Grosse
2003-09-07 19:25 ` mirtchov
2003-09-07 19:41 ` ron minnich
2003-09-07 20:18 ` boyd, rounin
2003-09-07 20:53 ` matt
2003-09-07 19:13 ` 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=7c0c961ff3835850b345e0aa09ce2209@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).