Your message dated Thu, 27 Jun 2013 10:20:53 +1000
with message-id
<CAA0ZO6CveSU58A21wRm6PDtzh0D5QaZz=0zrxfvujnae97f...@mail.gmail.com>
has caused the report #712680,
regarding libkrb5-26-heimdal: hprop broken after upgrade to wheezy
to be marked as having been forwarded to the upstream software
author(s) "<[email protected]>" <[email protected]>
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
712680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712680
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Hello Heimdal-Bugs,
I received this bug report. Do you have any ideas?
This is an old git version. Would the latest help?
Thanks
On 18 June 2013 23:57, Raoul Gunnar Borenius <[email protected]> wrote:
> Dear Maintainer,
>
> after Upgrade from Sqeeze to Wheezy hprop stopped working when using
> it to transfer the database to slaves:
>
> root@master:~# hprop SLAVE
> hprop: krb5_get_init_creds: Failed to find kadmin/hprop@XXX in keytab
> HDB: (unknown enctype)
> root@master:~#
>
> Dumping the database to a file works:
>
> root@master:~# hprop -n out
> root@master:~#
>
> I then recreated the principals
>
> kadmin/hprop
> hprop/SLAVE
>
> (and of course exportet hprop/SLAVE to SLAVE:/etc/krb5.keytab)
>
> but that did not help.
>
> Downgrading heimdal-kdc (including all supporting
> library packages) to version 1.4.0~git20100726.dfsg.1-2+squeeze1 fixed
> the problem.
>
> I then narrowed it down by upgrading the library-packages one by one:
>
> I could upgrade
>
> libasn1-8-heimdal
> libheimbase1-heimdal
> libwind0-heimdal
>
> without triggering the bug, but after upgrading
>
> libkrb5-26-heimdal
>
> the problem was back.
>
> Installing the newest version from sid (1.6~git20120403+dfsg1-3) does not
> improve the
> situation.
>
> I'm now running the following mixed setup which seems to work:
>
> ii heimdal-clients
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii heimdal-kdc
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libasn1-8-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libgssapi2-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libhcrypto4-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libhdb9-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libheimbase1-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libheimntlm0-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libhx509-5-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libkadm5clnt7-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libkadm5srv8-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libkafs0-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libkdc2-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> hi libkrb5-26-heimdal
> 1.4.0~git20100726.dfsg.1-2+ amd64
> ii libotp0-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libroken18-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libsl0-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
> ii libwind0-heimdal:amd64 1.6~git20120403+dfsg1-2
> amd64
>
> If you upgrade and downgrade libkrb5-26-heimdal between
> 1.6~git20120403+dfsg1-2 and
> 1.4.0~git20100726.dfsg.1-2+squeeze1 in this configuration you should be
> able to reproduce the bug.
>
>
> -- System Information:
> Debian Release: 7.1
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500,
> 'stable'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
> 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 libkrb5-26-heimdal depends on:
> ii libasn1-8-heimdal 1.6~git20120403+dfsg1-2
> ii libc6 2.13-38
> ii libcomerr2 1.42.5-1.1
> ii libhx509-5-heimdal 1.6~git20120403+dfsg1-2
> ii libroken18-heimdal 1.6~git20120403+dfsg1-2
> ii libsqlite3-0 3.7.13-1+deb7u1
> ii libssl0.9.8 0.9.8o-4squeeze14
> ii libwind0-heimdal 1.6~git20120403+dfsg1-2
>
> libkrb5-26-heimdal recommends no packages.
>
> libkrb5-26-heimdal suggests no packages.
>
> -- no debconf information
>
--
Brian May <[email protected]>
--- End Message ---
