Hi,
I am a bit puzzled by the OBEX specification and maybe someone here has a clue
about it.
It is about chapter 3.5 of OBEX-1.2 specification. The procedure is clear to
me but the digest response is not clearly stated:
What is the format of the digest response field 0x01 ("UserID", see 3.5.2.2)?
Or better: Does it have any specific character set? Or the format as specified
by 3.5.1.3? Or is it only a generic byte stream?
Same goes for the password.
Maybe such functionality could go into libopenobex? Function prototypes for a
server may look like:
void obex_auth_default_nonce (/* out */ uint8_t nonce[16],
uint8_t secret,
size_t len);
int obex_auth_add_challenge (obex_t* handle,
obex_object_t* obj,
const uint8_t nonce[16],
int user_request,
int full_access,
const uint16_t* realm);
int obex_auth_unpack_response (obex_headerdata_t h,
uint32_t size,
/* out */ uint8_t digest[16],
/* out */ uint8_t nonce[16],
/* out */ uint8_t user[20]);
/* function for the client are missing */
/* usable for server and client */
void obex_auth_calc_digest(/* out */ uint8_t digest[16],
const uint8_t nonce[16],
const uint8_t* pass,
size_t len);
During that I discovered that it is strange that obex_headerdata_t.bs is
declared const. How is one supposed to create one for OBEX_ObjectAddHeader()?
Casting is not the best approach...
HS
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users
