From: jago25_98 <jago25_98@bluebottle.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Reason to not enable encryption
Date: Tue, 28 Dec 2004 12:03:25 -0600 [thread overview]
Message-ID: <1104257005.41d19fedcd4db@bluebottle.com> (raw)
I seem to remember someone saying something like "Don't enable
encryption if you dual boot" but searched the list and could see why.
Maybe there was another reason to not use encryption
Am I mistaken?
Need to know because we have a new app born yesterday and it could
become encryption only:
http://www.symbianos.org/yabbse/index.php?board=2;action=display;threadid=7;start=15
Thanks for jogging my memory
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-12-28 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 18:03 jago25_98 [this message]
2004-12-29 10:31 ` [Bluez-users] Reason to not enable encryption 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=1104257005.41d19fedcd4db@bluebottle.com \
--to=jago25_98@bluebottle.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