public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Cc: marcel@holtman.org
Subject: Re: [Bluez-users] Security
Date: Wed, 24 Nov 2004 15:45:28 +0100	[thread overview]
Message-ID: <1101307528.27351.110.camel@pegasus> (raw)
In-Reply-To: <BAY12-F113FC2675619229A94FF908AB80@phx.gbl>

Hi,

> Does BlueZ support Bluetooth Security define in white paper (attachment)?

the whitepaper is not attached and actually you shouldn't do that. It is
enough to point to a web address. But again, be more specific. You can't
expect me to answer such general questions in details. If you want a
simple yes or no answer then say that and I assume that this answer will
be no. The reason is that mostly in every whitepaper or specification
there are some stupid things that makes no sense and thus they are not
supported.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-11-24 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 14:12 [Bluez-users] Security salvatore olgato
2004-11-24 14:45 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-06 14:56 salvatore olgato
2004-12-06 15:19 ` Marcel Holtmann

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=1101307528.27351.110.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtman.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