From: Philip Lawatsch <philip@lawatsch.at>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Limit communication to serveral devices
Date: Wed, 25 Aug 2004 21:50:50 +0200 [thread overview]
Message-ID: <412CED9A.2070405@lawatsch.at> (raw)
In-Reply-To: <1093443880.537.0.camel@pegasus>
Marcel Holtmann wrote:
> you must change the code of the accept routine in the RFCOMM server
> program that you are using.
This is not quite what I want. I'd like to limit this at lowest layer
possible. Actually I'm starting to wonder that there seems to be
_nothing_ to that, which, at least I think so, poses a potential
security risk.
kind regards Philip
next prev parent reply other threads:[~2004-08-25 19:50 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
2004-08-25 19:50 ` Philip Lawatsch [this message]
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=412CED9A.2070405@lawatsch.at \
--to=philip@lawatsch.at \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox