From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12609 invoked by alias); 25 Feb 2003 20:13:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12597 invoked from network); 25 Feb 2003 20:13:53 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 25 Feb 2003 20:13:53 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18nnLg-0008BQ-00; Tue, 25 Feb 2003 16:14:52 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18nlSQ-0002Nk-00; Tue, 25 Feb 2003 15:13:42 -0500 Date: Tue, 25 Feb 2003 20:13:00 -0000 From: Daniel Jacobowitz To: Kris Warkentin Cc: gdb@sources.redhat.com Subject: Re: ssh CVS access from another machine Message-ID: <20030225201341.GA9138@nevyn.them.org> Mail-Followup-To: Kris Warkentin , gdb@sources.redhat.com References: <003101c2dd09$f19df3e0$2a00a8c0@dash> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003101c2dd09$f19df3e0$2a00a8c0@dash> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00537.txt.bz2 On Tue, Feb 25, 2003 at 03:10:29PM -0500, Kris Warkentin wrote: > I'm trying to access the repository from home and not having any luck. It's > probably just my ignorance on the mechanism so if there is a doc I should > read, let me know. > > I had created an account (generating identity.pub, etc.) at work and now I > wanted to work from home. I copied the contents of my $HOME/.ssh directory > to my home machine (this is probably wrong) and then tried connecting. I > keep getting 'permission denied'. I tried removing identity.pub and config > (to get an interactive session) but that claimed "permission denied: > public-key/keyboard-interactive" > > Do I need to have multiple rsa keys on file or am I missing something else? At a guess: try using ssh -1 on the second machine; it may have a newer version of ssh and be trying a different protocol type. Copying the key ought to work. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer