Skip to content
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

Security Problem: Insecure encryption in LSLSystemAPI.cs #105

Open
zauberparacelsus opened this issue Apr 29, 2020 · 0 comments
Open

Security Problem: Insecure encryption in LSLSystemAPI.cs #105

zauberparacelsus opened this issue Apr 29, 2020 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers low hanging fruit Tasks that should be good to get your feet wet, but might not be priority for the core devs.

Comments

@zauberparacelsus
Copy link
Contributor

During the days of InWorldz, I had added a multi-function string processing/encoding function called iwStringCodec. One of its capabilities was that it could perform AES encryption and decryption.

However, in rushing to get the function completed, I made a very amateur-hour mistake: never base your encryption on code that was copied & pasted from StackOverflow.

So, in order to ensure that the code is actually secure, the encryption functions need to be rewritten by someone who knows what they are doing [IE: not me].

The relevant functions are:

@kf6kjg kf6kjg added bug Something isn't working good first issue Good for newcomers low hanging fruit Tasks that should be good to get your feet wet, but might not be priority for the core devs. labels Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers low hanging fruit Tasks that should be good to get your feet wet, but might not be priority for the core devs.
Projects
None yet
Development

No branches or pull requests

2 participants