From: Marcel Holtmann <marcel@holtmann.org>
To: Philip Lawatsch <philip@lawatsch.at>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Limit communication to serveral devices
Date: Wed, 25 Aug 2004 16:24:40 +0200 [thread overview]
Message-ID: <1093443880.537.0.camel@pegasus> (raw)
In-Reply-To: <412C9803.6080306@lawatsch.at>
Hi Philip,
> Call me paranoid but I would like to know if there is any way to limit
> all types of communication to just several devices by checking with the
> hardware addresses.
>
> I understand that in principle not being discoverable and the pin
> challenge should help you with being secure but to me this is not enough.
>
> I'm currently running 2 class 1 devices to serve my flat with rfcomm for
> dial in and I for sure do not want anyone besides me to get access to
> these com ports.
>
> Is there anything I can do to tighten security and limit all
> communication to just some devices?
you must change the code of the accept routine in the RFCOMM server
program that you are using.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-08-25 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 13:45 [Bluez-users] Limit communication to serveral devices Philip Lawatsch
2004-08-25 14:24 ` Marcel Holtmann [this message]
2004-08-25 19:50 ` Philip Lawatsch
2004-08-25 20:16 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 8:05 Michael Schmidt
2004-08-26 8:53 ` Philip Lawatsch
2004-08-26 12:10 ` Steven Singer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1093443880.537.0.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=philip@lawatsch.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.