On 3 February 2015 at 12:58, Always Learning <centos at u64.u22.net> wrote: >> If you really want to do this, I'd suggest running your >> test system in some kind of DMZ to prevent any exploit cascading into >> the rest of your network. > > Not really sure what a (USA military) DMZ looks like. Security has > always been my highest priority. "When in doubt, lock 'em out" is my > motto. A DMZ in this context is a network that has been isolated from the rest of your local network. You can access it from your local network, it can access the rest of the world, but it can't access your network. The idea is that, if a machine in the DMZ is compromised, it can only access other machines in the DMZ. Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd Suite 1416 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer." -- IBM maintenance manual, 1925