sudo-sys

sudo-sys@sudoroom.org

1 participants
883 discussions

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

1 week

*** SECURITY information for localhost ***

by zootboy＠sudoroom.org

localhost : Sep 12 04:28:54 : zootboy : a password is required ; PWD=/home/zootboy ; USER=root ; COMMAND=/usr/bin/tar -cvzf - /

3 weeks, 5 days

*** SECURITY information for localhost ***

by zootboy＠sudoroom.org

localhost : Sep 12 04:21:43 : zootboy : a password is required ; PWD=/home/zootboy ; USER=root ; COMMAND=/usr/bin/tar -cvzf - /

3 weeks, 5 days

*** SECURITY information for localhost ***

by zootboy＠sudoroom.org

localhost : Sep 12 04:17:40 : zootboy : a password is required ; PWD=/home/zootboy ; USER=root ; COMMAND=/usr/bin/tar -cvzf - /

3 weeks, 5 days

https://sudoroom.org - SSL Certificate Valid!

by StatusCake Team

This is an HTML mail. Please use a mail-client that supports this message

1 month

https://sudoroom.org - SSL Certificate Expiring Soon!

by StatusCake Team

This is an HTML mail. Please use a mail-client that supports this message

1 month

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

1 month, 1 week

apt-listchanges: news for sudoroom

by root

apache2 (2.4.65-1~deb11u1) bullseye-security; urgency=medium Following the resolution of CVE-2025-23048, some SSL-enabled websites may begin encountering the error (AH02032): . Misdirected Request: The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection. . This behavior is particularly noticeable with AWS Application Load Balancers. Although they support intelligent SNI handling, they do not (as of this writing) relay SNI data to the target server, resulting in failed connections when hostnames don’t align. . Without an SNI provided by the client, there is nothing httpd can do to determine which vhost/configuration should be used to provide the correct certificate (and TLS authentication eventually) whenever multiple vhosts listen on the same IP:port. . That's because reading the HTTP Host header necessarily has to happen after the TLS handshake/auth/decryption (and later renegotiation is not an option with TLSv1.3). . So those connections fall back to the first vhost declared on the IP:port for the TLS handshake part, and if the request Host header finally matches a different vhost with a different TLS configuration it's rejected with AH02032. . Before 2.4.64 the check was not accurate and would allow that, with security implications. . As a workaround, you may (after a risk analysis) generate a wildcard certificate. If you’re managing multiple domains, consolidate them into a single certificate by including each wildcard domain as an alias. Then, update the Apache configuration to reference this unified certificate. . Another possible workaround is to configure each virtual host to listen on a separate port. This approach avoids SNI-related issues by ensuring that each vhost is uniquely addressed through its own connection endpoint, thereby allowing distinct TLS configurations without ambiguity. . This error may also stem from a misconfigured HAProxy setup. In such cases, enabling dynamic SNI handling on HAProxy might be necessary to ensure that the correct hostname is passed through during the TLS handshake. After risk analysis, it could be done by using "sni req.hdr(Host)" directive. -- Bastien Roucariès <rouca(a)debian.org> Fri, 25 Jul 2025 20:33:38 +0200

1 month, 3 weeks

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

2 months, 1 week

https://sudoroom.org - SSL Certificate Valid!

by StatusCake Team

This is an HTML mail. Please use a mail-client that supports this message

3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys