<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Re: WEP-reg</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText42626 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Sudha Ramachandra<BR><B>Sent:</B> Tue
12/21/2004 12:35 PM<BR><B>To:</B> Jouni Malinen<BR><B>Subject:</B> RE:
WEP-reg<BR></FONT><BR></DIV>
<DIV>
<DIV id=idOWAReplyText53652 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>hi</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2> Actually on the user configuration
side i have to provide options for selecting the WEP key support to
include 64 or 128 or 152 or 256 key support for which the source
code has to support....just let me know if u have any ideas regarding
this.....also will 802.11b cards support 152 or 256 or is it the
802.111a or the 802.11b/g that support....what r the cards i have to
select...</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>with regards</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>sudha </FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B>
hostap-bounces+sudha.ramachandra=wipro.com@shmoo.com on behalf of Jouni
Malinen<BR><B>Sent:</B> Tue 12/21/2004 9:22 AM<BR><B>To:</B>
hostap@shmoo.com<BR><B>Subject:</B> Re: WEP-reg<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>On Tue, Dec 21, 2004 at 09:09:19AM +0530,
sudha.ramachandra@wipro.com wrote:<BR><BR>> can anybody help me
out with the implementation of WEP 152 bit and 256 bit key support in the
hostap source code.....as i am doing this as a part of my academic project....My
expereince regarding this is very less...<BR><BR>May I ask what is the topic of
the academic project? Research on<BR>unsecure encryption at any key
length?<BR><BR>Replace WEP_KEY_LEN definition (couple of places) to use larger
maximum<BR>key length than 13, set host_encrypt and host_decrypt to 1, and you
are<BR>more or less done. I would search for other places using 13
(e.g.,<BR>prism2_ioctl_siwencode()) and replace them with suitable maximum
length.<BR>These may also need some small changes to support more than
two<BR>different key length.<BR><BR>You will also need to make sure that the
tools you are using to<BR>configure keys (e.g., iwconfig) support the lengths
you selected.<BR>hostap_crypt_conf does not seem to care about the key length,
so it<BR>might work as-is.<BR><BR>--<BR>Jouni
Malinen
PGP id EFC895FA<BR>_______________________________________________<BR>HostAP
mailing list<BR>HostAP@shmoo.com<BR><A
href="http://lists.shmoo.com/mailman/listinfo/hostap">http://lists.shmoo.com/mailman/listinfo/hostap</A><BR></FONT></P></DIV></DIV>
</BODY>
</HTML>
<table><tr><td bgcolor=#ffffff><font color=#000000><br>
<br>
Confidentiality Notice <br>
<br>
The information contained in this electronic message and any attachments to this message are intended<br>
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If<br>
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately<br>
and destroy all copies of this message and any attachments.<br>
</font></td></tr></table>