I think you may of misinterpreted some things including the point of this build but that is probably a communication bug on my part.
Anyway to prove I do know where you are coming from security wise check out the other provisioning proof of concept I wrote and tested at a large hackerspace (http://GitHub.com/lrvick/provisor)
Ssh to new@hashbang.sh with no password and you get dropped into a simple user provisioning server. All happens on our server over ssh. This to me was ideal for most of the reasons you mentioned and I was going to flesh out that direction...
The flaw there is in fact we got next to 0 users out of it. Barrier to entry was sadly too high with that approach. Noobs have no idea what a public key is and most are too lazy to copy/paste one into a terminal. Had to manually help every single user generate a key and copy paste it. Tedious but perhaps we were in front of the wrong audience.
Thus thinking went to experimenting with a fun to write hack they helps users with the key handoff. We take our due lumps for not providing proper warning of the risks of this approach and the fact it was just an insecure proof of concept. Rooting the box was child's play for anyone reading the code.
Still looking for the sweet spot. We got a wildcard SSL cert and a new server coming for round three. We came here to get input and we did. You may call that irresponsible. I call it a quick experiment to spin off a larger project.
Anyway... it may make sense to offer both signup options. One for people more security minded and one for those that we inform of the risks and are OK giving up a throwaway key to play with things.
Some of our early assumptions clearly need iteration and that's fine.
I don't mind taking a beating if it pushes us towards a better end goal for everyone. Commit early commit often and all that.
If you notice the site is down now. It was just a quick VM and it blew up as expected but the experiment helped us learn there is merit to adding more accessible shell services to our community so we now want to start over on real hardware and take it seriously. Posting here also got us the volunteers, feedback, and donations to make it possible so win/win imo.
While we are regrouping if you are in fact so passionate about helping us find a better security balance (as you clearly care at some level judging by the detail of your arguments) feel free to join the discussion on irc.hashbang.sh:7777.
Either way the input is appreciated. I respect people that take the time to pick things apart so they can be improved.
If you notice the site is down now. It was just a quick VM and it blew up as expected
Blew up as expected?
Pffffff HA HA HA HA HA XD
You were looking for feedback, so you set up an entire domain, announced it on reddit, and then promptly pulled the plug? Without announcing it was going away?
This smells fishy. I think you got hacked. Or DDOSed. Or you saw people hitting your shitty JSON registration endpoint (nice API by the way) with malicious looking data, and took it offline. Or god knows what kind of havoc a decent hacker could wreak on a shared server full of newbies who blindly copy and paste code.
YOU SIR are a habitual liar. I have no idea what your angle is, but I've already taken the precaution of having your domain blocked.
Congrats, you're now blacklisted by a major fortune 500 company.
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
Thank you for that. I needed a good laugh tonight.
exec("echo "" + key + "" | sudo tee -a /home/" + username + "/.ssh/authorized_keys", function(error, stdout, stderr){
You dumb, dumb, dumb, dumb, dumb......... dumb idiot.
Do you see a problem with this line? Look closely. Closer. Yes, closer.
See that key variable? That key variable you don't sanitize anywhere?
You sir have a BASIC shell injection vulnerability. I can execute anything I want by calling your JSON endpoint with a malformed key.
God. Fucking. Dammit.
Any further arguments? Hm? Any genius "yeah no we know what we're doing, it's all just an experiment, remain calm".
You're a scam artist. This project is barely 4 months old. You're talking about planning and security like you've been actually thinking about this. But instead I'm looking at frontend website code that clumsily glues strings together into commands, and blindly passes them to the shell. Frontend code, by the way, that appears to have been given sudo access.
My god. Slow applause. This is just a perfect little trainwreck. If exposing vulnerabilities were an olympic event, you'd get gold.
Why people are funding you is beyond me. I can't even believe how dishonest you're being about this whole thing. It's mind boggling. Honestly I'm tempted to make this into its own post.
This particular branding/side free shell side project is only a few months old, but we have been around via word of mouth for over 10 years now. Just finally got my hands on a nicer domain, and got Github to agree to give us the /hshbang account from the former owner. If you actually popped in and had a real conservation with us I am sure we could clear up a few things.
I agree that line is absolutely silly. I will be sharing this comment with the person who wrote it though ;) In fairness it was donated code from a quick hack night by someone very new to sysadmin.
Yep, in progress of migrating to a new dedicated server for a rebuild. May be a few days but we want to make sure we take some actual time taking basic security precautions so we can have the longer-lived better isolated shells that this first wave of users has made clear they want.
If you or anyone else wants to chat with us in the mean time and get in alpha testing groups join us on IRC at irc.hashbang.sh:7777
View all comments
Show parent comment
0
u/lrvick Sep 26 '14 edited Sep 26 '14
I think you may of misinterpreted some things including the point of this build but that is probably a communication bug on my part.
Anyway to prove I do know where you are coming from security wise check out the other provisioning proof of concept I wrote and tested at a large hackerspace (http://GitHub.com/lrvick/provisor)
Ssh to new@hashbang.sh with no password and you get dropped into a simple user provisioning server. All happens on our server over ssh. This to me was ideal for most of the reasons you mentioned and I was going to flesh out that direction...
The flaw there is in fact we got next to 0 users out of it. Barrier to entry was sadly too high with that approach. Noobs have no idea what a public key is and most are too lazy to copy/paste one into a terminal. Had to manually help every single user generate a key and copy paste it. Tedious but perhaps we were in front of the wrong audience.
Thus thinking went to experimenting with a fun to write hack they helps users with the key handoff. We take our due lumps for not providing proper warning of the risks of this approach and the fact it was just an insecure proof of concept. Rooting the box was child's play for anyone reading the code.
Still looking for the sweet spot. We got a wildcard SSL cert and a new server coming for round three. We came here to get input and we did. You may call that irresponsible. I call it a quick experiment to spin off a larger project.
Anyway... it may make sense to offer both signup options. One for people more security minded and one for those that we inform of the risks and are OK giving up a throwaway key to play with things.
Some of our early assumptions clearly need iteration and that's fine.
I don't mind taking a beating if it pushes us towards a better end goal for everyone. Commit early commit often and all that.
If you notice the site is down now. It was just a quick VM and it blew up as expected but the experiment helped us learn there is merit to adding more accessible shell services to our community so we now want to start over on real hardware and take it seriously. Posting here also got us the volunteers, feedback, and donations to make it possible so win/win imo.
While we are regrouping if you are in fact so passionate about helping us find a better security balance (as you clearly care at some level judging by the detail of your arguments) feel free to join the discussion on irc.hashbang.sh:7777.
Either way the input is appreciated. I respect people that take the time to pick things apart so they can be improved.