[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 7 Jul 2018 14:11:05 +0200
From: Solar Designer <solar@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: [PATCH 0/5] pam_tcb update
On Sat, Jul 07, 2018 at 02:37:58AM +0300, Dmitry V. Levin wrote:
> On Fri, Jul 06, 2018 at 03:33:28PM +0200, Solar Designer wrote:
> > On Thu, Jul 05, 2018 at 02:29:19AM +0300, Dmitry V. Levin wrote:
> > > I've got a few patches for pam_tcb. Tested in Sisyphus.
> >
> > Thanks. I think we should get these into Owl-current (even though these
> > changes don't matter much for Owl yet), test them a bit more in there,
> > then release tcb 1.2. For the testing in Owl-current, use version
> > numbers like 1.1.x or even 1.1.9.x (indicating that we're closer to 1.2
> > than to 1.1).
>
> OK, but I'm not sure I remember correctly how to get anything into
> Owl-current.
Well, I hope you'll manage.
> > For the release, we also need updated LICENSE (copyright years) and
> > ChangeLog. We could also use this opportunity to relax the license for
> > our newly written source files (not inherited from pam_unix). There's
> > no reason to subject them to 3-clause BSD or GPL (BTW, of unspecified
> > version) that the whole thing is under for historical reasons - we can
> > as well use 0-clause BSD for them (add such comments to the files
> > themselves). If we go for this, we need to ask Rafal for his approval.
>
> I don't mind changing the license this way, although I don't see any
> practical difference so far.
I thought of this in context of possible contributions to and/or fork of
Alpine Linux, where tcb's code for accessing /etc/tcb safely could
become part of the passwd program. (I think Alpine doesn't use PAM.)
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
