It's not true that all widely used crypto implementations are open. Even open source projects themselves depend on closed implementations.
For example, Linux, OpenSSL, GnuTLS, libgcrypt, and dm-crypt may all use AESNI on x86, usually by default [1]. Linux now also uses a closed RdRand [2] RNG if available. The crypto implementation is secret. Even if you had the design, the tools to even make sense of it are themselves proprietary and built on layers of proprietary dependencies. Here's some relevant links: [1] http://www.intel.com/content/www/us/en/architecture-and-technology/advanced-encryption-standard--aes-/aes-ni-ecosystem-update.html [2] http://m.spectrum.ieee.org/computing/hardware/behind-intels-new-randomnumber-generator/0 On Jul 11, 2013 3:32 AM, "danimoth" <danim...@cryptolab.net> wrote: > If yes, ask yourself why *crypto design schemes and implementations are > open and widely known, and only keys are secret.
-- Too many emails? Unsubscribe, change to digest, or change password by emailing moderator at compa...@stanford.edu or changing your settings at https://mailman.stanford.edu/mailman/listinfo/liberationtech
