Parents (Total: 680)

The searched file hash is included in 680 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	0BB6F8634A07D33F1F4634BFEBF6E63D
PackageArch	noarch
PackageDescription	Dogtag Certificate System is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. These platform-independent PKI executables are used to help make Dogtag Certificate System into a more complete and robust PKI solution.
PackageMaintainer	Fedora Project
PackageName	pki-java-tools
PackageRelease	1.fc14
PackageVersion	1.3.1
SHA-1	004AD6C96F25FD140BE11E866D31E886A8CA958D
SHA-256	33EE50C70B3B366369200ABC85E4851D70321F0D80165587CF0D1CD15FDD3844

Key	Value
MD5	7A6170A71778F94E99D0C99FACC01190
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Online Certificate Status Protocol (OCSP) Manager is an optional PKI subsystem that can act as a stand-alone OCSP service. The OCSP Manager performs the task of an online certificate validation authority by enabling OCSP-compliant clients to do real-time verification of certificates. Note that an online certificate-validation authority is often referred to as an OCSP Responder. Although the Certificate Authority (CA) is already configured with an internal OCSP service. An external OCSP Responder is offered as a separate subsystem in case the user wants the OCSP service provided outside of a firewall while the CA resides inside of a firewall, or to take the load of requests off of the CA. The OCSP Manager can receive Certificate Revocation Lists (CRLs) from multiple CA servers, and clients can query the OCSP Manager for the revocation status of certificates issued by all of these CA servers. When an instance of OCSP Manager is set up with an instance of CA, and publishing is set up to this OCSP Manager, CRLs are published to it whenever they are issued or updated. For deployment purposes, an OCSP Manager requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * pki-silent Additionally, Certificate System requires ONE AND ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages: * dogtag-pki-theme (Dogtag Certificate System deployments) * redhat-pki-theme (Red Hat Certificate System deployments)
PackageMaintainer	Fedora Project
PackageName	pki-ocsp
PackageRelease	1.fc15
PackageVersion	9.0.1
SHA-1	00952E537C3195D44CC824EC63DBEE8696B0871A
SHA-256	4B8608EFBFD612E2774B0304168393A9FE3A08D96258908D409B7A9F676216EE

Key	Value
MD5	9D903477AB52CE269DE1B96C6E77FCC8
PackageArch	noarch
PackageDescription	This Certificate Authority (CA) User Interface contains the Dogtag textual and graphical user interface for the CA. This package is used by the Dogtag Certificate System. Several PKI packages require a "virtual" theme component. These "virtual" theme components are "Provided" by various theme "flavors" including "dogtag", "redhat", and "ipa". Consequently, all "dogtag", "redhat", and "ipa" theme components MUST be mutually exclusive! On Fedora systems, the "dogtag" theme packages are the ONLY available theme components. Similarly, the "ipa" theme packages are ONLY available on RHEL systems, and represent the default theme components. Alternatively, on RHEL systems, if the "dogtag" theme packages are available as EPEL packages, while they may be used as a transparent replacement for their corresponding "ipa" theme package, they are not intended to be used as a replacement for their corresponding "redhat" theme components. Finally, if available for a RHEL system (e. g. - RHCS subscription), each "redhat" theme package MUST be used as a transparent replacement for its corresponding "ipa" theme package or "dogtag" theme package.
PackageMaintainer	Fedora Project
PackageName	dogtag-pki-ca-theme
PackageRelease	1.fc17
PackageVersion	9.0.11
SHA-1	00E806E1C03C8D75A2CBEA943FB50FF71A1D2D45
SHA-256	BCC9A952C11DEB93AFD994CA9B94D41922F5C775F0EAED64821CE6286CA61460

Key	Value
MD5	D87210B1FB44562840CC140E71532427
PackageArch	noarch
PackageDescription	The Data Recovery Manager (DRM) is an optional PKI subsystem that can act as a Key Recovery Authority (KRA). When configured in conjunction with the Certificate Authority (CA), the DRM stores private encryption keys as part of the certificate enrollment process. The key archival mechanism is triggered when a user enrolls in the PKI and creates the certificate request. Using the Certificate Request Message Format (CRMF) request format, a request is generated for the user's private encryption key. This key is then stored in the DRM which is configured to store keys in an encrypted format that can only be decrypted by several agents requesting the key at one time, providing for protection of the public encryption keys for the users in the PKI deployment. Note that the DRM archives encryption keys; it does NOT archive signing keys, since such archival would undermine non-repudiation properties of signing keys. This package is one of the top-level java-based Tomcat PKI subsystems provided by the PKI Core used by the Certificate System. ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. PKI Core contains ALL top-level java-based Tomcat PKI components: * pki-symkey * pki-base * pki-tools * pki-selinux (f17 only) * pki-server * pki-ca * pki-kra * pki-ocsp * pki-tks * pki-javadoc which comprise the following corresponding PKI subsystems: * Certificate Authority (CA) * Data Recovery Manager (DRM) * Online Certificate Status Protocol (OCSP) Manager * Token Key Service (TKS) For deployment purposes, PKI Core contains fundamental packages required by BOTH native-based Apache AND java-based Tomcat Certificate System instances consisting of the following components: * pki-tools * pki-selinux (f17 only) Additionally, PKI Core contains the following fundamental packages required ONLY by ALL java-based Tomcat Certificate System instances: * pki-symkey * pki-base * pki-tools * pki-server PKI Core also includes the following components: * pki-javadoc Finally, if Certificate System is being deployed as an individual or set of standalone rather than embedded server(s)/service(s), it is strongly recommended (though not explicitly required) to include at least one PKI Theme package: * dogtag-pki-theme (Dogtag Certificate System deployments) * dogtag-pki-server-theme * redhat-pki-server-theme (Red Hat Certificate System deployments) * redhat-pki-server-theme * customized pki theme (Customized Certificate System deployments) * <customized>-pki-server-theme NOTE: As a convenience for standalone deployments, top-level meta packages may be provided which bind a particular theme to these certificate server packages.
PackageMaintainer	Fedora Project
PackageName	pki-kra
PackageRelease	2.fc19
PackageVersion	10.0.3
SHA-1	01EAFF6B30AD5DFE57092BFFAFFE127A0D595FAE
SHA-256	87689A1F9842760B2A57A93FDB8006F3BC35FBE3EB46337415A0E819C74A465F

Key	Value
MD5	026787BDE27DC2F155712855FAB2E897
PackageArch	noarch
PackageDescription	The PKI Server Package contains libraries and utilities needed by the following PKI subsystems: the Certificate Authority (CA), the Key Recovery Authority (KRA), the Online Certificate Status Protocol (OCSP) Manager, the Token Key Service (TKS), and the Token Processing Service (TPS).
PackageMaintainer	Fedora Project
PackageName	pki-server
PackageRelease	1.fc32
PackageVersion	10.8.3
SHA-1	0285A6D88C93A3DFDF0AE3C1725581140B1220A7
SHA-256	25AFD51F5CDF18E5382B9CCFE176EAE062584B9F3B8C8B697660F3340138788F

Key	Value
MD5	30CCA4923ACD234A9024D3F9A4472ED8
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Registration Authority (RA) is an optional PKI subsystem that acts as a front-end for authenticating and processing enrollment requests, PIN reset requests, and formatting requests. An RA communicates over SSL with a Certificate Authority (CA) to fulfill the user's requests. An RA may often be located outside an organization's firewall to allow external users the ability to communicate with that organization's PKI deployment. For deployment purposes, an RA requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-silent Additionally, Certificate System requires ONE AND ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages: * dogtag-pki-theme (Dogtag Certificate System deployments) * redhat-pki-theme (Red Hat Certificate System deployments)
PackageMaintainer	Fedora Project
PackageName	pki-ra
PackageRelease	1.fc15
PackageVersion	9.0.2
SHA-1	02BF36F9AE9188719CBCAC9BD470F882589B00D2
SHA-256	FA53BE53B9438DEB2C82E78D493CAF927E7AD66A91C5D75D4A1FC62E3465113E

Key	Value
MD5	4595D5FA714985478CB9CA1DC6ED555B
PackageArch	noarch
PackageDescription	The Online Certificate Status Protocol (OCSP) Manager is an optional PKI subsystem that can act as a stand-alone OCSP service. The OCSP Manager performs the task of an online certificate validation authority by enabling OCSP-compliant clients to do real-time verification of certificates. Note that an online certificate-validation authority is often referred to as an OCSP Responder. Although the Certificate Authority (CA) is already configured with an internal OCSP service. An external OCSP Responder is offered as a separate subsystem in case the user wants the OCSP service provided outside of a firewall while the CA resides inside of a firewall, or to take the load of requests off of the CA. The OCSP Manager can receive Certificate Revocation Lists (CRLs) from multiple CA servers, and clients can query the OCSP Manager for the revocation status of certificates issued by all of these CA servers. When an instance of OCSP Manager is set up with an instance of CA, and publishing is set up to this OCSP Manager, CRLs are published to it whenever they are issued or updated. This package is one of the top-level java-based Tomcat PKI subsystems provided by the PKI Core used by the Certificate System. ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. PKI Core contains ALL top-level java-based Tomcat PKI components: * pki-symkey * pki-base * pki-tools * pki-server * pki-ca * pki-kra * pki-ocsp * pki-tks * pki-tps * pki-javadoc which comprise the following corresponding PKI subsystems: * Certificate Authority (CA) * Data Recovery Manager (DRM) * Online Certificate Status Protocol (OCSP) Manager * Token Key Service (TKS) * Token Processing Service (TPS) For deployment purposes, PKI Core contains fundamental packages required by BOTH native-based Apache AND java-based Tomcat Certificate System instances consisting of the following components: * pki-tools Additionally, PKI Core contains the following fundamental packages required ONLY by ALL java-based Tomcat Certificate System instances: * pki-symkey * pki-base * pki-tools * pki-server PKI Core also includes the following components: * pki-javadoc Finally, if Certificate System is being deployed as an individual or set of standalone rather than embedded server(s)/service(s), it is strongly recommended (though not explicitly required) to include at least one PKI Theme package: * dogtag-pki-theme (Dogtag Certificate System deployments) * dogtag-pki-server-theme * redhat-pki-server-theme (Red Hat Certificate System deployments) * redhat-pki-server-theme * customized pki theme (Customized Certificate System deployments) * <customized>-pki-server-theme NOTE: As a convenience for standalone deployments, top-level meta packages may be provided which bind a particular theme to these certificate server packages.
PackageMaintainer	Fedora Project
PackageName	pki-ocsp
PackageRelease	2.fc22
PackageVersion	10.2.3
SHA-1	02CC26E3D55C942499ED38A8FF06CC1314B0379F
SHA-256	1553425D3591665CC231D2E9E05FFAB14E2615B582D76A6237B3FF56D87B4CA6

Key	Value
MD5	EB9071242B8D2269EAC813F7A689F648
PackageArch	noarch
PackageDescription	The PKI Utility Framework is required by the following four PKI subsystems: the Certificate Authority (CA), the Data Recovery Manager (DRM), the Online Certificate Status Protocol (OCSP) Manager, and the Token Key Service (TKS). This package is a part of the PKI Core used by the Certificate System. ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. PKI Core contains fundamental packages required by Certificate System, and consists of the following components: * pki-setup * pki-symkey * pki-native-tools * pki-util * pki-util-javadoc * pki-java-tools * pki-java-tools-javadoc * pki-common * pki-common-javadoc * pki-selinux * pki-ca * pki-silent which comprise the following PKI subsystems: * Certificate Authority (CA) For deployment purposes, Certificate System requires ONE AND ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages: * ipa-pki-theme (IPA deployments) * dogtag-pki-theme (Dogtag Certificate System deployments) * redhat-pki-theme (Red Hat Certificate System deployments)
PackageMaintainer	Koji
PackageName	pki-util
PackageRelease	1.fc15
PackageVersion	9.0.7
SHA-1	02D4B626EC953B7997D033BF7D254CEE0912FD3F
SHA-256	EA3916FF83E84181A6EE8BD143B182DA244BD5CC8BCEC47576B29F553812C81F

Key	Value
MD5	C8C1468F191F010A4C04ACA98531DF9A
PackageArch	noarch
PackageDescription	Dogtag Certificate System is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Dogtag Online Certificate Status Protocol Manager is an optional PKI subsystem that can act as a stand-alone Online Certificate Status Protocol (OCSP) service. The Dogtag Online Certificate Status Protocol Manager performs the task of an online certificate validation authority by enabling OCSP-compliant clients to do real-time verification of certificates. Note that an online certificate-validation authority is often referred to as an OCSP Responder. Although the Dogtag Certificate Authority is already configured with an internal OCSP service. An external OCSP Responder is offered as a separate subsystem in case the user wants the OCSP service provided outside of a firewall while the Dogtag Certificate Authority resides inside of a firewall, or to take the load of requests off of the Dogtag Certificate Authority. The Dogtag Online Certificate Status Protocol Manager can receive Certificate Revocation Lists (CRLs) from multiple Dogtag Certificate Authority servers, and clients can query the Dogtag Online Certificate Status Protocol Manager for the revocation status of certificates issued by all of these Dogtag Certificate Authority servers. When an instance of Dogtag Online Certificate Status Protocol Manager is set up with an instance of Dogtag Certificate Authority, and publishing is set up to this Dogtag Online Certificate Status Protocol Manager, CRLs are published to it whenever they are issued or updated.
PackageMaintainer	Fedora Project
PackageName	pki-ocsp
PackageRelease	2.fc13
PackageVersion	1.3.2
SHA-1	045699D6909FDBE9C5148D13727AE5BC9F7A9425
SHA-256	A36BB83732748A1A2576FE006481A89E5AAC5B30BC3F5BA26D7C0DAD3A30D0B7

Key	Value
MD5	F5786195E166A769F378748A77D2D2B2
PackageArch	noarch
PackageDescription	The PKI Framework contains the common and client libraries and utilities written in Python. This package is a part of the PKI Core used by the Certificate System. ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. PKI Core contains ALL top-level java-based Tomcat PKI components: * pki-symkey * pki-base * pki-base-python2 (alias for pki-base) * pki-base-python3 * pki-base-java * pki-tools * pki-server * pki-ca * pki-kra * pki-ocsp * pki-tks * pki-tps * pki-javadoc which comprise the following corresponding PKI subsystems: * Certificate Authority (CA) * Key Recovery Authority (KRA) * Online Certificate Status Protocol (OCSP) Manager * Token Key Service (TKS) * Token Processing Service (TPS) Python clients need only install the pki-base package. This package contains the python REST client packages and the client upgrade framework. Java clients should install the pki-base-java package. This package contains the legacy and REST Java client packages. These clients should also consider installing the pki-tools package, which contain native and Java-based PKI tools and utilities. Certificate Server instances require the fundamental classes and modules in pki-base and pki-base-java, as well as the utilities in pki-tools. The main server classes are in pki-server, with subsystem specific Java classes and resources in pki-ca, pki-kra, pki-ocsp etc. Finally, if Certificate System is being deployed as an individual or set of standalone rather than embedded server(s)/service(s), it is strongly recommended (though not explicitly required) to include at least one PKI Theme package: * dogtag-pki-theme (Dogtag Certificate System deployments) * dogtag-pki-server-theme * redhat-pki-server-theme (Red Hat Certificate System deployments) * redhat-pki-server-theme * customized pki theme (Customized Certificate System deployments) * <customized>-pki-server-theme NOTE: As a convenience for standalone deployments, top-level meta packages may be provided which bind a particular theme to these certificate server packages.
PackageMaintainer	Fedora Project
PackageName	pki-base
PackageRelease	1.fc24
PackageVersion	10.3.1
SHA-1	046321B94802C0AF935BDD25FC378235D3E56E96
SHA-256	73A7299D6BF83925E30C48129DBD715E6EC62D481071BBCEBC3D48086B0CF1A3