ca-certificates 20130610 source package in Ubuntu

Changelog

ca-certificates (20130610) unstable; urgency=low


  [ Michael Shuler ]
  * Install CAcert root and class3 certificates individually, no longer
    installing the concatenation of the two. The individual certificates
    are installed as cacert.org_root.crt and cacert.org_class3.crt for ease
    of identification. Additionally, this allows openssl maintainers to drop
    a problematic patch to c_rehash for handling multi-certificate files.
    (see #642314)  Closes: #692323
  * Update Vcs-* fields for lintian vcs-field-not-canonical
  * Update to machine-readable debian/copyright file v1.0

  [ Thijs Kinkhorst ]
  * Drop upgrading code for upgrades from Debian Etch and earlier. 
  * Remove obsolete debconf.org CA certificate. DebConf now uses an
    intermediate certificate signed by SPI. (Closes: #693405)
  * Remove obsolete SPI CA certiticate.
  * Update Standards-Version: 3.9.4 (no changes needed)
  * Clean up man page (LP#: 850997).

 -- Thijs Kinkhorst <email address hidden>  Mon, 10 Jun 2013 19:52:15 +0200

Upload details

Uploaded by:
Michael Shuler
Uploaded to:
Sid
Original maintainer:
Michael Shuler
Architectures:
all
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Saucy: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
ca-certificates_20130610.dsc 1.4 KiB e2be89bfb160dd80ea2b2996879c77e80eb5feb4569a125f2146ced43479fbb0
ca-certificates_20130610.tar.gz 290.6 KiB 9529a9cdfca53dc2ecea96171d8d2ff6ff343843f894af4d446686f02a6c03f2

Available diffs

No changes file available.

Binary packages built by this source

ca-certificates: Common CA certificates

 This package includes PEM files of CA certificates to allow SSL-based
 applications to check for the authenticity of SSL connections.
 .
 It includes, among others, certificate authorities used by the Debian
 infrastructure and those shipped with Mozilla's browsers.
 .
 Please note that Debian can neither confirm nor deny whether the
 certificate authorities whose certificates are included in this package
 have in any way been audited for trustworthiness or RFC 3647 compliance.
 Full responsibility to assess them belongs to the local system
 administrator.