Getting started with HS20 r2 (OSU client/server and such?)

Ben Greear greearb
Tue Mar 17 19:37:08 PDT 2015

And one final set of questions for today:

OSEN authentication seems to use a 'osu-ca.pem' file,
but I don't see anything that downloads or creates that.

I do see several other .pem files mentioned in the code.

Do you know where that osu-ca.pem comes from?

Also, it seems that 'current-working-directory' is used a
lot, and there are quite a few other hard-coded values and
file paths.

I am planning to work on making those cmd-line args so that
I have easier control over the application...  That sound
like a reasonable approach?


On 03/17/2015 11:02 AM, Ben Greear wrote:
> On 03/17/2015 08:22 AM, Jouni Malinen wrote:
>> On Tue, Mar 17, 2015 at 08:06:54AM -0700, Ben Greear wrote:
>>>> Number of clients may recognize OSEN configuration as WEP.
>>> Should this be fixed in the wpa-cli scan output to show OSEN instead
>>> of WEP?
>> Probably, or well, in wpa_supplicant scan result processing. It looks
>> like it does not currently have any special case for OSEN, so the [WEP]
>> default gets used if privacy is set.
> I can work on that...
>>> Ok.  What should happen before the cmd_signup() is called, or maybe a better
>>> question, how should a station determine that it should do cmd_signup?
>> That's pretty much the first operation.. The exact trigger depends on
>> what kind of user experience is desired for the specific device, but
>> that could be, e.g., scan showing no matching networks.
> Do you happen to have an example OSEN hostapd config file, and even
> better, a pair with one OSEN and one .1x config file meant to work
> together in conjunction with the hs20 client/servers?
> If not, would it be correct to assume that the OPEN/OSEN hostapd config
> file has all of the HS20 configurables, and the .1x is mostly just normal
> with .1x radius config info (ie, no HS20 attributes)?
> Thanks,
> Ben

Ben Greear <greearb at>
Candela Technologies Inc

More information about the Hostap mailing list