From: Micah Stetson <micah@cnm-vra.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] retry with aescbc
Date: Thu, 17 Oct 2002 19:59:10 -0700 [thread overview]
Message-ID: <20021017195910.A11608@cnm-vra.com> (raw)
In-Reply-To: <4359283da1a0b5191aa07b7f767493a1@plan9.bell-labs.com>; from rob@plan9.bell-labs.com on Tue, Oct 15, 2002 at 10:48:26PM -0400
> # 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
When I use cp to inject keys into factotum, I get weird results.
Should read -m always be used, or is this a bug in factotum?
Here's what I get reading /mnt/factotum/ctl after read -m:
key ek=2F n=reallylongnumber proto=sshrsa size=1024 !dk? !p? !q? !kp? !kq? !c2?
key dom=outside.plan9.bell-labs.com proto=p9sk1 user=micah !password?
key proto=vnc server=cephas !password?
But using cp, I get this:
key dom=outside.plan9.bell-labs.com ek=2F key='' key='' n=reallylongnumber proto=sshrsa server=cephas size=1024 user=micah !dk? !p? !q? !kp? !kq? !c2? !password? !password?
key dom=outside.plan9.bell-labs.com ek=2F key='' key='' n=reallylongnumber proto=p9sk1 server=cephas size=1024 user=micah !dk? !p? !q? !kp? !kq? !c2? !password? !password?
key dom=outside.plan9.bell-labs.com ek=2F key='' key='' n=reallylongnumber proto=vnc server=cephas size=1024 user=micah !dk? !p? !q? !kp? !kq? !c2? !password? !password?
I think this is a consequence of cp using a single write to copy
the file. I wouldn't bring it up except that rob uses cp in his
example.
Micah
next prev parent reply other threads:[~2002-10-18 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 2:48 rob pike, esq.
2002-10-18 2:59 ` Micah Stetson [this message]
-- 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=20021017195910.A11608@cnm-vra.com \
--to=micah@cnm-vra.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).