Bug#728306: freeradius only rotates /var/log/freeradius/radius.log, other logs (e.g. radacct/*) keep growing
G'day all I can confirm that on production systems with lots of roaming such logs can easily grow to multitude of 100M within 2-3 months. The current situation is not that ideal since most debian packages provide such method and radacct isn't rotated. I wanted to point out that the FR source actually contain a logrotate configuration for RedHat, so at least on this side they were willing to integrate something in use by a distribution. If things are not too different (i.e /var/log/freeradius vs. /var/log/radius location) there possibility of overlap/sharing? Upstream already has a /debian folder, I guess they'd welcome changes as their source can already build a .deb. Regards, Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691770: AW: freeradius: New upstream release 3.0.0
Package: freeradius Version: 2.1.12+dfsg-1.2 Followup-For: Bug #691770 Dear Maintainer, The freeradius team has released 3.0.0 which is a major rewrite of FreeRADIUS with a couple of modules rewritten for code cleanup and performance. 2.x will remain in maintenance for some time but thereafter ultimately left for the dead. Although this requires manual config migration (thus possibly better freeradius3?) for jessie this should not be missed. In the meantime 2.2.1 has been released on the 2.x branch and contains another round of bugfixes. -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709086: freeradius: Same issue here - ping
Package: freeradius Version: 2.1.12+dfsg-1.2 Followup-For: Bug #709086 Dear Maintainer, * What was the outcome of this action: mschap doesn't authenticate after logrotate (possibly other modules too) * What outcome did you expect instead: mschap not breaking on logrotate This problem is quite annoying since it breaks 802.1X which is pretty much essential once implemented in areas. Please consider Alan's (upstream author) patch for at least the current stable release wheezy. This patch is at least present in already-released FreeRADIUS releases 2.2.20 onwards. -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freeradius depends on: ii adduser3.113+nmu3 ii ca-certificates20130119 ii freeradius-common 2.1.12+dfsg-1.2 ii libc6 2.13-38 ii libfreeradius2 2.1.12+dfsg-1.2 ii libgdbm3 1.8.3-11 ii libltdl7 2.4.2-1.1 ii libpam0g 1.1.3-7.1 ii libperl5.145.14.2-21+deb7u1 ii libpython2.7 2.7.3-6 ii libssl1.0.01.0.1e-2 ii lsb-base 4.1+Debian8+deb7u1 ii ssl-cert 1.0.32 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages freeradius recommends: ii freeradius-utils 2.1.12+dfsg-1.2 Versions of packages freeradius suggests: pn freeradius-krb5none ii freeradius-ldap2.1.12+dfsg-1.2 pn freeradius-mysql none ii freeradius-postgresql 2.1.12+dfsg-1.2 -- Configuration Files: /etc/freeradius/clients.conf changed [not included] /etc/freeradius/eap.conf changed [not included] /etc/freeradius/modules/ldap changed [not included] /etc/freeradius/modules/mschap changed [not included] /etc/freeradius/modules/ntlm_auth changed [not included] /etc/freeradius/sites-available/default changed [not included] /etc/freeradius/sites-available/inner-tunnel changed [not included] /etc/freeradius/sql.conf changed [not included] /etc/freeradius/users changed [not included] /etc/logrotate.d/freeradius changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645881: AW: Bug#645881: critical update 29 available
Hi Von: Sylvestre Ledru [sylves...@debian.org] Gesendet: Freitag, 21. Oktober 2011 11:34 As for stable/oldstable: I noticed that Red Hat provided packages for update 29 for RHEL 4 (RHEL 5 onwards use OpenJDK): http://lwn.net/Articles/463919/ Well, I wonder how (if ?) they can do that... I'd expect RedHat has a agreement with Oracle that allows them to do so (including financial agreement) ;) - Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
