Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 23 Aug 2012 12:29:03 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: [PATCH] Speed up RACF encryption with a pre-computed lookup table

On Thu, Aug 23, 2012 at 12:36:20AM +0200, magnum wrote:
> On 2012-08-23 00:03, magnum wrote:
> > On 2012-08-22 23:24, Knug Carl Gustf wrote:
> >> Dearest computer friends,
> >>
> >> The attached patch speeds up RACF encryption by about 15% on my 64-bit
> >> Apple and Dell devices.
> > 
> > This is committed to git now
> 
> I was warned off-list that you use an obviously fake (stolen) email
> address @expressen.se in that git patch. That might end in trouble. I
> had to mess with public git history to remove it. I am not amused at
> all. Feel free to use a nick and an anonymous or even empty email
> address, but do *not* use one belonging to another person, dammit.

Besides this issue, the copyright status of these patches is not as
clear as I would have liked it to be.  Are the changes subject to
copyright?  If so, we need a copyright holder name or pseudonym and a
statement that the changes fall under the license already specified on
the source file (this statement should preferably be in the form of a
patch to the comment in the source file).  (Maybe this is implied from
the intent of the postings, which was to contribute the changes to the
community.  But it'd be best not to leave any doubt.)  Alternatively,
maybe the changes are too minor to be subject to copyright.  If so, a
statement from the author to this extent (stating that it's the author's
understanding that these changes are too minor to be subject to copyright)
would be of some help, although it is not entirely clear what this means
legally (so the copyright + license approach is best).

Thanks,

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.