Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am running a Debian system, using Firestarter as my firewall. All is working fine, except that in addittion to logging all attempts to access firewalled ports to the log file, these attempts also appear on the console screen.
It is driving me insane!! - I get halfway through typing a command, and suddenly it disappears beneath four lines of text telling me all the details of the inbound assault on port 135 from wherever!
I have looked through Firestarters firewall script, and also the config file. There doesn't seem to be anything about logging to the terminal aswell as to a log file. I wonder if it is part of some system logging feature I'm not aware of...
My question is... Is there an easy way to turn it off ??
You're in console F1 and probably have F1 - F8 to work with. Press Alt-F2 to go to console F2, etc for the others. The syslog.conf has "some" messages going to F1, so just use F2 for your work, which lets you press Alt-F1 to see messages.
Or kill the message output by changing the syslog.conf and restarting the syslog. Since you're new, just reboot. We'll go slow to get you up to speed.
# Emergencies are sent to everybody logged in.
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
# *.=notice;*.=warn /dev/tty8
# The named pipe /dev/xconsole is for the `xconsole' utility. To use it,
# you must invoke `xconsole' with the `-file' option:
# $ xconsole -file /dev/xconsole [...]
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
# busy site..
# *.=notice;*.=warn |/dev/xconsole
############ BASTILLE ADDITIONS BELOW : #################
# Log all kernel messages to the new file /var/log/kernel
# Log all logins to /var/log/loginlog
# Log additional data to the Alt-F7 and Alt-F8 screens (Pseudo TTY 7 and 8)
# DISABLED BY ME