On Wed, 2 Feb 2005, Eric Vought, Technical Director wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Satish Balay wrote: > | On Wed, 2 Feb 2005, Eric Vought, Technical Director wrote: > | > | > |>Symptoms: > |>sshd rejects all users but one (my account) with "*user* rejected > |>because not in AllowUsers". > | > | > | Maybe not releated - but I thought I'd sugest anyway.. > | > | Once I had problem with adding new users with > | 'system-config-users'. However I could add with 'adduser' - but ssh > | whouldn't accept the passwd. > | > | The thing that resolved this issue for me was running > | 'system-config-securitylevel' - in the 'Selinux' tab, disabling > | Selinux - and then re-enabling it again. > | > | Satish > | > That's interesting ... it may be related. Does SELinux cache the inodes > of configuration files? In other words, if I used an editor which does a > create-and-rename for saving files, would sshd be rendered incapable of > reading its own configuration? I think it was more of - due bad attributes (related to selinux) some files were not getting modified (or read correctly). Don't know how I landed in that bad state though.. It could just be one of the many kernel oops (resulting in hard reboots) I've had due to APM not working well with FC3 kernels. Satish
