Bitcoin Forum
December 02, 2016, 10:22:15 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Incorrect Firefox Warning for Bitcoin website  (Read 3167 times)
I-am-not-anonymous
Newbie
*
Offline Offline

Activity: 23


View Profile
February 15, 2010, 04:24:16 AM
 #1

I hate to be the bearer of annoying news, but:

http://farm3.static.flickr.com/2715/4357986935_a3a337fd96_o.jpg

http://farm3.static.flickr.com/2753/4357986949_21230f426e_o.jpg

Certificate details from firefox: http://www.flickr.com/photos/47538931@N04/show/

This doesn't bother me I still use the site, but I can't help but think some paranoid people might turn tail at the site of the bright yellow Danger signs.
1480717335
Hero Member
*
Offline Offline

Posts: 1480717335

View Profile Personal Message (Offline)

Ignore
1480717335
Reply with quote  #2

1480717335
Report to moderator
1480717335
Hero Member
*
Offline Offline

Posts: 1480717335

View Profile Personal Message (Offline)

Ignore
1480717335
Reply with quote  #2

1480717335
Report to moderator
1480717335
Hero Member
*
Offline Offline

Posts: 1480717335

View Profile Personal Message (Offline)

Ignore
1480717335
Reply with quote  #2

1480717335
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Xunie
Full Member
***
Offline Offline

Activity: 132



View Profile
February 15, 2010, 07:58:01 AM
 #2

Google Chrome 5.0.307.7 beta (on debian) reports the same thing.

Thank me for this post here: 1PyNKEyqtDFB4HBG8ueDVxdPZfgwC6gAqw
Caffeinism -- a toxic condition caused by excessive ingestion of coffee and other caffeine-containing beverage.
theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
February 15, 2010, 08:43:04 AM
 #3

The TLS certificate is self-signed, so the warning is "correct". The encryption is just as strong as any other HTTPS connection, but without a CA's signature the site's identity can't be guaranteed -- a man-in-the-middle attack could be used. Unfortunately, getting a signature costs money.

Verifying the certificate's fingerprint here before adding an exception will prevent any MITM attack. This is only necessary when you add an exception; subsequent MITM attempts will trigger a warning by your browser.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
I-am-not-anonymous
Newbie
*
Offline Offline

Activity: 23


View Profile
February 16, 2010, 03:31:41 AM
 #4

Unfortunately, getting a signature costs money.

Would something like this help:

http://cert.startcom.org/
http://www.cacert.org/

I don't mean to sound presumptuous or arrogant--I am fully aware of my own ignorance and that the above links could be completely useless--just a suggestion.


theymos
Administrator
Legendary
*
Offline Offline

Activity: 2492


View Profile
February 16, 2010, 05:17:17 AM
 #5

The CA's root certificate needs to be included in the browser to make the warning go away. CACert isn't included in any popular browser, and Startcom was only recently added to Windows. With Startcom, anyone who doesn't install the optional root certificates update in Windows update will still get an error in Chrome, Safari, and Internet Explorer. Firefox has had it built-in for a while.

HTTPS isn't the default (or really necessary) for bitcoin.org, so it doesn't much matter. If you want to manually switch to HTTPS, then you can deal with the self-signed certificate.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
I-am-not-anonymous
Newbie
*
Offline Offline

Activity: 23


View Profile
February 16, 2010, 05:30:30 AM
 #6

The CA's root certificate needs to be included in the browser to make the warning go away. CACert isn't included in any popular browser, and Startcom was only recently added to Windows. With Startcom, anyone who doesn't install the optional root certificates update in Windows update will still get an error in Chrome, Safari, and Internet Explorer. Firefox has had it built-in for a while.

HTTPS isn't the default (or really necessary) for bitcoin.org, so it doesn't much matter. If you want to manually switch to HTTPS, then you can deal with the self-signed certificate.

I see now why now why bitcoin doesn't need a CA, most people will not access it with the https protocol and therefore won't be spooked off by scary warning labels like the ones I got.  Good to know.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!