similar to: portable OpenSSH bugs.

On Tue, 3 Apr 2001, Niels Provos wrote: > Paul, something is broken in your openssh install. Definately. But is it the client or the server? I've sent it to the portable OpenSSH bug address. I'm using OpenSSH 2.5.2p2-1.7 on a RedHat 7.0 with all updates. Sometimes I can login fine, and sometimes I can't. It actually seems to almost alternate,

openssh 2.5.2p2 on Solaris 8 has PAM/cron problems. If I build it with PAM then cron quits working giving "cron audit problem." errors. If I turn PAM off then cron works but I get kicked out of any session where a password is needed (i.e. no .rhosts/.shosts or not using ssh-agent) with the message "Connection closed by IP#". I get through if I have a .rhosts/.shosts or use

I'm trying to connect from OpenSSH clients that are version 2.5.2p2 to several different HP-UX 11.00 machines that are running 2.5.1p1, but cannot. I can, however, connect to a Linux machine running 2.5.1p1 without problem. I get this message from both a Solaris 2.7 (x86) machine and a Solaris 2.6 (SPARC) machine. >From the x86 machine, I get ssh dozer 51 f6 46 8d 9d 98 17 a6 b6 10 79

'scp' returns a zero exit code, even if it fails to perform the desired task. bash-2.03$ scp nonexistent at no.such.domain:some/file .; echo $? ssh: no.such.domain: Name or service not known 0 'ssh' will however return a non zero exit code in a similar situation. bash-2.03$ ssh nonexistent at no.such.domain date; echo $? ssh: no.such.domain: Name or service not known 255

I am trying to resolve an issue with SSH2 version 2.5.2p2 on Solaris 2.6. SSH2, SSH1 and SCP all work fine in and out. The problem is with SFTP. I can SFTP out, but not in. I can't SFTP into itself. After I issue the command, I get a password prompt. After I give the password, the connection closes with an Exit Status 127. There are 3 other system configure the same and everything is

Hi, I am using OpenSSH 2.5.2p2 on Solaris 2.7 (Ultra 10) with 64bit support and have the following problem when connecting with the ssh2 protocol to non-solaris OS: On the client side, I do: /local/work/lysis/bin/slogin -v -2 -p 2222 rs30 On the server side (AIX 4.3), the sshd runs as follows: aix/sbin/sshd -p 2222 -d Full output follows at the end of this mail. The server is compiled with

v1.0.rc22 FC6 x86_64 So, here is my config: protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster at example.com } auth_master_user_separator = * auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot.masterusers master = yes } passdb pam { } userdb passwd { }

I have just seen this, that I thought was an old problem, show up again.. I noticed it when I let a domU stay on DHCP long enough to try to do a renew, then the DHCP server started logging about checksum errors: dhcpd: 5 bad udp checksums in 5 packets DHCP server is 1:9.6.ESV.R4+dfsg-0+lenny1 so newer DHCP releases may contain workaorunds allowing these packets.. Since I had this problem years

Hi, The following discussion was posted to comp.security.ssh however, it seems that my problems may be a bug in SSH. Could someone please indicate whether there is a bug fix, or perhaps whether I should go back a version or so. In summary: - Win98 machine (client) - OpenSSH as packaged with Cygwin tools 1.1.8 (openssh-2.5.2p2-3) - Connecting to a Sun running Solaris. ssh: SSH Secure Shell

http://bugzilla.mindrot.org/show_bug.cgi?id=119 Summary: Occassionally, SSH failed to connect and timeout after 2 hrs! Product: Portable OpenSSH Version: older versions Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

Greetings, I'm running OpenSSH_2.5.2p2, and OpenSSL-0.9.6a, on BSD/OS 4.0. Following the FAQ, I added the following line to my sshd_config in order to enable X11 forwarding: X11Forwarding yes Now openssh is disconnecting my sessions immediately after authentication and login with the following error messages: "error: socket: Protocol not supported" "Disconnecting: Command

Devang Patel wrote: > > On Dec 17, 2007, at 2:01 PM, John Criswell wrote: > >> Devang Patel wrote: >>> >>> On Dec 17, 2007, at 1:47 PM, John Criswell wrote: >>> >>>> Dear Devang Patel, >>>> >>>> In response to your comment on bug 1868, how do I get BottomPass to >>>> requires Pass2 before Pass1? Is it by

Dear Devang Patel, In response to your comment on bug 1868, how do I get BottomPass to requires Pass2 before Pass1? Is it by reversing the order of the calls to AU.addRequired()? -- John T. -- John T. Criswell jcriswel at bigw.org "It's today!" said Piglet. "My favorite day," said Pooh.

Version: OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090601f Platform: RedHat Linux 7.0 and Sun Solaris 2.6 I have the following problem: when I set up port forwarding for HTTP, running Squid at one end as an HTTP proxy and a browser at the other end (Netscape, IE) everything works fine, I can tunnel HTTP requests through OpenSSH but I keep seeing the following error messages that mess up

'Public Key Authentication' works for me. SERVERs: OpenSSH3.3p1 on linux - 2.4.x and 2.2.x kernels CLIENTs: Putty 0.52; OpenSSH 2.5.2p2,3.1p1,3.3p1 - with Public key ! SAMPLE: $ ssh -v SERVER echo 'NO problem to CONNECT' OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f debug1: ...... debug1: Remote protocol version 2.0, remote software version OpenSSH_3.3 debug1:

Hi all, I'm setting up a system where users will only be able to use "sftp" but not "ssh" to connect to the server (http://www.snailbook.com/faq/restricted-scp.auto.html). Here's the setup... Server: OpenSSH 2.5.2p2-1 on RH Linux Client: Commercial SSH 2.4 on Solaris The vendor on the client system creates a key pair and sends it to me. I then add the vendor's

This is debugs seen on server, whose keys are not accepted by the client: debug1: Seeding random number generator debug1: sshd version OpenSSH_2.5.2p2 debug1: load_private_key_autodetect: type 0 RSA1 debug1: read SSH2 private key done: name rsa w/o comment success 1 debug1: load_private_key_autodetect: type 1 RSA debug1: read SSH2 private key done: name dsa w/o comment success 1 debug1:

We use OpenSSH 3.5p1 on an embedded system. OpenSSH is configured to not permit password logins, /etc/ssh/sshd_config: ... PasswordAuthentication no ... At the same time, since there is no console and no way to "log in" other than by ssh, /etc/passwd has an "open" root account: root::0:0:root:/root:/bin/sh nobody:x:65534:65534:nobody:/tmp:/usr/bin/bash Apparently

Am 18.01.2017 um 22:21 schrieb Rowland Penny via samba: > Virtually the same as on Debian 8 and I can assure you it works with > Samba, did you try it ? can you please somehow strip your quotes? the only thing worser the TOFU ("text over, fullquote under") is full quote and a sinlge line of text at bottom

Hi everyone, I have a configuration for a router that load-balances between two ISPs. What happens is that if a source-destination combination is looked up, one of the two gateways will be chosen, and further lookups will stay on that gateway until the chosen combination "stales" out. Web browsing works, ftp works, kazaa and other applications work. ssh on windows (using putty) works.