similar to: Problem with ssh-keyscan: no hostkey alg

Hi, If I enable "UseLogin" under AIX, I get the following message upon login: /dev/pts/2: 3004-004 You must "exec" login from the lowest login shell. The manpage states: "In order to preserve the integrity of the system, only one session at a time is allowed to be logged in to a port. This means that the login command entered from the shell prompt cannot succeed,

I upgraded from OpenSSH_3.0.2p1 to OpenSSH 3.4p1. Starting SSHD or ssh-keygen I'm getting the "PRNG is not seeded". I have verified that prngd is running and "egc.pl /var/spool/prngd/pool get" runs just fine reporting 32800 bits of entropy. My platform is Solaris 8 (sparc) and I downloaded binaries from www.sunfreeware.com. My guess is the build of OpenSSH 3.4.p1 is

http://bugzilla.mindrot.org/show_bug.cgi?id=334 ------- Additional Comments From gray.openssh at mailnull.com 2002-12-06 08:58 ------- I will second this. It seems to just hang after a while even though both the server and the client are configured with KeepAlive enabled. It also looks to both sides like the connection is still open. The forwarded ports are still in netstat output but

http://bugzilla.mindrot.org/show_bug.cgi?id=165 ------- Additional Comments From markus at openbsd.org 2002-03-17 04:31 ------- never seen this. what does sshd -ddd say? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hi , I just recently installed OpenSSH_3.0.2p1 on a HP-UX box. The ssh works fine but the sftp is not. There is a firewall in between both the machine. Only SSH port is allowed from the source host to the destination machine. ssh works fine across the firewall. Below is the log. Thanks in advance . ~~~~~~~~~~~~~~~~~~~~~~~~~~~` <ixos2:/home/smorrx> sftp spdns1 Connecting to spdns1... smorrx

I'm getting core dumps from sshd when logging in using password authentication (using a public key works just fine). The core dump occurs just after entering a password--whether that password is correct or not. It only happens on this one machine. I've tried recompiling the entire setup--zlib, openssl & openssh--and the crash still occurs. It doesn't look like the putty-failure

http://bugzilla.mindrot.org/show_bug.cgi?id=88 ------- Additional Comments From markus at openbsd.org 2002-01-31 23:01 ------- this is an installation error on the target host, see: scp: warning: Executing scp1 compatibility. scp: FATAL: Executing ssh1 in compatibility mode failed (Check that scp1 is in your PATH). ------- You are receiving this mail because: ------- You are the assignee

http://bugzilla.mindrot.org/show_bug.cgi?id=109 ------- Additional Comments From stevesk at pobox.com 2002-03-31 05:06 ------- i'm not sure. can someone dup and debug this? can you still dup with 3.1p1? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

I?ve been tearing my hair out trying to get a Polycom phone (behind a NAT) to register to an * box behind a Cisco SIP ALG. With known good credentials configured on the phone and in *, I get 403 Bad Auth when trying to register. If I put the phone onto the same LAN as * it works fine without changing any authentication parameters whatsoever. If I make the secret blank (null) on the phone and *,

Has anyone here used Asterisk inside a WatchGuard firewall, talking via the WatchGuard SIP Application Layer Gateway to an outside SIP service? I have a customer doing just that, and I am 100% convinced there is a bug in the ALG regarding the media port number it inserts into the SDP when it rewrites it. However, either they or WatchGuard will not accept there is a bug, despite my very detailed

Hi, Has anyone seen this behavior before: - Set winbind separator = + - Start winbind, start samba - cannot authenticate users - change winbind separator = "+" - Restart samba - Authentication works okay for several days - somehow after several days, the separator gets changed to ", i.e. the double quote, at which point it no longer authenticates users okay. jeff

Hi All. While working on something I noticed core dumps from sshd. They don't seem to be related to what I was working on. It's from the process forked to run the shell. Just after the fork, fatal_remove_all_cleanups() is called, which looks like: fatal_remove_all_cleanups(void) { struct fatal_cleanup *cu, *next_cu; for (cu = fatal_cleanups; cu; cu = next_cu) {

===== Ladies/Gents, "ssh-keyscan.c" can't be linked statically against "libssh.a". You end up with `fatal()' being doubly defined. The patch below deletes the new "ssh-keyscan.c:fatal()" function and and restores the "ssh-keyscan.c:fatal_callback()" function with modifi- cations. The problem that both attempt to alleviate is the setting of the

FYI, I managed to install Version OpenSSH_3.0.2p1 on BSDI 3.0. we needed this for an old Gauntlet Firewall. I received an the following error during make install (cd scard && make DESTDIR= install) make: don't know how to make ./Ssh.bin. Stop *** Error code 2 I edited the scard/Makefile.in file and changed install: $(srcdir)/Ssh.bin to install: Ssh.bin Then I made a distclean and

The above version of OpenSSH seems to work fine most of the time, but when I connect to one server in particular I get a very odd looking login prompt: pts/0::mugz!xm[~] ssh -l mugz <host-name-omitted> otp-md5 414 cr6003 ext S/Key Password: otp-md5 265 cr4395 ext S/Key Password: otp-md5 332 cr9989 ext S/Key Password: scripter at crimelords.org's password: I enter my password 3 times in

Long post.. sorry. Ok.. I've got three systems, all running openssh-3.0.2p1. As a matter of fact, they were installed from the same built tree, so I know they are the same. Here's the deal. I've got three systems, call them source1, source2 and target. All are HP-UX 11.0 systems installed from the same tree. Source1 and source2 both have thier root rsa pub keys in target's

http://bugzilla.mindrot.org/show_bug.cgi?id=130 Summary: segfault on connect / Red Hat 6.1 w/OpenSSL 0.9.6c Product: Portable OpenSSH Version: 3.0.2p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=281 Summary: unable to authorize with local shadow password Product: Portable OpenSSH Version: -current Platform: MIPS OS/Version: IRIX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

This is a copy of the bug report I sent debian. Package: ssh Version: 1:3.0.2p1-9 Severity: important I want to be able to login between two hosts without entering passwords. ssh-keygen -t dsa * Copy key to other machine cat id_dsa.pub >> .ssh/authorized_keys chmod 600 .ssh/authorized_keys Trouble is that the originating host appears unable to parse its own keys. This is the

Hi, Folks ... Apologies in advance for the length of this message, but I wanted to be thorough, and provide as much info as I could. I'm trying to figure out a problem in trusted-host authentication using AIX hosts as clients, and a Sun host as the server; either I'm missing something real obvious, or there might be a bug somewhere in some piece of software involved here. -- All of