forked from yrutschle/sslh
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
Here's a list of features that have been suggested or | ||
sometimes requested. This list is not a roadmap and | ||
shouldn't be construed to mean that any of this will happen. | ||
|
||
- configurable behaviour depending on services (e.g. | ||
select() for ssl but fork() for ssh). | ||
|
||
- have certain services available only from specified subnets | ||
|
||
- some sort of "service knocking" allowing to activate a | ||
service upon some external even, similar to port knocking; | ||
for example, go to a specific URL to enable sslh forwarding | ||
to sshd for a set period of time: | ||
* sslh listens on 443 and only directs to httpd | ||
* user goes somewhere to https://example.org/open_ssh.cgi | ||
* open_ssh.cgi tells sslh | ||
* sslh starts checking if incoming connections are ssh, and | ||
if they are, forward to sshd | ||
* 10 minutes later, sslh stops forwarding to ssh | ||
|
||
That would make it almost impossible for an observer | ||
(someone who'd telnet regularly on 443) to ever notice both | ||
services are available on 443. | ||
|
||
|