Andrew Reid <[EMAIL PROTECTED]> writes: > I actually did this twice, since it's not possible, using the > syslog, to distinguish between a randomly-located segfault > (due to pointer-mishandling, for instance) and differences due > to relocation or other invocation-dependent differences. I got > the same backtrace both times.
I'm unable to reproduce this on x86, so it may be a 64-bit-specific issue. > The fact that the segfault was triggered also means that the bug is > still present in the current etch security-fix package, > krb5-admin-server-1.4.4-7etch2, which is now installed on this server. > It was ...-7etch1 which first showed the bug. Yes, I wouldn't expect anything in that security update to address this. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
