What all should go into the next debian packet?

[ftasnetamot]

Hello,

this discussion should collect things, which should go to the next debian packet. My idea is, that sslh users contribute with things from their daily experience. Hopefully we can motivate the debian maintainer, to give some wishes, what he likes to see, what could make his life easier (and hopefully will bring some more updates).
Furthermore sslh users could contribute the one or other pull request, as from my current perspective documentation is currently a bigger point. This looks like something, more of us could do together.

From my perspective, the current sys-v init-script needs a good rework:

• with a restart it kills all current sessions (at least for the sslh-fork implementation), but this is not really needed.
  deleting two lines will make your life happier.
• it has a reload-function implemented, which sends a HUP-signal to sslh. But sslh is not aware of this signal, so only the main process gets killed, while the first daughter process stays alive. This makes a next restart impossible, as the main listening address is used by this process, but that does not belong to the store PID

And, opening this discussion here, one thing, which is a must in any distribution repository:
Give hints, how and where users can contribute to the source of the project.

• sslh should give a good hint, when called with an invalid parameter. BTW there is right now no --help, -h -? or any other parameter, associated with help. Fortunately every wrong parameter gives the help information ;-)
• the man page should give this information