public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Artem Bizyukov <bizyukov@gmail.com>
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Re[2]: It may be a bug in hcidump
Date: Tue, 20 Sep 2005 17:58:55 +0200	[thread overview]
Message-ID: <1127231935.5168.86.camel@localhost.localdomain> (raw)
In-Reply-To: <e98637f4050920082942759d50@mail.gmail.com>

Hi Artem,

> I`m save dump with -w option.  hcidump fail only with -V option. I`m
> tested this tool on the same system but use glibc-2.3.2. The result is
> the same.

the problem is easy, because it is not a valid HCI frame and hcidump is
not doing any robustness checks.

< HCI Command: PIN Code Request Reply (0x01|0x000d) plen 4
  0000: 29 00 00 00                                       )...

A PIN code reply must include the BD_ADDR and not the connection handle.
Install bluez-utils-2.21 (or from CVS) and try again.

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-09-20 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 15:29 Re[2]: It may be a bug in hcidump Artem Bizyukov
2005-09-20 15:58 ` Marcel Holtmann [this message]
     [not found]   ` <e98637f405092102346d904d4a@mail.gmail.com>
2005-09-21 13:28     ` [Bluez-devel] Fwd: " Artem Bizyukov

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=1127231935.5168.86.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=bizyukov@gmail.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