aboutsummaryrefslogtreecommitdiff
path: root/security/sslproxy/pkg-descr
diff options
context:
space:
mode:
authorSteve Price <steve@FreeBSD.org>1999-06-06 17:49:47 +0000
committerSteve Price <steve@FreeBSD.org>1999-06-06 17:49:47 +0000
commit1e28a3746d77419601862eacd64db1c2d2f5c389 (patch)
tree9dc129f2831aa93351720535b4ebf8692bcaaf9a /security/sslproxy/pkg-descr
parent79baa33417f493d556d5bcf4c72b6d9406eb4eb3 (diff)
downloadports-1e28a3746d77419601862eacd64db1c2d2f5c389.tar.gz
ports-1e28a3746d77419601862eacd64db1c2d2f5c389.zip
Notes
Diffstat (limited to 'security/sslproxy/pkg-descr')
-rw-r--r--security/sslproxy/pkg-descr7
1 files changed, 7 insertions, 0 deletions
diff --git a/security/sslproxy/pkg-descr b/security/sslproxy/pkg-descr
new file mode 100644
index 000000000000..98ef70c795b4
--- /dev/null
+++ b/security/sslproxy/pkg-descr
@@ -0,0 +1,7 @@
+You probably know secure HTTP from secure web sites. Say, you want to operate
+a secure web server but have only a normal server. SSL Proxy can be your
+solution: It's plugged into the connection between the client and the server
+and adds Secure Socket Layer (SSL) support. Or the other way around: You have
+an ordinary telnet client but want to connect to a secure site. Just start SSL
+Proxy with the appropriate parameters and -- voila. That's what SSL Proxy can
+do for you.