Advertisement
Guest User

Untitled

a guest
Nov 27th, 2014
216
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.57 KB | None | 0 0
  1. AllowUsers
  2. This keyword can be followed by a list of user name patterns, separated by
  3. spaces. If specified, login is allowed only for user names that match one of
  4. the patterns. Only user names are valid; a numerical user ID is not recog‐
  5. nized. By default, login is allowed for all users. If the pattern takes the
  6. form USER@HOST then USER and HOST are separately checked, restricting logins
  7. to particular users from particular hosts. The allow/deny directives are
  8. processed in the following order: DenyUsers, AllowUsers, DenyGroups, and
  9. finally AllowGroups.
  10.  
  11. See PATTERNS in ssh_config(5) for more information on patterns.
  12.  
  13. PATTERNS
  14. A pattern consists of zero or more non-whitespace characters, ‘*’ (a wildcard that
  15. matches zero or more characters), or ‘?’ (a wildcard that matches exactly one charac‐
  16. ter). For example, to specify a set of declarations for any host in the “.co.uk” set
  17. of domains, the following pattern could be used:
  18.  
  19. Host *.co.uk
  20.  
  21. The following pattern would match any host in the 192.168.0.[0-9] network range:
  22.  
  23. Host 192.168.0.?
  24.  
  25. A pattern-list is a comma-separated list of patterns. Patterns within pattern-lists
  26. may be negated by preceding them with an exclamation mark (‘!’). For example, to
  27. allow a key to be used from anywhere within an organisation except from the “dialup”
  28. pool, the following entry (in authorized_keys) could be used:
  29.  
  30. from="!*.dialup.example.com,*.example.com"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement