light-locker in combination with libpam-krb5 creates incorrectly-named Kerberos credential caches

[Brian Knoll]

When logging into a system locked with light-locker by logging in via libpam-krb5 for Kerberos authentication, the credential cache is created with an incorrect name for the user.

The credential cache is always created as krb5cc_0 under these conditions, when the last part (the numeric part) should be the user ID of the user logging in. For instance, if the user's user ID is 1000, the file should be named krb5cc_1000, not krb5cc_0. The XScreensaver command handles this correctly under the exact same conditions, but light-locker, unfortunately, does not.

Please let me know how I can help.

Thank you,
Brian Knoll

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: light-locker 1.7.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Apr 16 20:01:08 2017
InstallationDate: Installed on 2017-03-11 (36 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian Knoll (brianknoll)]

I just wanted to add a quick note that this is Ubuntu 16.04 where I am seeing this, although the problem has existed for some time now.