> > Thanks a lot for everyone's help. Here is a more to-the-point list of > > what I'd like to accomplish: > > > > 1. encrypt CUPS printouts between remote server and local print server > > 2. add an additional layer of security around SSH and CUPS on local > > firewall/print server > > 3. add an additional layer of security around SSH, IMAP, and > > non-standard port HTTPS on remote server > > 4. enable access to SMTP on remote server for me which is blocked by > > my local ISP > > > > It sounds like I have 3 choices: > > > > 1. VPN > > 2. SSH tunneling > > 3. Zebedee tunneling > > > > Would all 3 of these choices accomplish all 4 requirements? I would > > think SSH tunneling can't really add an additional layer around SSH. > > I'd just like to reiterate that most of those don't need any extra > security. SSH and HTTPS are already secure, and IMAP and SMTP can be > accessed over SSL (like HTTPS). These are all secure enough to be > widely used without extra layers of encryption.
I'm surprised, but glad to hear this. I was under the impression that opening services like SSH and CUPS to the internet was a bad idea. I guess they're secure enough. That removes #2 and #3 from my 4-part list above. If I can print with CUPS via SSL and submit SMTP mail via alternate port 587, I won't need a VPN or tunnel. Thanks a lot for everyone's help. I'm going to start a new thread for those topics. - Grant -- gentoo-user@lists.gentoo.org mailing list
