linux-kernel - Re: [PATCH] MAINTAINERS: co-maintain random.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHmME9qECnsh0EhV8Zi0vFntqT4OaAbhfOXFFZBjQjzpReNAJg@mail.gmail.com>
Date:   Tue, 7 Dec 2021 16:49:10 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     "Theodore Y. Ts'o" <tytso@....edu>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: co-maintain random.c

On Sat, Dec 4, 2021 at 4:15 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
> On Sat, Dec 4, 2021 at 4:00 PM Theodore Y. Ts'o <tytso@....edu> wrote:
> > Thanks for stepping up.  There's no question that this Fall has been
> > insanely busy for me, and for the past 3 weeks or so, I've been on
> > vacation and Thanksgiving travel, and I'm still catching up on a
> > mountain of e-mail.
> >
> > Something that I think would make sense is that we set up a joint git
> > tree on git.kernel.org, for which we would both have access to push
> > to, and use a group maintainership model much like what other teams
> > have done.  Do you agree?
>
> Sure, that works for me. I had started using zx2c4/random.git. But
> I'll talk to Konstantin about moving that over to a shared repository
> in a group namespace.

We're all set now with
ssh://git@...olite.kernel.org/pub/scm/linux/kernel/git/crng/random.git

Jason