Hi, did anyone know, about SuSE had allready fixed this: http://web.mit.edu/kerberos/www/advisories/MITKRB5-SA-2002-002-kadm4.txt Greetings, -- Jörg Henner Fon: +49 (7 11) 48 90 83 - 0 ETES - EDV-Systemhaus GbR Fax: +49 (7 11) 48 90 83 - 50 Libanonstrasse 58 A * D-70184 Stuttgart Web: http://www.etes.de ______________________________________ Inflex - eMail Scanning and Protection Queries to: postmaster@etes.de
On Fri, Oct 25, 2002 at 02:49:22PM +0200, Joerg Henner wrote:
http://web.mit.edu/kerberos/www/advisories/MITKRB5-SA-2002-002-kadm4.txt
We are not affected as we ship Heimdal with krb4 disabled. Olaf -- Olaf Kirch | Anyone who has had to work with X.509 has probably okir@suse.de | experienced what can best be described as ---------------+ ISO water torture. -- Peter Gutmann
On Fri, 25 Oct 2002, Joerg Henner wrote: Hi, The Kerberos package we ship (heimdal) has got similar bug in its source, but our packages are NOT built with kerberos4 support, so installations from packages we provide are NOT affected. You can also determine it by looking whether kadmind binds to port 751, the kerberos 4 specific port. It does not in our case. For the other bugs found in heimdal we have updates for some weeks already. I would point you to SuSE-SA:2002:034 if you have questions regarding this. regards, Sebastian
Hi,
did anyone know, about SuSE had allready fixed this:
http://web.mit.edu/kerberos/www/advisories/MITKRB5-SA-2002-002-kadm4.txt
Greetings,
-- ~ ~ perl self.pl ~ $_='print"\$_=\47$_\47;eval"';eval ~ krahmer@suse.de - SuSE Security Team ~
participants (3)
-
Joerg Henner
-
Olaf Kirch
-
Sebastian Krahmer