From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4
Date: Tue, 5 Sep 2006 22:38:15 +0200 [thread overview]
Message-ID: <20060905203814.GA4515@suse.de> (raw)
In-Reply-To: <1157482774.5963.27.camel@localhost>
Hi,
On Tue, Sep 05, 2006 at 08:59:34PM +0200, Marcel Holtmann wrote:
> Hi Stefan,
> =
> > Well, that would mean that i'd have to document /var/lib/bluetooth/*/pi=
ncodes
> > and i'd want to avoid that.
> =
> you should avoid this when possible.
absolutely. This is why i'd rather provide passkey-agent as a band-aid :-)
> > snprintf(default_path, sizeof(default_path),
> > "/org/bluez/passkey_agent_%d", getpid());
> =
> That might do it. Of course every user must start this by hand and it is
> not automated somehow (init script or desktop startup). There can only
Yes. This is only for the "user has installed new openSUSE factory and now
wants to pair his device"-case. And now he even gets a warning that he shou=
ld
not build important parts of his enterprise infrastructure on the availabil=
ity
of passkey-agent :-)
> > Yes. But for the users, there is no way to pair their devices without a
> > passkey agent. And not everybody can use latest bluez-gnome, but might =
still
> > be a valuable tester for bluez-utils :-)
> =
> Let me put it this way. The 3.0 announcement came with a clear warning
> that the PIN helper is dead and we now need a default passkey agent for
> every desktop. It was one reason why I jumped to next major number. I
> don't do this without a serious reason. I provided an example of a
> passkey agent and the Maemo guys implemented a passkey agent for their
> platform, but nobody else seemed to care.
In the KDE case, i think that the kdebluetooth code is pretty much without
an active maintainer. But i have a promising new talent at hand that will
start fixing and bring it up to date :-)
> The passkey agent interface is fully language independent and they could
> have written one in C, C++, C#, Perl, Python, Java, Haskell and every
> language that provides a D-Bus binding. And again, nobody did. Now I
> gave people two examples on how to write a passkey agent. So they either
> do it now or start using GNOME ;)
There is already work being done for kdebluetooth, i have seen the
"prototype". But apparently the existing code is quite - "interesting"
and needs some cleanup before this can go out to the public.
Everything will be fine :-)
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
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 easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-09-05 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060903124043.2028.48247.reportbug@forza>
[not found] ` <1157367160.32195.54.camel@aeonflux.holtmann.net>
[not found] ` <20060904100025.GA17058@esaurito.net>
[not found] ` <1157371912.32195.69.camel@aeonflux.holtmann.net>
2006-09-05 10:32 ` [Bluez-devel] Bug#385857: [Pkg-bluetooth-maintainers] Bug#385857: please upgrade to bluez-utils and bluez-libs 3.4 Filippo Giunchedi
2006-09-05 11:07 ` Bug#385857: " Marcel Holtmann
2006-09-05 16:46 ` Stefan Seyfried
2006-09-05 17:13 ` Marcel Holtmann
2006-09-05 18:15 ` Stefan Seyfried
2006-09-05 18:59 ` Marcel Holtmann
2006-09-05 20:38 ` Stefan Seyfried [this message]
2006-09-05 21:08 ` 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=20060905203814.GA4515@suse.de \
--to=seife@suse.de \
--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