Hello all,
We have the same problem, not only on mschap, but also with ttls+pap and
peap+pap. The problem was seen from the wheezy version of freeradius
[1], but when upgraded to wheezy-backports [2] (freeradius 2.2.5) the
issue was not seen anymore, even with logrotate doing a daemon reload
(20 t
On Mon, Dec 09, 2013 at 02:59:50PM +0100, Rolf Wojtech wrote:
> This is a critical problem because it makes all installations based on
> mschap unstable.
Not everyone uses mschap, thankfully :)
Whoever is interested should investigate and do an NMU.
--
2. That which causes joy or happiness
Wheezy is still affected and I assume so is sid.
Maybe I am missing something but I would like to call into question if the
debian package "freeradius" is still maintained?
This is a critical problem because it makes all installations based on
mschap unstable. It could be fixed by the maintainer
Dear maintainers
We have to same problem and would like to see this fixed soon, thanks!
Regards
Tom
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
What's the status of this? Adding a simple 'restart' instead of 'reload'
works, do you need any help? would be nice to get this fixed in sid (and
later on in wheezy too).
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Int
Package: freeradius
Version: 2.1.12+dfsg-1.2
Severity: important
Tags: upstream
Dear Maintainer,
I just spent a few minutes looking at an issue we've been having with a debian-
based FreeRADIUS server we're running.
After some closer investigation, it turned out that the weekly logrotate was
caus
6 matches
Mail list logo
