similar to: [Bug 298] New: sshd fails to set user context, preventing all logins, also setgroups is failing

http://bugzilla.mindrot.org/show_bug.cgi?id=298 ------- Additional Comments From sshbugs at wayne47.com 2002-06-26 11:05 ------- Problem appears to be that setusercontext is being called after a chroot. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=286 Summary: sshd crash on connection Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: updates at

Team - I'm running Solaris 9 and gcc 3.1 on a Blade 1000, named jefferson. I built OpenSSH_3.3. I can use the client to connect out, but cannot use the client to connect to localhost (nor can I use a Linux box with OpenSSH_3.2.3 to connect to it). I *can* use F-Secure 3.0.0 on a Windoze box to get into it. I've tried configurations both with and without privsep enabled but get the same

root at ns2:~# sshd -D -dddd Too high debugging level. root at ns2:~# sshd -D -ddd debug1: sshd version OpenSSH_3.3 debug3: Not a RSA1 key file /usr/local/etc/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug3: Not a RSA1 key file /usr/local/etc/ssh_host_dsa_key. debug1: read PEM private key done: type DSA debug1: private host key: #1 type

http://bugzilla.mindrot.org/show_bug.cgi?id=882 Summary: Scp cannot copy self-referring directories Product: Portable OpenSSH Version: 3.8p1 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy:

Hi; I just attempted to install openssh-3.3p1 on a Sparc box running linux kernel 2.2.14-5.0 However any attempt to connect to the daemon causes a crash. (See below) Given the current security issue, will there be an available option for running the up coming 3.4 release on a Linux 2.2 kernel? Bob ><> ><> ><> ><> ><> ><>

'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:

http://bugzilla.mindrot.org/show_bug.cgi?id=299 Summary: mmap problem with 3.3p1 version Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: colin at

Hi guys, I have a OpenSSH 3.4p1 installation on a SourceMage box, and I am trying to connect to a OpenSSH 3.3p1 installation on a RedHat 7.x box and any other machine. The client fails with a "Host key verification failed." Any other client connects correctly to the RedHat box, and any other server that I try to connect to from the SourceMage box fails with the same error message.

http://bugzilla.mindrot.org/show_bug.cgi?id=297 Summary: sshd version 3.3 incompatible with pre-3.3 clients in ssh1 mode Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

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

Hi, version.h of the 3.3p1 portable release, and of (yesterday's) CVS tree says #define SSH_VERSION "OpenSSH_3.3" and not "OpenSSH_3.3p1". Is this an oversight, or are portable releases not tagged anymore? (I'm asking because I used this to distinguish between the different FreeBSD ports - "openbsd openssh" and "portable", which is harder

Hi there, I've been using rsync for a while to synchronize directories between my windows XP laptop and a redhat linux workstation. However, starting yesterday, rsync started hanging. From what I can tell, rsync completes the transfer and then just hangs rather than exiting. Here are the details: On the client machine (Windows XP): rsync version: 2.5.5, protocol version 26 ssh version:

Hello all, I was running some tests with openssh 3.7.1p2 and I noticed that PermitRootLogin without-password does not work when PAM is enabled. In fact, when PAM is enabled, PermitRootLogin will work as "yes" if " without-password" is used, no matter what kind of authentication is used for root login. Is that a bug, I missed something in the configurations, or expected

Hello. We have a few OS X machines running Jaguar 10.2 that's set to rsync over important files for backup purposes. The rsync was happening without any problems until the last Jaguar security update was installed a few weeks ago or so. Now they are giving the below errors and the rsync does not happen: @ERROR: setgroups failed rsync: connection unexpectedly closed (78 bytes read so far)

Using mysql for authentication. Successful username & password gives: Aug 27 15:10:03 master: Info: Dovecot v2.3.2.1 (0719df592) starting up for imap, pop3 (core dumps disabled) Aug 27 15:10:50 imap-login: Info: Login: user=<jlbrown at bordo.com.au>, method=PLAIN, rip=::1, lip=::1, mpid=24924, secured, session=<E+DEvWN0xcoAAAAAAAAAAAAAAAAAAAAB> Aug 27 15:10:50

On 11.10.2018 09:28, Heiko W. Rupp wrote: > Hello, > > I have recently upgraded to macOS 10.14 (Mojave) and am running into > an issue where one use can no longer log into dovecot via imap. Log shows > > Oct 11 08:10:27 imap(hwr)<12659><YpC/0+133+EAAAAAAAAAAAAAAAAAAAAB>: > Fatal: setgroups(501) failed: Too many extra groups > > and indeed, the user is in 17

On 11.10.2018 10:08, Heiko W. Rupp wrote: > On Thu, Oct 11, 2018 at 09:51:34AM +0300, Aki Tuomi wrote: >>> Looking at the source, I see this is handled in >>> src/lib/restrict-access.c::fix_groups_list(), >>> where above the call to setgroups() a gid_list2 is constructed. I >>> wonder if one could >>> have a config option to prevent adding all those

On Thu, Oct 11, 2018 at 10:55:39AM +0300, Aki Tuomi wrote: > Maybe. Have to see when we can implement it though. It could probably > leverage the min/max_gid setting. Actually that was a great hint. Setting last_valid_gid = 100 in the config and restarting helped. Having a filter-list instead of fixed upper/lower bounds would be more flexible. I guess though that in reality most

I've been trying to get my two Mac OS X computers to sync using rsync 2.5.5. I have one set up as the host with --daemon and the other with a client running. I was encountering an @ERROR: chroot failed error in my messages. I found that the problem lied in a misconfiguration of the rsyncd.conf file. I had tried to specify a POSIX pathway using the quoted foward-slash method. Once I got past