December 2012 - syslog-ng - lists.balabit.hu

Re: [syslog-ng] syslog-ng Digest, Vol 92, Issue 18
by Frank Scalzo 20 Dec '12

20 Dec '12

> Message: 12 > Subject: Re: [syslog-ng] having an issue with syslog and SElinux > > > On 2012-12-18 14:40, Frank Scalzo wrote: >> kernel: : type=1400 audit(1355841452.964:21866): avc: denied { fowner >> } for pid=861 comm="syslog-ng" capability=3 >> scontext=system_u:system_r:syslogd_t:s0 >> tcontext=system_u:system_r:syslogd_t:s0 tclass=capability >> >> >> How do i fix this without disabling SElinux > > Which Linux distribution are you using? And which versions of syslog-ng > and selinux? A copy of your syslog-ng configuration file would > also be helpful. Im running the following Red Hat Enterprise Linux Server release 6.3 (Santiago) selinux-3.7.19-187 syslog-ng 3.2.5 Installer-Version: 3.2.5 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.2#master#9d4bea28198bd731df1a61e980a2af5b88d81116 Compile-Date: Jan 15 2012 19:47:30 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: off Enable-SQL: on Enable-Linux-Caps: off Enable-Pcre: on Enable-Pacct: off conf below: @version:3.2 # syslog-ng configuration file. # # This should behave pretty much like the original syslog on RedHat. But # it could be configured a lot smarter. # # See syslog-ng(8) and syslog-ng.conf(5) for more information. # options { flush_lines(100); log_fetch_limit(100); log_iw_size(100); log_fifo_size(1000); time_reopen (10); log_fifo_size (1000); use_dns (yes); use_fqdn (yes); create_dirs (yes); keep_hostname (yes); }; source s_sys { file ("/proc/kmsg" program_override("kernel: ")); unix-stream ("/dev/log"); internal(); # udp(ip(0.0.0.0) port(514)); }; destination d_cons { file("/dev/console"); }; destination d_mesg { file("/var/log/messages"); }; destination d_auth { file("/var/log/secure"); }; destination d_mail { file("/var/log/maillog" flush_lines(10)); }; destination d_spol { file("/var/log/spooler"); }; destination d_boot { file("/var/log/boot.log"); }; destination d_cron { file("/var/log/cron"); }; destination d_kern { file("/var/log/kern"); }; destination d_mlal { usertty("*"); }; filter f_kernel { facility(kern); }; filter f_default { level(info..emerg) and not (facility(mail) or facility(authpriv) or facility(cron)); }; filter f_auth { facility(authpriv); }; filter f_mail { facility(mail); }; filter f_emergency { level(emerg); }; filter f_news { facility(uucp) or (facility(news) and level(crit..emerg)); }; filter f_boot { facility(local7); }; filter f_cron { facility(cron); }; #log { source(s_sys); filter(f_kernel); destination(d_cons); }; log { source(s_sys); filter(f_kernel); destination(d_kern); }; log { source(s_sys); filter(f_default); destination(d_mesg); }; log { source(s_sys); filter(f_auth); destination(d_auth); }; log { source(s_sys); filter(f_mail); destination(d_mail); }; log { source(s_sys); filter(f_emergency); destination(d_mlal); }; log { source(s_sys); filter(f_news); destination(d_spol); }; log { source(s_sys); filter(f_boot); destination(d_boot); }; log { source(s_sys); filter(f_cron); destination(d_cron); }; ## Additions for central syslog source s_udp { udp(); }; source s_tcp { tcp(ip(0.0.0.0) port(514)); }; destination d_hosts { file("/var/log/hosts/$HOST/$YEAR$MONTH$DAY" owner(syslog) group(syslog) perm(0644) dir_perm(0755) create_dirs(yes)); }; log { source(s_udp); destination(d_hosts); }; log { source(s_tcp); destination(d_hosts); }; # For testing: aka logger "my little pony" #log { source(s_sys); destination(d_hosts); }; ## End additions for central syslog # vim:ft=syslog-ng:ai:si:ts=4:sw=4:et: On Dec 20, 2012, at 8:59 AM, syslog-ng-request(a)lists.balabit.hu wrote: > Send syslog-ng mailing list submissions to > syslog-ng(a)lists.balabit.hu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.balabit.hu/mailman/listinfo/syslog-ng > or, via email, send a message with subject or body 'help' to > syslog-ng-request(a)lists.balabit.hu > > You can reach the person managing the list at > syslog-ng-owner(a)lists.balabit.hu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of syslog-ng digest..." > > > Today's Topics: > > 1. syslog-ng Insider - December 2012 (Peter Czanik) > 2. [Bug 213] Build Failure on AIX with syslog-ng-3.3.6 and gcc > 4.2.0 (bugzilla(a)bugzilla.balabit.com) > 3. [Bug 213] Build Failure on AIX with syslog-ng-3.3.6 and gcc > 4.2.0 (bugzilla(a)bugzilla.balabit.com) > 4. [Bug 214] Build / Install Issues on AIX > (bugzilla(a)bugzilla.balabit.com) > 5. [Bug 214] Build / Install Issues on AIX > (bugzilla(a)bugzilla.balabit.com) > 6. [Bug 173] Compile issues with syslog-ng_3.3.4.tar.gz > (bugzilla(a)bugzilla.balabit.com) > 7. [Bug 61] udp6 source declaration causes syslog forwarding to > assume IPv6 (bugzilla(a)bugzilla.balabit.com) > 8. [Bug 42] capabilities, chown, chmod > (bugzilla(a)bugzilla.balabit.com) > 9. [Bug 213] Build Failure on AIX with syslog-ng-3.3.6 and gcc > 4.2.0 (bugzilla(a)bugzilla.balabit.com) > 10. [Bug 61] udp6 source declaration causes syslog forwarding to > assume IPv6 (bugzilla(a)bugzilla.balabit.com) > 11. [Bug 61] udp6 source declaration causes syslog forwarding to > assume IPv6 (bugzilla(a)bugzilla.balabit.com) > 12. Re: having an issue with syslog and SElinux (Jose Pedro Oliveira) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 20 Dec 2012 12:01:01 +0100 > From: Peter Czanik <czanik(a)balabit.hu> > Subject: [syslog-ng] syslog-ng Insider - December 2012 > To: Syslog-ng users' and developers' mailing list > <syslog-ng(a)lists.balabit.hu> > Message-ID: <50D2EFED.9080108(a)balabit.hu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > Dear syslog-ng users, > > > This is the 19th issue of the syslog-ng Insider, a monthly newsletter > that brings you syslog-ng related news. > > Your feedback and news tips about the next issue is welcome at > documentation(a)balabit.com <mailto:documentation@balabit.com> > > > FEATURED NEWS > > > syslog-ng 3.4 beta1 is released > > ------------------------------- > > Version 3.4 beta1was released thisweek, right before the > Christmasholidays. It has many new features and bug fixes even since the > last alpha release, most notably a new AMQP destination a JSON parser > and a reworked syslog parser and network configuration, which makes > configuring syslog-ng even more simple and flexible. > > For a complete list of changes, check the announcement at > https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… > > For binary package availability check our 3^rd party binary page at > http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… > > > balabit.logstore 0.1.0 is released > > ---------------------------------- > > The second version of the balabit.logstore project was announced last > week. It is a library written in Clojure, that tries to provide a > convenient API to read syslog-ng PE LogStore files. Development is still > in its early phases, but it can already read unencrypted logstore files, > search in them and print many useful information about them. Compared to > the previous version, this has a Java API. > > For more details, check the announcement at > https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html > > > > NEW RELEASES: > > * > > syslog-ng OSE 3.4 beta1: > https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… > > * > > balabit.logstore 0.1.0: > https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html > > ARCHIVE > > > http://insider.blogs.balabit.com/ > > -- > Peter Czanik (CzP) <czanik(a)balabit.hu> > BalaBit IT Security / syslog-ng upstream > http://czanik.blogs.balabit.com/ > > > > > ------------------------------ > > Message: 2 > Date: Thu, 20 Dec 2012 13:02:58 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 213] Build Failure on AIX with > syslog-ng-3.3.6 and gcc 4.2.0 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120258.155B339DC65(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=213 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|--- |3.3.8 > CC| |algernon(a)balabit.hu > AssignedTo|bazsi(a)balabit.hu |algernon(a)balabit.hu > > > > > --- Comment #3 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:02:57 --- > Thanks for the report and the patch, I will apply this to 3.3's git head shortly, with some minor modifications: I don't want to replace GLOB_NOMAGIC with > GLOB_NOCHECK, as they're not the same. > > With GLOB_NOMAGIC, "/etc/syslog-ng/foo.conf" both would return foo.conf, but for "/etc/syslog-ng/conf.d/*.conf", NOCHECK would return the pattern, NOMAGIC > would return GLOB_NOMATCH. So on platforms that do have NOMAGIC, syslog-ng should use it, on others, it should fall back to NOCHECK as the next best option. > > I plan to do this with something along these lines: > > #ifndef GLOB_NOMAGIC > #define GLOB_NOMAGIC GLOB_NOCHECK > #endif > > Or better yet, implement NOMAGIC if the platform does not support it. I'll see which option is more feasible in our case. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 3 > Date: Thu, 20 Dec 2012 13:03:08 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 213] Build Failure on AIX with > syslog-ng-3.3.6 and gcc 4.2.0 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120308.8D50439DC58(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=213 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |ASSIGNED > > > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 4 > Date: Thu, 20 Dec 2012 13:06:40 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 214] Build / Install Issues on AIX > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120640.1E33C39DC6B(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=214 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |algernon(a)balabit.hu > AssignedTo|bazsi(a)balabit.hu |algernon(a)balabit.hu > > > > > --- Comment #2 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:06:40 --- > (In reply to comment #1) >> Also to note, version 3.2.5 does not have any issues with lib/syslog-ng/libafsocket.so dependencies... the ldd output doesn't seem to indicate a requirement >> for libsyslog-ng-crypto. >> > > libsyslog-ng-crypto was split out of libsyslog-ng in 3.3. > > My guess is that libsyslog-ng-crypto gets installed into /opt/local/syslogng/lib/syslog-ng/, which is not on the dynamic loader's path, and the AIX linker > thingies do not support RPATH. > > The best course of action here would be to link libsyslog-ng-crypto directly into libsyslog-ng, I believe. Or, move it out of lib/syslog-ng, into lib/ itself. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 5 > Date: Thu, 20 Dec 2012 13:06:52 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 214] Build / Install Issues on AIX > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120652.23B0039DC75(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=214 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|--- |3.3.8 > Status|NEW |ASSIGNED > > > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 6 > Date: Thu, 20 Dec 2012 13:09:21 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 173] Compile issues with > syslog-ng_3.3.4.tar.gz > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120921.688A011E004(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=173 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REOPENED |NEEDINFO > > > > > --- Comment #4 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:09:21 --- > (In reply to comment #3) >> (In reply to comment #2) >>> Is this still and issue, or can I close it? I don't think this is a bug in syslog-ng... >>> >> >> I am facing the same issue while compiling syslog-ng-3.4.0-alpha3 on CentoOS 6.3 . > [...] >> when i set the env varilable export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig , eventlog went through fine but glib gave errors >> checking for GLIB... no >> configure: error: Package requirements (glib-2.0 >= 2.10.1 gmodule-2.0 gthread-2.0) were not met: > [...] > > Can you attach the config.log files from all three configure runs? That would help me figure out what goes wrong. > > Thanks! > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 7 > Date: Thu, 20 Dec 2012 13:12:03 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 61] udp6 source declaration causes syslog > forwarding to assume IPv6 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220121203.AA09339DC23(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=61 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|3.0.6 |3.4.1 > > > > > --- Comment #5 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:12:03 --- > This is partially fixed in 3.4 already with the network() statement, we only need to force syslog() to set last_addr_family to IPv4. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 8 > Date: Thu, 20 Dec 2012 13:15:24 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 42] capabilities, chown, chmod > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220121524.A692E39DCAA(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=42 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |algernon(a)balabit.hu > Resolution| |FIXED > Status|REOPENED |RESOLVED > > > > > --- Comment #10 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:15:23 --- > I'm closing this issue, as I believe it is not relevant for recent syslog-ng anymore. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 9 > Date: Thu, 20 Dec 2012 14:12:50 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 213] Build Failure on AIX with > syslog-ng-3.3.6 and gcc 4.2.0 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220131250.317AC39DC2A(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=213 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution| |FIXED > Status|ASSIGNED |RESOLVED > > > > > --- Comment #4 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 14:12:49 --- > (In reply to comment #3) >> Or better yet, implement NOMAGIC if the platform does not support it. I'll see which option is more feasible in our case. > > This is what I ended up doing, as the code required was pretty simple. I pushed the fix for both the iv_event.h include and the GLOB_NOMAGIC implementation to > 3.3's master, both will be part of syslog-ng 3.3.8. > > Thanks for the report! > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 10 > Date: Thu, 20 Dec 2012 14:19:41 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 61] udp6 source declaration causes syslog > forwarding to assume IPv6 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220131941.CE0DC39DC95(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=61 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|3.4.1 |3.3.8 > > > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 11 > Date: Thu, 20 Dec 2012 14:23:47 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 61] udp6 source declaration causes syslog > forwarding to assume IPv6 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220132347.5C94639DCAC(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=61 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution| |FIXED > Status|ASSIGNED |RESOLVED > > > > > --- Comment #6 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 14:23:47 --- > I ended up fixing this in 3.3, by forcing the syslog() destination to use IPv4, similar to how the source does it. In 3.4, network() can be used if one wants > syslog over IPv6. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 12 > Date: Thu, 20 Dec 2012 13:58:55 +0000 > From: Jose Pedro Oliveira <jpo(a)di.uminho.pt> > Subject: Re: [syslog-ng] having an issue with syslog and SElinux > To: syslog-ng(a)lists.balabit.hu > Message-ID: <50D3199F.8020004(a)di.uminho.pt> > Content-Type: text/plain; charset=ISO-8859-1 > > On 2012-12-18 14:40, Frank Scalzo wrote: >> kernel: : type=1400 audit(1355841452.964:21866): avc: denied { fowner >> } for pid=861 comm="syslog-ng" capability=3 >> scontext=system_u:system_r:syslogd_t:s0 >> tcontext=system_u:system_r:syslogd_t:s0 tclass=capability >> >> >> How do i fix this without disabling SElinux > > Which Linux distribution are you using? And which versions of syslog-ng > and selinux? A copy of your syslog-ng configuration file would > also be helpful. > > jpo > -- > Jos? Pedro Oliveira > * mailto:jpo@di.uminho.pt * > > > ------------------------------ > > _______________________________________________ > syslog-ng maillist - syslog-ng(a)lists.balabit.hu > https://lists.balabit.hu/mailman/listinfo/syslog-ng > > > End of syslog-ng Digest, Vol 92, Issue 18 > *****************************************

2 1

having an issue with syslog and SElinux
by Frank Scalzo 20 Dec '12

20 Dec '12

kernel: : type=1400 audit(1355841452.964:21866): avc: denied { fowner } for pid=861 comm="syslog-ng" capability=3 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:syslogd_t:s0 tclass=capability How do i fix this without disabling SElinux

3 2

[Bug 61] udp6 source declaration causes syslog forwarding to assume IPv6
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=61 Gergely Nagy <algernon(a)balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |FIXED Status|ASSIGNED |RESOLVED --- Comment #6 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 14:23:47 --- I ended up fixing this in 3.3, by forcing the syslog() destination to use IPv4, similar to how the source does it. In 3.4, network() can be used if one wants syslog over IPv6. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 61] udp6 source declaration causes syslog forwarding to assume IPv6
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=61 Gergely Nagy <algernon(a)balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.4.1 |3.3.8 -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 213] New: Build Failure on AIX with syslog-ng-3.3.6 and gcc 4.2.0
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=213 Summary: Build Failure on AIX with syslog-ng-3.3.6 and gcc 4.2.0 Product: syslog-ng Version: 3.3.x Platform: PC OS/Version: AIX Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: blentz(a)cswg.com Type of the Report: --- Estimated Hours: 0.0 /bin/sh ../libtool --tag=CC --mode=compile gcc -g -Wl,-blibpath:/opt/local/syslog-ng/lib:/usr/lib:/lib,-brtl -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/syslog-ng/include -pthread -I/opt/local/syslog-ng/include/glib-2.0 -I/opt/local/syslog-ng/lib/glib-2.0/include -I/opt/local/syslog-ng/include/eventlog -I/opt/local/syslog-ng/include -I/opt/local/syslog-ng/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/opt/local/syslog-ng/include -Wall -pthread -D_LARGE_FILES=1 -MT mainloop.lo -MD -MP -MF .deps/mainloop.Tpo -c -o mainloop.lo mainloop.c libtool: compile: gcc -g -Wl,-blibpath:/opt/local/syslog-ng/lib:/usr/lib:/lib,-brtl -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/syslog-ng/include -pthread -I/opt/local/syslog-ng/include/glib-2.0 -I/opt/local/syslog-ng/lib/glib-2.0/include -I/opt/local/syslog-ng/include/eventlog -I/opt/local/syslog-ng/include -I/opt/local/syslog-ng/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/opt/local/syslog-ng/include -Wall -pthread -D_LARGE_FILES=1 -MT mainloop.lo -MD -MP -MF .deps/mainloop.Tpo -c mainloop.c -DPIC -o .libs/mainloop.o mainloop.c: In function 'main_loop_call': mainloop.c:177: warning: implicit declaration of function 'iv_event_post' mainloop.c: In function 'main_loop_call_init': mainloop.c:217: warning: implicit declaration of function 'IV_EVENT_INIT' mainloop.c:218: error: invalid use of undefined type 'struct iv_event' mainloop.c:219: error: invalid use of undefined type 'struct iv_event' mainloop.c:220: warning: implicit declaration of function 'iv_event_register' make[4]: *** [mainloop.lo] Error 1 make[4]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6/lib' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6' make: *** [all] Error 2 Making install in lib -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 42] New: capabilities, chown, chmod
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=42 Summary: capabilities, chown, chmod Product: syslog-ng Version: 3.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: zbyniu(a)pld-linux.org Type of the Report: bug Estimated Hours: 0.0 Let's take a look at syslog-ng-3.0.1/src/affile.c lines 60-83 1. CAP_SYS_ADMIN is needed only for /proc/kmsg, it is added w/o check 2. CAP_DAC_READ_SEARCH should be added only if open fail with errno 13 2a. CAP_DAC_OVERRIDE should be added only if open fail with errno 13 and with CAP_DAC_READ_SEARCH set 3. fchown needs CAP_CHOWN unconditionaly 4. fchmod needs CAP_FOWNER if file owner != euid (root here) 5. all caps should be restored summary: - CAP_SYS_ADMIN and CAP_DAC_OVERRIDE are set always even if unnecessary, and permanently - owner, group and perm doesn't work -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 10

[Bug 61] udp6 source declaration causes syslog forwarding to assume IPv6
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=61 Gergely Nagy <algernon(a)balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.0.6 |3.4.1 --- Comment #5 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:12:03 --- This is partially fixed in 3.4 already with the network() statement, we only need to force syslog() to set last_addr_family to IPv4. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

syslog-ng Insider - December 2012
by Peter Czanik 20 Dec '12

20 Dec '12

Dear syslog-ng users, This is the 19th issue of the syslog-ng Insider, a monthly newsletter that brings you syslog-ng related news. Your feedback and news tips about the next issue is welcome at documentation(a)balabit.com <mailto:documentation@balabit.com> FEATURED NEWS syslog-ng 3.4 beta1 is released ------------------------------- Version 3.4 beta1was released thisweek, right before the Christmasholidays. It has many new features and bug fixes even since the last alpha release, most notably a new AMQP destination a JSON parser and a reworked syslog parser and network configuration, which makes configuring syslog-ng even more simple and flexible. For a complete list of changes, check the announcement at https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… For binary package availability check our 3^rd party binary page at http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… balabit.logstore 0.1.0 is released ---------------------------------- The second version of the balabit.logstore project was announced last week. It is a library written in Clojure, that tries to provide a convenient API to read syslog-ng PE LogStore files. Development is still in its early phases, but it can already read unencrypted logstore files, search in them and print many useful information about them. Compared to the previous version, this has a Java API. For more details, check the announcement at https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html NEW RELEASES: * syslog-ng OSE 3.4 beta1: https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… * balabit.logstore 0.1.0: https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html ARCHIVE http://insider.blogs.balabit.com/ -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

1 0

[ANN]: balabit.logstore 0.1.0 - Open Source LogStore reader API
by Gergely Nagy 19 Dec '12

19 Dec '12

--------------------------------------------------------------- PACKAGE : com.balabit/logstore VERSION : 0.1.0 SUMMARY : Rewritten from scratch, now includes simple Java API DATE : 2012 December 15 HOMEPAGE : http://algernon.github.com/balabit.logstore --------------------------------------------------------------- DESCRIPTION: The balabit.logstore project is a library written in Clojure, that tries to provide a convenient API to read syslog-ng PE LogStore files. The reason behind the implementation is to have an independent, open source reader for the LogStore file format, so that one is not tied to syslog-ng to read one's logs stored in this format. An open implementation makes it possible to read these logs on systems where syslog-ng is not installed, or where the lgstool program is not available. LogStore itself is a storage format for log messages, supporting encryption, compression, secure timestamps, serialized messages (think name-value pairs as opposed to just a plain, formatted string) and a lot more. This format is being opened, and this library is meant to provide an implenetation for a LogStore reader, that will eventually support reading all kinds of LogStore files. This release is a complete rewrite of an earlier attempt, and this time, it comes with a simple Java API. EXAMPLE: Clojure: (ns example (:require [balabit.logstore.sweet :as logstore])) (prn (logstore/messages (logstore/from-file "/path/to/logstore/messages.store"))) Java: import BalaBit.LogStore; import clojure.lang.LazySeq; import clojure.lang.Keyword; import java.util.Map; public class LGSCat { public static void main(String[] args) { Keyword k = BalaBit.LogStore.keyword("MESSAGE"); Object o = BalaBit.LogStore.fromFile (args[0]); LazySeq s = (LazySeq) BalaBit.LogStore.messages (o); for (Object m : s.toArray()) { Map msg = (Map) m; System.out.println(msg.get(k)); } } } More examples can be found bundled with the sources, and as part of the documentation: http://algernon.github.com/balabit.logstore/#balabit.logstore.cli FEATURES: The library - while still experimental - can read most unencrypted LogStores, created by syslog-ng PE 4.0 or any later version, and the messages stored within can be explored. It comes with a test suite and quite a few examples. FUTURE DIRECTION: The library is very simple right now, the error handling is pretty much non-existent, and it does not perform any kind of validation. The Java API is very thin, and exposes far more Clojure-isms than it ideally should, this will be improved upon in the future. Once things stabilized a bit, we plan to publish ready to use JAR files that can be used from any Java or Clojure project. DOWNLOADS: The source is available from the git repository at github: git://github.com/algernon/balabit.logstore.git Documentation and more information about the library is available on its homepage at http://algernon.github.com/balabit.logstore/. -- |8]

1 1

newbie question
by Groups 14 Dec '12

14 Dec '12

Newbie question My Goals (2) To replace the current CentOS 5.x log server with a SL 6.x syslog-ng server. *************************************** *************************************** Goal 1 To have all Linux servers log by the following: All Linux servers are running either syslog or rsyslog - Accept logs from Linux servers and separate them to messages.$YEAR$MONTH$DAY secure.$YEAR$MONTH$DAY maillog.$YEAR$MONTH$DAY messages can be a 'catchall' ================== My success on Linux servers... The mods in the syslog-ng.conf I have for Linux servers does work but catches everything. *************************************** *************************************** Goal 2 To have all (Cisco) switches / routers log according to their current syslog settings Current syslog server uses /etc/hosts to log the following. Receive logging messages from network devices (Router/Switch/VPN) to 3 files #based on priority local4.err /var/log/NetLog/NetDeverr local4.notice,local4.!err /var/log/NetLog/NetDevnote local4.=debug,local4.=info /var/log/NetLog/NetDevdebug #Receive logging messages from all other devices to 3 files based on priority syslog.err /var/log/OtherLog/OthDeverr syslog.notice,syslog.!err /var/log/OtherLog/OthDevnote syslog.=debug,syslog.=info /var/log/OtherLog/OthDevdebug #Receive logging messages from all wireless devices to 3 files based on priority local3.err /var/log/NetLog/Wirelesserr local3.notice,local3.!err /var/log/NetLog/Wirelessnote local3.=debug,local3.=info /var/log/NetLog/Wirelessdebug #Receive logging messages from all UPS's to 3 files based on priority local5.err /var/log/UPSLog/UPSerr local5.notice,local5.!err /var/log/UPSLog/UPSnote local5.=debug,local5.=info /var/log/UPSLog/UPSdebug *************************************** Thx for any pointers. tk --------------------- rsyslog is turned off -- OS: Scientific Linux 6.2 (RHEL 6 clone) -- #syslog-ng -V syslog-ng 3.2.5 Installer-Version: 3.2.5 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.2#master#9d4bea28198bd731df1a61e980a2af5b88d81116 Compile-Date: Jan 15 2012 19:52:28 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: off Enable-SQL: on Enable-Linux-Caps: off Enable-Pcre: on Enable-Pacct: off -- syslog-ng.conf (out of the box) with one change create_dirs (yes); --------------------- @version:3.2 # syslog-ng configuration file. # # This should behave pretty much like the original syslog on RedHat. But # it could be configured a lot smarter. # # See syslog-ng(8) and syslog-ng.conf(5) for more information. # options { flush_lines (0); time_reopen (10); log_fifo_size (1000); long_hostnames (off); use_dns (no); use_fqdn (no); create_dirs (yes); keep_hostname (yes); }; source s_sys { file ("/proc/kmsg" program_override("kernel: ")); unix-stream ("/dev/log"); internal(); # udp(ip(0.0.0.0) port(514)); }; destination d_cons { file("/dev/console"); }; destination d_mesg { file("/var/log/messages"); }; destination d_auth { file("/var/log/secure"); }; destination d_mail { file("/var/log/maillog" flush_lines(10)); }; destination d_spol { file("/var/log/spooler"); }; destination d_boot { file("/var/log/boot.log"); }; destination d_cron { file("/var/log/cron"); }; destination d_kern { file("/var/log/kern"); }; destination d_mlal { usertty("*"); }; filter f_kernel { facility(kern); }; filter f_default { level(info..emerg) and not (facility(mail) or facility(authpriv) or facility(cron)); }; filter f_auth { facility(authpriv); }; filter f_mail { facility(mail); }; filter f_emergency { level(emerg); }; filter f_news { facility(uucp) or (facility(news) and level(crit..emerg)); }; filter f_boot { facility(local7); }; filter f_cron { facility(cron); }; ## Begin Mods source s_udp { udp( flags(no-parse) ); };# An UDP source source s_tcp { tcp( flags(no-parse) ); };# An TCP source ###### Filter statements ####### ### Linux logs filter f_mailhost {host(172.25.85.41); }; filter f_merlin {host(172.25.45.10); }; ###### Destination statements ####### destination d_linux_servers {file("/var/log/devices/linux_servers/$HOST/log.$YEAR$MONTH$DAY"); }; ###### Log statements ####### ### Linux servers log {source(s_udp); filter(f_merlin); destination(d_linux_servers); }; log {source(s_udp); filter(f_mailhost); destination(d_linux_servers); }; --------------------- Thx

1 0