pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/net/sslh Update COMMENT and DESCR to describe new feat...
details: https://anonhg.NetBSD.org/pkgsrc/rev/a8c7396b60e5
branches: trunk
changeset: 626528:a8c7396b60e5
user: apb <apb%pkgsrc.org@localhost>
date: Thu Nov 14 08:01:01 2013 +0000
description:
Update COMMENT and DESCR to describe new features added between
sslh-1.7a and 1.15.
diffstat:
net/sslh/DESCR | 30 +++++++++++++-----------------
net/sslh/Makefile | 5 +++--
2 files changed, 16 insertions(+), 19 deletions(-)
diffs (56 lines):
diff -r 7b6f69a07852 -r a8c7396b60e5 net/sslh/DESCR
--- a/net/sslh/DESCR Thu Nov 14 07:59:44 2013 +0000
+++ b/net/sslh/DESCR Thu Nov 14 08:01:01 2013 +0000
@@ -1,19 +1,15 @@
-sslh lets one accept both HTTPS and SSH connections on
-the same port. It makes it possible to connect to an SSH
-server on port 443 (e.g. from inside a corporate firewall,
-which almost never block port 443) while still serving HTTPS
-on that port.
+Sslh accepts connections on specified ports, and forwards
+them further based on tests performed on the first data
+packet sent by the remote client.
-The idea is to have sslh listen to the external 443 port,
-accept the incoming connections, work out what type of
-connection it is, and then fordward to the appropriate
-server.
+Probes for HTTP, SSL, SSH, OpenVPN, tinc, XMPP are
+implemented, and any other protocol that can be tested using
+a regular expression, can be recognised. A typical use case
+is to allow serving several services on port 443 (e.g. to
+connect to ssh from inside a corporate firewall, which
+almost never block port 443) while still serving HTTPS on
+that port.
-The protocol detection is made based on a small difference
-between SSL and SSH: an SSL client connecting to a server
-speaks first, whereas an SSH client expects the SSH server
-to speak first (announcing itself with a banner). sslh
-waits for some time for the incoming connection to send data.
-If it does before the timeout occurs, it is supposed to be
-an SSL connection. Otherwise, it is supposed to be an SSH
-connection.
+Hence sslh acts as a protocol demultiplexer, or a
+switchboard. Its name comes from its original function to
+serve SSH and HTTPS on the same port.
diff -r 7b6f69a07852 -r a8c7396b60e5 net/sslh/Makefile
--- a/net/sslh/Makefile Thu Nov 14 07:59:44 2013 +0000
+++ b/net/sslh/Makefile Thu Nov 14 08:01:01 2013 +0000
@@ -1,13 +1,14 @@
-# $NetBSD: Makefile,v 1.3 2013/11/08 13:33:55 obache Exp $
+# $NetBSD: Makefile,v 1.4 2013/11/14 08:01:01 apb Exp $
#
DISTNAME= sslh-1.15
+PKGREVISION= 1
CATEGORIES= net
MASTER_SITES= http://www.rutschle.net/tech/
MAINTAINER= pkgsrc-users%NetBSD.org@localhost
HOMEPAGE= http://www.rutschle.net/tech/sslh.shtml
-COMMENT= Multiplex ssl and ssh connections on the same port
+COMMENT= Multiplex ssl, ssh, and other connections on the same port
LICENSE= gnu-gpl-v2
USE_TOOLS+= gmake gzip pod2man
Home |
Main Index |
Thread Index |
Old Index