=== Monthrect is now known as Piper-Off [02:42] YamakasY: since you filled it up. srsly, it depends what you're up to === cpaelzer is now known as cpaelzer_afk === Lcawte|Away is now known as Lcawte [07:37] Can I rename the files of the network persistence instead of deleting them so that they will regenerate === Lcawte is now known as Lcawte|Away [09:36] Good morning. [10:33] can anyone suggest how I would sandbox a rails process, so that a user can connect to a machine and have access to a rails console, but no system commands? I've posted in detail here: http://serverfault.com/questions/741073/forcing-a-user-on-remote-connection-in-to-a-rails-console-and-prevent-them-acc === CiPi is now known as cipi === Piper-Off is now known as Monthrect === Monthrect is now known as Piper-Off === cipi is now known as CiPi === chmurifr- is now known as chmurifree === dasjoe_ is now known as dasjoe === _Kai__ is now known as _Kai_ [14:38] pmatulis: heh no I didn't puppet did but kernel management with puppet was a pain last periods with Ubuntu, buggy === Lcawte|Away is now known as Lcawte [18:41] Hello, so I seem to have made a slight mistake, and no longer have access to a dns lookup. I am not sure where the problem lies. I have edited my /etc/network/interfaces file to have a DNS of 8.8.8.8 and restarted the network interfaces with 'sudo /etc/init.d/networking restart' but that doesn't seem to apply the new name servers. [18:42] I don't want to restart the system, in case it looses it's cache. My end result is that I need to reinstall bind9 and isc-dhcp-server [18:42] caliculk: You are afraid of losing which cache? [18:42] caliculk: Umm... /etc/resolv.conf? [18:43] Check whats in there!! [18:44] SHouldn't resolv.conf be "updated" when reseting the network interfaces [18:44] No. [18:44] Dont know! But ifdown eth0 && ifup eth0 does that. === mikal_ is now known as mikal === Lcawte is now known as Lcawte|Away [21:47] How can you check your network for infected packets [21:48] durant: What do you mean by "infected packets"? [21:50] I need a way to look for packets [21:50] Which kind of packets? [21:50] * quantic predicts... [21:50] What are you actually trying to achieve? [21:50] tcp [21:51] durant: What is the actual issue behind that? [21:51] Which problem are you trying to solve by looking at tcp packets? [21:51] Trying to look for malware on my network [21:51] Then looking at tcp packages will not help you at all. [21:51] durant: patch stuff first [21:52] Is there a way to check for botnets [21:53] durant: No easy way. You need to monitor and analyze ALL traffic for doing so. [21:55] and that takes time and additional effort, too. [21:55] you're talking about a NIDS, and that's a complex beast. [21:56] ^ that [21:56] Like... that's a MAJOR undertaking even for someone that does it for a living. [21:57] NIDS solutions are the second most-complicated thing that I deploy in client environments. [21:58] And even more when just looking for "infected packets". [21:58] Malware identification is one of the most complex parts of a NIDS, which is already a complex system. [22:06] What is a good firewall you can use on linux [22:07] durant: Gonna be honest, you're asking questions that could be answered with the most cursory of Google searches. :/ [22:10] durant: iptables === Lcawte|Away is now known as Lcawte === Lcawte is now known as Lcawte|Away === bittin is now known as bittin_US