James Hartig [ARCHIVE] on Nostr: 📅 Original date posted:2014-03-02 📝 Original message:Didn't mean that bitcoind ...
📅 Original date posted:2014-03-02
📝 Original message:Didn't mean that bitcoind was connecting over port 443. I didn't even get a
chance to compile. I was literally just finished downloading the tar.gz
file when my server was terminated.
Still trying to convince them I wasn't attacking anyone so they can
re-enable the server.
Thanks,
--
James Hartig
Software Engineer @ Grooveshark.com
http://twitter.com/jameshartigOn Sun, Mar 2, 2014 at 3:56 PM, Wladimir <laanwj at gmail.com> wrote:
>
> On Sun, Mar 2, 2014 at 7:34 PM, James Hartig <fastest963 at gmail.com> wrote:
>
>> Heads up... downloaded the linux tar.gz to my OVH box and got my server
>> terminated. Screenshot from the email:
>>
http://cl.ly/image/3q0C2a3Y0T0V>>
>> They claimed I was attacking 88.198.199.140 over port 443.
>>
>
> Sounds very unlikely that bitcoind would connect to port 443, let alone
> 'attack' anything.
>
> Anything in debug.log regarding that IP?
>
> Wladimir
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140302/c3b35489/attachment.html>
Published at
2023-06-07 15:14:32Event JSON
{
"id": "dafb7cbf900ef8b190cbe10f76545edadc735ef91ae00bbc8e64b8ea92b6fb6e",
"pubkey": "30e30a537413a540db17f8494f731f227a64792ed5a45c0a6b65fc6235edd515",
"created_at": 1686150872,
"kind": 1,
"tags": [
[
"e",
"f39aef80e5ccec85d7d380af046513a4777d583a6062359c556cef2dbfcfcf0c",
"",
"root"
],
[
"e",
"42d5974e8b268e5d4058e84a6b9234aaa6e0e1064b52d626e5ca2c7a6818c93f",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "📅 Original date posted:2014-03-02\n📝 Original message:Didn't mean that bitcoind was connecting over port 443. I didn't even get a\nchance to compile. I was literally just finished downloading the tar.gz\nfile when my server was terminated.\n\nStill trying to convince them I wasn't attacking anyone so they can\nre-enable the server.\n\nThanks,\n--\nJames Hartig\nSoftware Engineer @ Grooveshark.com\nhttp://twitter.com/jameshartig\n\n\n\n\n\nOn Sun, Mar 2, 2014 at 3:56 PM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\n\u003e\n\u003e On Sun, Mar 2, 2014 at 7:34 PM, James Hartig \u003cfastest963 at gmail.com\u003e wrote:\n\u003e\n\u003e\u003e Heads up... downloaded the linux tar.gz to my OVH box and got my server\n\u003e\u003e terminated. Screenshot from the email:\n\u003e\u003e http://cl.ly/image/3q0C2a3Y0T0V\n\u003e\u003e\n\u003e\u003e They claimed I was attacking 88.198.199.140 over port 443.\n\u003e\u003e\n\u003e\n\u003e Sounds very unlikely that bitcoind would connect to port 443, let alone\n\u003e 'attack' anything.\n\u003e\n\u003e Anything in debug.log regarding that IP?\n\u003e\n\u003e Wladimir\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140302/c3b35489/attachment.html\u003e",
"sig": "65da535432612c2bf18e51062629358be2370f3c174901d491fe4ac818fb92feef39605a9d6579f9e32e9f48941be022ec68095ebba2abe8f5e420418446b8d6"
}