[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(no subject)

From: root
Subject: (no subject)
Date: Mon, 13 Aug 2001 05:07:48 -0400

>From address@hidden  Tue Feb  6 09:11:09 2001
>Return-Path: <address@hidden>
Received: from ( [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Tue, 6 Feb 2001 09:11:07 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14Pvgv-0001t9-00; Mon, 05 Feb 2001 19:09:05 -0500
Received: from ([])
        by with smtp (Exim 3.16 #1 (Debian))
        id 14Pvgb-0001sq-00
        for <address@hidden>; Mon, 05 Feb 2001 19:08:45 -0500
Received: from [] (
        by with esmtp (Exim 3.12 #1)
        id 14Pvga-0001ab-00; Mon, 05 Feb 2001 17:08:44 -0700
From: "Louis D. Zirkel III" <address@hidden>
X-Sender:  <address@hidden>
To: "David H. Thornley" <address@hidden>
cc: address@hidden
Subject: Re: Secure remote CVS
In-Reply-To: <address@hidden>
Message-ID: <address@hidden>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <>,
List-Id: Announcements and discussions for the CVS version control system 
List-Unsubscribe: <>,
List-Archive: <>
Date: Mon, 5 Feb 2001 17:08:42 -0700 (MST)
Status: O
Content-Length: 1692
Lines: 39

On Mon, 5 Feb 2001, David H. Thornley wrote:

> Now we'd like to be able to use CVS over considerably longer
> distances, securely.
> I recommended setting CVS_RSH=ssh, and was told that the users
> then had to type in their password for every file being transferred,
> and that is more typing than they're willing to put up with.

I don't believe you're prompted after every file.  It's been awhile since
I've used not used ssh-agent to rid myself entirely of having to enter
passwords, but back when I did I think I typed it in once and then the
whole session was one connection.  On the other hand... (read below)

> We're not about to use straight pserver, for security reasons.
> There has got to be a way to log into a remote server securely,
> but I don't know enough about the networking involved.
> Any pointers?

I personally use the ssh-agent that comes with most command line ssh
clients (I know PuTTY has a version as well although I've not tried it
yet).  Basically once you have it running you use ssh-add to add your
private key that SSH has created for you (it'll prompt you for the
passphrase) and then by placing your public key on the server you're
logging into it can negotiate the connection using the halves of the key.
The process is a bit more involved than that, but if this sounds feasible
I'd be more than happy to help you out with the particulars.  Let me know.

 Louis Zirkel III (address@hidden)             System Admin/Programmer
 "We're living on the Edge of the Century"                           -- Styx

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]