Author: Christian Decker 2014-03-02 21:11:01
Published on: 2014-03-02T21:11:01+00:00
Christian Decker speculated that the domain bitcoin.org could have resolved to the IP address mentioned in an email. He wondered if it might be an update check with a circular redirect, which could explain the numerous connection attempts. A user named James Hartig reported that he had downloaded a linux tar.gz file to his OVH box and received an email claiming that he was attacking 88.198.199.140 over port 443. Wladimir found it unlikely that bitcoind would connect to port 443 or attack anything. He asked if there was anything in debug.log regarding that IP. This exchange took place on the Bitcoin-development mailing list. The email screenshot showed that OVH had terminated James Hartig's server due to alleged attacking activity. However, it was unclear how the IP address and port were connected to bitcoind, the bitcoin client. The discussion did not provide any clear answers but raised concerns about potential security issues and updates related to bitcoin.org. Meanwhile, a promotional message about NetFlow Analyzer, a traffic analytics software tool, was shared on the mailing list.
Updated on: 2023-06-08T03:43:49.580419+00:00