From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] auth(2) auth_wep usage?
Date: Fri, 12 Aug 2005 10:30:23 -0400 [thread overview]
Message-ID: <ee9e417a05081207305219bff0@mail.gmail.com> (raw)
In-Reply-To: <200508120417.j7C4Hm613915@zamenhof.cs.utwente.nl>
> I got the impression I have first to push a key
> to factotum, after which auth_wep picks it up.
> is there a more direct way to do it?
> I could not find a libarary routine to push the key
> to factotum in some programmatic way.
read /sys/src/cmd/auth/factotum/wep.c
factotum wep hands off the key directly to the
ethernet card so as not to reveal the secret.
it doesn't sound like that's appropriate here
so just write it directly yourself.
russ
next prev parent reply other threads:[~2005-08-12 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 4:17 Axel Belinfante
2005-08-12 14:30 ` Russ Cox [this message]
2005-08-12 16:00 ` Axel Belinfante
2005-08-12 16:09 ` 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=ee9e417a05081207305219bff0@mail.gmail.com \
--to=russcox@gmail.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).