rpms/ca-certificates
7
0
Fork 0
Code Issues Pull Requests Releases Activity

- clarification updates to manual page

Browse Source
This commit is contained in:
Kai Engert 2013-07-09 12:50:17 +02:00
parent 9ac574b7ef
commit 540618e93b
2 changed files with 10 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ca-certificates.spec
View File

@ -27,7 +27,7 @@ Name: ca-certificates
# because all future versions will start with 2013 or larger.)
Version: 2013.1.94
Release: 14%{?dist}
Release: 15%{?dist}
License: Public Domain
Group: System Environment/Base
@ -286,6 +286,9 @@ fi
%changelog
* Tue Jul 09 2013 Kai Engert <kaie@redhat.com> - 2013.1.94-15
- clarification updates to manual page
* Mon Jul 08 2013 Kai Engert <kaie@redhat.com> - 2013.1.94-14
- added a manual page and related build requirements
- simplify the README files now that we have a manual page

17
update-ca-trust.8.txt
View File

@ -147,11 +147,9 @@ directories or in any of their subdirectories, or after adding a file,
it is necessary to run the 'update-ca-trust extract' command,
in order to update the consolidated files in /etc/pki/ca-trust/extracted/ .
Legacy applications that rely on legacy filenames benefit from configuration
updates only if this dynamic configuration feature is in the enabled state.
Applications that use the legacy PKCS#11 module libnssckbi.so with the
configuration feature in the enabled state, and any application capable of
Applications that load the legacy PKCS#11 module using filename libnssckbi.so
(which has been converted into a symbolic link pointing to the new module)
and any application capable of
loading PKCS#11 modules and loading p11-kit-trust.so, will benefit from
the dynamically merged set of certificates and trust information stored in the
/usr/share/pki/ca-trust-source/ and /etc/pki/ca-trust/source/ directories.
@ -218,18 +216,15 @@ FILES
-----
/etc/pki/tls/certs/ca-bundle.crt::
Legacy filename, file contains a list of CA certificates trusted for TLS server authentication usage, in the simple BEGIN/END CERTIFICATE file format, without distrust information.
If legacy support is disabled, this is a static file and will remain unchanged.
Only if the legacy support is enabled, this file is a symbolic link that refers to the consolidated output created by the update-ca-trust command.
This file is a symbolic link that refers to the consolidated output created by the update-ca-trust command.
/etc/pki/tls/certs/ca-bundle.trust.crt::
Legacy filename, file contains a list of CA certificates in the extended BEGIN/END TRUSTED CERTIFICATE file format, which includes trust (and/or distrust) flags specific to certificate usage.
If legacy support is disabled, this is a static file and will remain unchanged.
Only if the legacy support is enabled, this file is a symbolic link that refers to the consolidated output created by the update-ca-trust command.
This file is a symbolic link that refers to the consolidated output created by the update-ca-trust command.
/etc/pki/java/cacerts::
Legacy filename, file contains a list of CA certificates trusted for TLS server authentication usage, in the Java keystore file format, without distrust information.
If legacy support is disabled, this is a static file and will remain unchanged.
Only if the legacy support is enabled, this file is a symbolic link that refers to the consolidated output created by the update-ca-trust command.
This file is a symbolic link that refers to the consolidated output created by the update-ca-trust command.
/usr/share/pki/ca-trust-source::
Contains multiple, low priority source configuration files as explained in section <<sourceconf,SOURCE CONFIGURATION>>. Please pay attention to the specific meanings of the respective subdirectories.