From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] randomizer for passkey-agent
Date: Fri, 26 Oct 2007 13:14:06 -0600 [thread overview]
Message-ID: <d89ddf300710261214w6b6d8de4v328e7bada8a2f778@mail.gmail.com> (raw)
In-Reply-To: <1193422039.6117.3.camel@egore912.egore.lan>
Christoph
Your passkey agent could also send its key over dbus by itself. This
goes beyond the original purpose of the bluez example agent, so
instead of posting a diff, I suggest you post the whole thing as a
separate example.
Brad
On 10/26/07, Christoph Brill <egore@gmx.de> wrote:
> Hi
>
> the use case is quite simple. Imagin a headless system that is doing
> bonding via a deamon. The idea is to show a random passkey on a display
> and enable the mobile user to authenitcate using this passkey. I know
> that the passkey-agent is more a "proof of concept" version, but if it
> would generate random keys and if there was a dbus interface to the last
> generated key it would be pretty helpful. At least for me :-)
>
> If you dislike the idea I will split of a bugfix patch of the original
> one patch I sent that should be applied.
>
>
> Am Freitag, den 26.10.2007, 00:52 +0200 schrieb Marcel Holtmann:
> > Hi,
> >
> > > I wanted a passkey-agent that does not always use the same passkey so it can run in daemon mode and provide passkeys. This is an attempt to implement this functionality.
> >
> > you have to explain the use case for this one. The passkey-agent.c is
> > only an example on how to write a passkey agent. The GNOME and KDE
> > desktops provide their own ones that open input dialogs.
> >
> > Regards
> >
> > Marcel
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Bluez-devel mailing list
> > Bluez-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-26 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 13:07 [Bluez-devel] [PATCH] randomizer for passkey-agent eGore
2007-10-23 14:30 ` eGore
2007-10-25 22:52 ` Marcel Holtmann
2007-10-26 18:07 ` Christoph Brill
2007-10-26 19:14 ` Brad Midgley [this message]
2007-10-27 10:31 ` 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=d89ddf300710261214w6b6d8de4v328e7bada8a2f778@mail.gmail.com \
--to=bmidgley@gmail.com \
--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