Re: [Open1x-developers] xsupplicant library?

[Tom E. <to...@gr...>]

No, I have not documented the API yet, I am waiting to see how much interest
there is.

The API but it is fairly straightforward, just these methods below.
The client's main work is to fill one big structure, struct xsup_session_config,
which contains all needed authentication material for the eap method it wants to
use.


/* register callbacks for eap data / success / failure */
xsup_returntype xsup_setup_library(const struct xsup_library_config* conf);

xsup_returntype xsup_create_session(const struct xsup_session_config* conf,
xsup_cookie cookie);

void xsup_destroy_session(xsup_cookie cookie);

/* eap payload */
xsup_returntype xsup_received_eap_payload(xsup_cookie cookie, const uint8_t*
data, size_t length);




Josh Howlett wrote:
> Tom,
> 
>> I have taken xsupplicant 2.2.0 und have successfully split it into two parts:
>> - a library libxsup (containing mainly the eap_types)
>> - an xsupplicant application.
> 
> Great idea!
> 
> As it happens, I might have a use for this. Have you documented your API?
> 
> Josh.
> 
> JANET(UK) is a trading name of The JNT Association, a company limited
> by guarantee which is registered in England under No. 2881024 
> and whose Registered Office is at Lumen House, Library Avenue,
> Harwell Science and Innovation Campus, Didcot, Oxfordshire. OX11 0SG
> 

-- 
This e-mail and any of its attachments may contain proprietary information,
which is privileged, confidential or subject to copyright belonging to Grid Net,
Inc. This e-mail is intended solely for the use of the individual or entity to
which it is addressed. If you are not the intended recipient, you are hereby
notified that any dissemination, distribution, copying or action taken in
relation to the contents of this e-mail is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify the sender
immediately and permanently delete.