public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Singer <steven.singer@csr.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] DUN lookup on Samsung D500 raises SIGSEGV
Date: Wed, 03 Aug 2005 18:46:10 +0100	[thread overview]
Message-ID: <42F102E2.5060608@csr.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0508031910480.4458-100000@redbean.intranet.gw-instruments.de>

Peter Wippich wrote:
> without realy knowing the internals this looks to me like BlueZ does not
> support 32 Bit UUIDS. It is a little bit unusual to use 32 Bit UUIDs but
> legal. So BlueZ SDP Parser shall support them.

We've been through this before and someone also suggested that the 32 bit
UUIDs were the problem. They're not. The Samsung D-500 DUN SDP record is
incorrect (or at the very least bizarre) and sdptool doesn't do proper
input validation (always a security risk).

An archived copy of the thread starts at:

  http://sourceforge.net/mailarchive/message.php?msg_id=11057683

The correct diagnosis is at:

  http://sourceforge.net/mailarchive/message.php?msg_id=11057684

I suspect sdptool is "knows" that a BluetoothProfileDescriptorList
should be a sequence of sequences and so doesn't validate the input.
Perhaps the way to go is to add a getNextAsSequence call to sdptool
which looks to see if the next element in the stream is a sequence.
If it is, it returns it, if it isn't, it wraps it in a dummy sequence
with an appropriate length and returns that.

	- Steven
-- 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-08-03 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 13:10 [Bluez-devel] DUN lookup on Samsung D500 raises SIGSEGV Pedro Monjo Florit
2005-08-03 17:12 ` Peter Wippich
2005-08-03 17:46   ` Steven Singer [this message]
2005-08-03 18:38     ` Marcel Holtmann
2005-08-03 18:35   ` Marcel Holtmann
2005-08-04  8:11     ` Peter Wippich
2005-08-04  8:28       ` Marcel Holtmann
2005-08-04  8:54         ` Peter Wippich
2005-08-04  9:05           ` 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=42F102E2.5060608@csr.com \
    --to=steven.singer@csr.com \
    --cc=bluez-devel@lists.sourceforge.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