From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] authentification, encryption, and secure connection for rfcomm
Date: Sun, 24 Dec 2006 14:49:42 +0100 [thread overview]
Message-ID: <1166968182.15485.10.camel@violet> (raw)
In-Reply-To: <457403C1.7010801@palmsource.com>
Hi Frederic,
> This patch adds command line options to rfcomm (--auth, --encrypt,
> --secure, --master) as in pand. It also updates the man page.
you actually forgot one close(sk) in the error path and the manual page
changes are screwed up, but besides that patch is fine. I fixed this and
committed it.
Regards
Marcel
-------------------------------------------------------------------------
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:[~2006-12-24 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 11:17 [Bluez-devel] [PATCH] authentification, encryption, and secure connection for rfcomm Frédéric DALLEAU
2006-12-24 13:49 ` Marcel Holtmann [this message]
2006-12-24 14:00 ` I have acquired the Core Spec 2.1,can I develop it and patch to bluez kernel? 高 迎宾
2006-12-24 14:34 ` [Bluez-devel] I have acquired the Core Spec 2.1, can " 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=1166968182.15485.10.camel@violet \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.