-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submissions: Tiny AES #134
Comments
Crypto is one of those things you don't want to do yourself except as a
learning experience. This is mildly dangerous. Does the author have a
strong background in cryptography?
…On Fri, Oct 19, 2018 at 12:49 AM Photosounder ***@***.***> wrote:
Two file public domain AES encryption/decryption in C
https://github.com/kokke/tiny-AES-c
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#134>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AJ_EKHbJ6uAl5xYQ2ZEuWJcBn7tMRxiKks5umVnegaJpZM4Xvqqo>
.
|
Good point which I hadn't considered, however it could still be good for low security applications like decoding a public stream. I found out about Tiny AES from hlsdl which uses Tiny AES to decode streams, perhaps that's why I never thought of security as a problem in such a situation. So this couldn't replace a well security-tested implementation and you wouldn't want to put it in a server, but other than that it could probably be suitable for many things. Either way it definitely suits the philosophy and format of this catalogue of tiny libraries. |
Closing ticket. Link(s) should be already in the list. Please double-check. |
Two-file public domain AES encryption/decryption in C
https://github.com/kokke/tiny-AES-c
The text was updated successfully, but these errors were encountered: