4 ms·
Just because you put a warning label on a bad practice doesn't mean it's a good practice. Pumping your passwords through some random code on Github that has a
by criley2 5y ago
Just because you put a warning label on a bad practice doesn't mean it's a good practice.
Pumping your passwords through some random code on Github that has a "be smart" label doesn't make it a good idea.
Would be so easy to imitate you, reupload the code with an exploit. For giggles, if I was making this into a hijack I'd leave all your warnings in and even make them bigger and more obvious, confident in the knowledge that 99%+ of my stolen users wouldn't read the code or would just download the binaries sight unseen.
- balls187 5y ago> Just because you put a warning label on a bad practice doesn't mean it's a good practice. That is such a salient point, generally.
- provobro 5y agoFunny how common it is though
- Fnoord 5y ago1) Clone random git repo on Kali, related to Kali usage. 2) Don't read the code. 3) ??? 4) Forever don't know what or when it happened.
- rhizome 5y agoBREAKING: There is no perfect security. >Would be so easy to imitate you, reupload the code with an exploit. Put your keyboard where your fingers are: do it by tomorrow morning and post here when you're done.
- rhizome 5y agoAnd there ya go.
- wary 5y agoWell, why shouldn't people who already use insecure software with vulnerabilities (LastPass) without the possibility to even audit the code also run some code written by other people they don't know?