[37697] in Kerberos

home help back first fref pref prev next nref lref last post

Remove KEYRING from kernel! Re: KEYRING:persistent and ssh

daemon@ATHENA.MIT.EDU (Cedric Blancher)
Wed Sep 21 14:20:28 2016

MIME-Version: 1.0
From: Cedric Blancher <cedric.blancher@gmail.com>
Date: Wed, 21 Sep 2016 20:20:07 +0200
Message-ID: <CALXu0UejOGVj55+FMX0qYkHF8ZWe02f=ZwSgWfL2_0PAPBnovA@mail.gmail.com>
To: Russ Allbery <eagle@eyrie.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "<kerberos@mit.edu>" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

Depends what you call "nice". KEYRING is a gaping security hole in
case of Docker or chrooted apps because it "leaks" keys through the
isolation AND does this randomly even into other Docker instances.

IMO the whole KEYRING stuff should be removed from the Linux kernel
and replaced with a sane design.

Ced

On 21 September 2016 at 20:03, Russ Allbery <eagle@eyrie.org> wrote:
> tseegerkrb <tseegerkrb@gmail.com> writes:
>
>> Thanks for your help. Is my setup so special (kerberos/OpenLDAP/sssd/sshd)
>> nobody using it? I think i will ask debian/ubuntu or the openssh
>> maintainer for help.
>
> It's sadly quite unusual to use non-FILE ticket caches.  I wish it
> weren't, since KEYRING has nice security properties, but it's relatively
> new and the rest of the world has definitely not adapted yet.
>
> --
> Russ Allbery (eagle@eyrie.org)              <http://www.eyrie.org/~eagle/>
> ________________________________________________
> Kerberos mailing list           Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos



-- 
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post