From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] how to unlock screenlock?
Date: Thu, 30 Jun 2011 11:10:54 -0400 [thread overview]
Message-ID: <56ab11f414319152dd2ebd20057b12cf@ladd.quanstro.net> (raw)
In-Reply-To: <BANLkTinnXo5AQYZBn2on55CELQvKHDQ_cg@mail.gmail.com>
On Thu Jun 30 10:52:40 EDT 2011, yarikos@gmail.com wrote:
> check output of
> % grep 'proto=p9sk1' /mnt/factotum/ctl
>
> make sure the right key is on top of the list.
that doesn't seem like a reasonable way to select a key.
i don't see anything in factotum(4) that says that the the ctl
file has any particular order. the man page also says
All keys can have additional attributes that act either as
comments or as selectors to distinguish them in the auth(2)
library calls.
one would think that this would be the proper way to do it.
- erik
next prev parent reply other threads:[~2011-06-30 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 19:11 Nicolas Bercher
2011-06-29 19:33 ` Skip Tavakkolian
2011-06-30 14:51 ` Yaroslav
2011-06-30 15:10 ` erik quanstrom [this message]
2011-06-30 18:00 ` Russ Cox
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=56ab11f414319152dd2ebd20057b12cf@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).