similar to: [Bug 332] Authentication failures after updating to 3.4.p1

http://bugzilla.mindrot.org/show_bug.cgi?id=332 Summary: Authentication failures after updating to 3.4.p1 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

Has ANYONE been able to verify that Rhosts authentication works with 3.4.p1? Does it work with other SSHv2 implementations? Anybody tried it on a RedHat 7.3 system? Also, I'm curious about this code I found in sshd.c: /* * Check that the connection comes from a privileged port. * Rhosts-Authentication only makes sense from priviledged * programs. Of course, if

Folks, I have installed openssh-3.1.p1 and 3.4.p1 successfully int the past. When I tried to install 3.6.p1 it would not start. The init script created an error message to the affect the it could not find *ELF*. I the tried to reinstall 3.4.p1. It's startup said Error 255 .../sshd .. bailing. I then installed Solaris patch for /dev/random and reinstalled 3.4.p1... I got error .... sshd:

Hi, I am still having difficulties in logging in as a non root user. I have installed 3.4.p1. I am logging in from a Linux box that has been upgraded to 3.3p1 and experience no problems in loggin in to other linux boxes, root or non-root. Output from ./configure OpenSSH has been configured with the following options: User binaries: /usr/local/bin System

http://bugzilla.mindrot.org/show_bug.cgi?id=423 ------- Additional Comments From michael_steffens at hp.com 2002-11-02 02:40 ------- Created an attachment (id=162) --> (http://bugzilla.mindrot.org/attachment.cgi?id=162&action=view) Patch: Workaround for pw change in privsep mode (3.5.p1) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are

http://bugzilla.mindrot.org/show_bug.cgi?id=308 Summary: openssh 3.4 won't install or run on Solaris 8, on an Ultra 10 Sparc station Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: critical Priority: P1 Component: Build

Hi, Has anyone on this list tested out the new SE P1 phones ( http://www.uncrate.com/men/gear/cell-phones/sony-ericsson-p1/). It says it supports VOIP, wonder if it is working with asterisk. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070517/467cbea1/attachment.htm

Installed using pkd_add or ports BIND-9.6.0-P1 working fine. 1.But seems can't run under chroot well: ---------------------------------------------------------- Jan 27 13:54:08 ns named[36447]: starting BIND 9.6.0-P1 -c named.conf -t /var/named -u bind Jan 27 13:54:08 ns named[36447]: built with '--localstatedir=/var' '--disable-linux-caps'

http://bugzilla.mindrot.org/show_bug.cgi?id=423 ------- Additional Comments From stevesk at pobox.com 2003-01-02 11:52 ------- regarding log() clash, shouldn't the HP libsec log() be static or renamed or ? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

https://bugzilla.mindrot.org/show_bug.cgi?id=2199 Bug ID: 2199 Summary: "Too many authentication failures for root" does not log IP Product: Portable OpenSSH Version: 6.4p1 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

Hello, over the last few days I've been attempting to compile openssh-3.4p1 on a HP j5000 (hpux 10.20) but have run into some problems. I had found the paper from Kevin Steves and have been following his suggested steps. Perl, zlib, prngd, tcp_wrappers and openssl all compiled more or less as he described. The configure script runs without protest but make gets hung up in

We have AIX 4.3.3 ML09 and AIX 5.1 ML01 I have narrowed the problem down, it is nothing to do with uni/multiprocessor machines. Both rsync 2.3.1 compiled by Bull in an installp and a gcc compiled version of 2.4.5 ( by me ) both have exactly the same problem with SSH 3.1.p1 and both DONT have the problem with SSH 2.9.9p1 - so I assume this is something highly specific to SSH 3.1.1.p1 Hope this

Hi, Is FIPS 140-2 patch for openssh 6.3.p1 available somewhere or do I have to make one using http://www.openssl.com/export/openssh/openssh-6.0p1.fips-revised.patch ? Regards, Manish

Hello, I have been using FreeBSD-7.0STABLE with BIND-9.4.2 ( i guess, forget to check before upgrade) up to 2008-01-26 (yesterday). But after upgrade FreeBSD-7.0STABLE-->FreeBSD-7.1STABLE everything goes wrong. 1.BIND can't start anymore and giving me following message at /var/log/messages: . . . Jan 27 12:30:20 ns kernel: ad4: 152587MB <WDC WD1600AAJS-75PSA0 05.06H05> at

http://bugzilla.mindrot.org/show_bug.cgi?id=423 ------- Additional Comments From djm at mindrot.org 2003-03-10 12:06 ------- The patch looks good, but the only thing that makes me wary is the use of signals for IPC. Would it not be possible to do the chauthtok call earlier? E.g. after the call to do_pam_session() in do_exec_pty()? ------- You are receiving this mail because: ------- You

hi, i want to setup DNS server on centos 5.0, and find the preinstalled version is bind.x86_64 30:9.3.3-7.el5 , and bind.x86_64 30:9.3.3-9.0.1.el5 in the updates repository. but i need to upgrade bind to version 9.3.4-P1 to prevent from any known security bugs is there any way i can do ? thanks, Bell

Hello, As i still have issue i wonder if anyone using this version of openssl ? OpenSSL 0.9.7e-p1 I still cannot make puppet accept Certificate on freeBSD6 with this openssl version. I got the famous error 7 at 1 depth lookup:certificate signature failure and i havent find a way to get around that :( -- Cordialement, Ghislain _______________________________________________

Hello! Today I've found, downloaded and compiled openssh-2.2.0-p1. It basically worked, except that users other than root were not allowed to login. My system is a Linux-2.4.0-test7 with glibc-2.1.3. No PAM is installed/used. It uses MD5 passwords and shadow with account expiration feature. In handling of the latter, a probable bug was found. In auth.c, allowed_user(), there is a code at

Hi, Im using OpenSSH 4.0 p1 linked with zlib version less then 1.2.2 in a number of systems. These are all production systems where I can't upgrade the service. I have a question that if I disable the compression by setting "compression no" in sshd_config, will I be able to overcome the Buffer overflow vulnerability in zlib. I just glanced through the code and it seems sshd is

hi, i think that sftp-server should work fine, even if there are no 64 bit integers, just try 32 bit and panic if the top bit's are set... -------------- next part -------------- An embedded message was scrubbed... From: Brian Candler <B.Candler at pobox.com> Subject: Re: compatibility problem between openssh2.5.1 p1 or p2 and ssf Date: Sun, 4 Mar 2001 21:28:28 +0000 Size: 2221 Url: