From: David R. <n1...@ma...> - 2001-12-18 11:21:21
|
I've taken a look at the API for the key chain and I estimate that I'll have support done by the New Year. There is a lot of documentation to read to make sure that I implement it correctly, but it looks doable. -- Dave On Friday, December 14, 2001, at 08:07 PM, David Ross wrote: > I'm thinking that if the api is understandable enough that I'll move > all password storage into the keychain. > Though this has one downside - if I make a command line tool to allow > manipulation of the driver or just to init it, there would be no way to > access the keychain before you logged in (as far as I know) and it > would make the commandline tool darwin incompatible. > > I'll take a look into this, this weekend and get back to you on Sunday > on how long it will take me to get this done. > > -- Dave > > > On Friday, December 14, 2001, at 07:55 PM, Curtis Laser wrote: > >> The 128 bit network is driven by HP branded Lucent Access Points that >> are >> stuffed with Orinoco Gold cards. >> >> As I remember the keychain API you pass in something like an account >> or URL >> and you get the password for it back. The network could obviously be >> the >> "account". The only limitation would be one password per network but >> that >> doesn't seem all that restrictive. A big benefit of using the API is >> that >> the passwords are stored in an encrypted file. >> >> Curtis >> >> >> on 12/14/01 5:31 PM, yuriwho at yu...@ma... wrote: >> >>> Curtis, >>> >>> Interesting that the Orinoco Gold cards appear to be different >>> from the WaveLAN gold cards. What type of access point is driving your >>> 128 bit network? >>> >>> As far as keychain support for the prefpane is concerned, that >>> is an interesting idea. I know that Dave was planning to implement a >>> mechanism for saving passwords to a pref file (or pw file) but I don't >>> know if he has considered keychain support. Do you think it would work >>> well with saving multiple networks and passwords? If so, perhaps you >>> and >>> dave should discuss it. Please post any future development discussion >>> to >>> the devel list. >>> >>> Thanks for your feedback & interest in helping, >>> >>> Y >>> >>> On Thursday, December 13, 2001, at 12:24 PM, Curtis Laser wrote: >>> >>> >>>> I am running Mac OS X 10.1.1 (build 5M28). Version 1.1.0 of >>>> IOPCCardFamily.kext and version 1.0.1b2 of WirelessDriver.kext. >>>> >>>> I connect to both a 128 bit and 40 bit encrypted networks. I have >>>> tried a number of cards with this version of the software. >>>> >>>> Using an Orinoco Gold card I can connect to the 128 bit encrypted >>>> network, but not to the 40 bit encrypted network. The WEP key for the >>>> 128 bit network is a simple hex representation of the ASCII >>>> characters >>>> in the key. I tried both this approach and getting the key from >>>> Airport Config's utility with the 40 bit network and neither worked. >>>> >>>> I thought I might be doing something wrong, so I tried a Silver card >>>> (HP branded but essentially a silver Orinoco card) and this was able >>>> to connect to the 40 bit network (using the key from Airport Config) >>>> without problems. I suspect that there is a problem for Orinoco Gold >>>> cards accessing a 40 bit encrypted network. >>>> >>>> I can also confirm that I could connect to neither network using a >>>> WaveLAN gold card. >>>> >>>> I have considered adding Keychain support to the Wireless Config >>>> panel, but before I start mucking with the code I wanted to know how >>>> much turmoil that part of the code is currently experiencing, I >>>> wouldn't want to step on your toes. >>>> >>>> Thanks for all your hard work! >>>> Curtis Laser >>>> >>> >> > > > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel |