Re: Speck Cipher Integration with OpenSSL
William Bathurst <[email protected]> Tue, 9 Jan 2018 18:45:36 -0800
| Newsgroups | gmane.comp.encryption.openssl.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============8523499469704136893== Content-Type: multipart/alternative; boundary="------------C6F39AC9A420270A8E707F89" Content-Language: en-US This is a multi-part message in MIME format. --------------C6F39AC9A420270A8E707F89 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Dmitry, We implemented it using the same means as we saw the other ciphers. It was using the EVP functions. This way it could be included or excluded via makefile. Regards, Bill On 1/9/2018 12:23 AM, Dmitry Belyavsky wrote: > Dear William, > > Does SPECK implementation need to be a part of the OpenSSL bundle itself? > It can be added as engine, similar to Russian GOST support, with > minimal patches providing OIDs/NIDs if necessary. > > On Fri, Jan 5, 2018 at 9:52 PM, William Bathurst <[email protected] > <mailto:[email protected]>> wrote: > > Hello All, > > We have open sourced our work in regards to integrating the Speck > Cipher with OpenSSL. Basic information about this cipher can be > found here. > > https://en.wikipedia.org/wiki/Speck_(cipher) > <https://en.wikipedia.org/wiki/Speck_%28cipher%29> > <https://en.wikipedia.org/wiki/Speck_%28cipher%29 > <https://en.wikipedia.org/wiki/Speck_%28cipher%29>> > > SPECK is a lightweight block ciphers each of which comes in a > variety of widths and key sizes and is targeted towards resource > constrained devices and environments. This implementation is > currently implemented using the 128 and 256 block sizes. > > We are currently modifying the source from Apache to OpenSSL open > source licensing for the Speck/OpenSSL integration. Related > repositories such as the cipher itself will remain under the > Apache license. We would love input on the following items: > > 1) Community interest in such a lightweight cipher. > 2) Committers willing to help on the code for improvements. > 3) Information on how to make this available as a patch. > > We have currently integrated Speck with OpenSSL 1.1. We also have > an Speck Client software available for people who wish to test > this software. Future ports will be to mbedTLS. > > We have listed making it available as an issue: > > https://github.com/openssl/openssl/issues > <https://github.com/openssl/openssl/issues> > > OpenSSL/Speck Integration open source repositories: > > https://github.com/m2mi/openssl_speck > <https://github.com/m2mi/openssl_speck> > https://github.com/m2mi/open_speck > <https://github.com/m2mi/open_speck> > > Feel free to contact to to discuss the cipher and uses. > > With Regards, > Bill > > -- > openssl-dev mailing list > To unsubscribe: > https://mta.openssl.org/mailman/listinfo/openssl-dev > <https://mta.openssl.org/mailman/listinfo/openssl-dev> > > > > > -- > SY, Dmitry Belyavsky > > --------------C6F39AC9A420270A8E707F89 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hi Dmitry,</p> <p>We implemented it using the same means as we saw the other ciphers. It was using the EVP functions. This way it could be included or excluded via makefile.</p> <p>Regards,<br> Bill<br> </p> <br> <div class="moz-cite-prefix">On 1/9/2018 12:23 AM, Dmitry Belyavsky wrote:<br> </div> <blockquote type="cite" cite="mid:CADqLbzKP__2Neyt8x5e44xSC2PgzWth4bd+XKmL0VnS2gyzDDA@mail.gmail.com"> <div dir="ltr">Dear William, <div><br> </div> <div>Does SPECK implementation need to be a part of the OpenSSL bundle itself? </div> <div>It can be added as engine, similar to Russian GOST support, with minimal patches providing OIDs/NIDs if necessary.</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Fri, Jan 5, 2018 at 9:52 PM, William Bathurst <span dir="ltr"><<a href="mailto:[email protected]" target="_blank" moz-do-not-send="true">[email protected]</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello All,<br> <br> We have open sourced our work in regards to integrating the Speck Cipher with OpenSSL. Basic information about this cipher can be found here.<br> <br> <a href="https://en.wikipedia.org/wiki/Speck_%28cipher%29" rel="noreferrer" target="_blank" moz-do-not-send="true">https://en.wikipedia.org/wiki/<wbr>Speck_(cipher)</a> <<a href="https://en.wikipedia.org/wiki/Speck_%28cipher%29" rel="noreferrer" target="_blank" moz-do-not-send="true">https://en.wikipedia.org/wiki<wbr>/Speck_%28cipher%29</a>><br> <br> SPECK is a lightweight block ciphers each of which comes in a variety of widths and key sizes and is targeted towards resource constrained devices and environments. This implementation is currently implemented using the 128 and 256 block sizes.<br> <br> We are currently modifying the source from Apache to OpenSSL open source licensing for the Speck/OpenSSL integration. Related repositories such as the cipher itself will remain under the Apache license. We would love input on the following items:<br> <br> 1) Community interest in such a lightweight cipher.<br> 2) Committers willing to help on the code for improvements.<br> 3) Information on how to make this available as a patch.<br> <br> We have currently integrated Speck with OpenSSL 1.1. We also have an Speck Client software available for people who wish to test this software. Future ports will be to mbedTLS.<br> <br> We have listed making it available as an issue:<br> <br> <a href="https://github.com/openssl/openssl/issues" rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/openssl/ope<wbr>nssl/issues</a><br> <br> OpenSSL/Speck Integration open source repositories:<br> <br> <a href="https://github.com/m2mi/openssl_speck" rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/m2mi/openss<wbr>l_speck</a><br> <a href="https://github.com/m2mi/open_speck" rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/m2mi/open_s<wbr>peck</a><br> <br> Feel free to contact to to discuss the cipher and uses.<br> <br> With Regards,<br> Bill<span class="HOEnZb"><font color="#888888"><br> <br> -- <br> openssl-dev mailing list<br> To unsubscribe: <a href="https://mta.openssl.org/mailman/listinfo/openssl-dev" rel="noreferrer" target="_blank" moz-do-not-send="true">https://mta.openssl.org/mailma<wbr>n/listinfo/openssl-dev</a><br> </font></span></blockquote> </div> <br> <br clear="all"> <div><br> </div> -- <br> <div class="gmail_signature" data-smartmail="gmail_signature">SY, Dmitry Belyavsky</div> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> </blockquote> <br> </body> </html> --------------C6F39AC9A420270A8E707F89-- --===============8523499469704136893== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev --===============8523499469704136893==--