Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
On 16/09/15 16:15, John Foley wrote: > Is the "Async support" you have listed the same code that Intel > developed for Cave Creek? Or is the Intel contribution planned for a > follow-on release? It is all new code. However I have been developing it in collaboration with Intel. Matt ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
[openssl-dev] OpenSSL 1.1.0 Release Timetable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The OpenSSL Project team would like to announce the publication of our current plans for the OpenSSL 1.1.0 release timetable. This has been included in our release strategy available here: https://www.openssl.org/policies/releasestrat.html Yours The OpenSSL Project Team -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJV+UFyAAoJENnE0m0OYESRZiIH/0oT1j9Ipizi/IVjMSuE6BHY wDdvGuobNSwVUOb61TMxJejI6VX2mowZNjZrc8IdULYIVNnHNyF+iDNBrYQR+KcN bdVE8b1T6nzkKn8e7paI7cqdTYll59vE/p1fJ6uiZb0Y7oOLJ46jWuoRjtQB5xbw bJt8XweO7zR34ungk/kNLb76D8ZSKxGeaJsgD68ymJgOJdFpWHv4/phpg4eLClmk g+8g90COCfwQh9BskhVpUr5fT1+zxo91FA4HgQp3WdRhtcmYAbgoScc6/MWc73MH jIXEGBDURKaR0M2/WLf0Ezz/666ZxltjUhHNtOrhdv6waHmlpjsnYn1M7bxNh+Q= =R/23 -END PGP SIGNATURE- ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
On Wed, Sep 16, 2015 at 11:16:18AM +0100, Matt Caswell wrote: > The OpenSSL Project team would like to announce the publication of our > current plans for the OpenSSL 1.1.0 release timetable. This has been > included in our release strategy available here: > > https://www.openssl.org/policies/releasestrat.html Do you have any idea on what features are gonna be present in 1.1.0? I seem to remember someone mentioning that ChaCha20-Poly1305 support was being worked on by Andy Polyakov and is planned for the 1.1.0 release, is this still the case? Same goes for Curve25519/Curve448. Cheers signature.asc Description: Digital signature ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 16/09/15 15:38, Alessandro Ghedini wrote: > On Wed, Sep 16, 2015 at 11:16:18AM +0100, Matt Caswell wrote: >> The OpenSSL Project team would like to announce the publication >> of our current plans for the OpenSSL 1.1.0 release timetable. >> This has been included in our release strategy available here: >> >> https://www.openssl.org/policies/releasestrat.html > > Do you have any idea on what features are gonna be present in > 1.1.0? I seem to remember someone mentioning that ChaCha20-Poly1305 > support was being worked on by Andy Polyakov and is planned for the > 1.1.0 release, is this still the case? > > Same goes for Curve25519/Curve448. The best place to look for all the 1.1.0 changes that have taken place so far is the CHANGES file. This is available online here: https://www.openssl.org/news/changelog.html That only lists changes that have been committed so far. Off the top of my head other big changes that are coming include: - - State machine rewrite - - Async support - - IPv6 I've not heard anything from Andy in a while on his stuff so I'm not sure what the current state of play is with ChaCha/Poly. There's probably a ton of other stuff that I've forgotten and my colleagues will remind me about. Matt -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJV+YKyAAoJENnE0m0OYESR7QEH/0o7G/zcMWOGBqmw/D4lLi3C +zztovzleUGUsuFDCrpQOuhlDfWixjholnjC8VugCHCYNo+e3Lbx6gYk+BH2Xpz+ Nk7lFqdhAhjwsb3VMklLgYjb1fI7pZTfPhf3giUNPxxs+AOMrYVDjf0UMZlP955d u22ywOZHmf3CHNulhZ5sObT69SR/issxL6aeu2UwNofkcAJ/Q1rhSJICJeKsUCNr Ki9RHpHm4fkG2+97+dZxT4hmGXTQN7d5fAXuTpGZnycWi3p8GWXNi9XrY1PVmiUy +UA6RhLWznswUbXNcGE29ckFnM5BJB8SDOJcUcndi9pTsfQvpcO2ApMTMjxsz2M= =yEk5 -END PGP SIGNATURE- ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
> the current state of play is with ChaCha/Poly. There's probably a ton of other > stuff that I've forgotten and my colleagues will remind me about. I am committing to do all the new crypto if someone better qualified (and there are a couple of folks on the team) don't do so. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
Is the "Async support" you have listed the same code that Intel developed for Cave Creek? Or is the Intel contribution planned for a follow-on release? On 09/16/2015 10:54 AM, Matt Caswell wrote: > > > On 16/09/15 15:38, Alessandro Ghedini wrote: > > On Wed, Sep 16, 2015 at 11:16:18AM +0100, Matt Caswell wrote: > >> The OpenSSL Project team would like to announce the publication > >> of our current plans for the OpenSSL 1.1.0 release timetable. > >> This has been included in our release strategy available here: > >> > >> https://www.openssl.org/policies/releasestrat.html > > > Do you have any idea on what features are gonna be present in > > 1.1.0? I seem to remember someone mentioning that ChaCha20-Poly1305 > > support was being worked on by Andy Polyakov and is planned for the > > 1.1.0 release, is this still the case? > > > Same goes for Curve25519/Curve448. > > > The best place to look for all the 1.1.0 changes that have taken place > so far is the CHANGES file. This is available online here: > > https://www.openssl.org/news/changelog.html > > That only lists changes that have been committed so far. Off the top > of my head other big changes that are coming include: > - State machine rewrite > - Async support > - IPv6 > > I've not heard anything from Andy in a while on his stuff so I'm not > sure what the current state of play is with ChaCha/Poly. There's > probably a ton of other stuff that I've forgotten and my colleagues > will remind me about. > > Matt > > ___ > openssl-dev mailing list > > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev > ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
> There's probably a ton of other stuff that I've forgotten and my > colleagues will remind me about. There's BLAKE2. It already has mature and widely-used source code, including multiple independently-written portable C implementations, and Bill Cox has offered to integrate those into openssl: https://mta.openssl.org/pipermail/openssl-dev/2015-June/001791.html In light of the previous conversation and the way it ground to a halt, I would ask that we do the simple, easy thing now and don't re-raise any of the bike shed questions, so: * Don't implement the parallelized versions (BLAKE2bp and BLAKE2sp). * Don't change the names of the algorithms from "BLAKE2b" and "BLAKE2s" (they are already widely known under those names). * Don't integrate any of the optimized asm implementations, just a single portable C implementation. There. That ought to do it! The previous thread — in which I argued that BLAKE2 is worth supporting — starts here: https://mta.openssl.org/pipermail/openssl-dev/2015-June/001688.html Since I wrote that post, BLAKE2 has been promoted from Internet Draft to RFC. It doesn't have its RFC number yet but should get one any day now: https://datatracker.ietf.org/doc/draft-saarinen-blake2/ Regards, Zooko Wilcox-O'Hearn Founder, CEO, and Customer Support Rep https://LeastAuthority.com — Freedom matters. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Re: [openssl-dev] OpenSSL 1.1.0 Release Timetable
> * Don't implement the parallelized versions (BLAKE2bp and BLAKE2sp). > * Don't change the names of the algorithms from "BLAKE2b" and "BLAKE2s" > (they are already widely known under those names). > * Don't integrate any of the optimized asm implementations, just a single > portable C implementation. If Bill is willing to generate a GitHub PR (or RT with patch), we'll get that into the stream. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
