Not Secure
- Thread starter Genecop
- Start date
The friendliest place on the web for anyone who enjoys boating.
If you have answers, please help by responding to the unanswered posts.
If you have answers, please help by responding to the unanswered posts.
tiltrider1
Guru
- Joined
- Aug 2, 2017
- Messages
- 4,344
- Location
- Pacific North West
- Vessel Name
- AZZURRA
- Vessel Make
- Ocean Alexander 54
Http: has never had the security of Https: Your operating system must have just received an update. From now on all Http: sites will show not secure. Nothing else has really changed.
- Joined
- Jan 9, 2014
- Messages
- 4,179
- Location
- USA
- Vessel Name
- N/A
- Vessel Make
- 1999 Mainship 350 Trawler
This is the default behavior of your web browser. It is detecting that the site is using HTTP instead of HTTPS (HTTP over SSL). There is no sensitive data on the site, therefore no need to use SSL encryption.
This warning can be ignored.
This warning can be ignored.
The login pages here are secure (httpS) but as noted, the rest of the site is not. We store no financial info or other sensitive content here and we long ago changed login pages (where password data is passed) to meet current security standards.
Last year google began to push websites to use https instead of http as a security update. A few months ago they began to actually began to display that little red triangle;"not secure" on browser address lines.
We hand coded an update to make the LOGIN page https. This is the page where user credentials are passed and the only sensitive data we store. Once a member has logged in the site reverts to http (and the alert begins to display in browsers). Using https on all pages actually breaks some things the forum. Offsite links and hosted images may no longer work, ads don't display, photos, etc.
So... as you login the page is secure (https) but once you have logged in the regular site is http. Since no login/pass info is being sent on these pages we believe this is safe and reasonable. We will eventually switch to full SSL but as noted by other posters there are some concerns to weigh as we make that choice.
You can read more about the google alerts here: https://www.wired.com/story/google-chrome-https-not-secure-label/
Last year google began to push websites to use https instead of http as a security update. A few months ago they began to actually began to display that little red triangle;"not secure" on browser address lines.
We hand coded an update to make the LOGIN page https. This is the page where user credentials are passed and the only sensitive data we store. Once a member has logged in the site reverts to http (and the alert begins to display in browsers). Using https on all pages actually breaks some things the forum. Offsite links and hosted images may no longer work, ads don't display, photos, etc.
So... as you login the page is secure (https) but once you have logged in the regular site is http. Since no login/pass info is being sent on these pages we believe this is safe and reasonable. We will eventually switch to full SSL but as noted by other posters there are some concerns to weigh as we make that choice.
You can read more about the google alerts here: https://www.wired.com/story/google-chrome-https-not-secure-label/
