Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.
User-specific subconfiguration files are read when the client has stated the username it is trying to log in as. At this point, the server will obtain additional information about the user: does the user exist, what is the user's UID, and what groups the user belongs to. With this information, the server can read the user-specific configuration files specified with UserSpecificConfig in the main configuration file. The syntax is the following:
UserSpecificConfig pattern subconfig-file
You can use patterns of the following form:
where user is matched with the username and UID, group is matched with the user's primary and secondary groups, both group name and GID, and host is matched as described under AllowHosts on the sshd2_subconfig man page (Appendix sshd2 subconfig).
For example, the following would match any user in group "sftp" connecting from company.com:
Example 1: The following matches to users from ssh.com who have two-character usernames or the username sjl, and who belong to the group wheel.