[Savannah-cvs] [622] update AuthorizedKeysExec -> AuthorizedKeysCommand

[ineiev]

Revision: 622
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=622
Author:   ineiev
Date:     2023-05-20 16:31:30 -0400 (Sat, 20 May 2023)
Log Message:
-----------
update AuthorizedKeysExec -> AuthorizedKeysCommand

Modified Paths:
--------------
    trunk/sviki/SavannahArchitecture.mdwn
    trunk/sviki/SavannahServices.mdwn
    trunk/sviki/SshAccess.mdwn
    trunk/sviki/UserAuthentication.mdwn

Modified: trunk/sviki/SavannahArchitecture.mdwn
===================================================================
--- trunk/sviki/SavannahArchitecture.mdwn       2023-05-19 17:26:15 UTC (rev 
621)
+++ trunk/sviki/SavannahArchitecture.mdwn       2023-05-20 20:31:30 UTC (rev 
622)
@@ -83,7 +83,7 @@
 
 Alone among the Savannah hosts, it allows ssh from everywhere since that
 is part of VC access, and has a custom sshd_config directive
-`AuthorizedKeysExec` to look up ssh keys in the mysql database.
+`AuthorizedKeysCommand` to look up ssh keys in the mysql database.
 
 Users themselves are authenticated in `/etc/nsswitch.conf` with a
 `mysql` module (`libnss-mysql`), also directly against the mysql

Modified: trunk/sviki/SavannahServices.mdwn
===================================================================
--- trunk/sviki/SavannahServices.mdwn   2023-05-19 17:26:15 UTC (rev 621)
+++ trunk/sviki/SavannahServices.mdwn   2023-05-20 20:31:30 UTC (rev 622)
@@ -59,7 +59,7 @@
     of a group.  Before using ssh, the Savannah user must upload a
     public ssh key through the Savannah web interface. Upon attempted
     login, this user key is checked against the Savannah MySQL database,
-    using the `AuthorizedKeysExec` command defined in
+    using the `AuthorizedKeysCommand` command defined in
     `vcs0:/etc/ssh/sshd_config`.  The user must also be a member of the
     given group.
 

Modified: trunk/sviki/SshAccess.mdwn
===================================================================
--- trunk/sviki/SshAccess.mdwn  2023-05-19 17:26:15 UTC (rev 621)
+++ trunk/sviki/SshAccess.mdwn  2023-05-20 20:31:30 UTC (rev 622)
@@ -412,5 +412,5 @@
 
 -   What about `authorized_keys`?  Upon attempted
     login, this user key is checked against the Savannah MySQL database,
-    using the `AuthorizedKeysExec` command defined in
+    using the `AuthorizedKeysCommand` command defined in
     `vcs0:/etc/ssh/sshd_config`.

Modified: trunk/sviki/UserAuthentication.mdwn
===================================================================
--- trunk/sviki/UserAuthentication.mdwn 2023-05-19 17:26:15 UTC (rev 621)
+++ trunk/sviki/UserAuthentication.mdwn 2023-05-20 20:31:30 UTC (rev 622)
@@ -99,7 +99,7 @@
 * Unix user management, using
   [nsswitch](http://en.wikipedia.org/wiki/Name_Service_Switch) and
   [libnss-mysql](http://libnss-mysql.sourceforge.net/).
-* ssh key authentication, using the custom `AuthorizedKeysExec` option.
+* ssh key authentication, using the custom `AuthorizedKeysCommand` option.
 
 ### nsswitch and libnss-mysql