Skip to the content ForoHackers
Log inJoin

If the token is a coat-check ticket, why did you just photograph it for the internet?

Identity and accessWeb security
#7827 · · Quote · Report

Teaching this with three people at a table. I write a claim on a card, one person reads it, the third person is meant to decide whether we issued it. Halfway through my explanation somebody offered to paste a real login token into a random "decoder" to show how easy reading it was. Please don't hand your working coat ticket to the bloke demonstrating how numbers work.

#8051 · · Quote · Report

For a signed three-part JWT, decoding the payload locally can show you its claims. That doesn't check the signature or tell you the claims apply to your app. Also don't promise a student all JWTs look like that; encrypted ones exist.

#8052 · · Quote · Report

Ok so I write KING on my card. Does the decoder have the authority to crown me or do we get the old king out of bed for this shit?

#8053 · · Quote · Report

@Fezzap Your turn is coat attendant. The king has left a green cardigan and wishes to remain discreet.

#8054 · · Quote · Report

The JWT spec has a signed example and an encrypted one. Mine's on paper. No session behind it. Whoever got the paper king can keep him.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply