[ / / / / / / / / / / / / / ] [ dir / animu / doomer / egy / hkpol / jenny / kohl / strek / vichan ][Options][ watchlist ]

/tech/ - Technology

You can now write text to your AI-generated image at https://aiproto.com It is currently free to use for Proto members.
Email
Comment *
File
Select/drop/paste files here
Password (Randomized for file and post deletion; you may also set your own.)
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Expand all images

[–]

 No.1059951>>1060101 [Watch Thread][Show All Posts]

There are several emerging areas (e.g. sensor networks, healthcare, distributed control systems, the Internet of Things, cyber physical systems) in which highly-constrained devices are interconnected, typically communicating wirelessly with one another, and working in concert to accomplish some task. Because the majority of current cryptographic algorithms were designed for desktop/server environments, many of these algorithms do not fit into constrained devices.

NIST has initiated a process to solicit, evaluate, and standardize lightweight cryptographic algorithms that are suitable for use in constrained environments where the performance of current NIST cryptographic standards is not acceptable. NIST has published a call for algorithms (test vector generation code) to be considered for lightweight cryptographic standards. The deadline for submitting algorithms has passed.

NIST will hold a workshop on November 4-6, 2019 in Gaithersburg, MD, to discuss candidate algorithms, including design strategies, implementations, performance, cryptanalysis, and target applications.

July 20-21, 2015 First Lightweight Cryptography Workshop at NIST

October 17-18, 2016 Second Lightweight Cryptography Workshop at NIST

August 11, 2016 (Draft) NISTIR 8114 is published.

October 31, 2016 End of public comment period to Draft NISTIR 8114 Public comments received (August 11 - October 31,2016)

March 28, 2017 NISTIR 8114 Report on Lightweight Cryptography is published.

April 26, 2017 (Draft) Profiles for Lightweight cryptography standardization process is published.

May 14, 2018 (Draft) Submission Requirements and Evaluation Criteria for the Lightweight cryptography standardization process is published..

May 14, 2018 Federal Register Notice is published.

June 16, 2017 Public comments received (April 26 - June 16, 2017)

June 28, 2018 End of public comment period to the submission requirement. Public comments received (May 14-June 28, 2018).

August 27, 2018 Federal Register Notice is published

August 27, 2018 Submission Requirements and Evaluation Criteria for the Lightweight Cryptography Standardization Process is published.

January 4, 2019 Early submission deadline for early feedback

February 25, 2019 Submission dealine

March 29, 2019 Amendment Deadline

April 18, 2019 Announcement of the Round 1 Candidates

November 4-6, 2019 Third Lightweight Cryptography Workshop at NIST

 No.1059955>>1059962 >>1060072


 No.1059962


 No.1059966>>1059967

Watch a cipher win that turns out to be easily breakable with nation state level resources. I don't trust this push for muh micro devices one little bit.


 No.1059967>>1059977

>>1059966

>Watch a cipher win that turns out to be easily breakable with nation state level resources.

This is NIST, not NSA.


 No.1059977>>1059978

>>1059967

Remember Dual_EC_DRBG? Remember how suspiciously they went for Rijndael instead of Serpent?


 No.1059978>>1059992

>>1059977

>Dual_EC_DRBG

That was the NSA.

>Remember how suspiciously they went for Rijndael instead of Serpent?

No.


 No.1059992>>1059996

>>1059978

NIST ignored the warnings about Dual_EC_DRBG which makes them just as culpable.

>No.

They agreed that Serpent was more likely to be secure, but went for AES because muh speed.


 No.1059993>>1059999


 No.1059996

>>1059992

>NIST ignored the warnings about Dual_EC_DRBG which makes them just as culpable.

based. NIST can't be trusted anymore.

>Serpent was more likely to be secure

unbased. Rjindael was secure back then and is secure now. Only butthurt niggers bring up Serpent.


 No.1059999>>1060010

>>1059993

Wow. That oozes butthurt. How many words did they use to say

>serpent is more secure because it has more rounds and it is faster in hardware

LOL

Protip #1: You can increase the rounds of Rjindael.

Protip #2: Hardware performance doesn't matter if your hardware doesn't support it.


 No.1060010>>1060064

>>1059999

>conveniently skips the part where cipher implementations are much easier to audit

No surprise from the CIA nigger.


 No.1060064

>>1060010

> Not modding AES to be CIANIgger-proof

GitGud scrub


 No.1060072

>>1059955

Nice double dubs of documentation


 No.1060101

>>1059951 (OP)

>lightweight crypto

That's an oxymoron.

If a device cannot fully encrypt it's data stream, then it should be designed to be reasonably secure without crypto.

Weak crypto is the same as no crypto in the age of van supercomputers.




[Return][Go to top][Catalog][Screencap][Nerve Center][Cancer][Update] ( Scroll to new posts) ( Auto) 5
14 replies | 0 images | Page ?
[Post a Reply]
[ / / / / / / / / / / / / / ] [ dir / animu / doomer / egy / hkpol / jenny / kohl / strek / vichan ][ watchlist ]