Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
1–10 of 170 posts
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#2I agree with the premise though its easy to validate if these tools are sending data to a remote dest with the network activity developer tool in any of the major browsers.
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#3I use python -mjson.tool to validate JSON. And JQ to query it.
TLDR Don't use online services, you have no idea what they're doing with your data and if they run the open source version they say they do.
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#4I use python -mjson.tool to validate JSON. And JQ to query it. TLDR Don't use online services, you have no idea what they're doing with your data and if they run the open source version they say they do.
Or rather like with most online services, only feed them data you're comfortable with being shared to everyone.
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#5I use python -mjson.tool to validate JSON. And JQ to query it. TLDR Don't use online services, you have no idea what they're doing with your data and if they run the open source version they say they do.
I find these services useful when I first start using a format with test data. Then I usually look for something local for long term use.
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#6But using google, slack, skype, gitlab, bitbucket... is fine to send sensitive data?
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#7I agree with the premise though its easy to validate if these tools are sending data to a remote dest with the network activity developer tool in any of the major browsers.
Sure, but to be sure you’d have to validate it every time, because the site’s content may have changed since your last visit. Do you?
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#8If you never use production data for anything other than production this stops being a problem. You can put all the dev and staging JWTs you want in to jwt.io at no risk if those things aren't available to the outside world.
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#9But using google, slack, skype, gitlab, bitbucket... is fine to send sensitive data?
No, it definitely isn't. Github (and probably others) will show you big scary warning messages if you commit things like AWS keys.
Re: Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators
#10It sounded like the OP had some solid proof but eventually it boils down to "I'm suspicious".
It's a valid opinion just not an objective one