Bitcoin Forum
May 17, 2024, 06:54:47 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Blockchain.info is dropping support for all http:// requests on December 14th  (Read 1044 times)
NarC (OP)
Full Member
***
Offline Offline

Activity: 189
Merit: 100

BitcoinStoreStarter.com


View Profile WWW
December 12, 2014, 06:23:12 PM
 #1

From their /api page.
"Blockchain.info is dropping support for all http:// requests on December 14th. Please make sure all API requests use https://"

Does that mean any type of query to the blockchain api from my site (currently not a https://) will not work?

Blazr
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1005



View Profile
December 12, 2014, 06:33:19 PM
 #2

From their /api page.
"Blockchain.info is dropping support for all http:// requests on December 14th. Please make sure all API requests use https://"

Does that mean any type of query to the blockchain api from my site (currently not a https://) will not work?

Your website doesn't need to be HTTPS, it means that when you are querying blockchain.info you need to use HTTPS.

NarC (OP)
Full Member
***
Offline Offline

Activity: 189
Merit: 100

BitcoinStoreStarter.com


View Profile WWW
December 12, 2014, 06:36:56 PM
 #3

From their /api page.
"Blockchain.info is dropping support for all http:// requests on December 14th. Please make sure all API requests use https://"

Does that mean any type of query to the blockchain api from my site (currently not a https://) will not work?

Your website doesn't need to be HTTPS, it means that when you are querying blockchain.info you need to use HTTPS.

Ahhh yeah, I guess I read that totally wrong. Thanks for your response.

Martijnvdc
Sr. Member
****
Offline Offline

Activity: 322
Merit: 250


View Profile
December 12, 2014, 06:39:32 PM
 #4

From their /api page.
"Blockchain.info is dropping support for all http:// requests on December 14th. Please make sure all API requests use https://"

Does that mean any type of query to the blockchain api from my site (currently not a https://) will not work?

Your website doesn't need to be HTTPS, it means that when you are querying blockchain.info you need to use HTTPS.
Interesting. I wonder why they did that. What's the danger in not encrypting harmless queries such as checking a address balance? What secrets could it possibly reveal?
amaclin
Legendary
*
Offline Offline

Activity: 1260
Merit: 1019


View Profile
December 12, 2014, 07:15:05 PM
 #5

Quote
Interesting. I wonder why they did that. What's the danger in not encrypting harmless queries such as checking a address balance? What secrets could it possibly reveal?
The request or/and response can be modified by man-in-the-middle.
So... This is one more shoot to decentralization. We have to trust trird- (bc.i) and fourth-party (certificate issuer)
Blazr
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1005



View Profile
December 12, 2014, 07:22:17 PM
Last edit: December 12, 2014, 08:32:27 PM by Blazr
 #6

Quote
Interesting. I wonder why they did that. What's the danger in not encrypting harmless queries such as checking a address balance? What secrets could it possibly reveal?
The request or/and response can be modified by man-in-the-middle.
So... This is one more shoot to decentralization. We have to trust trird- (bc.i) and fourth-party (certificate issuer)

You can use certificate pinning so you don't have to trust any certificate authority.

gmaxwell
Staff
Legendary
*
Offline Offline

Activity: 4172
Merit: 8421



View Profile WWW
December 12, 2014, 08:24:55 PM
 #7

So... This is one more shoot to decentralization. We have to trust trird- (bc.i) and fourth-party (certificate issuer)
Uh. ... You realize this is a massive upgrade right?  Before you were trusting all of the hundreds of parties that could be MITMing your connection, and after you trust fewer (just bc.i their staff and contractors, cloudflare, and any certificate authority or someone who has compromised them or received a sub-CA cert from one).  The certificate issuer has no active role in the connection you make, their role was simply to one-time sign a public key bc.i presented to them and attest that it really was bc.i.
amaclin
Legendary
*
Offline Offline

Activity: 1260
Merit: 1019


View Profile
December 12, 2014, 09:12:48 PM
 #8

Quote
Uh. ... You realize this is a massive upgrade right?
You know my opinion. Bitcoin is dead. Already dead.
Because decentralization takes more energy than centralized systems.
You have to waste more and more energy/power/electricity day-to-day and month-to-month just to secure transactions
And every step to bitcoin2.0 is just a step to a centralization.
There is no other way.
Blazr
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1005



View Profile
December 13, 2014, 08:26:21 PM
 #9

Because decentralization takes more energy than centralized systems.

Thats not always true, have a look at Gnutella.

You have to waste more and more energy/power/electricity day-to-day and month-to-month just to secure transactions

No you don't, we only need enough hashpower to mitigate a 51% attack, it doesn't need to keep increasing, the only reason the hashrate is increasing right now is because mining equipment has gotten much more efficient in a very short period of time and more and more people are entering the bitcoin mining industry.

amaclin
Legendary
*
Offline Offline

Activity: 1260
Merit: 1019


View Profile
December 13, 2014, 08:49:30 PM
 #10

Quote
No you don't, we only need enough hashpower to mitigate a 51% attack

Would you physically destroy 1/2 worldwide old asics when the hashpower drop down twice from current values? But how?
Switched off equipment is non-profitable for mining, but suitable for attack Smiley
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!