-
Notifications
You must be signed in to change notification settings - Fork 27
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
Hello From No Text To Speech! #73
Comments
@andro2157 You've been caught! https://www.youtube.com/watch?v=y8crpVOLcpY |
Dumb vid tbh. Arguments:
At the end, no program can protect you from yourself and you should always know what you download and execute. |
I completely agree. The arguments made were absolutely ridiculous. |
My reply to NTTS : Hi! DiscordTokenProtector (later refered as "DTP") dev here, TLDR : DTP protects the TOKEN not the account, nor all your pc. And the bypass has been patched a long time ago. I just wanted to clarify some points. First of all, the main point of DTP is to protect your Discord token. Not your banking details or other sensitive information on your computer. Therefore, with no surprise, it will indeed only protect you from Discord grabbers. Something that does somewhat well from what you've shown. This software is opensource, so anyone can check the code, and compile their own versions of it. That's literally why I opensourced this project. And even if I were to push something malicious, it would be obvious in the diffs of the release. And there's no auto update, so it's won't infect every computer that downloaded DTP. About the "bypass", it has been patched for over a year now. I have seen many grabbers (even recent ones) that use this "bypass". Firstly, the bypass only works if you give admin permissions (with UAC) to the grabber - and if you do so, you've got much more stuff to worry about than just your Discord token as you stated. And second of all, even if you give admin perms, all it does is to remove DTP, and the grabber is NOT able to decrypt the token that is securely stored. The goal for the end user is that they can be protected from one vector of attack that is commonly used by grabbers. Yes, there are other ways (QR code phishing, RATs with full control of the PC, ...), but DTP's point is not to protect your Discord account, only your Discord TOKEN that is stored on your computer. |
I completely agree, NTTS usually doesn't do the best job of reviewing crap, which is why I don't bother watching him anymore. Especially after this video. The points he brought up where so stupid. |
But he is right, that the protector can be bypassed very easily. |
@Serpensin pls, read andro's message again. If you have UAC fully-fully disabled or if you stupidly give any program admin rights. Maybe you shouldn't care about your Discord client, cuz no one wanna update virus to bypass low-popular tool. But you should be aware of all other data on PC |
I've read that. |
Then read goodpractice.md. https://github.com/andro2157/DiscordTokenProtector/blob/master/goodpractice.md And if you don't need it, then you don't need it. It's easy as that |
Just not get token logged in the first place... |
You think that of me? No. I am the one, who grabs.
pierrelasse ***@***.***> schrieb am Mi., 15. Mai 2024, 06:22:
… Just not get token logged in the first place...
—
Reply to this email directly, view it on GitHub
<#73 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APD5CCX2SEVPOZK4HYLNKVLZCLPITAVCNFSM6AAAAAA74JJFT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJRGU2TGNZXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No description provided.
The text was updated successfully, but these errors were encountered: