summaryrefslogtreecommitdiff
path: root/cifs.upcall.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@samba.org>2012-07-20 10:30:50 -0400
committerJeff Layton <jlayton@samba.org>2012-07-20 10:30:50 -0400
commitc44d290f3b5f221e7617bdb409bb8e44ceafef3e (patch)
tree4b54fd2d23627313532fc0f3995fd3192d94bd04 /cifs.upcall.c
parent877701f3cc23df3cb2a293c060bdbf05a87bff6a (diff)
downloadcifs-utils-c44d290f3b5f221e7617bdb409bb8e44ceafef3e.tar.gz
cifs-utils-c44d290f3b5f221e7617bdb409bb8e44ceafef3e.tar.bz2
cifs-utils-c44d290f3b5f221e7617bdb409bb8e44ceafef3e.zip
cifscreds: add a check and warnings for session keyring problems
Many distros do not call into pam_keyinit to set up the session keyring properly at login time. When cifscreds add is used in such a session, the kernel will spawn a new session keyring in which to install the credentials. That keyring will then go away once the cifscreds process exits. Check for this situation by looking to see if the session and user-session keyrings are the same. Throw a warning if so, and add some verbiage to the cifscreds manpage that explains the issue. Also, if the session keyring can't be queried for any reason, then cause the program to error out. Acked-by: David Howells <dhowells@redhat.com> Reported-by: Milan Knížek <knizek.confy@gmail.com> Signed-off-by: Jeff Layton <jlayton@samba.org>
Diffstat (limited to 'cifs.upcall.c')
0 files changed, 0 insertions, 0 deletions