On Sunday 17 February 2008, Grant wrote:
What wasn't mentioned is that SSL covers transport encryption, not
necessarily application security. What that means is if you open IMAP,
SMTP, CUPS, and SSH daemons over the internet then you also need to keep
(better) track of security
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
On Sun, 2008-02-17 at 07:12 -0800, Grant wrote:
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
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
On Sun, 2008-02-17 at 12:03 -0800, Grant wrote:
Good points Albert. Is a daily 'emerge --sync emerge -avDuN world'
generally enough as far as tracking security vulnerabilities?
- Grant
That's not really for me to say. But I can tell you that although the
Gentoo developers take matters of
Good points Albert. Is a daily 'emerge --sync emerge -avDuN world'
generally enough as far as tracking security vulnerabilities?
- Grant
That's not really for me to say. But I can tell you that although the
Gentoo developers take matters of security seriously, there is no
full-time
Good points Albert. Is a daily 'emerge --sync emerge -avDuN world'
generally enough as far as tracking security vulnerabilities?
- Grant
That's not really for me to say. But I can tell you that although the
Gentoo developers take matters of security seriously, there is no
full-time
On Wed, 13 Feb 2008 08:19:48 -0800
Grant [EMAIL PROTECTED] wrote:
Even if you just want to encrypt some clear-text protocol that
doesn't have an encrypted equivalent, a vpn is still overkill.
For that you use ssh tunneling (which is essentially the same
thing as an encrypted
Even if you just want to encrypt some clear-text protocol that
doesn't have an encrypted equivalent, a vpn is still overkill. For
that you use ssh tunneling (which is essentially the same thing as
an encrypted version of a protocol). 'ssh -X' is the classic
example of easily
Hi Grant,
On Thu, Feb 14, 2008 at 1:19 AM, Grant [EMAIL PROTECTED] wrote:
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
On Wed, 2008-02-13 at 08:19 -0800, Grant wrote:
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
On Tuesday 12 February 2008, Grant wrote:
Use SSH if you need a quick ad-hoc connection or something
temporary. Use OpenVPN if you need something more permanent that is
always prsent and just works.
I need temporary, but automated. Can an ssh tunnel be set up in an
automated way?
Of
On Tue, 2008-02-12 at 19:30 +0200, Alan McKinnon wrote:
On Tuesday 12 February 2008, Etaoin Shrdlu wrote:
On Tuesday 12 February 2008, Alan McKinnon wrote:
Your statement it seems like running SSH inside a VPN is better
for security than running SSH on a non-standard port is
Grant wrote:
I'm hoping to use the vpn in three few ways:
1. imap and smtp between my laptop and the mail server
2. ssh from my laptop to the remote server
3. cups printing from the remote server to the print server
I don't think you need a VPN to SSH from your laptop to the remote
On Tue, 12 Feb 2008 19:42:44 +0200
Alan McKinnon [EMAIL PROTECTED] wrote:
What about having ssh, imap, smtp, cups, and possibly a non-standard
https port all hidden within a VPN? Should that be considered a
benefit of running a VPN?
One other thought about ssh+vpn, if you have VPN
On Tuesday 12 February 2008, Alan McKinnon wrote:
Perhaps confusingly, ssh itself can be used to create openVPN-like
VPNs (actually, much simpler), using the -w option and a couple of
tun (or tap) interfaces on the connected computers.
hehehe, I'd forgetten about that one for a bit :-)
On Tuesday 12 February 2008, Grant wrote:
Even if you just want to encrypt some clear-text protocol that
doesn't have an encrypted equivalent, a vpn is still overkill. For
that you use ssh tunneling (which is essentially the same thing as
an encrypted version of a protocol). 'ssh -X' is
Your statement it seems like running SSH inside a VPN is better
for security than running SSH on a non-standard port is
non-sensical. From a security and encryption perspective, ssh and
OpenVPN are exactly the same thing - stuff wrapped in an encryption
layer provided by ssl,
On Tuesday 12 February 2008, Etaoin Shrdlu wrote:
On Tuesday 12 February 2008, Alan McKinnon wrote:
Your statement it seems like running SSH inside a VPN is better
for security than running SSH on a non-standard port is
non-sensical. From a security and encryption perspective, ssh and
On Tuesday 12 February 2008, Alan McKinnon wrote:
Your statement it seems like running SSH inside a VPN is better for
security than running SSH on a non-standard port is non-sensical.
From a security and encryption perspective, ssh and OpenVPN are
exactly the same thing - stuff wrapped in an
On Tuesday 12 February 2008, Grant wrote:
I don't think you need a VPN to SSH from your laptop to the remote
server -- SSH is already encrypted.
For sure, but it seems like running SSH inside a VPN is better for
security than running SSH on a non-standard port or even port
knocking. If I
I don't think you need a VPN to SSH from your laptop to the remote
server -- SSH is already encrypted.
For sure, but it seems like running SSH inside a VPN is better for
security than running SSH on a non-standard port or even port
knocking. If I need to set up a VPN for printing,
On Monday 11 February 2008, Grant wrote:
The second guide deals with bridging and the first does not. Should
I be setting up bridging? The first guide seems simpler. Should I
be OK with that one? I'd hate to dig into one of them and then find
out I should have chosen the other.
- Grant
Hi Grant,
On Tue, Feb 12, 2008 at 5:41 AM, Grant [EMAIL PROTECTED] wrote:
I'm hoping to use the vpn in three few ways:
1. imap and smtp between my laptop and the mail server
2. ssh from my laptop to the remote server
3. cups printing from the remote server to the print server
I don't
I'm hoping to use the vpn in three few ways:
1. imap and smtp between my laptop and the mail server
2. ssh from my laptop to the remote server
3. cups printing from the remote server to the print server
I don't think you need a VPN to SSH from your laptop to the remote
server --
I do this with my work printer - the printer is locked down to a local
network - I can print from locked out offices/labs anywhere (and even
from home, picking up the printouts when I arrive - convenient!)
I also transfer sometimes large files (using scp) and run ssh sessions
and imap/smtp mail
On Mon, 11 Feb 2008 16:00:49 -0800
Grant [EMAIL PROTECTED] wrote:
You can print from your laptop to your printer at home while
overseas, for example.
Sounds very convenient ; )
--
gentoo-user@lists.gentoo.org mailing list
I'm hoping to use the vpn in three few ways:
1. imap and smtp between my laptop and the mail server
2. ssh from my laptop to the remote server
3. cups printing from the remote server to the print server
I don't think you need a VPN to SSH from your laptop to the
Hi Grant,
On Tue, Feb 12, 2008 at 8:11 AM, Grant [EMAIL PROTECTED] wrote:
I'm hoping to use the vpn in three few ways:
1. imap and smtp between my laptop and the mail server
2. ssh from my laptop to the remote server
3. cups printing from the remote server to the print
29 matches
Mail list logo