jose-util(1)
π NAME π
jose-util β bestie, it's a command-line utility for dealing with JOSE objects. That's the whole vibe. Manual section 1, entry one, no notes. π
π SYNOPSIS π
jose-util [<flags>] <command> [<args> ...]
π¦ DESCRIPTION π¦
okay so go-jose is out here trying to give the world a full implementation of the Javascript Object Signing and Encryption set of standards. Iconic behaviour honestly.
That means it's got your back with support for JSON Web Encryption, JSON Web Signature, and JSON Web Token standards. Three whole standards, one little CLI. Ate. π₯
π OPTIONS π
These are your top-level flags, the ones that work before you even pick a command. β¨
--helpβ shows you context-sensitive help. Obsessed with a tool that knows what you're looking at. She's also got--help-longand--help-manif you want the extended director's cut π--key=KEYβ the path to your key file, if that applies to what you're doing. AcceptsPEM,DER, orJWKformat. Pick your fighter π--in=INβ path to your input file, when relevant. If you leave it out she just reads fromstdin, chill like that.--out=OUTβ path to your output file, when relevant. Leave it out and she writes tostdout. Effortless queen. π--versionβ shows the application version. Simple, honest, no gatekeeping.
π encrypt β encrypt a plaintext, output ciphertext
encrypt --alg=ALG --enc=ENC [<flags>]
--alg=ALGβ the key management algorithm. LikeRSA-OAEP, for example.--enc=ENCβ the content encryption algorithm. LikeA128GCM, for example.--fullβ use the JSON Serialization format instead of compact. She's giving structured, she's giving verbose, she's giving full. β¨
π decrypt β decrypt a ciphertext, output plaintext
That's it. That's the job. Ciphertext goes in, plaintext comes out. Understood the assignment. π«Ά
βοΈ sign β sign a payload, output signed message
sign --alg=ALG [<flags>]
--alg=ALGβ the key management algorithm. LikeRSA-OAEP, for example.--fullβ use the JSON Serialization format instead of compact.
β
verify β verify a signed message, output payload
You give her a signed message, she gives you back the payload. Trust but verify, bestie. π
πͺ expand β expand JOSE object to JSON Serialization format
expand [<flags>]
--format=FORMATβ tells her what type of message you want expanded. It's eitherJWSorJWE, and it defaults toJWEif you don't say.
𧬠b64decode β decode a base64-encoded payload
And she's smart about it too β this one auto-selects standard/url-safe. No cap, she just figures it out. πΈ
π generate-key β generate a public/private key pair in JWK format
generate-key --use=USE --alg=ALG [<flags>]
Fresh keys, made to order, JWK format, house-made. π
--use=USEβ the desired public key usage (that's theuseheader). It's one of[enc sig]β pick one, you can't have both.--alg=ALGβ the desired key pair algorithm (that's thealgheader).--size=SIZEβ the key size, in bits. Like2048if you're generating an RSA key, for example.--kid=KIDβ an optional Key ID (thekidheader). If you don't set one, she generates a randomkidfor you. Honestly? Queen behaviour. π
π REPORTING BUGS π
Found a bug? Spotted something cursed? Please visit the riscemu issues tracking system at:
https://github.com/go-jose/go-jose/issues
They'd genuinely love to hear from you, fr fr. π
π AUTHORS π
This manual page was written by Bo YU <tsu.yubo@gmail.com> for the Debian project. Respect the author, she did the work. π«Ά
and that's the whole page, bestie β¨ this was jose-util, version 4.1.4, dated 17 July 2026. stay encrypted, stay iconic, mwah π
π¦ where this page comes from
- ubuntu stonking: jose-util 4.1.4-2 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms