›

Why is http//processing.org on my computer/browser regarded »untrustworthy« and blocked

nikolajnikolaj
edited March 2015 in General

I'm using Firefox as my browser, and i'm using a mac, and running Yosimite. For quite a while, everytim i used the search button at the processing homepage, i was told that it was unsecure. And now, Firefox decided to altogether block the page, because it thought it was untrustworhty, and told me that further use was on my own risk.

I do trust http//processing.org, (and i need the reference page) and the site has never asked me to give any personal information or anything, so why did it block it.

Tagged:

Answers

  • quarkquark

    Because it is https:// not http:// in other words secure HTTP connection and if like me you are using OSX and installed a recent security update it will come up with this message. Click I know the risks and create a security exception. No problems

  • nikolajnikolaj

    I did tell it that i do trust the site, and i do now have acces, but i would just like to know why it suddenly decided that it was insecure now, and not all the times i have been using it the latest few years. A new security update, would explain it

  • GoToLoopGoToLoop
    edited March 2015
    • The meaning of word "insecure" isn't explained well when it refers to https connections and their associated certificates!
    • When the message pops up, it means that the certificate being used by a domain wasn't issued (and paid for) by some big certificate company.
    • But the effect is exactly the same either way: an https connection is encrypted.
    • Only cases we should worry about that warning is when we're doing business like shopping and banking.
    • Otherwise it's just to scare us away to force a domain to buy a "trusted" certificate! :O)
  • GoToLoopGoToLoop

    ...but i would just like to know why it suddenly decided that it was insecure now, and not all the times i have been using it the latest few years.

    • As @quark mentioned, somehow the domain "processing.org" decided to use https only.
    • And in order to use https, the domain needs a certificate.
    • And if that certicate happens to be self-signed or not recognized by the browser, that scary warning pops up!
    • Since the connection is encrypted now, it's more secure than before.
    • There's no diff. on the quality of the encryption between a recognized and unrecognized certificate.
    • Its quality depends on the cipher used and whether or not the domain makes non-https connections to other domains!
Sign In or Register to comment.