You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2021. It is now read-only.
I was thinking maybe gord could get some use from some type of encryption on the token(s) (even just base64 would be better than nothing) I think it could also get more people to use gord as it's more secure than base-discord in a way
(For example: ripcord)
Why
Well for one, the token(s) are sitting in a config file (json) just raw text so even a skid could figure out how to properly extract it with relative ease
Implementation hints
I was thinking maybe AES256 GCM (like how browsers store their data) It's not unbeatable, hardly close to that. But anything would probably be better than raw text, I made this issue to see what people think of it, I could probably implement it myself if it's a wanted feature.
The text was updated successfully, but these errors were encountered:
What do you want
I was thinking maybe gord could get some use from some type of encryption on the token(s) (even just base64 would be better than nothing) I think it could also get more people to use gord as it's more secure than base-discord in a way
(For example: ripcord)
Why
Well for one, the token(s) are sitting in a config file (json) just raw text so even a skid could figure out how to properly extract it with relative ease
Implementation hints
I was thinking maybe AES256 GCM (like how browsers store their data) It's not unbeatable, hardly close to that. But anything would probably be better than raw text, I made this issue to see what people think of it, I could probably implement it myself if it's a wanted feature.
The text was updated successfully, but these errors were encountered: