[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [524] minor refinements
From: |
ineiev |
Subject: |
[Savannah-cvs] [524] minor refinements |
Date: |
Thu, 2 Feb 2023 06:11:14 -0500 (EST) |
Revision: 524
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=524
Author: ineiev
Date: 2023-02-02 06:11:12 -0500 (Thu, 02 Feb 2023)
Log Message:
-----------
minor refinements
Modified Paths:
--------------
trunk/sviki/AccessToCVSROOT.mdwn
trunk/sviki/CvsRsyncWriteAccess.mdwn
Modified: trunk/sviki/AccessToCVSROOT.mdwn
===================================================================
--- trunk/sviki/AccessToCVSROOT.mdwn 2023-02-02 11:01:50 UTC (rev 523)
+++ trunk/sviki/AccessToCVSROOT.mdwn 2023-02-02 11:11:12 UTC (rev 524)
@@ -1,3 +1,5 @@
+# Access to CVSROOT
+
We do not provide write access to CVSROOT in the CVS repositories because:
- CVSROOT permits server-side *hooks*, which means essentially giving
@@ -12,7 +14,7 @@
CVSROOT/config and CVSROOT/passwd. This is a security issue that we
want to avoid.
-### Question: SF provides write access to CVSROOT, how comes you don't?
+## Question: SF provides write access to CVSROOT, how comes you don't?
**A:** Note that you still do not have direct shell access
at SF. You can bypass this restriction through CVSROOT hooks but
@@ -22,11 +24,11 @@
commit as another system user that way. We would be interested in more
information on that point.
-### Question: Can I read (not write) the CVSROOT/ contents?
+## Question: Can I read (not write) the CVSROOT/?
I tried to get it via CVS:
- cvs -d :ext:me@cvs.savannah.nongnu.org:/cvsroot/myproject co CVSROOT
+ cvs -d :ext:me@cvs.savannah.nongnu.org:/cvsroot/my_group co CVSROOT
and I get an empty CVSROOT dir, this must be a new security feature?
@@ -36,4 +38,4 @@
However you still can read it using:
- rsync -av cvs.sv.nongnu.org::sources/myproject/CVSROOT .
+ rsync -av cvs.sv.nongnu.org::sources/my_group/CVSROOT .
Modified: trunk/sviki/CvsRsyncWriteAccess.mdwn
===================================================================
--- trunk/sviki/CvsRsyncWriteAccess.mdwn 2023-02-02 11:01:50 UTC (rev
523)
+++ trunk/sviki/CvsRsyncWriteAccess.mdwn 2023-02-02 11:11:12 UTC (rev
524)
@@ -1,3 +1,5 @@
+# Rsync access to CVS repositories
+
Since we provide rsync read-only access to the CVS repository, one may
expect to also get write access. But we do not provide direct write
access to the CVS repository for several reasons:
@@ -16,7 +18,7 @@
could also be used to trick CVS users into
executing malicious hooks under their username.
-So providing cvs write access is currently something we refuse.
+So providing CVS write access is currently something we refuse.
Users actually need write access in few cases:
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [524] minor refinements,
ineiev <=