[37709] in Kerberos
Re: KEYRING:persistent and ssh
daemon@ATHENA.MIT.EDU (Tina Harriott)
Tue Sep 27 09:20:27 2016
MIME-Version: 1.0
In-Reply-To: <CAJWqosUjoFaMrDOOoAGJ6pOUEpjK0tL1kZrK94KF0PWkw8L1Fw@mail.gmail.com>
From: Tina Harriott <tina.harriott.math@gmail.com>
Date: Tue, 27 Sep 2016 15:20:11 +0200
Message-ID: <CAH5-_XNciORghCcUszfm33ASb53YLiod5GiXkECqmo+kgdxxcg@mail.gmail.com>
To: t Seeger <tseegerkrb@gmail.com>
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On 16 September 2016 at 16:02, t Seeger <tseegerkrb@gmail.com> wrote:
> Hello,
>
> i have a little problem with the 'KRB5CCNAME' environment variable. I set
> the default_ccache_name to KEYRING:persistent:%{uid} but if i login it is
> set to "file:/tmp/krb5cc_${uid}_XXXXXXXXXX" cause ssh sets the KRB5CCNAME
> to file:/tmp/krb5cc_${uid}_XXXXXXXXXX...
> I found a workaround with adding "unset KRB5CCNAME" to /etc/bash.bashrc but
> this is not very nice.
> Did anyone had a similar problem and found a solution?
>
> Many thanks in advance and best regards
> ________________________________________________
> Kerberos mailing list Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
FYI KEYRING: will be removed in future versions of Linux kernel
because of the ongoing design defects.
Also, KEYRING is not secure, under certain scenarios (DOCKER&et al)
unrelated users/uids can obtain the secure data.
Tina
--
Tina Harriott - Women in Mathematics
Contact: tina.harriott.math@gmail.com
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
