Bitcoin Forum
May 11, 2024, 04:55:08 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: tampering with bip70 payment requests  (Read 560 times)
achow101 (OP)
Moderator
Legendary
*
expert
Offline Offline

Activity: 3388
Merit: 6635


Just writing some code


View Profile WWW
October 26, 2015, 11:47:13 PM
 #1

From what I can understand, if a payment request isn't signed using an X.509 certificate, then there isn't anywhere in the request that is hashed or signed to verify its integrity. So how does it prevent tampering with the request between the server and the user if no authentication is used? Or is there no such mechanism?

1715403308
Hero Member
*
Offline Offline

Posts: 1715403308

View Profile Personal Message (Offline)

Ignore
1715403308
Reply with quote  #2

1715403308
Report to moderator
1715403308
Hero Member
*
Offline Offline

Posts: 1715403308

View Profile Personal Message (Offline)

Ignore
1715403308
Reply with quote  #2

1715403308
Report to moderator
According to NIST and ECRYPT II, the cryptographic algorithms used in Bitcoin are expected to be strong until at least 2030. (After that, it will not be too difficult to transition to different algorithms.)
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4172
Merit: 8419



View Profile WWW
October 27, 2015, 12:22:42 AM
 #2

The mechanism would be that you've transported it over a secure transport in the first place, e.g. HTTPS or encrypted email. No different than a Bitcoin address or plain payment URI.
achow101 (OP)
Moderator
Legendary
*
expert
Offline Offline

Activity: 3388
Merit: 6635


Just writing some code


View Profile WWW
October 27, 2015, 12:29:50 AM
 #3

The mechanism would be that you've transported it over a secure transport in the first place, e.g. HTTPS or encrypted email. No different than a Bitcoin address or plain payment URI.
So if a merchant doesn't have an SSL certificate and thus doesn't support HTTPS and the request is sent over http, then someone could perform an MITM attack (just like with everything else using http) and could tamper with the request and the user wouldn't even know it. I personally feel that this is unsafe, especially when both the consumer and merchant have access to private keys which can sign that payment request so that, at a bare minimum, its integrity is verified.

edit: how come we are always told to verify the signatures and checksums of the software we download even if it was delivered through a secure mechanism like https? Shouldn't the same apply to the payment requests?

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!