Created
August 28, 2021 09:50
-
-
Save j4ck-d4n13ls/a50a134a2c11193a8e5793099eaaded8 to your computer and use it in GitHub Desktop.
Explanation about base64
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Great question! When you see base64 string, one way you can tell is if there are 1-3 equal ‘=‘ signs on the end, and this is padding. Ex. a2e771gafs==. This is because all base64 string is usually divisible by 4, and the padding is added so that it can be divisible by 4 properly. For example, the string above is divisible by 4 with the padding: a2e7, 71ga, fs==. Most of the time though base64 decoders don’t need this padding, but if you’re really unsure of what type of string it is, you can put it in a cipher text identifier and it’ll tell you it’s base64, for instance the CyberChef ‘Magic’ option can do that for you. But for me, I can just kinda tell right away because I’ve seen base64 so many times. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment