VesperOS/shadow
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

New upstream version 4.6

Browse Source
This commit is contained in:
Balint Reczey
2019-03-03 23:31:24 +01:00
parent 589f97ade4
commit b0729855e8
673 changed files with 18421 additions and 16992 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/split_groups/01_useradd_split_group/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/02_useradd_no_split_group/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 0
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/03_useradd_split_group_already_split/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/04_useradd_split_group_already_full/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/05_useradd_split_group_already_split_passwd_differ/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/06_useradd_split_group_already_split_GID_differ/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/07_useradd_split_group_already_split_user_in_both_lines/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/08_useradd_no_split_group_already_split/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 0
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/09_groupdel_split_group_already_split/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 2
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############
tests/split_groups/10_groupdel_no_split_group_already_split/config/etc/login.defs
+3 -3
View File
@@ -156,7 +156,7 @@ ERASECHAR 0177
KILLCHAR 025
# 022 is the "historical" value in Debian for UMASK when it was used
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# There is no One True Answer here : each sysadmin must make up their
# mind.
#UMASK 022
@@ -185,7 +185,7 @@ GID_MAX 60000
#
# Max number of login retries if password is bad. This will most likely be
# overriden by PAM, since the default pam_unix module has it's own built
# overridden by PAM, since the default pam_unix module has it's own built
# in of 3 retries. However, this is a safe fallback in case you are using
# an authentication module that does not enforce PAM_MAXTRIES.
#
@@ -274,7 +274,7 @@ MAX_MEMBERS_PER_GROUP 0
# #
# These options are now handled by PAM. Please #
# edit the appropriate file in /etc/pam.d/ to #
# enable the equivelants of them.
# enable the equivalents of them.
#
###############