First off, forgive me if this seems like an extremely naive and un-educated question. Any ways, so as above, is it a bad idea? I mean, thinking about it, it doesn't seem like a bad idea. My logic is this:
Sites should store passwords securely anyway, with salts and hashes (and sometimes peppers). Using a standard password such as
Password (for examples sake only) this would be salted and hashed into a much more "unreadable" format for storage when used for an account on a website. If done as it should be, should take a while for anyone to decrypt the password.
Now if I base-64
UGFzc3dvcmQ= and then use that as my password - I already have an additional 3 characters and then included that being salted and hashed - Should create a more secure hashed password? Right?
Does base 64 ultimately cause a password to be any more secure? Do websites either base-64 encode / decode before salting and hashing?
I get that if someone does manage to get the password DB and has a list of all the hashes, and assuming they manage to decrypt my password back to
UGFzc3dvcmQ= I get that its an easy guess to base 64 decode it, as its an obvious looking string.
Ultimately, will it serve me better using base 64 encoded password as opposed to full on cleartext? Also, what if I perform multiple encodings adding additional characters between encodes? For example:
password > UGFzc3dvcmQ= > U**E**GFz**n**c3**C**dv**o**cm**d**Q**E**= > VUVHRnpuYzNDZHZvY21kUUU9