Image via Wikipedia
What a few less people know is that base64 is the same as plaintext. Not only is it a very simple two way hashing function, if it can be called that, it's certainly not encryption, what's worse is that any coder worth their salt can recognise base64 encoding at a glance. Decoding it is trivial, many tools online can do it.
On top of all of that, django already stores its user's passwords very securily with one-way hashing AND salting.
So what the fuck am I doing trying to save passwords in base64?
The reason is in fact quite simple: External API's.
Here's the problem: what do you do when your service is accessing a third party API, which doesn't support OAuth or OAuth is impractical in your situation for various reasons and the API doesn't support some other means of logging in with a hashed password. Basically, the only way you can access this API is if you know the user's password?
The obvious solution is to fuck it and store plain-text passwords. Nothing you can do right? Hopefully nobody will hack your database and get to the passwords.
Sure. But what when you're browsing around for debugging purposes? How do you prevent yourself from accidentally reading someone's password?
That's where base64 comes in.
But since we don't want to make our code silly, here's a simple way of achieving this without ever having to worry about it again.
class PasswordManager(models.Manager):use_for_related_fields = Truedef create(self, *args, **kwargs):try:kwargs['password'] = base64.encodestring(kwargs['password'])except KeyError:passreturn super(PasswordManager, self).create(*args, **kwargs)def get(self, *args, **kwargs):data = super(PasswordManager, self).get(*args, **kwargs)try:data.password = base64.decodestring(data.password)except AttributeError:passreturn dataclass GoogleAccount(models.Model):user = models.ForeignKey(User, unique=True)email = models.CharField(max_length=255)password = models.CharField(max_length=255)objects = PasswordManager()
Basically we write a module manager that encodes all passwords in insert queries to base64 and decodes them again on select queries. For completeness sake it's also good to define a filter function where we perform the decoding on the whole set of returned entries. But for this sort of thing that's rarely needed because you're rarely going to be performing third party actions for miriads of users at once.
This way we achieve perfectly seamless base64 storage of passwords. Nice and easy.
Here's how it works 👇
Then get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career.
"Man, love your simple writing! Yours is the only email I open from marketers and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Ready to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization
Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.
Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️