[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-cvs] [444] Amend notes on CVS_RSH
From: |
ineiev |
Subject: |
[Savannah-cvs] [444] Amend notes on CVS_RSH |
Date: |
Thu, 16 Sep 2021 05:04:25 -0400 (EDT) |
Revision: 444
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=444
Author: ineiev
Date: 2021-09-16 05:04:24 -0400 (Thu, 16 Sep 2021)
Log Message:
-----------
Amend notes on CVS_RSH
Modified Paths:
--------------
trunk/sviki/SshAccess.mdwn
Modified: trunk/sviki/SshAccess.mdwn
===================================================================
--- trunk/sviki/SshAccess.mdwn 2021-06-24 08:35:09 UTC (rev 443)
+++ trunk/sviki/SshAccess.mdwn 2021-09-16 09:04:24 UTC (rev 444)
@@ -209,15 +209,23 @@
(Or whatever VC command, if you're not using cvs.)
-- Another reason for rejection as above can be that you failed to
- set the `CVS_RSH` environment variable to `ssh`, as in:
+- Another reason for CVS failure can be that the `CVS_RSH`
+ environment variable isn't set to `ssh`, as in:
export CVS_RSH=ssh # Bourne-compatible shells
setenv CVS_RSH ssh # C shells
Without this, cvs will be trying to use rsh instead of ssh for the
- connection, and rsh is not allowed (it's insecure by design).
+ connection, and rsh is not allowed (it's insecure by design):
+ $ cvs commit -m 2021.08.30.103430
+ cvs commit: Examining .
+ cvs.sv.gnu.org: Connection timed out
+ cvs [commit aborted]: end of file from server (consult above messages
if any)
+
+ This happens when you have the real rsh installed as opposed
+ to having a symbolic link to ssh which is common as of 2020.
+
- Another problem can arise when you are trying to connect from
behind a broken NAT router. During session setup, after the
password has been given, OpenSSH sets the TOS (type of service)
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Savannah-cvs] [444] Amend notes on CVS_RSH,
ineiev <=