It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: 3ncrypt0Rdie
a reply to: yuppa
Seems to me that you may need another dubbie; im likely the guy running your operation, lol just kidding.
I am an American who is trying to make a difference no money involved in any of my post. so far a waste of time actually.
do you have something interesting to add to this conversation?
The latest iteration of the browser expands in-context user warnings for non-secure HTTP pages with logins. Users will now be confronted with a “This connection is not secure. Logins entered here could be compromised.” message when they try to enter a username and password field on a non-HTTPS page.
Chrome users who navigate to some HTTP sites will be notified, starting in January, they’re on a site that isn’t secure.
Google said today the browser will begin explicitly labeling HTTP connections that feature either a password or credit card form as non-secure. The company said the plan is its first step toward marking all HTTP sites as non-secure, though it didn’t provide a timetable for the undertaking.
originally posted by: jedi_hamster
originally posted by: Springer
a reply to: ElectricUniverse
It's FireFox...
and that means what exactly?
just state the obvious, because some people seem to fail to realize it.
ATS doesn't use any sort of connection encryption and as far as i know, never did. so it's not something new, it never was secure to begin with.
bottom line is, yes, someone can sniff on your connection to ATS and hijack it, at least in theory. random person with no knowledge won't do it, but it's technically possible.
seriously, with let's encrypt certificates being free and comments like that, it feels like you're avoiding ssl on purpose.
originally posted by: vlawde
If I use Firefox, I see that on many websites..but not with Chrome
originally posted by: BlueAjah
a reply to: charlyv
SSL is not difficult to implement. Not at all.
For less than $200 per year, a few minutes to add the certificate to the server, a couple of lines added to .htaccess files, and a site can be safe.
ETA: well,,, safeR. Nothing is ever totally safe.
ETA: I see one more thing - the URLs in your page content would need to be changed to https. But since that seems to be scripted, it should not be hard to change.
originally posted by: jedi_hamster
originally posted by: ANNED
I had the problem on ATS and three other sites.
I rolled back my computer three days and the problem went away.
It was the firefox update that cause this problem.
It did not happen on internet explorer , duckduckgo. yahoo, bing,
This left firefox update as the problem so i did the roll back.
it's like sticking your head in the sand in case of danger.
the warning is there for a reason. throwing away reasonable warning and future security patches, because you can't be bothered to be reminded that ATS isn't using a secure connection? that's silly.
it's not firefox to blame. it's ATS.
originally posted by: anonfamily
ATS is by no means secure...
The lack of encryption is small in comparison to the major security flaws they have elsewhere.