Bug 1021133 - docs-check: Shared Certificate Tools
Summary: docs-check: Shared Certificate Tools
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: security-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On: 998546
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-19 17:19 UTC by Pete Travis
Modified: 2019-11-07 15:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 998546
Environment:
Last Closed: 2019-11-07 15:29:47 UTC


Attachments (Terms of Use)

Description Pete Travis 2013-10-19 17:19:31 UTC
+++ This bug was initially created as a clone of Bug #998546 +++

This is a tracking bug for Change: Shared Certificate Tools
For more details, see: http://fedoraproject.org//wiki/Changes/SharedCertificateTools

Fedora now has infrastructure for sharing system trusted certificates between the various crypto libraries.

--- Additional comment from Stef Walter on 2013-08-29 08:32:51 EDT ---

Substantiably testable using p11-kit-0.19.4 which is in Fedora 20.

--- Additional comment from Jaroslav Reznik on 2013-10-11 04:46:13 EDT ---

This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].

All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be 
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/20/Schedule
===========================

Docs Task: Identify documentation that is impacted by this change and open bugs as required.

Comment 1 Petr Bokoc 2019-11-07 15:29:47 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.


Note You need to log in before you can comment on or make changes to this bug.