Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A buch of junk appears on my console. It looks something like "IN=eth0 OUT= MAC=ff:ff:ff" etc. Someone from my LUG said that iptables was sending messages to the console and that to stop it I could edit /etc/syslog.conf and restart syslog. I went ahead and changed the two lines that directed to /dev/console and * to /dev/null, but I'm still getting these messages. Even if it had stopped the junk, I would still like to know why iptables is doing this(if it really is iptables) and how to stop it. It all started when I used firestarter for the first time, but there doesn't seem to be any option when it comes to directing messages. Any help or background information would be much appreciated.
Change "#kern.* /dev/null" to read "kern.PRIO /dev/console", where PRIO is one of crit or alert*. Restart syslogd.
*Read "man syslog.conf", under "Selectors", the part about priorities.
This is strange. It seems like you get a certain type of message "kern" "emerg" or whatever at a certain priority directed to a certain file/device/whatever. I can't imagine why things would show up on my console when I directed them to /dev/null. I followed your advice and I'm now waiting to see if I get any junk. Thanks much.
I'm now waiting to see if I get any junk
for pri in debug info notice warn err crit alert emerg panic; do
logger -p kern.$pri "gimme junk (pri: $pri)"; done
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.