3 ms·
Be careful with this kind of stuff. Someone posted a link [0] to a GitHub repo here a few days ago that would fire up a miner on some AWS GPU instances... exce
by jlgaddis 9y ago
Be careful with this kind of stuff.
Someone posted a link [0] to a GitHub repo here a few days ago that would fire up a miner on some AWS GPU instances... except that they hard-coded their own account (wallet) into it so any profits would go to them. It hit the HN front page pretty quickly.
This might be completely legit but, at minimum, take a few minutes to look through the code before you just blindly deploy it.
[0]: https://news.ycombinator.com/item?id=16249372 https://news.ycombinator.com/item?id=16249372
- alexellisuk 9y agoAlways read the code - this is why I'm not supplying a binary. I don't even know if this is valid within the T&Cs - but I hope it will be interesting and of educational value at the least.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- swedish_mafia 9y agoBut you are supplying a binary ! This docker container calls a pre-compiled binary ./cpuminer. There is no way to tell if this binary faithfully uses the bitcoin address provided in the command line (yes there is some code there but you cannot confirm that this it was compiled from that code.) But it gets worse. Even if someone does disassemble the binary, you could update the the docker container to add this capability, and nobody will be able to tell because the image gets pulled each time.
- alexellisuk 9y agoHave you taken a moment to read the README? The Dockerfile is linked in the mine-with-docker project. You are well within your rights to rebuild that. The concern raised was what happened with the cloud API.