897 karma · joined March 8, 2016
[1] https://en.wikipedia.org/wiki/Atrocities_in_the_Congo_Free_S... -- "... The collection of hands became an end in itself. Force Publique soldiers brought them to the stations in place of rubber; they even went out to harvest them instead of rubber ... They became a sort of currency ..."
https://github.com/Bhargav1912/test_1/pull/2/files
Following the files used reveals the pool and wallet used. The pool lets you look up the stats for this wallet. For this wallet, it says:
> Total Paid: 163000 TRTL - 42.16$
But I guess the culprit is rotating wallets. Judging by the hash rate, the pool estimates a weekly income of 700$. It could be a multiple of this if the culprit uses multiple wallets at once.
bash$ time factor 50316869230723462603
50316869230723462603: 3962800609 12697300267
real 0m0.009s
user 0m0.009s
sys 0m0.000sOne way to check how the editor behaves is to run
ls -li run.sh
before and after editing the script. The first number in the output is the inode of the file; if it stays the same then the file was overwritten.I've tested this, and indeed when editing the file with vim, I can't reproduce the "dangerous" behavior. To trigger this behavior, I'd have to overwrite the script file, e.g. by
1. create script run.sh with "sleep 30" etc
2. create script run1.sh with "sleep 3" instead
3. start run.sh
4. overwrite script: cat run1.sh > run.sh
5. after the sleep, the commented line does execute
Are there editors that actually overwrite the original file, instead of creating a new file? I thought the latter is the recommended approach as it can prevent data loss e.g. if there's a crash during writing the file.P.S. If the script in question is on a network file system, things may be different even for vim. E.g. on NFS the file handle doesn't behave fully like a regular POSIX file handle, and the NFS server might actually reopen the file between reads, thus delivering the modified contents to the bash process.
> This code is up-to-date and is matching the build on the Play Store.
which seems to be in conflict with your statement.
From a cynical point of view, the governments in the west might see this disease as a god-send. It mostly kills the old and sick. So if you let it run its course through the whole population, the strain on pension and public health systems will (eventually) be reduced -- "sozialverträgliches Frühableben" as one German top medic once called it. A disease that mostly leaves the young and productive part of the population intact might thus be welcomed as a solution to the demographic problems in the west.
Note, I don't agree with this point of view, but it might help explain the timid response in the west.
Android has a feature of "Bluetooth scanning" to improve device location (similar to Wifi scanning). I'm not sure, but even if Bluetooth is disabled in the menu, this might still activate Bluetooth occasionally and perhaps reveal the Bluetooth MAC to the (nearby) world?