This is a little sideproject I've been working on. If you love i3, you'll love this project. Minimalistic in system resource usage, yet packed with features to get so much more out of your i3bar. Because this is only something I can work on in my spare time, I haven't finished many modules yet (like CPU usage, battery, device mounts etc etc.). I only got around to get the framework working properly so far. This is why I'm looking for contributors to get this thing everyday-ready. It is going to add a nice look, buttons and dynamic blocks to your i3bar, al the while using less system resources than i3status by saving block updates through push-updates, caching and individual block update intervals. Let me know what you think, it's my first public Rust project.
There is now more evidence supporting that there are no backups, e.g. he doesn't even store information about which servers he already looted (he is erasing the same servers twice or more). Until someone has logs that prove otherwise on bigger datasets, nobody should pay this guy.
Also it seems implausible seeing the vast amount of data which he would need to have backed up, closing in several hundreds of terabytes, based on an estimation of last year.
Another log shows that he even connects to the same server twice sometimes, deleting his own message just to re-insert it- That means he doesn't even save which servers he deleted. Such blunt action is remarkable.
My thoughts, too. But before claiming this I at least wanted to encourage a second look. I also ensured this was the only time he connected, so there is no plausable way he is backing up the data.
Shouldn't be hard to get the IP etc, as you can just connect to affected servers and review the global log. Just search for mongoDB on shodan and see for yourself.
I am not affected by this hostage taking. On the contrary, I am one of the authors of the aforementioned info paper from early '15 warning about this kind of stuff. If you want more information about the incident back then, look me up my name is Kai Greshake. The paper linked above also contains all you need to know about why this incident today happened. As a response MongoDB also updated their security guidelines back then, but refused to change the open-default mechanism and easy-to-do-wrong configuration, arguing that it was aconcious design choice.Turns out this was a bad decision, at least in my eyes, as this is not the first related incident, there were many breaches etc. based around open-default databases in the past 2 years, exposing millions of account info, voting data, and industry equipment.
Sure but then we can just use the energy to suck all the co2 out of the atmosphere and blow it out into solar orbit or something. There are better materials to use for making plastics with infinite energy, although I'm probably not qualified to make that statement.
This was debunked years ago. Making plastics from CO2 is possible, but an energy hungry process which does not suck up any relevant amount of carbondioxide from our atmosphere. It isn't going to be the climatesaver they claim it to be. This is not a manufacturing issue, but depends on basic thermodynamics.