[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] RE: Security manager implementation inclusion of LMP Command/Resp onse



Hi Ulf
 Pls correct me if am wrong
 for the securtiy mgr implementation

 Roughly this would be the reqd work on the stack

 in src/sec_client.c
 under void sec_man_init(enum security_requests user)
{
 there would be a switch for each of the user (HCI,RFCOMM,L2CAP)
 The security mgr would have a unix socket listening to incoming requests
 (since i guess most of the ipc used here in user mode is via unix sockets)

The security mgr would take care of initiailizing service specific funcions

 under void sec_man_check(enum security_requests user, BD_ADDR bd_addr, u32 service_data,
              u32 user_data)

again a switch and a similar communication with the security mgr using 
the above unix sockets...

for each of the  user

one query at this point interaction of l2cap, rfcomm and other multiplexing
protocols with the security mgr are straightforward as they involve
checking against the database for access,straighforward checking of 
some parameters in some service/database structure..

The same applies for ESCE and Registration procedures too

but In case of HCI, this requires interaction with the HCI for commands
and waiting for the response.... Could you shed some light on this...
How would i invoke the appropriate HCI interfaces and how does HCI
respond to these in terms of events..How do I capture the response from the HCI

also in the case of emulation mode connection b/w 2 linux boxes via a nullmodem
cable, How can I ensure the testing of these interfaces, in short how
can i invoke the various HCI, functionality w/o the actual hardware
Thanks in advance
 
 Regards, 
 Danny 
 




Thus Said Ulf Hansson On Mon, Mar 05, 2001 at 11:18:30AM +0100 :
*->> -----Original Message-----
*->> From: Daniel Ezekiel [mailto:danny@xxxxxxx.com]
*->> Sent: Monday, March 05, 2001 11:01 AM
*->> To: Ulf Hansson
*->> Cc: 'danny@xxxxxxx.com
*->> Subject: Security manager implementation inclusion of LMP
*->> Command/Response
*->> 
*->> 
*->> Hi Ulf,
*->> *->http://www.bluetooth.com/developer/whitepaper/whitepaper.asp
*->> in the last section 4.5 Interface with HCI/LMP
*->> only describes the Command/response  of the HCI
*->> Dont you think the command/response ofLM
*->> viz., 
*->> LMP_comb_key
*->> LMP_encryption_key_size
*->> LMP_in_rand
*->> LMP_start_encryption_req
*->> LMP_stop_encryption_req
*->> LMP_temp_rand
*->> LMP_temp_key
*->> LMP_unit_key
*->> 
*->> also fall under the purview of the security manager the required
*->> Interfaces need to be provided.
*->
*->No, because we can not change the behaviour of the link manager other than 
*->by issuing HCI commands. All HCI commands needed ought to be provided (but
*->if you guys find anything missing, do not hesitate ... :-) 
*->
*->/Regards
*->Ulf
*->
*->> Would appreciate a quick response
*->> Thanks in advance
*->>  
*->>  Regards, 
*->>  Danny 
*->>  
*->> 
*->> 
*->> 
*->> Thus Said Ulf Hansson On Fri, Mar 02, 2001 at 09:11:36AM +0100 :
*->> *->
*->> *->> -----Original Message-----
*->> *->> From: Daniel Ezekiel [mailto:danny@xxxxxxx.com]
*->> *->> Sent: Friday, March 02, 2001 8:05 AM
*->> *->> To: bluetooth-dev@xxxxxxx.com
*->> *->> Subject: [bluetooth-dev] Security manager implementation
*->> *->> 
*->> *->> 
*->> *->> Hi
*->> *->>  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 
*->> *->
*->> *->http://www.bluetooth.com/developer/whitepaper/whitepaper.asp
*->> *->
*->> *->Regards
*->> *->/Ulf
*->> *->-
*->> *->To unsubscribe from this list: send the line "unsubscribe 
*->> bluetooth-dev" in
*->> *->the body of a message to majordomo@xxxxxxx.com
*->> 
*->> -- 
*->>    _____________________________________________
*->> 
*->>     Daniel D. Ezekiel                                
*->>     E-Mail  : danny@xxxxxxx.com                         
*->>     Fone    : 91-80-5281461  Extn: 3322 
*->> 
*->>     PGP Key : hkp://keys.pgp.com/danny@xxxxxxx.com       
*->>    ______________________________________________
*->> 
*->> 
*->> 
*->-
*->To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
*->the body of a message to majordomo@xxxxxxx.com

-- 
   _____________________________________________

    Daniel D. Ezekiel                                
    E-Mail  : danny@xxxxxxx.com                         
    Fone    : 91-80-5281461  Extn: 3322 

    PGP Key : hkp://keys.pgp.com/danny@xxxxxxx.com       
   ______________________________________________

-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com