[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: SSHD AllowUsers not limiting users anymore

Hi Chris,

I'm not aware of anything special in my PAM configuration, I think It is still using the default configs.

user1 is a complete different user than any other, It has its unique user id.
If a create a brand new user, the same problem happens.

I could say I'm using the correct /etc/ssh/sshd_config because other changes to the file are read.
To be sure, as you can see at my last e-mail, I passed the -f  command line option to run sshd.

The DenyUsers option is not working as well. I tried it with user1 and it does not block the user.

Below follow my /etc/pam.d/sshd, if you need any other file, please, let me know.

Thanks again for your help.

# PAM configuration for the Secure Shell service

# Standard Un*x authentication.
@include common-auth

# Disallow non-root logins when /etc/nologin exists.
account    required     pam_nologin.so

# Uncomment and edit /etc/security/access.conf if you need to set complex
# access limits that are hard to express in sshd_config.
# account  required     pam_access.so

# Standard Un*x authorization.
@include common-account

# SELinux needs to be the first session rule.  This ensures that any
# lingering context has been cleared.  Without this it is possible that a
# module could execute code in the wrong domain.
session [success=ok ignore=ignore module_unknown=ignore default=bad]        pam_selinux.so close

# Set the loginuid process attribute.
session    required     pam_loginuid.so

# Create a new session keyring.
session    optional     pam_keyinit.so force revoke

# Standard Un*x session setup and teardown.
@include common-session

# Print the message of the day upon successful login.
# This includes a dynamically generated part from /run/motd.dynamic
# and a static (admin-editable) part from /etc/motd.
session    optional     pam_motd.so  motd=/run/motd.dynamic
session    optional     pam_motd.so noupdate

# Print the status of the user's mailbox upon successful login.
session    optional     pam_mail.so standard noenv # [1]

# Set up user limits from /etc/security/limits.conf.
session    required     pam_limits.so

# Read environment variables from /etc/environment and
# /etc/security/pam_env.conf.
session    required     pam_env.so # [1]
# In Debian 4.0 (etch), locale-related environment variables were moved to
# /etc/default/locale, so read that as well.
session    required     pam_env.so user_readenv=1 envfile=/etc/default/locale

# SELinux needs to intervene at login time to ensure that the process starts
# in the proper default security context.  Only sessions which are intended
# to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad]        pam_selinux.so open

# Standard Un*x password updating.
@include common-password

On Thu, Nov 12, 2015 at 12:34 PM, Christoph Anton Mitterer <calestyo@scientia.net> wrote:
On Wed, 2015-11-11 at 20:20 -0200, Paulo Roberto wrote:
> The option AllowUsers of /etc/ssh/sshd_config stopped working.
I did a small check, and it still works here, as expected... anything
special with your PAM? Are you sure that you checked on the right hosts
with the right sshd_config in place? Or could user1 be a synonym to the
allowed one (i.e. same UID)?)


Reply to: