9829cb0dea
Instead we will the use the CA certificate provided by the ca-certificates packages, which is now a mandatory depency of pve-manager since 067d24db982be44ff64cb5eb61a3297bba6afdc9 and pve-manager 4.2-17. This change allows us in the future to use different CA for our https repositories. This changed has been tested OK with the following combination: * https repository using a StartCom certificate: works * https repository using a Let's encrypt certificate: works User visible changes: * none : the new configuration file 75pveconf silently overwrites the olderone, except if local changes were made in which case you're presented with the traditional debian menu (keep local/ use packager version/ diff / open a shell)
17 lines
433 B
Plaintext
17 lines
433 B
Plaintext
/etc/init.d/pve-manager
|
|
/etc/init.d/pvedaemon
|
|
/etc/init.d/pveproxy
|
|
/etc/init.d/spiceproxy
|
|
/etc/init.d/pvestatd
|
|
/etc/vz/vznet.conf
|
|
/etc/vzdump.conf
|
|
/etc/logrotate.d/pve
|
|
/etc/apt/apt.conf.d/75pveconf
|
|
/etc/apt/sources.list.d/pve-enterprise.list
|
|
/etc/network/if-up.d/mtu
|
|
/etc/network/if-pre-up.d/vlan
|
|
/etc/network/if-post-down.d/vlan
|
|
/etc/network/if-up.d/bridgevlan
|
|
/etc/network/if-up.d/bridgevlanport
|
|
/etc/modprobe.d/pve-blacklist.conf
|