Thanks Valerie,

A gentleman by the name of Quaker Fang, who says he is a developer 
responsible for this function on the project stated unequivocally that 
it is not currently possible to use WPA with the Broadcom 4318 chip in 
my HP Pavillion DV5115nr. I have decided to stop pursuing getting this 
working until a fix is provided in a build later this year. Until then I 
will just use Windows XP.

Thank you very much for being attentive to my questions!

Emery Rudolph
Sr. System Administrator
Office of Information Technology
University of Maryland University College
Phn:   301-985-7447
Email: Erudolph at umuc.edu
http://www.umuc.edu



Valerie Bubb Fenwick wrote:
> Hi Emery -
>
> So, you do not have strong crypto enabled on this
> machine. YOu didn't send the result of "ls /kernel/crypto/sparcv9"
> or "ls /kernel/crypto/", but I'm guessing you have never
> installed these packages.
>
> That being the case, you don't need to "upgrade" them, either.
>
> NOw, it's possible that the WPA driver depends on the stronger
> crypto - you'll need to ask whomever works on that code,
> this is probably not the right forum.
>
> Hope that helps!
>
> Valerie
>
> On Fri, 22 Feb 2008, Super-User wrote:
>
>> Valerie,
>>
>> I booted back up to Solaris. Here is the output you requested.
>> ------------------------------------
>> spica / -> cryptoadm list
>>
>> User-level providers:
>> Provider: /usr/lib/security/$ISA/pkcs11_kernel.so
>> Provider: /usr/lib/security/$ISA/pkcs11_softtoken.so
>>
>> Kernel software providers:
>>   des
>>   aes
>>   arcfour
>>   blowfish
>>   sha1
>>   sha2
>>   md5
>>   rsa
>>   swrand
>>   ecc
>>   md4
>>
>> Kernel hardware providers:
>> -----------------------------------------
>>
>>
>>
>> Valerie Bubb Fenwick wrote:
>>> HI Emery -
>>>
>>> They are part of the closed-bin tar files. Did you install those?
>>>
>>> It is easy to see if they are there. Please send me the output of
>>> $ cryptoadm list
>>>
>>> and
>>> $ ls /kernel/crypto/  (or ls /kernel/crypto/sparcv9 if your on sparc)
>>>
>>> and I can tell you whether or not they are installed.
>>>
>>> I don't know enough about the behaviour of hte WPA driver, though.
>>>
>>> You can find the on-closed-bins tar files here:
>>> http://dlc.sun.com/osol/on/downloads/current/
>>>
>>> which will contain the contents of the SUNWcry & SUNWcryr packages.
>>>
>>> Also, the more appropriate alias for these type of questions
>>> is probably crypto-discuss at opensolaris.org :)
>>>
>>> Valerie
>>>
>>> On Thu, 21 Feb 2008, Emery Rudolph wrote:
>>>
>>>> Hello Valerie,
>>>>
>>>> There is so much conflicting information regarding this matter, I 
>>>> am glad to speak to a primary developer. My confusion is that I 
>>>> keep hearing that I would need to upgrade these packages, but I do 
>>>> not have them installed at all. I have read some information saying 
>>>> it was included with the build and others saying I need to download 
>>>> and install them. Can you tell me which is correct? If I do not 
>>>> have them installed can you send the the exact link to the packages.
>>>>
>>>> Additionally, would you know if the lack of these packages would 
>>>> result in WPA WAPs showing up as WEP in the dladm scan-wifi output?
>>>>
>>>> Emery
>>>>
>>>>
>>>> Hi Emery -
>>>>
>>>> Yes, you do need to upgrade the SUNWcry/SUNWcryr packages everytime 
>>>> you upgrade
>>>> your system. These are available in the closed-bin tar bundle, 
>>>> associated
>>>> with each build.  I'm not sure, specifically, how this affects WPA 
>>>> driver, but
>>>> I do know that changes in the core crypto components often require 
>>>> all the
>>>> modules to be updated as well for other tasks.
>>>>
>>>> This is documented here:
>>>> http://www.opensolaris.org/os/project/crypto/Documentation/sunwcry/
>>>>
>>>> This will soon be changing, as I am wrapping up a project to pull 
>>>> strong
>>>> crypto into the base OS.
>>>>
>>>> hope that helps,
>>>>
>>>> Valerie
>>>>
>>>
>>> Valerie
>>
>
> Valerie


Reply via email to