This is the last call for comments for the review of debconf templates for ca-certificates. The reviewed templates will be sent on Friday, July 06, 2007 to the package maintainer as a bug report and a mail will be sent to this list with "[BTS]" as a subject tag. --
Template: ca-certificates/trust_new_crts Type: select _Choices: yes, no, ask Default: yes _Description: Trust new certificate authorities' certificates? This package may install new CA (Certificate Authority) certificates when upgrading. You may want to check such new CA certificates and select only certificates that you trust. . - yes: new CA certificates will be trusted and installed; - no : new CA certificates will not be installed by default; - ask: prompt for each new CA certificates. Template: ca-certificates/new_crts Type: multiselect _Choices: ${new_crts} _Description: New certificates to activate: During upgrades, new certificates will be added. Please choose those you trust. Template: ca-certificates/enable_crts Type: multiselect _Choices: ${enable_crts} _Description: Certificates to activate: This package installs common CA (Certificate Authority) certificates in /usr/share/ca-certificates. . Please select the certificate authorities you trust so that they're installed into /etc/ssl/certs. They will be compiled into a single /etc/ssl/certs/ca-certificates.crt file.
Source: ca-certificates Section: misc Priority: optional Maintainer: Fumitoshi UKAI <ukai@debian.or.jp> Build-Depends: debhelper (>> 4.1.16), po-debconf Build-Depends-Indep: ruby Standards-Version: 3.5.9 Package: ca-certificates Architecture: all Depends: openssl, ${misc:Depends} Enhances: libssl0.9.8, openssl Description: Common CA certificates This package includes the followings PEM files of CA certificates: . - spi-inc.org - db.debian.org - debconf.org - Mozilla builtin CAs - CACert.orgs - Brazilian government - Signet - QuoVadis . It allows SSL-based applications to check for the authenticity of SSL connections. . Please note that certificate authorities whose certificates are included in this package are not in any way audited for trustworthiness and RFC 3647 compliance, and that full responsibility to assess them belongs to the local system administrator.
Attachment:
signature.asc
Description: Digital signature