[Savannah-cvs] [564] retitle

[ineiev]

Revision: 564
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=564
Author:   ineiev
Date:     2023-02-09 03:32:34 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
retitle

Modified Paths:
--------------
    trunk/sviki/ShellAccess.mdwn

Modified: trunk/sviki/ShellAccess.mdwn
===================================================================
--- trunk/sviki/ShellAccess.mdwn        2023-02-09 08:25:14 UTC (rev 563)
+++ trunk/sviki/ShellAccess.mdwn        2023-02-09 08:32:34 UTC (rev 564)
@@ -1,6 +1,7 @@
-Shell access in general
------------------------
+# Shell access
 
+## In general
+
 Savannah does not provide shell accounts for users, since running
 arbitrary commands is far too large an attack vector.  We do use the
 Unix login mechanism and [[SshAccess]] but only certain commands can be
@@ -21,10 +22,8 @@
 it is not a good idea to use it (plus we'd have to patch the CVS
 validation).
 
+## As root, for Savannah workers
 
-Shell access (as root) for Savannah workers
--------------------------------------------
-
 For those working on Savannah itself (support requests, development,
 etc.), shell and root access may be needed.  (It is not needed to handle
 new project submissions, and it's a good idea to do those for a while
@@ -56,10 +55,8 @@
 root@mgt0.savannah.gnu.org; see [[ListServer]] for tasks that this is
 needed for.
 
+## As separate user, for Savannah workers
 
-Shell access (as separate user) for Savannah workers
-----------------------------------------------------
-
 Some sv workers like to have personal accounts on the servers.  The best
 approach for this is to have it be completely separate from normal
 user-level Savannah access.  Here was the process for `luca` in April