From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] retry with aescbc
Date: Tue, 15 Oct 2002 22:48:26 -0400 [thread overview]
Message-ID: <4359283da1a0b5191aa07b7f767493a1@plan9.bell-labs.com> (raw)
Russ fixed the rc buglet, so if you get new stuff from sources you can use
# retry until good password
ramfs -m /n/kremvax >[2] /dev/null #suppress unmount message
status = 'failed to authenticate'
while(~ $status *'failed to authenticate'*)
auth/aescbc -d < lib/factotum.aes > /n/kremvax/factotum
cp /n/kremvax/factotum /mnt/factotum/ctl
unmount /n/kremvax
Also, Eric fixed a buglet in aescbc so it takes <CR> for an answer,
making it possible to get out of this loop by providing an empty
password.
-rob
next reply other threads:[~2002-10-16 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 2:48 rob pike, esq. [this message]
2002-10-18 2:59 ` Micah Stetson
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 3:02 Russ Cox
2002-10-16 8:49 Charles Forsyth
2002-10-16 8:29 Charles Forsyth
2002-10-16 2:05 rob pike, esq.
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=4359283da1a0b5191aa07b7f767493a1@plan9.bell-labs.com \
--to=rob@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).