[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANO7a6yeDaJhGX9xCzYC3awrj1yf1eJkY_V=5=Kh22a_YK8J2A@mail.gmail.com>
Date: Thu, 18 Apr 2013 21:01:22 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: doc/ licensing
On Thu, Apr 18, 2013 at 8:31 PM, Solar Designer <solar@...nwall.com> wrote:
> Ideally, we need to re-license our documentation under more relaxed terms
> than GPLv2.
I am not sure how we are going to do it. Are we going to include
license text in each of these files?
> OFFICE unclear; Dhiru?; documentation
> README.mozilla unclear; Dhiru?; documentation
> README.pwsafe unclear; Dhiru?; documentation
IIRC, I have authored these files.
> SIPcrack-LICENSE N/A; Martin J. Muench; documentation; Martin's copyright statement and 3-clause BSD license
This is the license text itself ;)
> pdfcrack_README GPLv2+; Henning Noren; documentation; GPLv2+ is per pdfcrack license, this file also says that parts of pdfcrack code are "copyright 1995-2006 Glyph & Cog, LLC" and that "PDF data structures, operators, and specification" are copyrighted by Adobe, however "data structures" are probably not subject to copyright, and pdfcrack (and thus JtR) probably does not include the rest
> pdfcrack_TODO GPLv2+; Henning Noren; documentation; GPLv2+ is per pdfcrack license
These files can be safely removed since we no longer use the pdfcrack "engine".
--
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.
