[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#783790: kerberos ticket written to wrong file



Package: kscreensaver
Version: 4:4.14.2-1
Severity: normal

On a system with kerberos authentication (through pam-krb5)

Login through kdm, the ticket is written in a file (eg
/tmp/krb5cc_4468_CkfHCh) and environment variable KRB5CCNAME is setup
accordingly.

Ater unlocking the screen, the ticket is written in another file, eg
/tmp/krb5cc_pam_wFd4iA and original ticket file deleted.

This makes ALL kerberos using programs client lose their way to get
authenticattion through kerberos, unless the ticket file is manually
renamed.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'stable'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kscreensaver depends on:
ii  kde-runtime               4:4.14.2-2
ii  kde-workspace-bin         4:4.11.13-2
ii  libc6                     2.19-18
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglu1-mesa [libglu1]    9.0.0-2
ii  libkdecore5               4:4.14.2-5
ii  libkdeui5                 4:4.14.2-5
ii  libkexiv2-11              4:4.14.2-1
ii  libkio5                   4:4.14.2-5
ii  libkparts4                4:4.14.2-5
ii  libkscreensaver5          4:4.11.13-2
ii  libqt4-opengl             4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqtcore4                4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqtgui4                 4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libstdc++6                4.9.2-10
ii  libx11-6                  2:1.6.2-3

Versions of packages kscreensaver recommends:
ii  kde-window-manager  4:4.11.13-2

Versions of packages kscreensaver suggests:
ii  kscreensaver-xsavers  4:4.14.2-1

-- no debconf information


Reply to: