Disable Node-Red on Unicorn

Let’s figure out how to disable Node-Red on #unicorn

@the we’ll get it done together!

Sounds good, I might need to generate a new key to get back on unicorn

posted an updated key and dropped in #unicorn as well, @lindner @croepha welcome to the par’tay

https://www.noisebridge.net/wiki/User:Ⅹ#KEY

If you have time today go for it. I am quite busy on week days.

···

On Mon, Jul 26, 2021, 9:00 AM the via Noisebridge <noreply@discuss.noisebridge.info> wrote:

the Ⅹ, Driveway Enthusiast
July 26

posted an updated key and dropped in #unicorn as well, @lindner @croepha welcome to the par’tay

https://www.noisebridge.net/wiki/User:Ⅹ#KEY


Visit Topic or reply to this email to respond.


In Reply To

the Ⅹ, Driveway Enthusiast
July 26

Sounds good, I might need to generate a new key to get back on unicorn


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

will do, did you get a chance to update key or add dave or paul, I can see if Dan still has access handy somewhere.

I added the people asking on Slack. Take a look in authorized keys in case there are others.

I fully removed npm from the base file system. It was hammering our CPU; now it is fine. Couple thoughts:

@the your account has been very active in top, so perhaps we should just fully remove it from the system if you’ve lost your SSH key.

ufw is lookling like swiss cheese. @themanmaran just got a letter related to our services that is posted on #rack, so we should go through and lock down all of the open ports in the firewall we aren’t using.

removed allow rule for node-red 1880 port. also for 8008, which the letter complained of. That port relates to scuttlebutt so it might go offline, but I don’t have time to troubleshoot at the moment.

Thoughts and suggestions appreciated. I’ll be offline for the next week, but please do step up if you wish to work on this! Thanks. :heart: