January 2010 - syslog-ng - lists.balabit.hu

Help with spoofing hostname
by PAUL WILLIAMSON 06 Feb '10

06 Feb '10

Thanks for the suggestions yesterday. As usual, there are multiple ways to solve the problem, each of them equally easy! Now on to my next issue... We have a product called Symantic SIM (Security Information Manager) that is on the receiving end of some forwarded messages. I have the keep_hostname(yes) option enabled, and when our SIM gets the message, the originating hostname is in the message. The problem is that is seems like the SIM is detecting that the message is coming from my loghost where Syslog-ng is installed, and tagging every message like it's from that instead of the actual host. We've been over the config with their engineers and our security department, and this is what we got back from Symantec today. "The hostname is available in the message, so it looks like that part is working. The problem is this, the message the SSIM sees is: <TIME> <Syslog Server IP> <Message> The SSIM then puts the syslog server IP as the source and destination of the host. Essentially the message needs to be sent to the SSIM as: <TIME> <Originating device Source IP> <Message> To do this, the message will need to be spoofed." So, I have two questions: 1. Can the messages be spoofed? 2. Does anyone else use this product and would be willing to share configs (of either syslog-ng or SSIM). Thanks, Paul ************************************ This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information. There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission. ************************************

2 1

syslog-ng MSGHDR
by Mij 06 Feb '10

06 Feb '10

Dear syslog-ng folks, I am the maintainer of sshguard, see http://www.sshguard.net . Sshguard can be interfaced with syslog-ng. Multiple users of syslog-ng recently reported that switching to 3.x required a configuration change for preserving the original logging format, see https://sourceforge.net/mailarchive/forum.php?thread_name=EE040D72-0185-41E… https://sourceforge.net/mailarchive/forum.php?thread_name=DA2160C1-09A0-475… We reflected the reports by updating the setup docs to contain a block for the 2.x version and one for 3.x , see http://www.sshguard.net/docs/setup/getlogs/syslog-ng/ However, this change is not apparent in your documentation or changelogs, and other users reported that with even more recent versions, the "old format" is again the correct one. Can you clarify what is the intended template for producing entry tags of the classic format "Jan 21 12:54:09 examplehost proftpd[18965]: applmsg" in the different versions? thanks

2 3

What testing has been done for the new features in open source version of syslog-ng version 3.x
by Janani Janakiraman 06 Feb '10

06 Feb '10

I am trying to judge the level of confidence for the latest stable open-source version of syslog-ng version 3.0.5. Where can I find the test results of the tests that have been run again version 3.0.5 of syslog-ng? I want to find out if tests have been run to test the new features in Version 3.x specifically support for the new IETF-syslog protocol standard ( RFC5424 ). Do any of the major Linux distros support version 3.x of syslog-ng? Thanks, Janani

3 4

config file question
by Rory Toma 05 Feb '10

05 Feb '10

OK, I have a question. I've found that it is good to run several syslog-ng processes when dealing with tens of thousands of log files. So, I'd like to receive everything in one syslog-ng process, and forward them, via localhost, to about a hundred or so different syslog-ng processes on the same machine. Is there a good way to write a (log; filter; dest;) line that would round-robin between a bunch of destinations in a single line?

4 6

Logs not identical.
by Andy Loughran 29 Jan '10

29 Jan '10

Guys, I have had some issues with my httpd server, therefore had to enable some Debug Logging. This is in a different format to the rest of the logs. I have had the httpd.conf set logging to syslog:local1, and had the following in place to parse the logs log { source(s_sys); fillter(f_fac1); destination(d_logserver); }; that worked fine. However, I noticed it wasn't logging my Apache2::Resource debugs, here's an example of the two types of logs: [Fri Jan 29 16:00:30 2010] [debug] prefork.c(991): AcceptMutex: sysvsem (default: sysvsem) Apache2::Resource: PID 30247 attempting to set `DATA'=400:500 ...ok the top line is logged, but the second line isn't. I found this out, by setting httpd.conf to log to /var/log/httpd/error.log instead of syslog. For some reason syslog isn't getting/is cutting out the Apache2:: lines. So, I thought it prudent to get the httpd.conf to log to the file, and then get syslog-ng to read from this file. source s_httpd_err { file("/var/log/httpd/error.log" follow_freq(1) flags(no-parse)); }; I then put that straight into a separate file, with no filters. destination d_httpd_err { file("/logs/httpd_error.log"); }; log { source(s_httpd_err); destination(d_httpd_err); }; However, the destination is missing the Apache2:: logs - but has the normal formatted logs. Is there a filter still being applied, even though I don't specify one? Let me know if you need more information to help me solve my problem. Thanks, Andy

1 0

now on to my next problem
by Rory Toma 28 Jan '10

28 Jan '10

I'm getting a lot of dropped messages. The messages are getting to my syslog-ng server, but when I do an strace, I have: accept(3, 0x7fff5783dc10, [285598969948537856]) = -1 EAGAIN (Resource temporarily unavailable) Here is the config: @version: 3.0 options { flush_lines (3); time_reopen (10); log_fifo_size (1000000); long_hostnames (off); use_dns (no); use_fqdn (no); create_dirs (yes); dir_perm (0755); keep_hostname (yes); ts_format("iso"); }; are there some other params I should be adjusting?

2 2

pattern database : first feedback and thoughts
by Christophe Brocas 27 Jan '10

27 Jan '10

Hello, I have start to play with pattern database. It is a very good starting point to do alerting when syslog-ng finds some logs belonging to (for example) security class. 1. Bug The current online pattern db snapshot provides the system-apache2.xml file. This file is not in a xml format but is just a set of log messages (it seems). 2. Class Can you tell us on what kind of criteria is used ti choose the class value (for example : system vs security class) of a particular log entry ? 3. Pattern database contribution / management / delivering Despite a big effort from Balabit (thanks for it !) to deliver an impressive first release (8000 log messages, 200 applications), I am sure that a community effort is the only way to maintain a good quality level of this database. You release the pattern database under the CC by-nc-sa licence. It is a very good way to start a community effort. In order to build a community around pattern database, I think some interesting points may be : - Having a dedicated DNS name and website (logpattern.org is available). Balabit can be of course the main sponsor of the website. But to be able to attract people and even more other companies for database contribution, I think all the communication / site management would have to rely on individuals and not on Balabit company. - Providing open log entry submission process through multi ways (web form, (D)VCS or bugreport system) - Providing a regular (each week, month or three months for ex.) database snapshot release cycle. If you want some help for the website, I can be involved :-) Thank you very much this pattern database effort :-) Christophe -- Christophe Brocas CNAMTS/DDSI/DSEC 12, allées Haussmann 33300 Bordeaux fixe : +33 (0)5.57.85.53.55 mobile : +33 (0)6.77.05.19.01 fax : +33 (0)5.56.39.84.48 keyid : 0x237E9DB2 ***************************************************** "Le contenu de ce courriel et ses eventuelles pièces jointes sont confidentiels. Ils s'adressent exclusivement à la personne destinataire. Si cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre à d'autres personnes ni le reproduire. Merci de le renvoyer à l'émetteur et de le détruire. Attention : L'Organisme de l'émetteur du message ne pourra être tenu responsable de l'altération du présent courriel. Il appartient au destinataire de vérifier que les messages et pièces jointes reçus ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses éventuelles pièces jointes sont celles de l'émetteur. Elles ne reflètent pas la position de l'Organisme sauf s'il en est disposé autrement dans le présent courriel." ******************************************************

2 1

trouble shoot program() function
by Sal Polifemo 26 Jan '10

26 Jan '10

Hi everyone. I am trying to send mail notifications using the syslog-ng program() function and it's not working. To verify the filter works I use the same filter to log to a file and the data is going to the file correctly. When I run the script manually "grep ASA-5-111008 log_file | /usr/local/bin/cisco-cfg.pl" mail is generated. I added code to write to a file and that did not work. I am including the syslog-ng.cfg snippet and the cisco-cfg.pl code. Any ideas how I can trouble shoot why the email is not being sent from syslog-ng Thanks for you help syslog-ng.conf =========== source external { udp(port(514)); tcp(ip(0.0.0.0) port(5000) max-connections(300)); }; destination d_cisco_config{ program ("/usr/local/bin/cisco-cfg.pl"); }; destination test { file ("/var/log/HOSTS/test"); }; filter f_firewall_config{ match("ASA-6-605005") or match("ASA-5-111008"); }; log { #log to file to test that filter is working source(external); filter(f_firewall_config); destination(test); }; log { source (external); filter (f_firewall_config); destination(d_cisco_config); }; /usr/local/bin/cisco-cfg.pl ================ #!/usr/bin/perl -n use strict; use warnings; my $d_month = ""; my $d_day = ""; my $d_hour = ""; my $d_min = ""; my $d_sec = ""; my $host = ""; my $user = ""; my $command = ""; my $user_pc = ""; my $interface = ""; my $title = ""; my $to = ""; my $from = ""; my $subject = ""; if (/ASA\-5\-111008/) { /(\w{1,3})\s*(\d{1,2})\s(\d{2})\d{2})\d{2}).*?(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}).*?'(.*?)'.*?'(.*?)'/; $d_month =$1; $d_day = $2; $d_hour = $3; $d_min = $4; $d_sec = $5; $host = $6; $user =$7; $command = $8; $to = 'user(a)mail.com'; $title = "$host Firewall config alert"; $from = 'root(a)cadis.net'; open( MAIL, "|/usr/sbin/sendmail -t"); print MAIL "EOT"; ## Mail Header print MAIL "To: $to\n"; print MAIL "From: $from\n"; print MAIL "Subject: Firewall config change on $host\n\n"; ## mail body print MAIL "Host: $host\n"; print MAIL "Edited by: $user\n"; print MAIL "Command issued: $command\n"; print MAIL "Log stamp: $d_month $d_day $d_hour:$d_min.$d_sec\n"; print MAIL "\n\n"; print MAIL "Log message:\n"; print MAIL "$_\n"; print MAIL "EOT"; close( MAIL ); }

2 1

need help with a match filter
by Rory Toma 25 Jan '10

25 Jan '10

I'm trying to dynamically create lognames and directories form the host name that is sent. My hosts' names are of the form foo_<mac address> I want to create a destination that would be /logs/foo_<first 9 digits of mac address>/<date>/foo_<mac_address>.log Here is what I tried so far, and it does not work, but is close. Can someone suggest a config that might work? Thx. I can do this individually, but having 100+ filters and 100+ log lines in the config really slows things down. #filter for foo filter foo_filter { match('host("foo_[0-9A-F]\{9\}$")' flags("store-matches")); }; # foo destinations destination foo_dest { file("/logs/$0/$R_YEAR$R_MONTH$R_DAY/$HOST-$R_YEAR$R_MONTH$R_DAY.log" owner(root) group(root) perm(0444) template("$YEAR-$MONTH-$DAY $HOUR:$MIN:$SEC $MSG\n") template_escape(no)); };

1 1

Messages dropped...
by Pontius, Brian D CIV NAVSISA 25 Jan '10

25 Jan '10

I apologize for what seems to be repost of a rather similar problem but I having looked through the archives and unable to find answers. I am running syslog-ng 3.0.4 on Solaris 10 x86 (64bit). I have about 200 hosts, all running over udp. I have 1 heavy hitter, which is my firewall. I puts about 1500 messages a minute. It seems that syslog-ng is able to handle this amount of traffic but I am having trouble figuring out why I can't seem to make it work that way. I started to notice that I was dropping udp packets by running netstat -s |grep udpInOverflows. I tweaked the udp buffers by setting them to their max ndd -set /dev/udp udp_max_buf 1073741824 ndd -set /dev/udp udp_recv_hiwt 65536 I was still losing packets until I started to tweek my syslog-ng.conf and added the so_rcvbuf entries. The problem is, the logfiles do not reflect that all of the messages are making it. I only know this because the firewall is also logging to another standalone solaris server running standard syslogd and the syslog-ng's firewall's logs are still only getting 1/3 of the logs. Here is my syslog-ng.conf @version:3.0 # syslog-ng configuration file. # # This should behave pretty much like the original syslog on SunOS. But # it could be configured a lot smarter. # # See syslog-ng(8) and syslog-ng.conf(5) for more information. # # 20000925 gb(a)sysfive.com # Global Options options { flush_lines (2000); time_reopen (10); time_sleep (50); log_fifo_size (100000); log_fetch_limit (50000); chain_hostnames (yes); use_dns (yes); use_fqdn (no); keep_hostname (yes); dns_cache (yes); dns_cache_size (2000); dns_cache_expire(87600); create_dirs (yes); owner(splunk); group(Unix_users); dir_group(Unix_users); perm(0640); dir_perm(0750); stats_level(1); }; ######################################################## # Sources # Sun Remote port source s_sun { udp(ip("xxx.xxx.xxx.101") port(514) so_rcvbuf(1073741824)); }; # Hp Remote port source s_hp { udp(ip("xxx.xxx.xxx.102") port(514) so_rcvbuf(1073741824)); }; # Other Remote port source s_other { udp(ip("xxx.xxx.xxx.103") port(514)); }; # ESX Remote port source s_esx { udp(ip("xxx.xxx.xxx.104") port(514) so_rcvbuf(1073741824)); }; # Linux Remote port source s_linux { udp(ip("xxx.xxx.xxx.105") port(514) so_rcvbuf(1073741824)); }; # Switch Remote port source s_switch { udp(ip("xxx.xxx.xxx.106") port(514) so_rcvbuf(1073741824) ); }; source s_local { internal(); }; ######################################################## # Destinations # Sun destinations destination d_sun_cons { file("/shares/logfiles/syslog/sun/$HOST/console"); }; destination d_sun_mesg { file("/shares/logfiles/syslog/sun/$HOST/messages"); }; destination d_sun_syslog { file("/shares/logfiles/syslog/sun/$HOST/syslog"); }; destination d_sun_auth { file("/shares/logfiles/syslog/sun/$HOST/auth"); }; destination d_sun_audit { file("/shares/logfiles/syslog/sun/$HOST/audit.log"); }; # HP destinations destination d_hp_cons { file("/shares/logfiles/syslog/hp/$HOST/console"); }; destination d_hp_mail { file("/shares/logfiles/syslog/hp/$HOST/mail.log"); }; destination d_hp_syslog { file("/shares/logfiles/syslog/hp/$HOST/syslog.log"); }; # SAN destinations destination d_switch { file("/shares/logfiles/syslog/switches/$HOST/syslog.log"); }; # Other destinations destination d_other { file("/shares/logfiles/syslog/other_devices/$HOST/syslog.log"); }; # ESX destinations destination d_esx_cons { file("/shares/logfiles/syslog/esx/$HOST/console"); }; destination d_esx_mesg { file("/shares/logfiles/syslog/esx/$HOST/messages"); }; destination d_esx_mail { file("/shares/logfiles/syslog/esx/$HOST/maillog"); }; destination d_esx_auth { file("/shares/logfiles/syslog/esx/$HOST/secure"); }; destination d_esx_cron { file("/shares/logfiles/syslog/esx/$HOST/cron.log"); }; # Linux destinations destination d_linux_cons { file("/shares/logfiles/syslog/linux/$HOST/console"); }; destination d_linux_mesg { file("/shares/logfiles/syslog/linux/$HOST/messages"); }; destination d_linux_mail { file("/shares/logfiles/syslog/linux/$HOST/maillog"); }; destination d_linux_auth { file("/shares/logfiles/syslog/linux/$HOST/secure"); }; destination d_linux_cron { file("/shares/logfiles/syslog/linux/$HOST/cron.log"); }; destination d_local { file("/shares/logfiles/syslog/syslog-ng.log"); }; ######################################################## # Filtering # Sun Remote Filtering filter f_sun_mesg { level(err) or level(crit) or (facility(kern)) or (facility(daemon)) or (facility(mail) and level(crit)); }; filter f_sun_syslog { facility(mail); }; filter f_sun_auth { facility(auth); }; filter f_sun_audit { facility(13); }; filter f_sun_cons { level(crit) or level(alert) or (facility (auth)) or level(emerg); }; # Hp Remote Filtering filter f_hp_mail { facility(mail); }; filter f_hp_syslog { level(info); }; filter f_hp_cons { level(alert) or level(emerg); }; # SAN Remote Filtering #filter f_san { level(info); }; # ESX Remote Filtering filter f_esx_cons { level(emerg); }; filter f_esx_mesg { level(info) or facility(auth) or facility(local6) or facility(local5) or facility(local7) or (facility(mail) and level(crit)); }; filter f_esx_auth { facility(auth); }; filter f_esx_mail { facility(mail); }; filter f_esx_cron { facility(cron); }; # Linux Remote Filtering filter f_linux_cons { level(emerg); }; filter f_linux_mesg { level(info) or facility(auth) or facility(local6) or facility(local5) or facility(local7) or (facility(mail) and level(crit)); }; filter f_linux_auth { facility(auth); }; filter f_linux_mail { facility(mail); }; filter f_linux_cron { facility(cron); }; ######################################################## # Logging # Sun Remote Logging log { source(s_sun); filter(f_sun_cons); destination(d_sun_cons); flags(flow-control); }; log { source(s_sun); filter(f_sun_mesg); destination(d_sun_mesg); flags(flow-control); }; log { source(s_sun); filter(f_sun_syslog); destination(d_sun_syslog); flags(flow-control); }; log { source(s_sun); filter(f_sun_auth); destination(d_sun_auth); flags(flow-control); }; log { source(s_sun); filter(f_sun_audit); destination(d_sun_audit); flags(flow-control); }; # Hp Remote Logging log { source(s_hp); filter(f_hp_mail); destination(d_hp_mail); flags(flow-control); }; log { source(s_hp); filter(f_hp_syslog); destination(d_hp_syslog); flags(flow-control); }; log { source(s_hp); filter(f_hp_cons); destination(d_hp_cons); flags(flow-control); }; # SAN log { source(s_switch); destination(d_switch); flags(flow-control); }; # SAN log { source(s_other); destination(d_other); flags(flow-control); }; # ESX Remote Logging log { source(s_esx); filter(f_esx_cons); destination(d_esx_cons); flags(flow-control); }; log { source(s_esx); filter(f_esx_mesg); destination(d_esx_mesg); flags(flow-control); }; log { source(s_esx); filter(f_esx_mail); destination(d_esx_mail); flags(flow-control); }; log { source(s_esx); filter(f_esx_auth); destination(d_esx_auth); flags(flow-control); }; log { source(s_esx); filter(f_esx_cron); destination(d_esx_cron); flags(flow-control); }; # Linux Remote Logging log { source(s_linux); filter(f_linux_cons); destination(d_linux_cons); flags(flow-control); }; log { source(s_linux); filter(f_linux_mesg); destination(d_linux_mesg); flags(flow-control); }; log { source(s_linux); filter(f_linux_mail); destination(d_linux_mail); flags(flow-control); }; log { source(s_linux); filter(f_linux_auth); destination(d_linux_auth); flags(flow-control); }; log { source(s_linux); filter(f_linux_cron); destination(d_linux_cron); flags(flow-control); }; log { source(s_local); destination(d_local); }; Thanks for any help you can offer. Brian Pontius

2 2