From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200508120417.j7C4Hm613915@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu From: Axel Belinfante Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Aug 2005 06:17:48 +0200 Subject: [9fans] auth(2) auth_wep usage? Topicbox-Message-UUID: 76abd660-ead0-11e9-9d60-3106f5b1d025 I have a program that somehow* gets a (wavelan) wep key and wants to set it (pass it to the wavelan driver). I've seen there is auth_wep but I can't make it work. It fails in the dial. I tried to give it strings like "#l" or "#l0" but that does not work, especially when I invoke this auth_wep twice. 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. The simplest trick seems to be to just open the right control file and write the control string by hand, and avoid auth_wep. am I once more overlooking something? assuming I want key beefdabeef set at index 1, on the ether0 device, what should I do? Axel. p.s. the pipe approach to interact with tls works great. *) somehow: via 802.1x eap-ttls-pap. it has worked, but needs cleanup. needs some support here and there in the system - I'll patch/create those and/or discuss them here, in due time.