From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] auth on terminal
Date: Thu, 25 Mar 2004 17:00:57 +0200 [thread overview]
Message-ID: <81132473206F3A46A72BD6116E1A06AE056175@black.aprote.com> (raw)
> However I do have a key, and the factotums are the same
> (the contents transfered securely via Neware :-)
If you're not running secstored(8), then your factotums are nonpersistent.
Factotum(4) looks for a secstore on startup; if it's not found at
tcp!$auth!5356 it gives up and does not use it even if later you start one.
next reply other threads:[~2004-03-25 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 15:00 Tiit Lankots [this message]
2004-03-25 15:09 ` andrey mirtchovski
2004-03-25 15:10 ` andrey mirtchovski
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 16:16 Tiit Lankots
2004-03-25 15:45 plan9fans
2004-03-25 15:14 Tiit Lankots
2004-03-25 15:09 Tiit Lankots
2004-03-25 13:36 plan9fans
2004-03-25 13:43 ` Fco.J.Ballesteros
2004-03-25 13:55 ` David Presotto
2004-03-25 14:51 ` Steve Simon
2004-03-25 15:31 ` Richard Miller
2004-03-25 14:00 ` Richard Miller
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=81132473206F3A46A72BD6116E1A06AE056175@black.aprote.com \
--to=t.lankots@aprote.ee \
--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).