Nice UPS, for sure. I think we'd want that. I'm not sure if we have
space (or need) for the rack, but I'm adding sudo-sys in case someone
thinks it would be worth picking up.
I could pick up the UPS, possibly later this evening. I don't think I
have a way to transport the rack, even if we decide we want it.
On Mon, 28 Aug 2017 10:26:02 -0700
Gabriel Rodriguez <gabriel.rodriguez(a)gmail.com> wrote:
> I don't suppose you want a free rack/power supply?
>
> Or maybe you know someone who might want it?
>
> I'm moving and can't take it.
>
> Unfortunately I can't deliver this to you, you have to pick it up.
> Also offered is a paper cutter. I'm flying out Thursday so let me
> know asap. Location is in Albany adjacent to El Cerrito plaza. I
> tried to send pics of their condition but I hit your mail server's
> size limit so here are some links to the product pages:
>
>
> Rack:
>
> http://www.apc.com/shop/us/en/products/NetShelter-WX-13U-w-T
> hreaded-Hole-Vertical-Mounting-Rail-Vented-Front-Door-Black/P-AR100HD
>
> UPS:
>
> https://www.tripplite.com/smartonline-120v-1.5kva-1.2kw-doub
> le-conversion-ups-2u-rack-tower-extended-run-snmpwebcard-
> option-usb-db9-serial~SU1500RTXL2UA/
>
> If you can't use these - no big deal.
--
Charley Sheets
On Mon, Aug 28, 2017 at 8:16 PM, Greg <gregshuflin(a)gmail.com> wrote:
> Hello! My name's Greg, I've been dropping by Sudo Room on occasion and I
> notice that the Sudo Commons wifi network doesn't seem to have IPv6
> connectivity. If there's a way to make this happen, I'd love to help out
We're about to install a new router, been waiting on the right
hardware. I can make sure ipv6 works on the new router, but can't
speak for the wifi access points.
Somebody's infected windows laptop? Or spoofed user agent? I'm not
sure the best way to filter out stuff like this.
---------- Forwarded message ----------
From: Support <support(a)lmi.net>
Date: Mon, Aug 28, 2017 at 4:14 PM
Subject: Re: [omni-accounts] [LMi.net #82139] [ABUSE] Your server
142.254.26.9 has been registered as an attack source
To: accounts(a)omnicommons.org
Hello,
We have received a report that your IP address has participated in
sending known spam/a large-scale attack against another
network/detected malicious requests from the IP listed below.
The reported IP address is: 142.254.26.9
==================
16/Aug/2017:08:46:34 - 142.254.26.9 - - [ +0300] "POST /xmlrpc.php HTTP/1.0"
302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101
Firefox/40.1"
16/Aug/2017:08:46:35 - 142.254.26.9 - - [ +0300] "POST /xmlrpc.php HTTP/1.0"
302 - "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101
Firefox/40.1"
]
Url: [www1.edis.at:60412/verify.php]
Remote connection [142.254.26.9:65325]
Agent: [Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101
Firefox/40.1]
Url: [noranoritastudiosandros.gr/xmlrpc.php]
Remote connection [142.254.26.9:53884]
Agent: [Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101
Firefox/40.1]
Post data: [Array
(
[<?xml version] => "1.0" encoding
)
]
It is likely that your network was compromised and needs to be
secured. Please check your network to ensure this does not repeat.
Best,
--
LMi.net Technical Support
510-843-6389 Ext. 4
lmi.net/support
I can't physically be there but seeing complains that the internet is
down at Omni. I can't remotely access any machines there. Is anybody
able to go check? Thanks.
I'm sick of reminding people exactly how to request key cards. From
now on let's just send people to this URL:
https://omnicommons.org/keys/
It won't (and probably shouldn't) automatically add someone's card to
the door computer. But it will send a formatted email to the keys
list, which already exists for this purpose:
https://omnicommons.org/lists/listinfo/keys
The code is at /home/occupy/public_html/keys/index.php. It could use
lots of love, such as:
* somebody with front end skills to give it nice CSS
* A writer to give it a nice intro text
* A coder to make it better/safer/more automated
This repo was a mess with many dangling branches and un-committed
code. With some merging magic, I created a new 'master' branch which
all previous branches can fast-forward to, and updated the ref names
on both the door computer and github. I also committed the code which
has been running live for several months, so github now reflects
reality.
I added some things to the gitignore file (node_modules, etc) -
otherwise no checked out files are changed. Only the git refs.
https://github.com/sudoroom/doorjam
There remains one unmerged branch, called "ledstrip", which is very
old (2014) and I didn't want to deal with that.
The "declaration of intent to join" apparently just went blank when
submitted.
Should we just switch it out with a notice saying "Please answer these
questions in an email to this address"?
--
marc/juul
Is there any need to renew our Gandi-signed SSL cert for sudoroom.org
(which expires in May)? I was thinking we could just switch to Let's
Encrypt. Anyone agree/disagree?
--
Charley Sheets