WARNINGS

[hakavlad]

Add WARNINGS to the README.

For example see https://github.com/hakavlad/tird/blob/main/README.md#warnings

Such warnings are intended to help the user more accurately assess the capabilities of the program and avoid some errors.

It would be:

Warnings

• ⚠️ The author is not a cryptographer.
• ⚠️ Picocrypt has not been independently audited.
• ⚠️ Picocrypt probably won't help much when used in a compromised environment.
• ⚠️ Picocrypt probably won't help much when used with short and predictable keys.
• ⚠️ Sensitive data may leak into the swap space.
• ⚠️ Picocrypt does not erase sensitive data from memory after use.
• ⚠️ Picocrypt does not encrypt Comments by default.
• ⚠️ Actually Picocrypt does not protect you from three-letter agencies like the NSA: defense against three-letter agencies requires a comprehensive approach, not just the use of one tool.
• ⚠️ After the audit, changes may be made that violate backward compatibility to resolve identified issues.

[HACKERALERT]

@hakavlad @1z5q @CodeCracker-oss @njhuffman @BigPanda97 sorry to ping you guys, I won't do it frequently and only during the early phases of this organization. This seems like a nice and simple task for testing out the PR flow. If someone wants to, feel free to add a little bit of text to the readme and open a PR. Then we can test to make sure that 3 reviewers are required to merge.

[njhuffman]

I'll put up a pr next weekend, if no one gets to it sooner.