If you need information about setting up ssh and obtaining the public keys for the Panix user hosts, please see www.panix.com/help/ssh.html.
Secure Port Forwarding lets you use that SSH connection for things
besides straight UNIX shell sessions: things like Web browsing,
email, and FTP.
You can avoid including headers from elsewhere using SSH proxying
to send mail directly from the userhosts. The instructions are
similar to those for web proxying, above,
with appropriate modification of the port.
(The local port doesn't have to be 9000, it can be any
unprivileged port that you're not using for other purposes. If
you are setting up more than one proxy, you'll need a separate
session, with a different port number, for each.)
For details on setting up specific SSH or Web browsing software, refer
to the documentation for that program.
© Copyright 2001, Public Access Networks Corporation
[ Panix Home ] [ Security Help ] [ Help System Index ] [ Top of This Page ]
Introduction
How to set up SSH port forwarding to Panix for Web proxying
Local port: 9000
Remote server: 127.0.0.1 Remote port: 8008
(Panix maintains Privoxy web-proxy service on port 8008 of all our
userhosts. If you want "ad-blocking" too, use remote port
8118 instead.)
Sending email through an SSH tunnel
Users of some high-speed connections may discover that even when
they use Panix's SMTP server, their outbound message headers include
node information that causes some spam filters to reject their email.
Local port: 9000 Remote server: mail.panix.com Remote port: 25
(Port 25 is the standard port for SMTP.)