This article will not lecture you on all the various variations of what you can do, or what you shouldn’t do even if you are already doing it wrong. Or how other authentication methods are superior when the “password” is ubiquitous. No, this article, rather, delivers a definitive technical guide…

Significantly improve JWT token security for your customers and you. Including a System JWT Issuing Fingerprint within the JWT token could deliver you significant security improvements without any inconvenience to your users…. It’s a win, win… or if you don’t agree, let me know why! JWT Fingerprint: If you’re creating a JWT…

If you can conceptually understand something then you can apply your own intelligence and logic to that. I hope this article will bring that conceptual understanding. Despite not being a technical article I further hope it will bring low-level, technical and fundamental understanding too. Let’s re-imagine ChatGPT has an image: We understand that LLM’s like ChatGPT…

Why your perfectly checked input is now tainted. And how to FIX IT. You’re an amazing developer, you taint check all of your incoming data and you religiously guard against SQL injection and you check for possible buffer-overflow data patterns and you…you… you check for everything. …you are religious and…

Most "browsers" such as Chrome or Safari will always include this however often with libraries or command line tools which are typically used via bad actors do not set this as standard so the browser fingerprint changes. I now recommend combining the following headers into a MD5 HASH which creates a unique fingerprint which does not inconvience the user: (the fact that MD5 is not considered secure anymore is not relevant in this scenario)