From: "Claudio Takahasi" <cktakahasi@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] intercept new authentication events
Date: Thu, 5 Apr 2007 15:11:34 -0300 [thread overview]
Message-ID: <e1effdeb0704051111x2a26674bx866114aad1bf6f0@mail.gmail.com> (raw)
In-Reply-To: <BAY107-F11C9029CAA2F0071A01144D8650@phx.gbl>
On 4/5/07, Adolfo Bulfoni <iaquintovski@hotmail.com> wrote:
> Hi Marcel
> thanks for your quick reply.
>
> I've checked the passkey-agent util program in /bluez-utils/daemon/ and if
> I try running it, an error message comes up saying there is already a
> passkey agent running on my PC.
> How can I intercept the events sent by this agent? What are the functions
> that need to be called to get the output events from it?
> A "dirty" workaround for my app might be to tail the /var/log/syslog file,
> where the pin_code_request event is logged, together with the remote device
> address. But I'd prefer a cleaner solution.
> Thanks in advance,
> regards
>
> Adolfo
>
Hi Adolfo,
You can develop your own passkey agent. Here is a brief description
how the passkey agent works:
http://wiki.bluez.org/wiki/Security
BR,
Claudio
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-04-05 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 15:07 [Bluez-devel] intercept new authentication events Adolfo Bulfoni
2007-04-05 18:11 ` Claudio Takahasi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 8:05 Adolfo Bulfoni
2007-04-05 9:29 ` 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=e1effdeb0704051111x2a26674bx866114aad1bf6f0@mail.gmail.com \
--to=cktakahasi@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