From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Set security level?
Date: Wed, 28 Nov 2007 11:53:31 -0300 [thread overview]
Message-ID: <474D80EB.5070501@aircable.net> (raw)
In-Reply-To: <56C8D22F4B7F104DBE581411F10682E9268FE8@beyondsoft.dyndns.org>
I know, that's because the phone is using security level 0. I want to
know how to set it from the bluez side.
> Most phones don't require pairing when using obex push (not obex ftp). =
>
> -----Urspr=FCngliche Nachricht-----
> Von: bluez-devel-bounces@lists.sourceforge.net [mailto:bluez-devel-bounce=
s@lists.sourceforge.net] Im Auftrag von Manuel Naranjo
> Gesendet: Mittwoch, 28. November 2007 14:22
> An: BlueZ development
> Betreff: [Bluez-devel] Set security level?
>
> Hello everyone,
>
> I'm working on an Open Source Proximity marketing solution. And I need
> to know something, I know that there's a way to send files over obex
> without the need to pair (depending on the phone capabilities off
> course, and user acceptance). I know that this can be used for spamming,
> but that's not my intention.
>
> The question would be, is there any way to change the security level of
> a connection via dbus? I know this has to be handled at a very low
> level, before you can even get the rfcomm connection, and I don't think
> this should be handled for the hole hci device because this would be a
> security issue.
>
> Thanks,
> Manuel
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
> =
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-11-28 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 13:22 [Bluez-devel] Set security level? Manuel Naranjo
2007-11-28 14:39 ` Matthias Becker
2007-11-28 14:53 ` Manuel Naranjo [this message]
2007-11-29 20:22 ` Marcel Holtmann
2007-11-29 20:25 ` Manuel Naranjo
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=474D80EB.5070501@aircable.net \
--to=manuel@aircable.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.