From: James Hartig <fastest963@gmail•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] 0.9.0 release candidate two
Date: Sun, 2 Mar 2014 15:59:43 -0500 [thread overview]
Message-ID: <CAM6j61u46e4TGNPUJH1oMg7imKTuSafupzMVWjZPGtuY0a0fFQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJAKJHHK31wzjrAJVdb6Rw8WRVc6b4eEjWrj0GxXH=aCnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
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/jameshartig
On Sun, Mar 2, 2014 at 3:56 PM, Wladimir <laanwj@gmail•com> wrote:
>
> On Sun, Mar 2, 2014 at 7:34 PM, James Hartig <fastest963@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
>
>
[-- Attachment #2: Type: text/html, Size: 2071 bytes --]
next prev parent reply other threads:[~2014-03-02 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 13:54 Gavin Andresen
2014-03-02 18:34 ` James Hartig
2014-03-02 20:56 ` Wladimir
2014-03-02 20:59 ` James Hartig [this message]
2014-03-02 21:11 ` Christian Decker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM6j61u46e4TGNPUJH1oMg7imKTuSafupzMVWjZPGtuY0a0fFQ@mail.gmail.com \
--to=fastest963@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox