[Bug 1970194] Re: ubuntu 22.04 package wordpress incompatible with default php version 8.1
@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 that the distribution takes care of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970194 Title: ubuntu 22.04 package wordpress incompatible with default php version 8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1970194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970194] [NEW] ubuntu 22.04 package wordpress incompatible with default php version 8.1
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 that applying this patch generates the expected installation behaviour as usual with a working admin user interface. ** Affects: wordpress (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970194 Title: ubuntu 22.04 package wordpress incompatible with default php version 8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wordpress/+bug/1970194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905187] Re: fail2ban cannot safely enable roundcube-auth jail with 20.04 LTS
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1905187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905187] [NEW] fail2ban cannot safely enable roundcube-auth jail with 20.04 LTS
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: /var/log/roundcube/errors.log After appending the .log everthing seems to work as expected. ** Affects: redmine (Ubuntu) Importance: Undecided Status: New -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1905187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: [SRU] after upgrade to 20.04: dane support is not working
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 to 20.04: dane support is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: [SRU] after upgrade to 20.04: dane support is not working
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 posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: problem talking to server private/tlsmgr: No such file or directory posttls-finger: warning: no entropy for TLS key generation: disabling TLS support posttls-finger: using DANE RR: _25._tcp.www.bueren.space IN TLSA 3 0 1 D7:BC:71:07:19:28:E7:97:F9:86:52:02:EB:90:99:4B:B1:DB:EE:8D:FF:B5:D5:6D:15:B2:D8:AC:25:99:AA:5F -- 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 to 20.04: dane support is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
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 client-side TLS engine posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: problem talking to server private/tlsmgr: No such file or directory posttls-finger: warning: no entropy for TLS key generation: disabling TLS support posttls-finger: using DANE RR: _25._tcp.www.bueren.space IN TLSA 3 0 1 D7:BC:71:07:19:28:E7:97:F9:86:52:02:EB:90:99:4B:B1:DB:EE:8D:FF:B5:D5:6D:15:B2:D8:AC:25:99:AA:5F -- 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: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868955 Title: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
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 unbound-resolvconf # dig +dnssec A www.dnssec.cz | grep ad ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 Taking a short look into the package-helper for unbound-resolvconf I don't see anything obvious. I changed the settings after or because of reading this blog: https://blobfolio.com/2017/05/fix-linux-dns-issues-caused-by-systemd- resolved/ -- 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: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
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. Additionally I resisted building Postfix from source to detect the deeper bug reason but if this bug doesn't process maybe this would be an option. I enjoyed the idea from this blogpost: https://briefings.threeletter.agency/post/120317637998/fixing-postfix-a -trip-down-a-smtp-tls-rabbit -- 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: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] Re: after upgrade to 20.04: posttls cannot connect to private/tlsmgr
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 may use to send some local mail to: ubuntu-bug@bueren.space This is valid DANE domain and to reproduce the issue use the following tls policies: smtp_tls_policy_maps = hash:/etc/postfix/tls_policy $ cat /etc/postfix/tls_policy bueren.space dane-only The smtp local client tries to verifiy the TLSA entries by using DNSSEC. I simply use a local unbound DNS server. This setting stopped working after the upgrade. Maybe the posttls-finger is not so important, but this will trouble all mail admins who have some dane-only entries in their policy (Oops, my DNS Server DNSSEC is bogus -> Nope. Probably the other mail server isn't DANE safe anymore -> Nope.). -- 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: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868955] [NEW] after upgrade to 20.04: posttls cannot connect to private/tlsmgr
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 posttls-finger: initializing the client-side TLS engine posttls-finger: using DANE RR: _25._tcp.www.bueren.space IN TLSA 3 0 1 D7:BC:71:07:19:28:E7:97:F9:86:52:02:EB:90:99:4B:B1:DB:EE:8D:FF:B5:D5:6D:15:B2:D8:AC:25:99:AA:5F posttls-finger: setting up TLS connection to www.bueren.space[31.15.68.4]:25 Ubuntu 20.04: $ posttls-finger -t30 -T180 -c -L verbose,summary bueren.space posttls-finger: initializing the client-side TLS engine posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: connect to private/tlsmgr: No such file or directory posttls-finger: warning: problem talking to server private/tlsmgr: No such file or directory posttls-finger: warning: no entropy for TLS key generation: disabling TLS support Sending email to this domains stopped working with the following (obviously wrong) error message in mail.log: to=, relay=none, delay=2126, delays=2126/0.01/0/0, dsn=4.7.5, status=deferred (non DNSSEC destination) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: postfix 3.4.10-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Wed Mar 25 11:22:11 2020 EtcMailname: mail.kivitendo.de Hostname: www.kivitendo.de InstallationDate: Installed on 2016-12-14 (1196 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PostconfMydomain: kivitendo-erp.de PostconfMyhostname: www.kivitendo-erp.de PostconfMyorigin: /etc/mailname ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ResolvConf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 nameserver 127.0.0.1 search kivitendo-erp.de SourcePackage: postfix UpgradeStatus: Upgraded to focal on 2020-03-02 (23 days ago) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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: after upgrade to 20.04: posttls cannot connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1868955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789091] [NEW] redmine upgrade post-installation script crashes
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 upgrade redmine breaks with this verbose output (some german is involved): redmine (3.4.4-1) wird eingerichtet ... dbconfig-common: writing config to /etc/dbconfig-common/redmine/instances/default.conf dbconfig-common: flushing administrative password `/var/www` is not writable. Bundler will use `/tmp/bundler/home/root' as your home directory temporarily. Could not find builder-3.2.3 in any of the sources Run `bundle install` to install missing gems. Ok, builder has a lower version number: ruby-builder/bionic,bionic,now 3.2.2-4 (installed) Running bundle install on the console with some options did not help either. I am not an expert in ruby (on rails) and the first googling did not offer any help either. Thanks Jan ** Affects: redmine (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789091 Title: redmine upgrade post-installation script crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redmine/+bug/1789091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
