>> The monitor door.sudoroom.org (https://door.sudoroom.org/) is currently DOWN
>> (Connection Timeout).
Matthew Senate <mattsenate(a)gmail.com> wrote:
>> I haven't seen this come back up yet. Any reason why this might be
>> disconnected? Any access issues?
> I can't ssh into tamale either. I suspect either hardware or network issues.
UPDATE: sudoroom's network was down. I can access it again now.
Still has an expired certificate though...
> The monitor door.sudoroom.org (https://door.sudoroom.org/) is currently DOWN
> (Connection Timeout).
On Fri, Jun 13, 2014 at 11:33 AM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> I haven't seen this come back up yet. Any reason why this might be
> disconnected? Any access issues?
I can't ssh into tamale either. I suspect either hardware or network issues.
On Sun, Jun 1, 2014 at 3:25 PM, Marc Juul <juul(a)labitat.dk> wrote:
> Oh. I see. It was trying to make a nice .onion address. Well it was using
> 600+ % CPU which probably isn't nice on a shared server? I suspended the
> process. If you feel that it's fine to keep it running then I don't have a
> problem. I don't know what the linode policy is on this.
I think it's fine. It's running at maximal niceness (ionice -c 3 nice
-n 18) so won't impact our own services. That's a good point about
sharing with other customers, I hadn't considered that. The only data
point I can offer about their policy is I have done this on half a
dozen other linode servers and they've never said a word. :)
Last week the sudoroom.org server had a compromise. We are pretty sure
that it was caused by an outdated Tor which I had stupidly installed
from Ubuntu's repos instead of from torproject.org. Tor was running as
a client and serving some .onion addresses but was not any kind of
relay or middle/exit node.
On Monday (May 19) Linode started getting complaints that our ip
address was scanning parts of the internet for port 22. At that point
we started auditing and upgrading some neglected services. We also
started filtering and logging outgoing iptables. The next day we
caught another scan in progress and realized it was probably the
"debian-tor" user, so we switched to the more up-to-date package from
torproject.org. We haven't seen another scan since then.
We will keep most outgoing packets filtered at least until we switch
to a new server. That's going to happen soon, as soon as sudoroom has
a proper debit card. We can open up specific ports meanwhile if you
need them.
The drama is probably over but this is just to let you all know that happened.
The power to all of sudo room was turned off and on again at the circuit
breaker tonight between 4 and 5 am.
This was done by am obviously drunk Timon. I don't know why he was flicking
switches in the circuit breaker box. He apologized and claimed to not know
that any of the circuit breakers were related to sudo room.
I told him that he'd just caused all of our infrastructure to hard reset.
He became agitated and started complaining that I was staying on the topic
after he had already explained himself. I then asked him to leave the
common space. He refused, became very agitated, claimed a legal right to be
in the common space and among other things requested that I leave his
vicinity. I felt threatened by his behavior.
Most of the sudo room infrastructure seemed to recover gracefully from the
hard reboot. The internet connection did not come back up automatically,
but after a couple of reboots of the DSL modem the connection was back.
--
marc/juul
Hey all,
I added a slew of templates to our wiki, including baseline infoboxes,
corresponding templates and styles that help those infoboxes run, and
particularly a Recipe infobox that uses the "hrecipe" microformat to help
parsers find our recipe data!
https://sudoroom.org/wiki/Template:Infobox_recipe
I plan to implement this box soon for sudo mate, and various other sudo
food hacks!
// Matt
p.s. microformat in question:
http://microformats.org/wiki/microformats2#h-recipe
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey all,
Just noticed that when loading https://sudoroom.org/calendar from my
Firefox, I am immediately redirected to
https://sudoroom.org/wp-login.php?action=logout&_wpnonce=51eee2a608 and
asked if I'm sure I want to log out.
I'll be at sudo this evening if anyone wants to see the bug replicated
and take a poke at it.
Cheers,
Jenny
http://jennyryan.nethttp://sudomesh.orghttp://thevirtualcampfire.orghttp://technomadic.tumblr.com
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
- -Laurie Anderson
"Storytelling reveals meaning without committing the error of defining
it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
- -Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTeqTtAAoJEHTWWpBUSeDhai8IALYkQB5iBiIxGwi//PqgXhEg
xh/rQhl7Y5gA22258LKMYz+dUIRxXjXJTxrc/5NUwO9NKfcIy97YwFMSnnfEqxQs
jfI6QuMnNHj8p0Wzhtc+Xcd7U9JidASArbrWNs3J6Cb/nN32h+ARDSfKp6nGzdBf
ebvpxJYNZDHOLUL0Oz8EgjE6CFZZlqa8x0XIEOFYjm/X4QQbe41A+sZ3TAJEOScr
zmGVgWVx0SxYNA11b1co0vHBPjPyZJLRkeSBFYkrnBVZg5YJZIg9YYt2bUKgmhta
V90Kr1oy1gzf9FLi6+L1qWYopiQ9ssF/fP3ffQj4tHRIjVnPGGHXu3IA5xahzOE=
=ZX8q
-----END PGP SIGNATURE-----
Hey all,
Daniel and I had a discussion of things we'll need for a Reboot'd network.
There's a preliminary wishlist, but other docs and additions are welcome:
https://sudoroom.org/wiki/Network/Reboot
// Matt
