Re: Speck Cipher Integration with OpenSSL

--===============6571524676654866834==
Content-Type: multipart/signed; boundary="nextPart5620018.EvUFcXy35C"; micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPart5620018.EvUFcXy35C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

On Monday, 8 January 2018 22:10:07 CET William Bathurst wrote:
> Hi Hanno/all,
>=20
> I can understand your view that "more is not always good" in crypto. The
> reasoning behind the offering can be found in the following whitepaper:
>=20
> https://csrc.nist.gov/csrc/media/events/lightweight-cryptography-workshop=
=2D20
> 15/documents/papers/session1-shors-paper.pdf
>=20
> I will summarize in a different way though. We wish to offer an
> optimized lightweight TLS for IoT. A majority of devices found in IoT
> are resource constrained, for example a device CPU may only have 32K of
> RAM. Therefore security is an afterthought by developers. For some only
> AES 128 is available and they wish to use 256 bit encryption. Then Speck
> 256 would be an option because it has better performance and provides
> sufficient security.

so security is afterthought, but they got out of their way to use "more=20
secure" (debatable) option?

sorry, that does not hold water
=2D-=20
Regards,
Hubert Kario
Senior Quality Engineer, QE BaseOS Security team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purky=C5=88ova 115, 612 00  Brno, Czech Republic
--nextPart5620018.EvUFcXy35C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEYeeuxEU+3unL/K+dkqjRuAHS9fUFAlpVAHMACgkQkqjRuAHS
9fXLahAAi/P4qmvrKUYgVd8m1YyT5mxdfYpfd1PI2d7bElt4r+AeynPIT3mm5b46
dJdbM1nzpC4sluS/eBj4NnTqgaOSrWj3ce+tfijnMv20b7GueMM9qx928jFlkvk9
YuiViI+WxquyfP0mvQSQxBgiwQiJ9ZrqW2TnG74ZzTDSDPVr0wk5aFqhpc2TpcME
/XKU8Sq4a0QmVxK4+zMiwHdEi91tjjZdRprx8WVug7wJN4NrQMeXyd6i9Gkw76kT
kors6CMxzbuWtba0pXUx/RyvYif68jii0PD4R4kUlbqFihaY9CWz1Rp7OPNUCcta
iMw4dtyBDWB2VGoJpHaF8EJGsyIzIhoJB7QtdsMTTI3+zIoDtr6U8OhV+QYmA8AP
DRKtssBj/uIYIWcLUlMWPT9B7QsBQ5zbpqkG6TKA81VCuccPMPmu2OMJ7zd4D/By
KFICz/tMSsOZkYzYf9j5fmj8CuwZMtFK+/BDbd0YCuUMXX66I2FIryH6CacwbBgr
MJMwd9IpErgr4E83bJfZ4eTJrXoapz6s2TC4EUDy41EdE5034vKLuNqzEYswl33B
G96jqMKJ7rh7J1IfarmuQHArlkrWRMg8tsH46UG2ubeIu+6/1mRCjmjd+/aifTwn
5sCZe0u4XbE4kXRCcn5IYOeRNKYFx7hjXSNh6S5zIO8vpHnPcwU=
=BkQ9
-----END PGP SIGNATURE-----

--nextPart5620018.EvUFcXy35C--


--===============6571524676654866834==
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

--===============6571524676654866834==--