From: Nils M Holm <nmh@t3x.org>
To: 9fans@cse.psu.edu
Subject: [9fans] ipso(1) patch
Date: Sun, 14 Mar 2004 14:54:13 +0100 [thread overview]
Message-ID: <2004031413541300-84310@Symmetry.UUCP> (raw)
I just put my passwords in a secstore and got the following message
when running ipso:
can't dial tcp!$auth!5356
secstore authentication failed
secstore read failed - bad password?
After adding '-s $auth' to the auth/secstore invocation in /rc/bin/ipso,
everything works fine. However, I guess that ipso is supposed to run
fine without this modification. Am I missing something?
Anyway, while looking at ipso, I thought that an option to just fetch
the factotum keys without displaying them would be nice. So I added the
'-q' flag which does this.
BTW, is there any common format for supplying patches for Plan 9?
I guess that using diff(1) would cause trouble when patching an
already-patched file, since it uses absolute line numbers.
Below, there is a context diff containing my changes to ipso, in
case anyone is interested.
Nils.
----- ipso(1) -q cdiff -----
*** ipso.old Sun Mar 14 14:31:31 2004
--- ipso Sun Mar 14 14:34:36 2004
***************
*** 11,16 ****
--- 11,17 ----
name = secstore
get = secstoreget
put = secstoreput
+ edit = yes
fn secstoreget{
auth/secstore -i -g $1 <_password
***************
*** 50,57 ****
name = aescbc
get = aesget
put = aesput
case *
! echo >[2=1] 'usage: ipso [-s] [file ...]'
exit usage
}
shift
--- 51,60 ----
name = aescbc
get = aesget
put = aesput
+ case -q
+ edit = no
case *
! echo >[2=1] 'usage: ipso [-aqs] [file ...]'
exit usage
}
shift
***************
*** 68,74 ****
bind -c /tmp /srv
cd /tmp
! echo '
Warning: The editor will display the secret contents of
your '$name' files in the clear.
'
--- 71,77 ----
bind -c /tmp /srv
cd /tmp
! if (~ $edit yes) echo '
Warning: The editor will display the secret contents of
your '$name' files in the clear.
'
***************
*** 103,109 ****
sleep 2; date > _timestamp # so we can find which files have been edited.
# edit the files
! $editor `{for(i in $files) basename $i}
# copy the files back
for(i in `{editedfiles}){
--- 106,113 ----
sleep 2; date > _timestamp # so we can find which files have been edited.
# edit the files
! if (~ $edit yes) $editor `{for(i in $files) basename $i}
! if not if (~ factotum $files) read -m < factotum > /mnt/factotum/ctl
# copy the files back
for(i in `{editedfiles}){
--
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/
next reply other threads:[~2004-03-14 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 13:54 Nils M Holm [this message]
2004-03-14 15:25 ` David Tolpin
2004-03-14 15:36 ` David Presotto
2004-03-14 18:55 ` boyd, rounin
2004-03-14 18:54 ` boyd, rounin
2004-03-14 16:07 ` David Presotto
2004-03-15 7:29 ` Nils M Holm
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=2004031413541300-84310@Symmetry.UUCP \
--to=nmh@t3x.org \
--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).