[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131001143512.GA11265@lonestar>
Date: Tue, 1 Oct 2013 20:05:12 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: MIT-licensed files
On 10/01/13 at 03:18pm, Solar Designer wrote:
> Besides the (now changed) 7z format, there are a few more source files
> with MIT license. I think most of those should be changed to use our
> standard cut-down BSD license wording instead. Only those files where
> we're using code from third-party authors (not direct contributors to
> JtR) should retain their original licenses (so if they were under MIT
> license, it makes sense to keep our changes under MIT license too).
>
> Here are the files:
>
> src/agilekeychain_fmt_plug.c
> src/opencl_agilekeychain_fmt.c
>
> src/lastpass_sniffed_fmt_plug.c
>
> src/opencl_blockchain_fmt.c
>
> src/blockchain_fmt_plug.c
>
> src/cloudkeychain_fmt_plug.c
>
> run/1password2john.py
>
> run/office2john.py
(I have lazily snipped too many lines)
The licensing problems in these files should be fixed now. I have
committed my fixes to the "bleeding-jumbo" branch.
Do my changes look OK?
--
Dhiru
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.
