On Wed, Feb 3, 2010 at 9:36 PM, David McGuffey
davidmcguf...@verizon.net wrote:
I'm trying to reduce the attack surface to a home machine that is always
on and connected to the Internet. It is running CentOS 5.4, with tight
iptables rules and sits behind a Verizon FiOS firewall/switch also
On Thu, 2010-02-04 at 09:19 -0500, Ross Walker wrote:
On Feb 3, 2010, at 9:36 PM, David McGuffey davidmcguf...@verizon.net
wrote:
I'm trying to reduce the attack surface to a home machine that is
always
on and connected to the Internet. It is running CentOS 5.4, with
tight
On Feb 5, 2010, at 6:55 PM, David McGuffey davidmcguf...@verizon.net
wrote:
On Thu, 2010-02-04 at 09:19 -0500, Ross Walker wrote:
On Feb 3, 2010, at 9:36 PM, David McGuffey
davidmcguf...@verizon.net
wrote:
I'm trying to reduce the attack surface to a home machine that is
always
on
On Feb 3, 2010, at 9:36 PM, David McGuffey davidmcguf...@verizon.net
wrote:
I'm trying to reduce the attack surface to a home machine that is
always
on and connected to the Internet. It is running CentOS 5.4, with
tight
iptables rules and sits behind a Verizon FiOS firewall/switch
David McGuffey wrote:
I'm trying to reduce the attack surface to a home machine that is always
on and connected to the Internet. It is running CentOS 5.4, with tight
iptables rules and sits behind a Verizon FiOS firewall/switch also
configured with tight rules.
I was wondering how to best
David McGuffey wrote:
I was wondering how to best block all network access to it when I log
off...then unblock it when I log on. Changing iptables requires root
access...as does running ifdown and ifup scripts.
You could use sudo to call them.. But I don't really understand your
concern, if
6 matches
Mail list logo