Re: punycode licensing

2019-07-10 Thread Dmitry Belyavsky
Dear Tim, Formally I am a contributor with a signed CLA. I took a code definitely permitting any usage without any feedback, slightly modified it (at least by openssl-format-source and splitting between header and source), and submitted it as my feedback to OpenSSL. I still think that it will be

Re: punycode licensing

2019-07-10 Thread Salz, Rich
I will take the hint and stop commenting on this thread.

SHA-256 assembly language optimization

2019-07-10 Thread Paul Sheer
Hello, I'd like to ask about improving SHA-256 performance: I see on this page, https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/sha-256-implementations-paper.pdf Intel gives a reference implementation of SHA-256 for its own processors. How is OpenSSL's implementation

Re: punycode licensing

2019-07-10 Thread Tim Hudson
Previous assertions that if the license was compatible that we don't need a CLA in order to accept a contribution were incorrect. You are now questioning the entire purpose of contributor agreements and effectively arguing they are superfluous and that our policy should be different. You are (of

Re: punycode licensing

2019-07-10 Thread Salz, Rich
Thank you for the reply. >The license under which the OpenSSL software is provided does not require >"permission" to be sought for use of the software. See

Re: Vote FYI: Remove function codes from error reporting functions as per PR#9058

2019-07-10 Thread Richard Levitte
The vote closed today, with the following result: +1: 4 0: 3 (where one is a -0) -1: 0 The vote passes. Cheers, Richard On Thu, 04 Jul 2019 18:01:59 +0200, Richard Levitte wrote: > > topic: Remove function codes from error reporting functions as per PR#9058. > comment: Discussed