summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDamien Miller <djm@cvs.openbsd.org>2012-04-12 02:43:56 +0000
committerDamien Miller <djm@cvs.openbsd.org>2012-04-12 02:43:56 +0000
commit7d06e61d1ef69a6ce67fca8bfcec4eb20ec259a0 (patch)
tree21db8fdbe7251e98d7615c790f4ec39089b61f6c
parent1a6e66dda01b4e1ea7d87b8b08d0cd3c8b847206 (diff)
mention AuthorizedPrincipalsFile=none default
-rw-r--r--usr.bin/ssh/sshd_config4
-rw-r--r--usr.bin/ssh/sshd_config.56
2 files changed, 7 insertions, 3 deletions
diff --git a/usr.bin/ssh/sshd_config b/usr.bin/ssh/sshd_config
index 6b5083888e8..74f0b13756d 100644
--- a/usr.bin/ssh/sshd_config
+++ b/usr.bin/ssh/sshd_config
@@ -1,4 +1,4 @@
-# $OpenBSD: sshd_config,v 1.85 2012/04/12 02:42:32 djm Exp $
+# $OpenBSD: sshd_config,v 1.86 2012/04/12 02:43:55 djm Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
@@ -47,6 +47,8 @@
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile .ssh/authorized_keys
+#AuthorizedPrincipalsFile none
+
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
diff --git a/usr.bin/ssh/sshd_config.5 b/usr.bin/ssh/sshd_config.5
index 1d56d7234f5..a5045d1e083 100644
--- a/usr.bin/ssh/sshd_config.5
+++ b/usr.bin/ssh/sshd_config.5
@@ -33,7 +33,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $OpenBSD: sshd_config.5,v 1.137 2012/04/12 02:42:32 djm Exp $
+.\" $OpenBSD: sshd_config.5,v 1.138 2012/04/12 02:43:55 djm Exp $
.Dd $Mdocdate: April 12 2012 $
.Dt SSHD_CONFIG 5
.Os
@@ -198,7 +198,9 @@ After expansion,
is taken to be an absolute path or one relative to the user's home
directory.
.Pp
-The default is not to use a principals file \(en in this case, the username
+The default is
+.Dq none ,
+i.e. not to use a principals file \(en in this case, the username
of the user must appear in a certificate's principals list for it to be
accepted.
Note that