Revision: 565
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=565
Author: ineiev
Date: 2023-02-09 04:11:30 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
update from SavannahServices
Modified Paths:
--------------
trunk/sviki/SshAccess.mdwn
Modified: trunk/sviki/SshAccess.mdwn
===================================================================
--- trunk/sviki/SshAccess.mdwn 2023-02-09 08:32:34 UTC (rev 564)
+++ trunk/sviki/SshAccess.mdwn 2023-02-09 09:11:30 UTC (rev 565)
@@ -410,8 +410,7 @@
is well GNU Savannah, and not a fake website. It is totally
different from your SSH key.
-- **Obsolete**: What about `authorized_keys`? `authorized_keys` is
maintained on the
- server side, at Savannah. This is done automatically, based on the
- public keys you upload to the web interface. (Savannah admin info:
- specifically, in `/etc/ssh/authorized_keys/`USERNAME on the
- subhosts; a cron job `sv_authorized_keys` runs on each vm.)
+- What about `authorized_keys`? Upon attempted
+ login, this user key is checked against the Savannah MySQL database,
+ using the `AuthorizedKeysExec` command defined in
+ `vcs0:/etc/ssh/sshd_config`.
