Hey Robert, > On 14 Jan 2015, at 01:35, Robert McWilliam <[email protected]> wrote: > > I have restored SSH access to doorbot, but ATM only for me: I have > removed all other keys and changed the passwords. > > I don't think it is a good idea to restore access to the same "anyone > who asks for it" level we've been running with up to now.
I don’t think allowing access to doorbot is bad, allowing *sudo* access is. If it weren’t for sudo access, I wouldn’t have been able to do `sudo killall sshd`. (Again, I’m really sorry about that.) > The previous permissive access to doorbot was because we were hosting > a number of "toy" applications there: the LED sign, text to speech > stuff, sensors, cards against hackspace, red alert and probably others > that I've forgotten. I liked that we had a machine to dump these on > and there was some nice collaboration as different people have updated > some of those apps. For the stuff where it was just a server hackr > would be a great alternative but some of it depends on being connected > to hardware in the space. I'd like to offer my previous laptop to be > set-up somewhere in the space to host these kind of apps. It's > reasonably powerful (about 3 year old i5) and idles at about 8W so > shouldn't cost much to run. One option would just be to run all the toys in a VM on doorbot and give people access to the VM. It’d be slow, sure, but none of this stuff really needs to be ultra-fast, and if someone screws up, only the toys are lost. Thoughts? -- Andrea Faulds http://ajf.me/ _______________________________________________ 57north-discuss mailing list [email protected] http://lists.57north.co/listinfo/57north-discuss
