similar to: openssh password aging/expiration on Solaris 8

Hello I have compiled Openssh3.5 on Solaris 2.6 It works well on 2.6, 2.7 and solaris 8 but on solaris 8 it try to log in /var/adm/wtmp file and it dose not exist. What can I do to fix this. Read something about "build sol" insted of "configure"....but where do i find information about this command (build sol). Mail me on: daniel.d.olsson at telia.se Thanks

Hi, We found that the OpenSSH server code sends it version string as "SSH-1.5_OpenSSH_3.5" to the client during the intial phases of connection establishment. Futher more some clients like telnet client displays this version string on error. Like for example if we typed "Telnet host <> port 22" on a solaris workstation, where the host is a machine which is running

Hi List(s) A customer of mine reported that sftp didn't work for them. It seems to work just fine for me on that system, and after checking into it I noticed that the customer used psftp, while I use sftp from either cygwin or the linux version from openssh. The openssh version of sftp works in all cases, priv-sep on or off. However, the putty psftp breaks as soon as I turn on priv-sep

Here is the user-dependent IdentityFile patch for openssh3.5 (BSD version), which allows private key files to be placed system wide (for all users) in a secure (non-NFS) mounted location. This addresses an important security hole on systems where home directories are NFS mounted, particularly if there are users who use blank passphrases (or when lpd is tunneled through ssh on systems running lpd

Anyone have password aging working in Openldap 2.2.13-7 on Centos? The system continues to prompt for a new password regardless of whether it's been changed or not. Thanks -- Flambeau Inc. Technology Center - Baraboo, WI Email : tblader at flambeau.com Keyserver: http://pgp.mit.edu KeyID: 0x00E9EC2C

Author: jjj Repository: /hg/zfs-crypto/gate Revision: bc396b853096b1dea0d08dc856e6d6b5827d5cf7 Log message: 6311010 pam_passwd_auth can''t deal with old SunOS aging Files: update: usr/src/lib/pam_modules/passwd_auth/passwd_auth.c

Our server is only opened 22 sshd port... We wants our server secuirty is more higher, so decide to password aging policy... Linux command is "chage" is very useful, but openssh3.3 higher version is not effected... [root at radius ~]# chage -l test Minimum: 0 Maximum: 2 Warning: 2 Inactive: 2 Last Change: May 09, 2003 Password Expires: May

Our server is only opened 22 sshd port... We wants our server secuirty is more higher, so decide to password aging policy... Linux command is "chage" is very useful, but openssh3.3 higher version is not effected... [root at radius ~]# chage -l test Minimum: 0 Maximum: 2 Warning: 2 Inactive: 2 Last Change: May 09, 2003 Password Expires: May

I've compiled 3.7.1p2 on AIX 5.1 w/pam compiled in, but not enable in the sshd_config. Also applied Darrens 3.7.1p2 patch25. I am having issues w/password aging when maxage is set to anything >0. i dont believe this function was ever working (at least not in 3.5p1). Can anyone verify this? Thanks, Ryan __________________________________ Do you Yahoo!? Protect your identity with Yahoo!

I've got an old Dell Optiplex (Pentium-II, 1998 Vintage) which is successfully running an X100P card. I'm hoping to upgrade to a TDM400. Has anybody tried running these cards in old Optiplex machines? I'm not particularly worried about horsepower - more about the motherboard having a PCI bus that's able to power up the card... -Ronan

I use dovecot with shadow support and i have a problem with aging password, if the password is ended dovecot continue to log me in... It's possibile to disable login if the password is ended? Hi, Jacopo -- Linux, Windows Xp ed MS-DOS (anche conosciuti come il Bello, il Brutto ed il Cattivo). -- Matt Welsh

Greetings ... A quick question more to confirm a few things reguarding SMB passwords, which I hope might be able to look at for password aging. I saw some discussion on samba-tech list, but nothing conclusive. LM and NT hashs don't have a salt? Do they? ... In other words, a password "password" LM hashed, always comes out as "E52CAC67419A9A224A3B108F3FA6CB6D" not

Samba version 2.999+3.0cvs20020906-1 for Debian Somehow the Samba password is aging and is requiring a reset once a month for a couple of users. I can't see anything in the man pages to indicate that the passwords age, so how is Samba doing it, and how do I stop this behavior? One user is on Windows 2000 and the other on Windows XP. The Windows passwords are not aging and neither are

Hi, I've seen many people complaining winbind can't handle expired Windows AD accounts and doesn't ask to change them. Is it something people can't just configure properly or it is not supported by design? Have anyone had luck getting it working properly? Thanks!

Greetings. I have just upgraded to samba 3.0.25a (from 3.0.24 AFAIR). I have also upgraded schema file in openldap's configuration directory. As I have had some more time I have discovered sambaMaxPwdAge and that it may be read with pdbedit in human readable form. Great :-) But what if I would like to force a user to change her password right at next login? I have tried to set

I have two folders, let's call them Server and Archive. What I want to do is send all the files from server that are older than? say 30 days to archive and delete them from server. OK, no problem. However, I also want to delete any files from Server that already exist on Archive. So let's say on 28-01-2013 I have Server: 23-10-2011 31-12-2012 14-12-2012 17-01-2013 Archive: 23-10-2011

Is password aging/expiration a functional feature in Samba 3? I have compiled and installed the alpha 12 release and while I can set password aging in the account policies via NT's account manager, Samba 3 does not seem to be honoring it. __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com

Ok, I'm rigging myself up a Samba 3 PDC for a variety of Windows clients. Anything from 98 on up to XP and everything in between. For the most part it hasn't been a big deal. I've got a couple of questions I want to run by the list and see if anyone has figured this one out. My first question is about the [profiles] share. Is this share really needed? The documentation never

Compile openssh-3.8p1 with gcc and the following flags --prefix=/tmp/build/sshd --with-ssl-dir=/tmp/build/lib --with-utmpx, no PAM. Everything complies correctly, and I changed sshd_config to use "UseLogin yes" When my client connects (using the newer ssh client too), I do not get the message that my password will expire in xx days, but sshd shows that it is picking up that info (next

I'm looking at the password aging and account lock checks in auth.c:allowed_user(), and specifically their behaviour on HP-UX. First, should this code be ifdef'd away if we're using PAM? Next: /* Check account expiry */ if ((spw->sp_expire > 0) && (days > spw->sp_expire)) return 0; If I lock an account by entering too many incorrect passwords, sp_expire