puppet module for yrutschle/sslh, uses sslh-fork
If applicable, this section should have a brief description of the technology the module integrates with and what that integration enables. This section should answer the questions: "What does this module do?" and "Why would I use it?"
If your module has a range of functionality (installation, configuration, management, etc.) this is the time to mention it.
- A list of files, packages, services, or operations that the module will alter, impact, or execute on the system it's installed on.
- This is a great place to stick any warnings.
- Can be in list or paragraph form.
This module requires pluginsync enabled
class { 'sslh':
listen_port => '444',
}
sslh::protocol { 'ssh':
host => '127.0.0.1',
port => '22',
}[root@centos7 sslh]# curl -I https://10.0.2.15:444 --insecure
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Mon, 08 Jan 2018 17:26:18 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: http://systemadmin.es
[root@centos7 sslh]# ssh -p 444 [email protected]
The authenticity of host '[10.0.2.15]:444 ([10.0.2.15]:444)' can't be established.
ECDSA key fingerprint is SHA256:2pWcmnQ4P38EUSSXNp89uG0um/K01bz/mWMJC3TMj2M.
ECDSA key fingerprint is MD5:24:23:14:32:58:14:91:76:55:91:20:87:e3:dc:30:c7.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[10.0.2.15]:444' (ECDSA) to the list of known hosts.
[email protected]'s password:
Last login: Mon Jan 8 13:32:38 2018 from 10.0.2.2
Welcome to your Vagrant-built virtual machine.
[vagrant@centos7 ~]$ logout
Connection to 10.0.2.15 closed.
[root@centos7 sslh]#
Put the classes, types, and resources for customizing, configuring, and doing the fancy stuff with your module here.
Here, list the classes, types, providers, facts, etc contained in your module. This section should include all of the under-the-hood workings of your module so people know what the module is touching on their system but don't need to mess with things. (We are working on automating this section!)
This is where you list OS compatibility, version compatibility, etc.
We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature
- create RPMs for it: https://github.com/repoforge/rpms/blob/master/specs/sslh/sslh.spec
- create PPA for debian based distros
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Added some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request