From: rudolf.sykora@gmail.com
To: 9fans@9fans.net
Subject: Re: [9fans] how to use secstore in p9p
Date: Sun, 9 Dec 2012 16:19:03 +0100 [thread overview]
Message-ID: <ff72544e026c6e36f61c740205a06b8b@redstar.rudas.dom> (raw)
In-Reply-To: <20121208192741.68150302@zinc.9fans.fr>
> Please apply the following patch. It should fix your problem.
>
> http://codereview.appspot.com/6906057
>
> cd $PLAN9
> hget http://codereview.appspot.com/download/issue6906057_2002.diff | patch -p1
> cd src/cmd/auth/factotum/
> mk nuke && mk install && mk clean
>
> This is a remnant of a bug we fixed two years ago.
>
> --
> David du Colombier
Thanks for the patch. This helped and what I wanted (with secstore)
now works. Still I dare have a few remaining questions:
When I now run factotum, I get:
;factotum
redstar Dec 9 15:08:15 secstore from ?!?
secstore password:
redstar Dec 9 15:08:18 secstore from ?!?
redstar Dec 9 15:08:52 AUTH ruda
redstar Dec 9 15:08:52 [ruda] GET factotum
redstar Dec 9 15:08:52 [ruda] BYE
which is ok, but there still is a few-second-long delay (say 10 sec)
between me entering the password and the response (initially I thought
the thing had hung again). So
1/ Why is there the delay?
2/ What does the 'secstore from ?!?' message want to convey?
Finally,
3/ I've created an empty $PLAN9/ndb/auth file in order to get rid of the
'no ndb/auth' message, which used to appear when trying to run the
'sectore' command. What is this all about?
Thanks again for the working patch and for any potential answer to my
questions!
Ruda
prev parent reply other threads:[~2012-12-09 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 15:42 Rudolf Sykora
2012-12-08 17:29 ` Rudolf Sykora
2012-12-08 18:27 ` David du Colombier
2012-12-09 14:43 ` rudolf.sykora
2012-12-09 15:18 ` rudolf.sykora
2012-12-09 17:14 ` David du Colombier
2012-12-09 18:06 ` Rudolf Sykora
2012-12-09 15:19 ` rudolf.sykora [this message]
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=ff72544e026c6e36f61c740205a06b8b@redstar.rudas.dom \
--to=rudolf.sykora@gmail.com \
--cc=9fans@9fans.net \
/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).