@Simon: Uh, my idealistic world view is destroyed ;-).
Best practice used to be to stick with the distribution's packages because they
will take care of all nasty edge cases and security bugs.
If the wordpress package really is badly maintained it would be better
to remove it than to suggests
Public bug reported:
22.04 ships with php 8.1, due to some mysql logging issue the
installation of a new wordpress sites dies with a white screen of death
if wp-admin/install.php is called.
Upstream wordpress fixed the issue with:
https://core.trac.wordpress.org/changeset/51582 and I can confirm
** Package changed: redmine (Ubuntu) => fail2ban (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905187
Title:
fail2ban cannot safely enable roundcube-auth jail with 20.04 LTS
To manage
Public bug reported:
The jail roundcube-auth checks the roundcube error.log
The error.log name was changed in 20.04 - fail2ban tries to look for:
cat /etc/fail2ban/paths-common.conf | grep round
roundcube_errors_log = /var/log/roundcube/errors
But instead in 20.04 this has been moved to:
I am not sure how to tag this bug (fix-verified).
In the above dialog I can only set the state to fix-released ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868955
Title:
[SRU] after upgrade
Hi,
I added the proposed repo and it works as expected.
Jun 27 10:49:26 www postfix/master[1920]: daemon started -- version 3.4.13,
configuration /etc/postfix
root@www:~# posttls-finger -t30 -T180 -c -L verbose,summary bueren.space
posttls-finger: initializing the client-side TLS engine
Hi Lucas,
yes your ppa version seems to work.
I can also send emails again with the dane-only policy.
Details:
The warning still exists, but posttls-finger gets a valid RR record:
root@www:~# posttls-finger -t30 -T180 -c -L verbose,summary bueren.space
posttls-finger: initializing the
You can foolproof this with your settings by writing to my test mail
account and setting this domain to dane-only:
"I created one test account you may use to send some local mail to:
ubuntu-bug@bueren.space"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
HI Nick,
nice idea, sounds reasonable, but ...
I am not using systemd.resolv and I can see the ad flag if I query unbound
locally.
I am simply guessing: Maybe tlsmgr really needs systemd?
Anyway here are my settings and snippets:
sudo systemctl disable systemd-resolved
sudo systemctl enable
Hi Nick,
yep. My workaround was to change this to dane instead of dane-only.
It is a tiny bit disappointing that it is still broken because I prefer to use
ubuntu as a server system instead of debian.
Reading this discussion I guess the feature is working in debian but not in
ubuntu.
Thanks for your replies.
@andreas:
Well, it was a bit hidden in my bug report but the real issue is that postfix
doesn't delivers mail to dane-only domains:
to=, relay=none, delay=2126, delays=2126/0.01/0/0,
dsn=4.7.5, status=deferred (non DNSSEC destination)
I created one test account you
Public bug reported:
My postfix configuration uses dane-only policies for some domains.
After upgrading from LTS 18.04 to the current developing LTS 20.04 this stopped
working.
Compare the following commands:
Ubuntu 18.04:
$ posttls-finger -t30 -T180 -c -L verbose,summary bueren.space
Public bug reported:
While upgrading from ubunut 16.04 LTS to 18.04 LTS redmine post-
installation script throws the following error:
Could not find builder-3.2.3 in any of the sources
Details:
$ apt-cache show redmine
Gave me two versions 3.4.4 and the version from 16.04 LTS
Doing a
$ apt
13 matches
Mail list logo
