similar to: [Bug 633] Password authentication fails in HP-UX trusted mode due to DISABLE_SHADOW

Dear developers, The HPUX 10.20 trusted system hack doesn't work yet as intended. I have adapted the auth-passwd.c file to make it work. Please find a context diff file attached to this file. This diff is against the latest OpenSSH 2.2.0p1 released Sept 2, 2000. Also on HPUX 10.20, xauth is not found at the standard location. Perhaps this standard location could be changed automagically

I have used SSHD from openssh-3.7.1p1 on HP-UX 11:11. It works correctly and the entry in the logfile is: Sep 24 07:01:20 garm sshd[6625]: Accepted password for japs from 192.38.97.131 port 2463 Next I have upgraded to openssh-3.7.1p2 and restarted SSHD. It does not accept the password any more and the entries in the logfile are: Sep 24 12:21:38 garm sshd[19542]: User japs not allowed because

http://bugzilla.mindrot.org/show_bug.cgi?id=423 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |627 nThis| | Status|NEW |ASSIGNED ------- Additional

maybe this is a silly question ;-) But why is it possible to login on a machine with a locked account (passwd -l ) via pubkey-authentication (authorized_keys) ? I use OpenSSH3.01p1on Solaris8 with PAM support so I thought this should not happen. If this is the normal behaviour and built in intentionally what would be the easiest way to lock an account without deleting the users authorized_keys ?

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

Hi Damien, I noticed you merged a couple of ifdefs in the fix for bug #442. The cvs comment says "Fix Bug #442 for PAM case". The code is now roughly: #if !defined(USE_PAM) && defined(HAVE_SHADOW_H) && \ !defined(DISABLE_SHADOW) && defined(HAS_SHADOW_EXPIRE) spw = getspnam(pw->pw_name); passwd = spw->sp_pwdp; #else passwd =

Hi. I have found a error of openssh-2.1.1p2 port on systems with a mixture of shadowed and non-shadowed passwords. I reported a same type of error to Mr. Miller when openssh-1.2.1pre23 was released. On our systems, our local machines have shadowed /etc/passwd (and /etc/shadow) and our NIS server distributes non-shadowed password of general users. We have to use

Hi All. I noticed that xcrypt.c now has some variable declarations after code within a block (for some sets of #ifdef's). Won't that choke some compilers? Should it do something like the attached? -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually

How can I tell if option "with-acl-support" is compiled in Solaris smbd? Here's the output using ldd: bash-2.05$ ldd /usr/local/samba/sbin/smbd libldap.so.2 => /usr/lib/libldap.so.2 liblber.so.2 => /usr/lib/liblber.so.2 libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 libkrb5.so.3 => /usr/lib/libkrb5.so.3 libk5crypto.so.3

Tried to upgrade our Samba 2.2.8a domain controller (Solaris 8) to Samba 3.0.2a. Compiled using gcc 3.3.2, linked to libiconv-1.8, popt-1.7 and cups-1.1.20. I shut down the Samba 2.2.8a. Removed everything in var/locks. Did a "make install" to install 3.0.2a, then restarted Samba. My smb.conf is basically the same as 2.2.8a with "domain admin group" removed. When I stared

http://bugzilla.mindrot.org/show_bug.cgi?id=647 Summary: Setting "UsePAM no" in sshd_config gives error if not config'ed w/ --with-pam Product: Portable OpenSSH Version: -current Platform: Sparc OS/Version: SunOS Status: NEW Severity: minor Priority: P4 Component: sshd

Hello All, We have been successfully using PAM_LDAP authentication with OpenSSH-3.6 on our HP-UX 11.11. When OpenSSH-3.7.1p2 is installed [with Darrens' password expiry patch 26], and when Shadow password bundle is installed on the system, our ssh authentication failed. Even, when the source is compiled without Darren's patch, the same bahaviour is seen and there is no success. When

OpenSSH 3.0 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. This release contains many portability bug-fixes (listed in the ChangeLog) as well as several new features (listed below). We would like to thank the

Dear Dovecote devotees, I have been going through dovecot configuration for the first time. I am not an experienced systems administrator so I had to do a left turn to read up about PAM while doing all the configuration for my new webmail service. I found that the writing in the dovecot documentation about PAM to be rather misleading in at least one aspect. The documentation I am specifically

Hi! as I just noted, after scp the connection does not shut down properly. When I do a "scp file targethost:path", on targethost a "sshd" process is left running. I do use --with-default-path="/usr/local/openssh/bin:/usr/bin:/usr/local/bin" to assure, that the corrensponding openssh-scp is used. It also seems, that normal sessions are not always closed properly.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I built Dovecot (0.99.5) from Ports on FreeBSD 5.0. The mail client (Kmail) cannot login and it complains that authentication process died. The only thing in the logs is: Feb 2 18:13:01 karo imap-login: Disconnected [client-ip] I tried also passwd authentication method, but its symptoms are the very same. My configure can be found at

Hello all, First off, i''m talking about a SXDE build 89. Sorry if that was discussed here before, but i did not find anything related on the archives, and i think is a "weird" issue... If i try to remove a specific file, i got: # rm file1 rm: file1: No such file or directory # rm -rf dir2 rm: Unable to remove directory dir2: Directory not empty Take a look: ------- cut

Hi all, I see that the premade binaries for Samba on Solaris, even recent versions, have ADS support not compiled in. I see more ad domains than nt4 domains these days, so I am going to compile it myself with ads on. I want to ask the experienced if there are any gotchas with ads Samba on Solaris, or something about Solaris that makes ads Samba support difficult. Thanks Jason

I'm testing both sunfreeware and official sun (sfw) samba on Solaris 10. For some reason since yesterday, the smbd process just "hangs" at the start. No log is generated on server side Where smbd is started, I can't find any open port on 139 or 145 My OS is Solaris 10 # uname -a SunOS labo2 5.10 Generic_142900-13 sun4v sparc SUNW,SPARC-Enterprise-T5120 #

Greetings, I have compiled OpenSSH-3.6.1p2 on SCO 3.2v4.2 and the following problem occurs: I am unable to login as root using when strictmode is set to yes. output of debug: Failed none for root from 192.168.1.1 port 1199 ssh2 debug1: userauth-request for user root service ssh-connection method publickey debug1: attempt 1 failures 1 debug2: input_userauth_request: try method publickey debug1: