public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Ubuntu edgy + Keyboard + dbus + security mode 3
Date: Mon, 13 Nov 2006 19:29:07 +0100	[thread overview]
Message-ID: <1163442547.26272.66.camel@localhost> (raw)
In-Reply-To: <200611131907.13234.Kilian.Lackhove@web.de>

Hi Kilian,

> I added the --encrypt option to my /etc/defaults/bluetooth and restarted the 
> deamon while running "bluez-pun --dbus". After a few seconds my keyboard 
> worked again and hcitool con showed 
> 
> ACL XX:XX:XX:XX:XX:XX handle 42 state 1 lm MASTER AUTH ENCRYPT
> 
> But even though everything seemed to have worked fine, I wasnt asked for a 
> pin... So my Question: Is everything really alright (and secure) now?

yes it is. However you might wanna consider call "hcitool key ..." to
establish a new link key if you don't know where the old one came from.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-11-13 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.19693.1163411759.8777.bluez-users@lists.sourceforge.net>
2006-11-13 18:07 ` [Bluez-users] Ubuntu edgy + Keyboard + dbus + security mode 3 kilian
2006-11-13 18:29   ` Marcel Holtmann [this message]
2006-11-07 17:57 kilian
2006-11-13  8:21 ` 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=1163442547.26272.66.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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