4 ms·
For JWTs, I agree with this stance, since they are security credentials and therefore basically all of them are sensitive information. I don't discourage onlin
by shadowgovt 6y ago
For JWTs, I agree with this stance, since they are security credentials and therefore basically all of them are sensitive information.
I don't discourage online tooling in general. It's a risk/benefit trade-off---No, you shouldn't paste sensitive information into websites run by other people in general, but for non-sensive information where you don't care if the online tool is logging it or not, go for it. There are significant advantages to not having to roll your own for every single thing you need to do.
Carried to its extreme conclusion, "Don't use online tooling" implies "Don't read jvt.me," because who knows what that website is doing while vending you blog posts? clearly, you should roll your own solution by maintaining your own private collection of knowledge that you never share with anyone else. ;)
- tester34 6y ago>For JWTs, I agree with this stance, since they are security credentials and therefore basically all of them are sensitive information. As long as it's prod env and your expiration time is somewhat reasonable, then I don't think it is sensitive at all unless you're storing an actual sensitive informations in them.
- gruez 6y agoSo you're just hoping that there isn't a bad guy on the other side trying to use the credentials in real time? Seems like a bad assumption to make, especially for a site that's specifically made for pasting in JWTs.
- recursive 6y agoNo. No one's hoping anything. It's more like a realization that even if there's a bad guy, they're only going to be able to pwn your dev environment, which has no valuable data in it, and can be replaced with a script.
- deleted 6y ago[deleted]