From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
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 18:00:34 +0200 [thread overview]
Message-ID: <200508121600.j7CG0Yo00221@demeter.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 12 Aug 2005 10:30:23 -0400." <ee9e417a05081207305219bff0@mail.gmail.com>
> > 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
I already had done so.
> factotum wep hands off the key directly to the
> ethernet card so as not to reveal the secret.
i see. just curious, is there any particular reason it
only supports keys 1-3 and not 4? (adding is trivial)
> it doesn't sound like that's appropriate here
> so just write it directly yourself.
fully correct. turned out I already had the
control-fd to the card open...
next prev parent reply other threads:[~2005-08-12 16:00 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
2005-08-12 16:00 ` Axel Belinfante [this message]
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=200508121600.j7CG0Yo00221@demeter.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).