And you seriously can't see this happening with Trump? Really?

Unless of course that router is in a hospital or medical insurance office. Then someone very well could die due to incorrect treatment or lack of treatment.

HTTPS is the only real answer. Rules like what are being proposed are hard to enforce. But properly implemented authentication and encryption will make such rules unnecessary.

I have a pfSense router built on a C2758 Atom CPU (specifically this board: http://www.supermicro.com/prod...) paired to a couple of Unifi APs (http://www.amazon.com/Ubiquiti-Networks-Enterprise-Unifi-UAP/dp/B00HXT8R2O). Its the best home network I have ever had. And that is including some DD-WRT stuff that I used to use for wifi in conjunction with some actual Cisco gear that I used to use. (ASA 5505 firewall, 3745 router, ect...) I can't see myself ever going back to a consumer grade wifi router. Sure its total overkill. But being able to set up a Site to Site VPN to my friend's place and an OpenVPN server for remote access without having to worry about CPU usage is pretty nice. Being able to have separate SSIDs and corresponding VLANs for guests and my kids and such is also nice. The Unifi APs give better wifi than any consumer grade device I have ever used. I am seriously considering upgrading to dual band AC models.

Apply an activation crack or join it to a domain. Either one will do the trick just fine.

The fact that you say you are "encrypting" something with SHA1 tells me that you are not qualified to work on any product that uses encryption. If you must do something like this at least use bcrypt or pbkdf2. SHA1 and SHA2 are both not the best choice for what you are doing.

And TLS 1.0 and 1.1 both use md5(data).sha1(data) to sign the initial handshake. And since concatenating hashes provides no real additional security this lets an attacker muck around with the initial TLS exchange and perform a protocol downgrade attack by defeating TLS_FALLBACK_SCSV and/or also choose the symmetric cipher used in the TLS session. While its not a full plaintext recovery of the TLS session contents it is certainly not a good thing.

Actually concatenating hashes together doesn't do much for security at all. In fact it does almost nothing. See: http://link.springer.com/chapt...

99.99% of internet users are not like you. They do not understand, nor do they care about, how TLS and certificate authorities work. If they see a little lock in their address bar then they are "safe" as far as they are concerned. To most people a StartSSL cert is exactly the same as an EV cert used by a banking site. The fact that one creates a green address bar or whatever and the other does not is totally lost on them and makes no difference. Granted this is a problem. But I don't think it is one that can be solved via technical means. Lets face it. Most people just don't know enough about how the internet works to be able to use it safely.

I don't think the VA is a model other healthcare providers should be trying to emulate.

This closely mirrors my own experience with Republic Wireless. I have been using their Moto G on the $25 a month plan for about a year and it has been flawless. The only wifi networks I use are at home and at the office (and the occasional free wifi at a a coffee shop, hotel, or the like) but that covers something like 70% of my phone usage anyway. I stream Pandora over the cell network every day while commuting to and from work and I have never even come close to data cap. Call hand-offs between wifi and cell and seamless and the phone is very smart about avoiding bad wifi connections or access points with blocked ports. The only real downside is the limited selection of phones. The Moto X, Moto G, and Moto E are all they offer so if you are in love with the latest iPhone or Samsung Galaxy you are out of luck. However the Moto phones are reasonable high end, mid range, and entry level devices respectively.

I am running three screens on two Nvidia GeForce 210s in Mate on Mint 16. (Two screens on one card and one screen on the other.) Once I installed the binary Nvidia driver and ran Nvidia's X Server Settings tool everything worked flawlessly.