[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bluetooth-dev] Security manager implementation
When I am running the stack on emulation mode b/w 2 linux boxes connected
via a null modem cable.. How can I ensure that the security features
can be called and tested as i integrate them
the menu prompt displays the following commands
rf_conn <xx:xx:xx:xx:xx:xx> <server channel>
rf_send <bytes> <dlci>
sdp_conn <xx:xx:xx:xx:xx:xx> <profile>
test_conn <xx:xx:xx:xx:xx:xx> <psm>
getinfo <xx:xx:xx:xx:xx:xx> <type>
bb_disc <hci handle>
Which of these are relevant when running in emulation mode
I can establish a ppp connection b/w both m/c's via the stack
Does it make sense in using sdp_conn while using in emulation mode
if I want to provide a list of services and want the sdp to recognise it
what do I do...
Could you also give a brief note on what each of the above command does ?
Thus Said Ulf Hansson On Fri, Mar 02, 2001 at 09:11:36AM +0100 :
*->> -----Original Message-----
*->> From: Daniel Ezekiel [mailto:firstname.lastname@example.org]
*->> Sent: Friday, March 02, 2001 8:05 AM
*->> To: email@example.com
*->> Subject: [bluetooth-dev] Security manager implementation
*->> could someone pls xplain the implementation that would be reqd in
*->> the following functions....
*->> void sec_man_init(enum security_requests user);
*->This is to be called from each user of the security manager. Currently only
*->used by L2CAP and RFCOMM. Other users may be defined as well.
*->With this function it is possible to initialize the usage of the security manager
*->from (for) each user.
*->> void sec_man_check(enum security_requests user, BD_ADDR bd_addr,
*->> u32 service_data, u32 user_data);
*->With this function, each user checks to see if the user (e.g. RFCOMM) should
*->allow the device bd_addr access to its service. If the security manager chooses
*->not to, it should respond negatively.
*->> void sec_man_event(enum security_requests user, BD_ADDR
*->> bd_addr, u8 event,
*->> u8 *param, u8 param_len);
*->When using the security manager, it is the one to enable authentication and
*->encryption therefore it will have to react to events regarding the security.
*->It may also react to event from the other device, i.e. it requesting authentication.
*->The entire security concept is described in the white paper called Bluetooth
*->Security Architecture on
Daniel D. Ezekiel
E-Mail : firstname.lastname@example.org
Fone : 91-80-5281461 Extn: 3322
PGP Key : hkp://email@example.com
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org