tags 481874 moreinfo thanks I'm just trying to reproduce this problem - can't make it!
Lets assume: We add a local ca-cert to /usr/local/share/ca-certificates like told in update-ca-certificates(8) cp /usr/share/doc/openvpn/examples/sample-keys/ca.crt /usr/local/share/ca-certificates/testcert.crt and run update-ca-certificates afterwards Updating certificates in /etc/ssl/certs... 1 added, 0 removed; done. Now testcert.crt appears in /etc/ssl/certs as link to /usr/local/share/ca-certificates/testcert.crt Now the upgrade case: Preparing to replace ca-certificates 20090814+nmu2 (using .../ca-certificates_20090814+nmu3_all.deb) ... Unpacking replacement ca-certificates ... Setting up ca-certificates (20090814+nmu3) ... (+nmu3 includes no changes affecting the reported behavior) Updating certificates in /etc/ssl/certs... 31 added, 3 removed; done. 31 are newly provided through +nmu3 and 3 got removed. Now, my testcert is still in /etc/ssl/cert but is now called testcert.pem as a .pem-extension is required for openssl's c_rehash. So i see the following action: Users want to place automatically there ca-certs into /etc/ssl/certs should only place the certs in /usr/local/share/ca-certificates and run update-ca-certificates once. Stefan -- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ---------- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
