pve-manager/debian/conffiles
Fabian Grünbichler cfbc6d9e25 Do not use a hardcoded Certificate Authority for https repositories
Instead we will the use the CA certificate provided by the
ca-certificates packages, which is now a mandatory depency of
pve-manager since 35e0ea9a1d and
pve-manager 3.4-15. 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)

Cherry-Picked-By: f.gruenbichler@proxmox.com (from 4.2)
2016-08-17 13:35:28 +02:00

15 lines
334 B
Plaintext

/etc/init.d/pve-manager
/etc/init.d/pvedaemon
/etc/init.d/pveproxy
/etc/init.d/spiceproxy
/etc/init.d/pvebanner
/etc/init.d/pvenetcommit
/etc/init.d/pvestatd
/etc/cron.daily/pve
/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