After installing sudo 1.8.29 from pkgsrc (security/sudo) I started frequently seeing this warning message:
sudo: setrlimit(3): Invalid argument
It took a few rounds, but eventually I applied an acceptable patch for the pkgsrc-2019Q4 release. Later an upstream workaround was committed and included in the sudo 1.8.30 release. (more…)
pve-root-ca.pem file in Keychain Access (File > Import Items), then open the item and mark it trusted (e.g. Always trust).
The new requirements for trusted certificates on macOS Catalina and iOS 13 blocked me from accessing the web UI on Proxmox installations (NET::ERR_CERT_REVOKED). Fresh installations would work, as Proxmox has been updated to generate “better” certificates. Existing installations, unfortunately, are not automatically fixed on upgrading to Proxmox 6.
Certificate management on Proxmox is handled with pvenode(1) — except when it isn’t. There is no functionality there for regenerating the self-signed certificates. An older wiki page for HTTPS certificate configuration provided some useful hints: pvecm(1) has an updatecerts command. It won’t, however, regenerate existing (unexpired) certificates.
Against the warnings on the Certificate mangement page I thought I’d try removing the apparently relevant files manually:
cd /etc/pve rm pve-root-ca.pem priv/pve-root-ca.key nodes/*/pve-ssl.{key,pem}
Then I regenerated the certificates and restarted pveproxy(8) on each node:
pvecm updatecerts --force systemctl restart pveproxy
Refreshing the page in the browser restores access to the web UI.