linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-devel@lists.sourceforge.net
Subject: [PATCH] Updated man page for hcid.conf
Date: Sat, 17 Sep 2005 22:18:10 +0200	[thread overview]
Message-ID: <1126988290.14893.35.camel@yeti> (raw)

[-- Attachment #1: Type: text/plain, Size: 85 bytes --]

Marcel,

Attached is a patch to update the man page for hcid.conf as well.

Fredrik


[-- Attachment #2: hcid.conf.5-updates.patch --]
[-- Type: text/x-patch, Size: 1087 bytes --]

--- bluez-utils-2.21.orig/hcid/hcid.conf.5	2004-12-25 19:06:00.000000000 +0100
+++ bluez-utils-2.21.new/hcid/hcid.conf.5	2005-09-17 22:15:05.000000000 +0200
@@ -58,11 +58,17 @@
 ERR
 
 .TP 
+\fBdbus_pin_helper\fP
+
+Declaring this parameter enables the D-BUS message bus system for PIN
+requests.
+
+.TP 
 \fBsecurity\fP  none|auto|user
 
 \fInone\fP means the security manager is disabled. \fIauto\fP uses
-local PIN for incoming connections. \fIuser\fP always asks the user
-for a PIN.
+local PIN, by default from /etc/bluetooth/pin, for incoming
+connections. \fIuser\fP always asks the user for a PIN.
 
 .SH "DEVICE SECTION"
 Parameters within a device section with no specifier, the default
@@ -230,5 +236,11 @@
 .I /etc/bluetooth/hcid.conf
 Default location of the global configuration file.
 
+.TP 
+.I /etc/bluetooth/pin
+Default location of local PIN file, used for incoming connections in
+security mode \fIauto\fP. The file contains the PIN code terminated by
+newline.
+
 .SH "AUTHOR"
 This manual page was written by Edouard Lafargue, Fredrik Noring and Maxim Krasnyansky.

             reply	other threads:[~2005-09-17 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 20:18 Fredrik Noring [this message]
2005-09-20 14:56 ` [Bluez-devel] Re: [PATCH] Updated man page for hcid.conf 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=1126988290.14893.35.camel@yeti \
    --to=noring@nocrew.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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).