Gitup wifi password software#

If you get into that mindset, you’ll be a lot safer.īy the way, ‘ Github dorks‘ are now a thing. It boils down to this: never put passwords or other sensitive items directly in your source code.

The smarter our IoT solutions become, the more they interact with remote systems and the more they need credentials. For example, are you sure you haven’t used that password anywhere else? And while it might be just your home wifi password today, tomorrow it might be more sensitive credentials for an online account. But it’s a good idea to avoid the habit of throwing credentials into code. Now you might say that some hacker, living on the opposite side of the world, or even in the next county, is not going to be able to do much with your wifi password. Well, the harm is that one day you might choose to share your code on Github, having forgotten that there’s sensitive information in it. But when you’re hacking together an Internet of Things (IoT) toy for personal use in your own home, what’s the harm?

Gitup wifi password software#

You should never hard-code credentials into your software – in principle. That’s not a huge issue (see below), but neither is it a good idea. Recently, I found myself wanting to share some code via Github, but realised it contained my wifi password.