Bug#349261: Bug#342943: only kronolith2 fixed

2006-02-09 Thread Martin Schulze
Ola Lundqvist wrote: I haven't managed to find any more bugs relating to this particular security hole that isn't fixed by the previous patch in this bug report. kronolith seems to be fairly badly coded wrt security issues though. I'd suggest depreciating kronolith1 and forcing

Bug#349261: Bug#342943: only kronolith2 fixed

2006-02-09 Thread Lionel Elie Mamane
On Thu, Feb 09, 2006 at 10:47:28AM +0100, Martin Schulze wrote: Ola Lundqvist wrote: I'd suggest depreciating kronolith1 and forcing people on to kronolith2, whcih although only a little better, is actually supported upstream. The problem is that kronolith2 depends on version 3 of the horde

Bug#349261: Bug#342943: only kronolith2 fixed

2006-02-09 Thread Martin Schulze
Lionel Elie Mamane wrote: The problem is that kronolith2 depends on version 3 of the horde framework (rather than version 2), that the two versions of horde cannot meaningfully cooperate and there are still some horde2 applications that have not been ported to horde3. Basically, upstream

Bug#349261: Bug#342943: only kronolith2 fixed

2006-01-29 Thread Ola Lundqvist
Hello On Sun, Jan 29, 2006 at 09:33:12PM +0100, Lionel Elie Mamane wrote: On Sun, Jan 29, 2006 at 06:15:23PM +, Neil McGovern wrote: On Sat, Jan 28, 2006 at 09:23:31PM +0100, Martin Schulze wrote: Neil McGovern wrote: A fairly odd bug. It only affects the app if REGISTER_GLOBALS is