That should work too. It bypasses our security model for Bluetooth and
other network sockets though :)

On Mon, Nov 24, 2008 at 1:09 PM, pavan savoy <[EMAIL PROTECTED]> wrote:
> Ok, Thank you, So If I just do the Android_paranoid_network='N' then,
> everything should go fine. I hope this doesn't break anything else.
>
> Regards,
> Pavan Savoy.
>
> On Mon, Nov 24, 2008 at 12:59 PM, Nick Pelly <[EMAIL PROTECTED]> wrote:
>>
>> hcid immediately drops to UID bluetooth. See android_bluez.c
>>
>> We also have modifications to the kernel so that only processes with
>> root, or gid bt or gid bt_admin can create new Bluetooth sockets for
>> security. Since hcid immeidately drops root you'll need the bt_admin
>> gid.
>>
>> Nick
>>
>> On Mon, Nov 24, 2008 at 12:49 PM, pavan savoy <[EMAIL PROTECTED]>
>> wrote:
>> > Hi,
>> >
>> > I suppose I am having permission problems with the hcid service.
>> > I can do a start hcid, but cannot do a hcid -f /etc/hcid.conf as root.
>> > i.e I
>> > get a Can't open HCI socket: permission denied error.
>> > Why is that ?
>> >
>> > Should I edit the Manifest or something for this ?
>> >
>> > regards,
>> > Pavan Savoy
>
>

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to