From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] cryptographic signatures & factotum
Date: Fri, 12 Mar 2004 14:14:55 +0100 [thread overview]
Message-ID: <025d01c40834$05b6e390$67844051@SOMA> (raw)
In-Reply-To: <efb3cb105223eba43e8b8de5dcdbd1f1@plan9.bell-labs.com>
> Yes, modulo my bugs in the security stuff. Our password algorithm is
> only DES. Brute force would eventually work. We should be moving to
> a new alg.
http://plan9.bell-labs.com/magic/man2html/4/factotum
By default when factotum starts it looks for a secstore(1) account on $auth
for the user and, if one exists, prompts for a secstore password in order to
fetch the file factotum, which should contain control file commands. An
example would be
key dom=x.com proto=p9sk1 user=boyd !hex=26E522ADE2BBB2A229
key proto=rsa service=ssh size=1024 ek=3B !dk=...
where the first line sets a password for challenge/response
authentication, strong against dictionary attack by being a long random
string, and the second line sets a public/private keypair for ssh
authentication, generated by ssh_genkey (see ssh(1)).
next prev parent reply other threads:[~2004-03-12 13:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 23:03 steve-simon
2004-03-11 23:41 ` andrey mirtchovski
2004-03-11 23:57 ` 9nut
2004-03-12 0:03 ` George Michaelson
2004-03-12 0:09 ` boyd, rounin
2004-03-12 0:30 ` George Michaelson
2004-03-12 9:07 ` Bruce Ellis
2004-03-12 11:49 ` boyd, rounin
2004-03-12 12:14 ` boyd, rounin
2004-03-12 1:18 ` bs
2004-03-12 0:27 ` matt
2004-03-12 0:49 ` a
2004-03-12 19:52 ` rog
2004-03-12 1:02 ` Geoff Collyer
2004-03-12 9:23 ` Steve Simon
2004-03-12 13:03 ` David Presotto
2004-03-12 13:14 ` boyd, rounin [this message]
2004-03-12 13:35 ` David Presotto
2004-03-12 14:02 ` boyd, rounin
2004-03-12 16:23 ` John Kodis
2004-03-12 19:08 ` boyd, rounin
2004-03-14 3:39 ` Nick Jamieson
2004-03-14 3:53 ` boyd, rounin
2004-03-14 5:31 ` Nick Jamieson
2004-03-14 5:37 ` boyd, rounin
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='025d01c40834$05b6e390$67844051@SOMA' \
--to=boyd@insultant.net \
--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).