[Savannah-cvs] [624] update references of sv_get_authorized_keys

[ineiev]

Revision: 624
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=624
Author:   ineiev
Date:     2023-05-21 08:34:12 -0400 (Sun, 21 May 2023)
Log Message:
-----------
update references of sv_get_authorized_keys

Modified Paths:
--------------
    trunk/sviki/BackEndSetup.mdwn
    trunk/sviki/UserAuthentication.mdwn

Modified: trunk/sviki/BackEndSetup.mdwn
===================================================================
--- trunk/sviki/BackEndSetup.mdwn       2023-05-21 11:49:48 UTC (rev 623)
+++ trunk/sviki/BackEndSetup.mdwn       2023-05-21 12:34:12 UTC (rev 624)
@@ -170,9 +170,7 @@
     ### users' keys when they log with SSH to @vcs.sv.gnu.org .
     ### The users' keys are stored in savane database.
 
-    $ cd /opt/savannah/bin
-    $ export PERL5LIB=/opt/savannah/share/perl/5.18.2
-    $ ./sv_get_authorized_keys agn | cut -b1-40
+    $ /opt/savannah/bin/sv_get_authorized_keys agn | cut -b1-40
     ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvsw+
     ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCe
     ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDf
@@ -192,7 +190,7 @@
 As NON-ROOT user (e.g. agn), run:
 
     cd /opt/savannah/usr/bin
-    ./sv_groups --only-git --debug
+    ./sv_groups --only-git --verbose --dry-run
 
 This will show demonstrate how 'sv_groups' scans the groups
 (=projects) in the savane database, and for each one, checks if the

Modified: trunk/sviki/UserAuthentication.mdwn
===================================================================
--- trunk/sviki/UserAuthentication.mdwn 2023-05-21 11:49:48 UTC (rev 623)
+++ trunk/sviki/UserAuthentication.mdwn 2023-05-21 12:34:12 UTC (rev 624)
@@ -150,7 +150,7 @@
 The file `/etc/ssh/sshd_config` on `download0:` and `vcs0:` servers have the 
line:
 
     ...
-    AuthorizedKeysCommand      /root/bin/sv_get_authorized_keys
+    AuthorizedKeysCommand      /opt/savane/bin/sv_get_authorized_keys
     ...
 
 When users log in to Savannah servers using ssh, they specify the account:
@@ -158,7 +158,7 @@
     git clone agn@git.sv.gnu.org:/srv/git/datamash.git
 
 The user is therefore known, and OpenSSH needs to find user's public keys.
-The `/usr/local/bin/sv_get_authorized_keys` Perl script simply queries
+The `sv_get_authorized_keys` Perl script simply queries
 the ssh public keys of the user (splitting them by `###` delimiter):
 
     ...
@@ -172,7 +172,7 @@
 
 Manually invoking `sv_get_authorized_keys` looks like:
 
-    vcs0:~# /usr/local/bin/sv_get_authorized_keys agn
+    vcs0:~# /opt/savane/bin/sv_get_authorized_keys agn
     ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvs [...]
     ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQ [...]