Need to find a file transfer service that is tunnels easily (e.g., for use with SSH)
...
Okay kids, because I half-way value security (let alone cost), our
current remote access for our users comprises of SSH over the
public Internet to a Linux box behind our firewall (we punch a hole
through it for port 22). Windows clients use TeraTerm Pro with
TTSSH as a client (with Blowfish being the preferred encryption
algorithm), establishing their own Internet connection (dial-up,
cable, xDSL, etc...). And we forward ports such as 25 (smtp), 110
(pop3), 5900-5999 (vnc) as necessary for services.
Personally, I like this arrangement for 2 reasons:
1. Don't have to deal with the hassle nor security fears
of maintaining my own dial-in connections/modems
2. I don't put my security/systems at risk because of
what is located on my user's home computers unlike
VPNs (where everything's open on my network to their
unsecured home system)
Unfortunately, I have one _major_issue_ with this arrangement, file
transfers. Since FTP does not easily forward/tunnel (for various
reasons, but mainly because the server opens another port for an
actual data connection -- something not noticable until you
actually try to transfer data), we have been using receive/send
zmodem (rz/sz) with limited fan-fare. Basically, while the
engineers don't mind it too much, the less tactful admins do.
So, I guess what I'm looking for is UNIX/Linux file transfer server
with UNIX/Windows clients that runs on a single port and can be
tunneled over something like SSH. It can run on any port, I'm not
picky, just as long as it can be tunneled.
One option that I haven't fully explored is to find a nice little
HTTP 1.1 server build specifically for this (anyone know of one?).
With such a server, all you need is a web browser. In fact, I
could do it with Zope (or Apache + scripting), but I don't have
time to work out all the details. But using a web browser as a
client would be sufficient enough, as long as the server has
buttons/scripts/mechanisms to allow uploading. Again, it can run
on any port, separate or alongside Apache -- either way is fine
with me.
Anyone got any suggestions? I'm assuming the HTTP 1.1 route is
easiest, but if there is an alternate system with at least a basic
client GUI, I'd be willing to look into it.
Thanx in advance ...
-- TheBS
--
Bryan "TheBS" Smith CONTACT INFO
***********************************************************
Chat: thebs413 @ AOL/MSN/Yahoo (see http://Everybuddy.com)
Email: mailto:[EMAIL PROTECTED],[EMAIL PROTECTED]
Legal: http://www.SmithConcepts.com/legal.html
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
