AES + Integration with `Io` #7

New issue

Open

opened 2023-11-01 12:25:32 +00:00 by jordan · 2 comments

jordan commented

2023-11-01 12:25:32 +00:00

Owner

While it may not strictly be necessary for Telodendria, I think it would be cool to have an AES implementation in Cytoplasm. We should also add an IoAes API which allows streams to be encrypted on the fly using GCM.

Attached is the official NIST specification.

While it may not strictly be necessary for Telodendria, I think it would be cool to have an AES implementation in Cytoplasm. We should also add an `IoAes` API which allows streams to be encrypted on the fly using GCM. Attached is the official NIST specification.

NIST.FIPS.197-upd1.pdf

1.1 MiB

jordan added the

enhancement

label 2023-11-04 19:34:52 +00:00

uis commented

2023-12-02 17:22:37 +00:00

I don't think touching crypto is good idea. Maybe use implementation from TLS library?

jordan commented

2023-12-05 13:05:18 +00:00

Author

Owner

Everyone says not to touch crypto, but somebody has to do it, and honestly it isn't that hard. Conceptually it is not difficult to understand, and the specifications are very thorough. There are also plenty of good, high-quality test suites that can verify the correctness of an implementation.

This for sure isn't something that would replace the already-existing TLS implementations we support in Cytoplasm. It would just be a fun exercise, although someday I would definitely love to implement a TLS library. Understanding cryptography is really important. It's critical for our digital safety and privacy. I think knowing how it works is a good thing because everyone relies on it so heavily and if only a few people understand it, that sounds dangerous.

So I think touching crypto is a great idea. A low-priority idea that I probably won't be able to get to for a long time, but a good idea nonetheless.

Everyone says not to touch crypto, but *somebody* has to do it, and honestly it isn't that hard. Conceptually it is not difficult to understand, and the specifications are very thorough. There are also plenty of good, high-quality test suites that can verify the correctness of an implementation. This for sure isn't something that would replace the already-existing TLS implementations we support in Cytoplasm. It would just be a fun exercise, although someday I would definitely love to implement a TLS library. Understanding cryptography is really important. It's critical for our digital safety and privacy. I think knowing how it works is a good thing because everyone relies on it so heavily and if only a few people understand it, that sounds dangerous. So I think touching crypto is a great idea. A low-priority idea that I probably won't be able to get to for a long time, but a good idea nonetheless.