public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Shane Volpe" <shanevolpe@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] PAN security questions
Date: Wed, 12 Dec 2007 12:31:22 -0500	[thread overview]
Message-ID: <8c7950360712120931u1177fbf2jdd0fbff1d24dea51@mail.gmail.com> (raw)
In-Reply-To: <1197474566.5644.12.camel@aeonflux>

Marcel,
The paraphrase exchange is unencrypted correct?  So I would really
need to come up with some method of security   as it would be easy to
get the password by sniffing.  I guess this is probably not a big
issue as I could use a gpg key or ssh style key and require some
encrypted ack message sent with gpg or ssh and if it is not encrypted
with the right key then just boot the connection.  I would be
interested in hearing how others handle it.   The only way this would
fail is if someone leaked one of the private keys.
Regards,
Shane

On Dec 12, 2007 10:49 AM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Shane,
>
> > PAND MAN file lists the following options regarding security:
> > --encrypt -E
> >     Enable encryption
> > --secure -S
> >     Secure connection
> >
> > The PAND howto (http://bluez.sourceforge.net/contrib/HOWTO-PAN)
> > explains --encrypt as follows:
> >      "activates BT security (authentication and encryption)"
> >
> > so then what does the option --secure do?
>
> the --encrypt does authentication and then encrypt the link. With the
> --secure you do the authentication, then encrypt the link and then make
> sure the link key will be re-generated. It is an extra step of
> protection since the link key itself has no expiration date.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>



-- 
Registered Linux User: #293401

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-12-12 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 13:08 [Bluez-users] PAN security questions Shane Volpe
2007-12-12 15:49 ` Marcel Holtmann
2007-12-12 17:31   ` Shane Volpe [this message]

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=8c7950360712120931u1177fbf2jdd0fbff1d24dea51@mail.gmail.com \
    --to=shanevolpe@gmail.com \
    --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