by Suff » 19 Apr 2021, 13:33
The main issue with HTTP, is that when you enter the password on the site, anyone who is monitoring the link will see your password in clear.
Without spending a chunk of money, enabling HTTPS on this site is not worth the hassle. So just make sure that your password for this site is something you don't care if it can be seen.
Banking is an entirely different issue which is far, far, more secure. WM is right about the issue with passwords to the phone that you carry around with you. Personally this is an issue for me because I quite often live in hotels where it may be safer to have my phone on me than to have it in the hotel. My phone that takes the passwords is encrypted, has a start up password and you have to enter the SIM pin. In short the phone doesn't go at all without a password and you have to enter a password and 2 pins to start it up and it won't unlock without a password or my fingerprint. Even then the security keeps demanding codes to activate. Some of my banking is via fingerprint, but some of it is on password, pin AND code to the phone.
I can't think of it being much safer. If someone steals the phone and tries to bank they are stuffed. If they attack me, take the phone and use my finger to open it up, they'll have to stay with me until they finally get into an account with very little money. The rest are secured by passcodes which I can't give if they have knocked me out.
There are 10 types of people in the world:
Those who understand Binary and those who do not.