Hi,
I would like to hear opinions on handling of default outgoing pin/passkey in
hcid. It is my understanding that there is no way to actually set a default
outgoing pin from /var/lib/bluetooth/<sba>/pincodes. The only way to set it
is through the dbus interface, right?
Would be a patch to read default outgoing pincode from pincodes suitable?
Right now in debian I've implemented a (suboptimal) solution like pincodes but
with a modified passkey-agent, reading the pincode from stdin (so it doesn't
show up in ps) and using --default. See also
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378850
thanks,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
To be learned in an art&C, the Theory is sufficient; to be a master of
it, both the Theory and practice are requisite.
-- Charles Hutton
Hi Filippo,
> > the idea of a default PIN for outgoing connections is actually kinda
> > stupid. You don't wanna do this on a system with input capabilities. And
> > so far we never had a default PIN for outgoing connections.
>
> I was thinking more of a "fallback" pin, also I don't see how it is stupid to do
> have a default outgoing pin, it is not obvious whether you have input
> capabilities. Do you mind expanding on this? I would like to understand your
> point better.
the use of /var/lib/bluetooth/<bdaddr>/pincodes is kinda problematic,
because these will overwrite the passkey agent. This feature was only
added for development purpose.
We don't wanna have a fallback PIN and you might wanna ask yourself for
what it is really useful. Having a default PIN is only useful when we
have no input capability and this is for the passkey agent to decide. It
is even a security risk to make the hcid provide a default PIN.
> > Check the bluez-gnome CVS repository. It now contains a fully
> > replacement for the bluez-pin that works with the new passkey agent
> > interface of hcid. It is only based on GTK and the D-Bus GLib bindings
> > and works pretty well so far.
>
> thanks! I was just looking for a replacement, is it released somewhere or just
> onto cvs?
Hopefully in a few minutes.
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-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hello Marcel,
On Sun, Aug 20, 2006 at 04:24:53PM +0200, Marcel Holtmann wrote:
> the idea of a default PIN for outgoing connections is actually kinda
> stupid. You don't wanna do this on a system with input capabilities. And
> so far we never had a default PIN for outgoing connections.
I was thinking more of a "fallback" pin, also I don't see how it is stupid to do
have a default outgoing pin, it is not obvious whether you have input
capabilities. Do you mind expanding on this? I would like to understand your
point better.
> Check the bluez-gnome CVS repository. It now contains a fully
> replacement for the bluez-pin that works with the new passkey agent
> interface of hcid. It is only based on GTK and the D-Bus GLib bindings
> and works pretty well so far.
thanks! I was just looking for a replacement, is it released somewhere or just
onto cvs?
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
UNIX IS user friendly, it is just selective who his friends are.
Hi Filippo,
> I would like to hear opinions on handling of default outgoing pin/passkey in
> hcid. It is my understanding that there is no way to actually set a default
> outgoing pin from /var/lib/bluetooth/<sba>/pincodes. The only way to set it
> is through the dbus interface, right?
> Would be a patch to read default outgoing pincode from pincodes suitable?
>
> Right now in debian I've implemented a (suboptimal) solution like pincodes but
> with a modified passkey-agent, reading the pincode from stdin (so it doesn't
> show up in ps) and using --default. See also
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378850
the idea of a default PIN for outgoing connections is actually kinda
stupid. You don't wanna do this on a system with input capabilities. And
so far we never had a default PIN for outgoing connections.
Check the bluez-gnome CVS repository. It now contains a fully
replacement for the bluez-pin that works with the new passkey agent
interface of hcid. It is only based on GTK and the D-Bus GLib bindings
and works pretty well so far.
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-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel