Announcement
Collapse
No announcement yet.
Basic Security
Collapse
This topic is closed.
X
X
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
-
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
A Microsoft buddy of mine once wore a shirt with that phrase at TechEd. Nearly got fired for it. Alas, those who bear witness for the truth must also bear the consequences...
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Is the computer behind a NAT router or gateway? Please describe your network architecture a bit more. You might even draw a quick diagram, label the interface IP addresses, and post a photo of it.
- Top
- Bottom
Comment
-
well, it is a laptop, being dragged from a NAT network to an enterprise-class network infrastructure(school),
I need to run a webserver for testing purposes, that SHOULD not be available to other systems on the network,
this is my setup at home:
the kubuntu-laptop is the Samsung at the left
router to internet is a NAT-router from our ISP
networks are:
left side of Astaro(my systems): 192.168.123.0/24
right side(other stuff): 192.168.2.0/24
but as I said, I also drag it to school, where we use 10.0.0.0/?, or family(192.168.1.0/24, 192.168.2.0/24, 172.16.1.0/24),
I get around a lot of different networks(NAT networks, Enterprise class networks, or just some non-internetconnected testing networks),
I just don't want other people to see what I am doing on that local webserver, since it's non of their bussiness.
I do some webdevelopment for myself, and I am just experimenting with coding(HTML,PHP, CSS and their powers). it's just a little bit of privacy I want
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Thanks for the illustrations, that helps a lot.
My suggestion would be to bind all your services only to localhost (127.0.0.1 for IPv4, ::1 for IPv6). This eliminates the need to configure iptables. It's the approach I've taken for services that run on my server but shouldn't be visible outside the box itself (PostgreSQL, SpamAssassin, ClamAV, OpenDKIM).
Alternately, you could leave the services at their defaults (that is, bound to the real NIC) and then create iptables rules to block inbound traffic from everything except localhost.Last edited by SteveRiley; Mar 22, 2013, 12:57 PM.
- Top
- Bottom
Comment
Comment