l "live"
accounts limiting the scope of any attack if they manage to get into the
server. Maybe this is beyond the scope of bitcoind, not sure.
Thanks,
--
James Hartig
Software Engineer @ Grooveshark.com
http://twitter.com/jameshartig
--
hanks,
--
James Hartig
Software Engineer @ Grooveshark.com
http://twitter.com/jameshartig
On Sun, Mar 2, 2014 at 3:56 PM, Wladimir wrote:
>
> On Sun, Mar 2, 2014 at 7:34 PM, James Hartig wrote:
>
>> Heads up... downloaded the linux tar.gz to my OVH box and got my server
>> t
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.
Thanks,
--
James Hartig
Software Engineer @ Grooveshark.com
http://twitter.com/jameshartig
rtable. If
they want to run them both as the same user with no SELinux or file
protections (this isn't stopping or encouraging that) they're already doing
that now with bitcoind, albeit with possibly a larger attack surface.
Thanks,
--
James Hartig
Software Engineer @ Grooveshark.com
http:
4 matches
Mail list logo