From: Radek Rurarz <fotopiper@o2.pl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] PIN helper
Date: Thu, 9 Mar 2006 06:44:24 +0100 [thread overview]
Message-ID: <20060309064424.584539d2.fotopiper@o2.pl> (raw)
In-Reply-To: <20060308221644.GA4516@beta.private.mielke.cc>
On Wed, 8 Mar 2006 17:16:44 -0500
Dave Mielke <dave@mielke.cc> wrote:
> [quoted lines by Radek Rurarz on 2006/03/08 at 23:01 +0100]
>=20
> >Some things I would like to have:
> >1. checking the permissions of the file
>=20
> Do you mean that you'd like it to log via syslog if the permissions
> are unsafe?
That would be nice. But first of all, if the permissions are wrong (the
propper ones set in a config file, or in the script itself) the script
should not use the file and either refuse the connection =3D ERR (and
syslog the error) or fallback to other methods of geting the PIN (if
allowed).
> >2. an option to chose wheather a promp should be used even if there
> >is no pin in the file, possibly to chose another pinhelper if there
> >is no pin (for instance the one for X, if that fails to create a
> >promp).
> >
> >3. In the pins file another 'slot' for the name of the device
> >(not nessesary the one advertised by it, rather to have an idea whot
> >is it)
>=20
> These are good ideas. Thanks. I'll do them.
I'll be greatful :)
My regards.
--=20
Rados=B3aw Rurarz
Warsaw Poland
GG: 7249330
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-03-09 5:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 21:19 [Bluez-devel] PIN helper Radek
2006-03-08 21:40 ` Dave Mielke
2006-03-08 22:01 ` Radek Rurarz
2006-03-08 22:16 ` Dave Mielke
2006-03-09 5:44 ` Radek Rurarz [this message]
2006-03-09 5:55 ` Dave Mielke
2006-03-09 6:06 ` Radek Rurarz
2006-03-09 6:12 ` Dave Mielke
2006-03-09 18:29 ` Radek Rurarz
2006-03-09 19:34 ` Dave Mielke
2006-03-09 21:55 ` Radek Rurarz
2006-03-09 22:04 ` Radek Rurarz
2006-03-10 1:33 ` Dave Mielke
2006-03-10 7:28 ` Radek Rurarz
2006-03-10 13:35 ` Dave Mielke
2006-03-10 18:10 ` Radek Rurarz
2006-03-10 17:25 ` Dave Mielke
2006-03-10 18:13 ` Radek Rurarz
2006-03-10 18:39 ` Dave Mielke
2006-03-10 19:22 ` Radek Rurarz
2006-03-10 20:55 ` Dave Mielke
2006-03-10 22:24 ` Radek Rurarz
2006-03-10 23:04 ` Dave Mielke
2006-03-13 4:08 ` KrAnTi KaMbHaMpAtI
2006-03-10 20:56 ` Dave Mielke
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=20060309064424.584539d2.fotopiper@o2.pl \
--to=fotopiper@o2.pl \
--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;
as well as URLs for NNTP newsgroup(s).