From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Cc: 9trouble@plan9.bell-labs.com
Subject: [9fans] Patch to wavelan driver, specify heys in hex.
Date: Sun, 29 Jun 2003 15:01:16 -0400 [thread overview]
Message-ID: <200306291901.h5TJ1G703256@augusta.math.psu.edu> (raw)
So my sysadmins at work set up a wireless lan, but made the WEP key a
random string of hex digits that doesn't easily convert into a UTF
sequence I can put in a file. So I made a small change to the wavelan
driver to recognize keys that start with ``0x'' as hex strings and
convert them to a binary encoding as appropriate. It's not perfect, as
I'm not checking for decoding errors, nor are non-hex heys that start
with ``0x'' handled, but I wanted to send it out for others who might
be faced with a similar setup.
- Dan C.
next reply other threads:[~2003-06-29 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 19:01 Dan Cross [this message]
2003-06-29 19:05 ` Dan Cross
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=200306291901.h5TJ1G703256@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
--cc=9trouble@plan9.bell-labs.com \
/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).