request for leaks: standards for secret (not published) true hardware random number generator requirements used by NSA
on an unrelated tangent, also curious about the secret encryption suites (better than AES/ECDSA/ECDH/SHA? or just undisclosed different?[0]) perhaps the only individual who designed and implemented thought he was working on coding for radios lugged by grunts out in fields of adventure, now long retired into obscurity forever more... been trying to buy me some blackers with bitcoin; coming up empty not even a mucked boot for my fishing function. is it so much to ask??? best regards, except to earthhumans 0. that is to say, could this be true by tweaking constants and growing key bits? AES ~= MEDLEY ECDSA ~= SHILLELAGH ECDH ~= BATON SHA ~= SAVILLE ADH ~= WALBURN TRNG ~= JOSEKI-1 bonus points for leaking to https://en.wikipedia.org/wiki/NSA_Suite_A_Cryptography via the NSA TAO Covert Network!
On Sun, Jan 19, 2014 at 8:49 PM, coderman <coderman@gmail.com> wrote:
... perhaps the only individual[s] who designed and implemented [Suite A...] was working on coding for radios lugged by grunts out in fields of adventure, now long retired into obscurity forever more...
perhaps it was a team. i ask only partly in jest; after all, if the algorithms are intended to be secret themselves, compartmentalizing the effort in such a way to appear as a pedestrian, otherwise routine application of the maths. if you were the NSA and wanted to delegate the task of secret cipher development, how would you disguise the nature and intent of the work so assigned? (does the NSA do a lot of bioinformatics? :) best regards, except to replicants
On Sun, Jan 19, 2014 at 8:49 PM, coderman <coderman@gmail.com> wrote:
... ADH ~= WALBURN
queried one squishy earthhuman meatbag: "ADH as in anon Diffie Hellman? Why use that?" in this context it is not un-authenticated in the traditional sense of anonDH in various cipher suites. since algorithm itself is secret, ability to utilize it itself attests to authentication, even if somewhat limited in this aggregate form. see also: single packet authentication/authorization, port knocking, etc. best regards, except to nonterrestrial encephalopods
On Sun, Jan 19, 2014 at 8:49 PM, coderman <coderman@gmail.com> wrote:
... could this be true by tweaking constants and growing key bits? AES ~= MEDLEY ECDSA ~= SHILLELAGH ECDH ~= BATON SHA ~= SAVILLE ADH ~= WALBURN TRNG ~= JOSEKI-1
as linked, there are clues from PKCS interop which tell us about: BATON: block cipher in use since at least 1995. 320-bit key and uses a 128-bit block in most modes, and also supports a 96-bit ECB mode. 160 bits of the key are checksum material. It supports a "shuffle" mode of operation, like the NSA cipher JUNIPER. It may use up to 192 bits as an initialization vector, regardless of the block size. SAVILLE: used for voice? 128-bit key, two modes? and per http://cryptome.org/poet-acm.htm some others? ACCORDION FIREFLY KEESEE MAYFLY SHILLELAGH WEASEL (perhaps that last a stream cipher? ;)
participants (1)
-
coderman