4 ms·

Honest question (IT/security noob) -- why does it not provide that much more security? I like verifying that my traffic is going where I want.

winternett 5y ago
With Encryption being applied to every site as a requirement is relatively new since google made it a requirement in Chrome. Previously it was only required for secured transactions like purchases and working on health care records etc... And very rightfully so. Now Google Chrome flags even simple (informational) sites for not being encrypted, and (quite possibly) rightfully so because of the potential for tracking/abuse, but adding encryption to a site is costly for independent sites (not hosted on social media or corporate platforms like blogs etc... You shouldn't be required to encrypt a baking recipe site if you don't want to... Ultimately laws should discourage data abuse, and/or encryption should be inherently provided for every site/app uniformly by all web host providers (natively and inherently, and at a far lower price than it is now, generally speaking). Too many people are running widely varying encryption measures, and implementing security in too many different ways to ensure that it is stable across the Internet. Security is best when it is uniform, fortified by rules and regulations, and updated ritually.
- freeflight 5y ago
  > Security is best when it is uniform So when web traffic is uniformly not encrypted that's more secure than if it is encrypted by varying degrees and implementations? Tbh your complaint reads along the lines of "Perfect is the enemy of good enough". SSL may not be perfect, but it sure as hell is better than running pretty much the whole web in the clear. Particularly as pretty much all of your complaints do not really have anything to do with SSL itself, but rather in how Chrome surfaces a lack of SSL a certificate and how your hoster handles installing certificates. Both of which are things you can personally change something about.
  - Jiro 5y ago
    >Both of which are things you can personally change something about. No, because "how Chrome surfaces a lack of SSL" is about your users' Chrome, not your own instance of Chrome. You cannot personally change the Chrome that is run by your users.

winternett 5y ago

With Encryption being applied to every site as a requirement is relatively new since google made it a requirement in Chrome. Previously it was only required for secured transactions like purchases and working on health care records etc... And very rightfully so. Now Google Chrome flags even simple (informational) sites for not being encrypted, and (quite possibly) rightfully so because of the potential for tracking/abuse, but adding encryption to a site is costly for independent sites (not hosted on social media or corporate platforms like blogs etc... You shouldn't be required to encrypt a baking recipe site if you don't want to... Ultimately laws should discourage data abuse, and/or encryption should be inherently provided for every site/app uniformly by all web host providers (natively and inherently, and at a far lower price than it is now, generally speaking). Too many people are running widely varying encryption measures, and implementing security in too many different ways to ensure that it is stable across the Internet. Security is best when it is uniform, fortified by rules and regulations, and updated ritually.

freeflight 5y ago
> Security is best when it is uniform So when web traffic is uniformly not encrypted that's more secure than if it is encrypted by varying degrees and implementations? Tbh your complaint reads along the lines of "Perfect is the enemy of good enough". SSL may not be perfect, but it sure as hell is better than running pretty much the whole web in the clear. Particularly as pretty much all of your complaints do not really have anything to do with SSL itself, but rather in how Chrome surfaces a lack of SSL a certificate and how your hoster handles installing certificates. Both of which are things you can personally change something about.
- Jiro 5y ago
  >Both of which are things you can personally change something about. No, because "how Chrome surfaces a lack of SSL" is about your users' Chrome, not your own instance of Chrome. You cannot personally change the Chrome that is run by your users.