Mitigate Salt issue #29004, fixes "expire" on *BSD

Unreasonable values for 'expire' (after 9999-12-31
on Linux, before 1975-01-01 on *BSD) get divided
by 86400 (number of seconds in a day) when too big
or multiplied by 86400 when too small.

Tested on CentOS 6 (Salt 2015.5.5) and FreeBSD 10.2
(Salt 2015.8.0) with following values:

  - 24854 (2038-01-18 in days since epoch)
  - 157766400 (1975-01-01 00:00:00 UTC in seconds since epoch)
  - 3313526400 (2075-01-01 00:00:00 UTC in seconds since epoch)
  - 16000 (2013-10-22 in days since epoch)
  - 18000 (2019-04-14 in days since epoch)

(Sponsored by av.tu-berlin.de and fokus.fraunhofer.de)

Don't add sudo group by default.

update pillar.example to include uid

in an attempt to save others from digging into the source (to confirm this detail)

Adds 'empty_password' statement for states.user.present (issue #97)

changing visudo checking to avoid wrong reporting when launched in a test mode

Fix minor bug for ssh known_hosts management with salt >= 2015.5.5.

This version complains that "argument port can not be used in
conjunction with argument hash_hostname", so add hash_hostname
to the fields we handle in the formula so we can override it
if needed.

Added ability to specify room number, home phone, and work phone

Add possibility to manage the user's global git configuration.

Add possibility to manage ssh's known_hosts file.

Manage arbitrary user files

Add ssh_auth_pillar option.

iteritems() -> items, break some way to long lines

sry, could not resist.

This formula doesn't really require the sudo group (unless
there are actually users in that group). Moreover, on FreeBSD
the 'admin' group would be wheel and not sudo.

Add support for .profile file

Add missing ssh_config test to create .ssh folder

This reverts commit a0392693e3.

Do not escape value of `enforce_password`

Fixes #82.

Rework ssh_keys_pillar-related states

Adding support for the enforce_password option.

This will allow users change their passwords after the initial setting in Salt.

the user's .ssh directory should be created if ssh_auth_file is supplied

SSH key pairs deployed via the user's ssh_keys_pillar dict aren't
handled the same as the user's ssh_keys, e.g., file ownership and
permissions aren't specified, and the keying material gets copied
directly into the SLS file.  This change rewrites the two templated
file.managed states to behave as follows:

  - set the files' owner to be the user

  - set the files' group to be the user's primary group

  - for the public key, set the mode to 644 (u=rw,go=r)

  - for the private key, set the mode to 600 (u=rw,g=)

  - pull the files' contents directly from pillar

Some smaller changes.

Signed-off-by: René Jochum <rene@jochums.at>

Signed-off-by: René Jochum <rene@jochums.at>

Conflicts:
	pillar.example
	users/init.sls

Signed-off-by: René Jochum <rene@jochums.at>

Add sudo_rules syntax examples for rules with colons

fix permission of GA config file