| Age | Commit message (Collapse) | Author |
|---|
|
Currently ssh_authorized_key has some logic about $user being false or
'', but it sets its value to default to 'root'.
So, in order to use the name as the user's name, one has to clear the
user parameter, which is totally redundant.
Since it is sometimes useful to publish multiple keys for a user, the
$user parameter is useful.
To make using ssh_authorized_key for one-key normal users simpler, make
$user default to being empty (which will use $name as the user name).
'root' can always be specified either via the name or by the $user
paramter.
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
|
|
When one uses the $name to define the user that should receive an SSH
key, setting $user to a negative value, ssh_authorized_key currently
creates the authorized_keys file under /home/.ssh/authorized_keys
Fix this by changing ${user} to ${real_user} in the key's path.
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
|
|
When the os of a client is not one of those that use a specialized
class, (e.g. FreeBSD) the inclusion is currently broken: it tries to
include sshd::default which does not exist.
Change this to include sshd::base instead.
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
|
|
option, even though it is listed in the man page, and commented out in the default config file. I filed a bug with debian (#607238)
|
|
the defaults when not specified
|
|
should be 'check_ssh_port'
|
|
|
|
checks and the pre-requirements
|
|
use 'include sshd::debian', then none of the variables are set, and you
will fail to parse the templates
|
|
internal nagios_service name)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit d4fba70a51eeb253b0155f378ce7735df9479cd4.
|
|
|
|
and instead allow for a version change through an if variable. thanks ng!
|
|
|
|
if we are to have the possibility of potentially overriding the version number it must be done in the base class
|
|
installed by providing the variable $sshd_ensure_version, which defaults to the previous value of present when not specified
|
|
sshd_head_additional_options and one called sshd_tail_additional_options.
the first puts the value at the beginning of the file, and the second at
the end.
This is necessary due to some option ordering requiring things to be
before others
|
|
|
|
Conflicts:
manifests/init.pp
Conflict due to indentation formatting differences
|
|
also export the key based on ip address, removing all warnings
|
|
http://projects.reductivelabs.com/issues/show/1799#note-1
|
|
note that this removes the user => root default
|
|
git-svn-id: https://svn/ipuppet/trunk/modules/sshd@2674 d66ca3ae-40d7-4aa7-90d4-87d79ca94279
|
|
git-svn-id: https://svn/ipuppet/trunk/modules/sshd@2672 d66ca3ae-40d7-4aa7-90d4-87d79ca94279
|
|
/etc/init.d/ssh, which means that name needs to be set to 'ssh', and
pattern needs to be set to 'sshd', and then we set the hassstatus and
hasrestart depending on the lsbdistcodename
|
|
or lenny
|
|
$debian_version is detected,
etch does not have a ssh restart option in the initscript, but lenny does
|
|
is different from the vim
mode, then there is a difference between these two editor's formatting that needs to be resolved
|
|
|
|
preferable because a stop/start operation can leave sshd broken
because the stop wont stop before the start is run. On the next puppet
run ssh will be brought back up, but its a hair-raising few minutes
while you wonder what happened
|
|
|
|
git-svn-id: https://svn/ipuppet/trunk/modules/sshd@2527 d66ca3ae-40d7-4aa7-90d4-87d79ca94279
|
|
git-svn-id: https://svn/ipuppet/trunk/modules/sshd@2317 d66ca3ae-40d7-4aa7-90d4-87d79ca94279
|
|
|
|
git-svn-id: https://svn/ipuppet/trunk/modules/sshd@2272 d66ca3ae-40d7-4aa7-90d4-87d79ca94279
|
