c-jwt-cracker
c-jwt-cracker copied to clipboard
base64 decoding problem
Hello,
Their is a reason of not using the base64 decoding function of openssl that is already linked with the binary ? https://github.com/openssl/openssl/blob/5477e84273e5877fad53d6b3fd794ed80c2c9524/crypto/ct/ct_b64.c#L24
Regards, BestPig
No :) Feel free to test it and open a PR :)
On Jul 8, 2019, at 4:50 PM, BestPig [email protected] wrote:
Hello,
Their is a reason of not using the base64 decoding function of openssl that is already linked with the binary ? https://github.com/openssl/openssl/blob/5477e84273e5877fad53d6b3fd794ed80c2c9524/crypto/ct/ct_b64.c#L24 https://github.com/openssl/openssl/blob/5477e84273e5877fad53d6b3fd794ed80c2c9524/crypto/ct/ct_b64.c#L24 Regards, BestPig
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brendan-rius/c-jwt-cracker/issues/8?email_source=notifications&email_token=ABKYTOLQDVJ4U7TK6D5N4RDP6NAZRA5CNFSM4H635N52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G53OMUQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ABKYTOKDXSSVT4R32LBPRLLP6NAZRANCNFSM4H635N5Q.
Fixed by https://github.com/brendan-rius/c-jwt-cracker/pull/9