Hi, > Am Tuesday 06 January 2009 17:34:38 schrieb Marcel Holtmann: > > Hi Hendrik, > > > > > > I have been searching about the OBEX authentication implementation > > > > around the open source communities and found the source code by > Hendrik > > > > Sattler in one of openobex mailing archives and obexpushd project. > > > > > > > > I wonder why those codes are not included in the current openobex > > > > version. According to the OBEX spec, the implementation of OBEX > > > > authentication is mandatory though its adoption is depending on each > > > > profile. For the FTP, this feature should be implemented. > > > > > > > > I see no codes about OBEX authentication in openobex 1.4 except two > > > > header type constant declarations. Do you have a plan for the > > > > implementation or any reasons for excluding this feature? > > > > > > I am working on making the implementation better and integrate it. You > > > will find it in my git tree when done. > > > However, no device known to me actually uses this form of > authentication > > > but use transport authentication instead (e.g. bluetooth pairing). > > > > for some really strange reasons it is mandatory for the Bluetooth > > Phonebook Access profile. So you do pairing and then have to support > > OBEX authentication. It is not useful, but mandatory to support (if the > > other side initiates it). > > I have it almost completely integrated, currently doing the doxygen stuff. > IIRC, it is also mandatory for a file browsing service server. > > Someone needs to review it, though, as it is completely untested. A public > domain MD5 implementation comes with it (written in 1993). > > The patch is now in the updates branch of my git tree at gitorious.org. > You > can view it here: > http://gitorious.org/projects/openobex/repos/mainline/commits/69af139c5e71 > 9df2eb289ca003b70ae0bef56922 > > HS >
I tried to test OBEX authentication client and server functionality using linux PC with bluez 3.26 and obexpushd 0.6 and nokia N95 handset. I ran obexpushd with "obexpushd -nda ./test.txt" command in which text file contains a id:passwd tuple as the -a option explains in the obexpushd doc file. It seems that N95 accepts the server side OBEX authentication challenge request because it prompts a passcode window. But when I enter a password written in test.txt N95 repeats prompting the passcode window again and again until obexpushd dies due to seg. fault. Obexpushd generates logs as below: obexpushd 0.6 Copyright (C) 2006-2007 Hendrik Sattler This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. Listening on bluetooth channel 9 OBEX_EV_ACCEPTHINT, OBEX_CMD_CONNECT Connection from "bluetooth/[00:18:42:E7:24:1A]:9" 0: OBEX_EV_REQHINT, OBEX_CMD_CONNECT 0: OBEX_EV_REQ, OBEX_CMD_CONNECT 0: OBEX_EV_REQDONE, OBEX_CMD_CONNECT 0: OBEX_EV_REQHINT, OBEX_CMD_CONNECT 0: OBEX_EV_REQ, OBEX_CMD_CONNECT 0: OBEX_EV_REQDONE, OBEX_CMD_CONNECT ... Other handsets simply closes its connection without prompting a passcode window. I wonder if I missed something or obexpushd doesn't work well with N95. How can I test this functionality? Thanks. Best Regards, Jo ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
