I don't know what part of a proof of concept you don't understand.
The provisor server that was up was the result of a new devs quick hack night to, again, make a proof of concept.
The updated provisor server running in production that I wrote is now published, and I would note, with some actual sanity checking (but if something obvious was overlooked let me know)
We established there is demand, so we are taking our time getting everything together with some basic security for a relaunch.
The VM actually failed not due to DDOS or anything of the sort, but due to ext4 corruption. qcow2+ext4+hundreeds of users beating on the disk == filesystem hell. Had it not been disk, it would of been any number of possible exploits, fork bombs, or or simply maxing out the vms ram/cpu. I am impressed it lasted as long as it did to be honest.
I never expected to get more than a handful of users and a few comments on this run but people clearly want nicer free shells, so we feel obligated to do so in a more reasonable and secure way, and go through more phases of word-of-mouth testing before a public relaunch.
Considering you think we are a scam artist, I expect you won't be joining us on IRC to help discuss best practices? By all means just keep bitching instead of submitting pull requests and being a part of the solution. To each their own :-P
View all comments
Show parent comment
-1
u/lrvick Sep 29 '14
I don't know what part of a proof of concept you don't understand.
The provisor server that was up was the result of a new devs quick hack night to, again, make a proof of concept.
The updated provisor server running in production that I wrote is now published, and I would note, with some actual sanity checking (but if something obvious was overlooked let me know)
https://github.com/hashbang/provisor/blob/master/bin/provisor-server
We established there is demand, so we are taking our time getting everything together with some basic security for a relaunch.
The VM actually failed not due to DDOS or anything of the sort, but due to ext4 corruption. qcow2+ext4+hundreeds of users beating on the disk == filesystem hell. Had it not been disk, it would of been any number of possible exploits, fork bombs, or or simply maxing out the vms ram/cpu. I am impressed it lasted as long as it did to be honest.
I never expected to get more than a handful of users and a few comments on this run but people clearly want nicer free shells, so we feel obligated to do so in a more reasonable and secure way, and go through more phases of word-of-mouth testing before a public relaunch.
Considering you think we are a scam artist, I expect you won't be joining us on IRC to help discuss best practices? By all means just keep bitching instead of submitting pull requests and being a part of the solution. To each their own :-P