From e369fc08906383e6d5c39832f31bb6600a33f887 Mon Sep 17 00:00:00 2001 From: Simo Sorce Date: Fri, 11 Nov 2011 16:59:21 -0500 Subject: Set more strict permissions on keyring We want to confine access to the keyring to the current process and not let root easily peek into the keyring contents. --- src/providers/krb5/krb5_delayed_online_authentication.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/providers') diff --git a/src/providers/krb5/krb5_delayed_online_authentication.c b/src/providers/krb5/krb5_delayed_online_authentication.c index 02f09919a..d5dea3bb4 100644 --- a/src/providers/krb5/krb5_delayed_online_authentication.c +++ b/src/providers/krb5/krb5_delayed_online_authentication.c @@ -258,7 +258,7 @@ errno_t add_user_to_delayed_online_authentication(struct krb5_ctx *krb5_ctx, #ifdef USE_KEYRING new_pd->key_serial = add_key("user", new_pd->user, new_pd->authtok, - new_pd->authtok_size, KEY_SPEC_THREAD_KEYRING); + new_pd->authtok_size, KEY_SPEC_SESSION_KEYRING); if (new_pd->key_serial == -1) { ret = errno; DEBUG(1, ("add_key fialed [%d][%s].\n", ret, strerror(ret))); -- cgit