From owner-ssh@clinet.fi Fri May 18 16:48:19 2001 Received: from smtp1.clinet.fi (smtp1.clinet.fi [194.100.2.57]) by hutcs.cs.hut.fi (8.9.3/8.9.3) with ESMTP id QAA21393 for ; Fri, 18 May 2001 16:48:19 +0300 (EET DST) Received: from mail.clinet.fi (mail.clinet.fi [194.100.0.7]) by smtp1.clinet.fi (Postfix) with ESMTP id 9379C2065A; Fri, 18 May 2001 16:48:12 +0300 (EEST) Received: (from majordom@localhost) by mail.clinet.fi (8.9.3/8.9.3) id QAA12727 for ssh-outgoing; Fri, 18 May 2001 16:22:40 +0300 Received: from mailscreen2.btitele.com (mail.btitele.com [198.143.222.251]) by mail.clinet.fi (8.9.3/8.9.3) with SMTP id QAA12721 for ; Fri, 18 May 2001 16:22:37 +0300 Received: From POSTOFFICE.BTITELE.COM (10.1.1.227[10.1.1.227 port:1780]) by mailscreen2.btitele.com Mail essentials (server 2.422) with SMTP id: <400825@mailscreen2.btitele.com> for ; Fri, 18 May 2001 9:21:47 AM -0400 smtpmailfrom Received: by postoffice.btitele.com with Internet Mail Service (5.5.2653.19) id ; Fri, 18 May 2001 09:17:42 -0400 Message-ID: <549AB966B45DD311A58A0000E86CEA8D0CAED55A@postoffice.btitele.com> From: David Edward Shapiro To: "'ssh@clinet.fi'" Subject: FW: dsa key failing to generate Date: Fri, 18 May 2001 09:17:41 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-ssh@clinet.fi Precedence: bulk I still have the problem with generating dsa keys. Can they be generated on another solaris 2.7 system and copied to a different server? I think I tried this and I could not connect using dsa to the system with the dsa key I made on another system,yet I saw a note somewhere saying you could do this. David -----Original Message----- From: David Edward Shapiro [mailto:David.Edward.Shapiro@btitele.com] Sent: Monday, May 07, 2001 4:57 PM To: 'ssh@clinet.fi' Subject: dsa key failing to generate I am trying to install ssh 2.5.2p2 on solaris 2.7 (zlib 1.13 and tcpwrapper7.6) but it fails to generate the dsa key. It cycle between time() and getpid() (saw this with truss) and eventually dies with: time() = 989266013 getpid() = 24365 [24364] time() = 989266013 getpid() = 24365 [24364] time() = 989266014 getpid() = 24365 [24364] Received signal #24, SIGTSTP [default] Received signal #1, SIGHUP [default] siginfo: SIGHUP pid=24314 uid=0 *** process killed *** Another strange thing is that other ssh 2.5.2p2 stations can access with ssh1, but securecrt 3.3b5 does not connnect with ssh1 and shows no error message (just a blank warning box). David