sudo-sys

sudo-sys@sudoroom.org

4 participants
743 discussions

Start a nNew thread

Cron <root@sudoroom> cd / && run-parts --report /etc/cron.hourly

by root＠sudoroom.org

run-parts: /etc/cron.hourly/droplet-agent exited with return code 100

4 months, 4 weeks

Cron <root@sudoroom> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

by root＠sudoroom.org

/etc/cron.daily/tor-blocklist-update: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 18478 100 18478 0 0 20084 0 --:--:-- --:--:-- --:--:-- 20062

5 months, 1 week

Re: [sudo-discuss] Re: our mailing list system needs help

by Jake

we're still getting "[sudo-info] Delayed Mail (still being retried)" emails every day...are we retrying to the messages still? Is there a good way to remove those? I can do it if you give me a hint where to look, or what tools to use to dig into this. thank you for your help -jake On Sat, 2 Dec 2023, Jake Watters via sudo-discuss wrote: > Yes please block Tor for now, until we have a better solution > > -jake > > On Sat, Dec 2, 2023, 15:10 Sean Greenslade via sudo-discuss < > sudo-discuss(a)sudoroom.org> wrote: > >> On Fri, Dec 01, 2023 at 09:19:53PM -0800, Jake via sudo-discuss wrote: >>> our mailing list system (postorius) is having problems... we're not sure >> what >>> it is but it looks like some spammer is entering random addresses into >> the >>> "join this mailing list" field and then our system is trying to email a >>> confirmation to those addresses. >>> >>> Anyone want to log in and take a look at it, try to figure out what's >> going >>> on, and figure out a way to fix it? We might need to add a CAPTCHA or at >>> least a checkbox or some sort of puzzle so that people can't just >>> automatically enter email addresses in and have us email them. >> >> I've been doing a bit of investigation on this. It appears that the >> spammer is using Tor to make the subscription requests. I see 68 >> hits to the web interface subscription endpoint within the past day, and >> reverse lookups reveal: >> >>> sortie-tor.a-n-o-n-y-m-e.net. >>> LuxembourgTorNew4.Quetzalcoatl-relays.org. >>> exit-node1.tor-for-privacy.com. >>> tor-exit-anonymizer.appliedprivacy.net. >>> tor-exit-anonymizer.appliedprivacy.net. >>> tor-exit-anonymizer.appliedprivacy.net. >>> tor-exit-anonymizer.appliedprivacy.net. >>> vps-b79172cc.vps.ovh.net. >>> tor-exit-router-xp67.quido.org. >>> fixecalendar.net. >>> tor.d-ku.de. >>> tor-exit.mci.august.is. >>> tor.node15.shadowbrokers.eu. >>> tor-exit-14.zbau.f3netze.de. >>> tor-exit-16.zbau.f3netze.de. >>> tor-exit-5.zbau.f3netze.de. >>> tor-exit-6.zbau.f3netze.de. >>> tor-exit-11.zbau.f3netze.de. >>> tor-exit-12.zbau.f3netze.de. >>> berlin01.tor-exit.artikel10.org. >>> berlin01.tor-exit.artikel10.org. >>> tor-exit-134.relayon.org. >>> tor-exit-136.relayon.org. >>> berlin01.tor-exit.artikel10.org. >>> berlin01.tor-exit.artikel10.org. >>> tor-exit-72.cccs.de. >>> tor-exit-80.cccs.de. >>> tor-exit-81.cccs.de. >>> tor-exit-82.cccs.de. >>> 185-220-102-242.torservers.net. >>> tor-exit-relay-2.anonymizing-proxy.digitalcourage.de. >>> tor-exit-relay-8.anonymizing-proxy.digitalcourage.de. >>> 185-220-102-8.torservers.net. >>> vmi1262847.contaboserver.net. >>> sortie-tor.a-n-o-n-y-m-e.net. >>> tor-exit1-terrahost08.tuxli.org. >>> tor-exit-info.middelstaedt.com. >>> dedicated.sollutium.com. >>> onion.xor.sc. >>> 22.tor-exit.nothingtohide.nl. >>> 26.tor-exit.nothingtohide.nl. >>> 30.tor-exit.nothingtohide.nl. >>> 33.tor-exit.nothingtohide.nl. >>> 34.tor-exit.nothingtohide.nl. >>> 7.tor-exit.nothingtohide.nl. >>> 12.tor-exit.nothingtohide.nl. >>> 15.tor-exit.nothingtohide.nl. >>> 07.rkv.exit.tor.loki.tel. >>> tor.exit.1.newyork.shimadate.com. >>> tor33.quintex.com. >>> tor59.quintex.com. >>> tor76.quintex.com. >>> mail.waytoslowmanagement.de. >>> tor-exit-router.quido.org. >>> exitor.zof.sh. >>> nosoignons.cust.milkywan.net. >>> this-is-a-tor-node---9.artikel5ev.de. >>> tor.node14.shadowbrokers.eu. >> >> My knee-jerk reaction would be to block Tor from our mailing list web >> interface, but I'd want to put that suggestion to the community first. >> Note that users are able to subscribe to mailing lists by direct email >> without using the web interface, so if users wish to maintain anonymity, >> they still have a path. >> >> --Sean >> >> _______________________________________________ >> sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org >> To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org >> More options at >> https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/ >> >

5 months, 1 week

Cron <www-data@sudoroom> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly

by root＠sudoroom.org

ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line 181, in run_with_lock log.exception("Failed to update the fulltext index: %s", e) File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 447, in __exit__ self.unlock() File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 398, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

5 months, 1 week

[sudo-info] Delayed Mail (still being retried) (fwd)

by Jake

i don't understand what these messages mean - something about sudoroom.org failing to send emails to people? Why is this happening? -jake This is the mail system at host sudoroom.org. #################################################################### # THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. # #################################################################### Your message could not be delivered for more than 3 hour(s). It will be retried until it is 2 day(s) old. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <robcestes725(a)gmail.com>: host alt1.gmail-smtp-in.l.google.com[64.233.171.27] said: 450-4.2.1 The user you are trying to contact is receiving mail at a rate that 450-4.2.1 prevents additional messages from being delivered. Please resend your 450-4.2.1 message at a later time. If the user is able to receive mail at that 450-4.2.1 time, your message will be delivered. For more information, please 450-4.2.1 visit 450 4.2.1 https://support.google.com/mail/?p=ReceivingRate ej11-20020a056808384b00b003b89291f44fsi270057oib.133 - gsmtp (in reply to RCPT TO command) NOTE: emails to the Info list were sent to an individual email address (such as info(a)sudoroom.org) with the PRESUMPTION OF PRIVACY. They may include personal information which the sender would not have sent to a public list (such as sudo-discuss). If you must forward messages to a public list, please take great care to REMOVE SENSITIVE INFORMATION! _______________________________________________ Info mailing list -- info(a)sudoroom.org To unsubscribe send an email to info-leave(a)sudoroom.org

5 months, 1 week

*** SECURITY information for humans.sudoroom.org ***

by jay＠humans.sudoroom.org

humans.sudoroom.org : Nov 20 19:25:14 : jay : 3 incorrect password attempts ; TTY=pts/5 ; PWD=/home/jay/tinydnssec ; USER=root ; COMMAND=/bin/su -

5 months, 1 week

Re: [sudo-discuss] Re: help with omni commons front door access

by Jake

You will need ssh access to the server that hosts the door access software please send me your ssh public key and i'll set you up an account. you will have to ssh in and then you can run the script that generates new door access username/passwords what username do you want? -jake On Thu, 23 Nov 2023, Paige P wrote: > I would like to help add accounts (re: request recently in consensus), but > have only been doing this via physical card key. > > Could someone share steps to do that? If it involves ssh, I saved the host > address from when you showed me last time, Jake, but lost the password. > > Thanks, > Paige > > > On Tue, Aug 15, 2023 at 5:22 PM Andrew R Gross via sudo-discuss < > sudo-discuss(a)sudoroom.org> wrote: > >> I’ll do it. >> >> On Fri, Aug 11, 2023 at 12:43 PM Jake via sudo-discuss < >> sudo-discuss(a)sudoroom.org> wrote: >> >>> we need a volunteer to help administer the front door access control >>> system. >>> >>> Someone comfortable with shell commands and vim and ssh, please speak up! >>> >>> extra bonus if someone is available to help with cgi scripts for basic >>> html >>> stuff, in order to make a way for nontechnical people of omni (who have >>> password access) to approve card access. >>> >>> we can collaborate on this of course but i need someone to take over the >>> basic >>> responses to the keycard requests now. >>> >>> -jake >>> _______________________________________________ >>> sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org >>> To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org >>> More options at >>> https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/ >>> >> -- >> *Andrew R Gross, (he/him)* >> 412.657.5332 - shrad.org <http://www.shrad.org> >> _______________________________________________ >> sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org >> To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org >> More options at >> https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/ >> >

5 months, 2 weeks

sending email from sudoroom.org

by Jake

I would like to send out reminders to people who are listed as "members" of sudoroom but whose payments are no longer going through, but I don't think it makes sense for me to do that from my personal email address. Is there a way to send email from sudoroom.org and is anyone available to help make this happen? My plan at this point is basically to take the people who are listed as "members" in sudo-humans and who are not set up for monthly payments right now, and send something like "this is an automated email letting you know that your sudo-humans account is not presently configured for automatic monthly payments. Perhaps this is not surprising for you, for one of the following reasons: 1. fuck sudoroom 2. i dont have any money 3. i pay using paypal, configured on my end 4. i totally forgot about sudoroom, unsubscribe 5. this email address doesn't exist or hopefully 6. Oh thank you for reminding me!!! what's my password?? glad you asked, here's your password, we reset it for you since we expected you lost it: ajs;ldfkja;sldkjf now go enter your credit card information and rejoin the mailing list and show up" -jake

5 months, 3 weeks

tinydns on sudoroom.org

by Jake

i want to install tinyDNS on sudoroom.org to provide an alternate DNS server for spaz.org and g-cipher.net any objections or advice? -jake

5 months, 3 weeks

Your Site: https://sudoroom.org Is Now Back Up

by StatusCake Team

StatusCake Alert -- statuscake.com Website Monitoring Your website https://sudoroom.org has recovered. Total downtime: 00:15:19 To view more details about why your test went down, log into your account: https://app.statuscake.com/

5 months, 3 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys