phc-discussions - Re: [PHC] PHS API copyright?

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 for Android: free password hash cracker in your pocket

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

Date: Wed, 14 May 2014 20:47:08 +0200
From: Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] PHS API copyright?

The submissions all include intellectual property statements, so it
seems that the PHC website only requires a disclaimer of liability. I
added that one, copied verbatim from eSTREAM:

"The information on this web site is provided as is, and no guarantee
or warranty is given or implied that the information is fit for any
particular purpose. The user thereof uses the information at his or
her sole risk and liability."

https://password-hashing.net/disclaimer.html

On Mon, May 12, 2014 at 8:38 PM, Marsh Ray <maray@...rosoft.com> wrote:
> From: Krisztián Pintér [mailto:pinterkr@...il.com]
>>
>> i was under the impression that the PHC function have
>> descriptive purposes only, not intended to be actually
>> used. it is a programmer's way describing how to set
>> up and invoke the alogrithm in a general way.
>
> By having the same signature, it also allows test programs to swap out function pointers for maximally-fair comparisons.
>
> While I too am shocked by the recent court ruling about APIs, it's hard to imagine it will be a huge impact on PHC. Jean-Philippe is "discussing this with qualified people".
>
> Don't worry, we'll do the right thing.
>
> - Marsh
> ------------------
> My personal opinions only, boilerplate disclaimers apply.