Sounds like you’re proposing WebAuthn which already exists. Keep in mind that there are attacks against RSA with PKCS1 padding. I’d use a more secure cryptographic primitive than RSA (I.e. elliptic curves) - there’s a reason cryptographic experts don’t look towards RSA these days.
this post was submitted on 22 Aug 2023
2 points (100.0% liked)
Cryptography @ Infosec.pub
438 readers
1 users here now
Questions, answers, discussions, and literature on the theory and practice of cryptography
Rules (longer version here)
- Stick to cryptography / infosec
- Be a good netizen - be kind, act in good faith, maintain high quality, don't mislead
- Link directly to original sources
- Don't use us to cheat on challenges or tests!
- Crypto review requests must show the algorithm
- CTF / challenges and puzzles must use modern crypto
- Avoid making duplicate posts
- All use of AI / LLM and their prompts MUST be disclosed in your submissions and comments
##Related resources;
- Reddit cryptography forums 1 & 2; /r/crypto /r/cryptography
- Cryptology ePrint archive
- Discussion site for ePrint papers
- Libera Chat's IRC:s #crypto - (IRC protocol URL)
- Metzdowd cryptography mailing list
- Randombit cryptography mailing list
- StackExchange cryptography community
founded 2 years ago
MODERATORS
Is there a particular reason you want to use your own implementation instead of JWT? If you just want an alternative to JWT, there is also PASETO.
I wanted to let my users encrypt their payload with my public key so only I can decrypt that payload. Just like how PGP works. Eventually I've used hybrid encryption with AES for encrypting the payload and RSA for encrypting AES secret key.
Just to let you know this post is almost 2 years old :)