public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Susanne Goldammer <susanne.goldammer@gmx.de>
To: Iain Hibbert <plunky@rya-online.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Make bluetoothd start w/o SDP Server
Date: Thu, 12 Nov 2009 11:47:16 +0100	[thread overview]
Message-ID: <4AFBE7B4.5010709@gmx.de> (raw)
In-Reply-To: <1258020990.988942.3883.nullmailer@galant.ukfsn.org>

Hi Iain,

thanks for you reply!

I think you missunderstood a bit.

First, yes it is a handsfree kit.

But: We don't want to provide our own proprietary SDP Stuff. This makes
no sense cause we want to be compatible to other BT-devices supporting
interesting BT-profiles like HFP etc. And also I was talking about the
SDP-Server side means i want to sent responses.

What we want to do is robustness testing, means our test SDP Server
listens for a SDP request (which can come from headunit but also from
any other sdp capable mobile phone or whatsoever to request the services
provided by the communication partner). We have some predefined correct
answers for some of the SDP requests, but before sending the one fitting
for the received request we fuzz the answer, means we make it invalid
regarding length etc. pp.

Then we send this answer to the bt device under test and look if it
becomes instable cause e.g. of missing checks in SDP implementation.

There are thousands of tools like scapy doing such things for tcp/ip
stack. We are doing similar tests for Bluetooth communication ( L2CAP,
Obex and finally  SDP, too). Here a correct and primarily robust
implementation needs to be ensured through testing. The best way to do
so is to confront the DuT with such invalid packets.

I hope this help to understand a bit better.

  reply	other threads:[~2009-11-12 10:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 14:00 Make bluetoothd start w/o SDP Server Susanne Goldammer
2009-11-10 14:05 ` Bastien Nocera
2009-11-10 14:19   ` Susanne Goldammer
2009-11-12  9:21     ` Susanne Goldammer
2009-11-12 10:16       ` Iain Hibbert
2009-11-12 10:47         ` Susanne Goldammer [this message]
2009-11-12 12:13       ` Stefan Seyfried
2009-11-12 12:55         ` Susanne Goldammer
2009-11-12 13:08           ` Stefan Seyfried
2009-11-12 14:13             ` Susanne Goldammer
2009-11-12 14:57               ` Bastien Nocera
2009-11-12 15:16                 ` Susanne Goldammer
2009-11-13 11:33                   ` Johan Hedberg
2009-11-13 11:58                     ` Marcel Holtmann
2009-11-13 12:33                       ` Johan Hedberg
2009-11-13 12:36                       ` Susanne Goldammer

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=4AFBE7B4.5010709@gmx.de \
    --to=susanne.goldammer@gmx.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=plunky@rya-online.net \
    /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