Čollective №thing

Many people, such as myself, decide to invest in home security camera systems.  Most of them nowadays allow you connect directly to the system via your smartphone.   As I am in the computer security field, I tend to wonder just how secure things are in my own home.  So I put my NiteOwl 16 channel DVR system to the Pepsi challenge.  It failed horribly. Whenever I send my username and password across the internet to look at my home security cameras, the credentials are sent in clear text.  Anyone in computer security knows is a not a good thing.  Clear-text credentials are very easy to intercept.  And most people don't know how to properly defend themselves and their home against cyber threats.  So lots of people will use one password for everything.  So if someone was to intercept this DVR password, the attacker has a lot of helpful information. The intercepted information will include: the username, which is likely the username also used in at least one of the computers on t

this tutorial involves 2 computers, a client and a server.  As you should know, a client will connect to the server.  You can always add an ssh server to your client machine, but we aren't going to worry about that today. on the client machine: # cd /home/username The username needs to be the username you are going to use to connect, and that username must exist on the server machine as well.  You can do it other ways, but that is a complication we won't get into today. # mkdir .ssh # chmod 700 .ssh/ # cd .ssh # ssh-keygen -t rsa -b 2048 (some ssh servers like hardware appliances require dsa, so use ssh-keygen -t dsa in those cases) Accept the default values and it should put the keys in the folder you just created. # chmod 640 id_rsa.pub # chmod 600 id_rsa # nano /etc/ssh/ssh_config Add the following line (or uncomment the line if it already exists) IdentityFile ~/.ssh/id_rsa Then use CTRL-O to save and CTRL-X to exit One the server machine: Install the SSH se