konevsa/pve-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3,013 Commits 1 Branch 0 Tags
Commit Graph

3 Commits

Author SHA1 Message Date
Emmanuel Kasper
ce532dac59 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 8204daafaf4063dabd8a23c36dfb16719650d2fc 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)
 2016-08-17 12:35:16 +02:00
Dietmar Maurer
d47f3a7e41 install CA certificates used by our repositories 2013-07-25 11:33:55 +02:00
Dietmar Maurer
60d3dcced9 avoid apt autoremoval for pve-kernel packages 2013-07-25 07:53:07 +02:00