Parents (Total: 127)

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

Key	Value
MD5	4D9611044C1D8D8E12484092D1BA1A97
PackageArch	noarch
PackageDescription	The PKI ACME responder is a service that provides an automatic certificate management via ACME v2 protocol defined in RFC 8555.
PackageMaintainer	AlmaLinux Packaging Team <packager@almalinux.org>
PackageName	pki-acme
PackageRelease	2.module_el8.4.0+2337+9830f79e
PackageVersion	10.10.5
SHA-1	01DF8730406C5FFAD50BE8CBAFECFDECC7C1928A
SHA-256	1A2E60AB81ABDB0151FE363E7FC238F14031195A84ACBF1B7C7F862614C10419

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	CF318AAA540AFDC9E6B9BE28B6563DAE
PackageArch	noarch
PackageDescription	The Key Recovery Authority (KRA) is an optional PKI subsystem that can act as a key archival facility. When configured in conjunction with the Certificate Authority (CA), the KRA 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 KRA 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 KRA archives encryption keys; it does NOT archive signing keys, since such archival would undermine non-repudiation properties of signing keys.
PackageMaintainer	Fedora Project
PackageName	pki-kra
PackageRelease	3.fc33
PackageVersion	10.9.4
SHA-1	0733D0B79BC12513749233C2891283EC4913705C
SHA-256	F56147499F09A238BFAE627ED1462E6321C2A0D603790733D1C962CB5263D88A

Key	Value
MD5	DA1CE84428530606B26FE67885B6EBE8
PackageArch	noarch
PackageDescription	The Certificate Authority (CA) is a required PKI subsystem which issues, renews, revokes, and publishes certificates as well as compiling and publishing Certificate Revocation Lists (CRLs). The Certificate Authority can be configured as a self-signing Certificate Authority, where it is the root CA, or it can act as a subordinate CA, where it obtains its own signing certificate from a public CA.
PackageMaintainer	CentOS Buildsys <bugs@centos.org>
PackageName	pki-ca
PackageRelease	2.module_el8.5.0+893+b6aab8cb
PackageVersion	10.11.0
SHA-1	08F917E674C3D8764974F1D26E3C0B5BDF92A11C
SHA-256	7E7FD4246557B4E94FCDEF0109986B1BAACDD027634779E3BF063CD3661B8021

Key	Value
MD5	0E8D0CBFFDC5B921E8B52BD9DA68803C
PackageArch	noarch
PackageDescription	The PKI Server Package contains libraries and utilities needed by other PKI subsystems.
PackageMaintainer	AlmaLinux Packaging Team <packager@almalinux.org>
PackageName	pki-server
PackageRelease	2.module_el8.5.0+2592+8eb38ccc
PackageVersion	10.11.2
SHA-1	09A80DB5605661A627D3652FE6D52097F95486DB
SHA-256	F28CC56DE6090CB227381DD69DA05F0746B9D6484A4E0FBBC544551260CD193C

Key	Value
MD5	0942D0646F27E835FDE54D136CFEA58A
PackageArch	aarch64
PackageDescription	The Token Processing System (TPS) is an optional PKI subsystem that acts as a Registration Authority (RA) for authenticating and processing enrollment requests, PIN reset requests, and formatting requests from the Enterprise Security Client (ESC). TPS is designed to communicate with tokens that conform to Global Platform's Open Platform Specification. TPS communicates over SSL with various PKI backend subsystems (including the Certificate Authority (CA), the Key Recovery Authority (KRA), and the Token Key Service (TKS)) to fulfill the user's requests. TPS also interacts with the token database, an LDAP server that stores information about individual tokens. The utility "tpsclient" is a test tool that interacts with TPS. This tool is useful to test TPS server configs without risking an actual smart card.
PackageMaintainer	Fedora Project
PackageName	pki-tps
PackageRelease	1.fc32
PackageVersion	10.8.3
SHA-1	0B27FAE24FC23A9CAD067F7864DBE6576918D057
SHA-256	73E519FFD75F847D5BC5D3DE9097B0ECF56096D221E5B28CF78A964A9B7F830A

Key	Value
MD5	E3C1D6D6A2465381D9852BA53D490C5C
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.
PackageMaintainer	Fedora Project
PackageName	pki-ocsp
PackageRelease	1.fc32
PackageVersion	10.8.3
SHA-1	0E0E398260FBCF25EAC9C17DC2D3EAE7FD958693
SHA-256	59A2A2DB79506AD78EA55E69CB91B574D7C6E6B449A0ABD378934C6C162FC05E

Key	Value
MD5	F22902725B55ADC3EDB625E58FD66CA8
PackageArch	noarch
PackageDescription	The PKI Framework contains the common and client libraries and utilities written in Java. This package is a part of the PKI Core used by the Certificate System. 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	CentOS BuildSystem <http://bugs.centos.org>
PackageName	pki-base-java
PackageRelease	15.el7_9
PackageVersion	10.5.18
SHA-1	1071EA7AC4776D5E3D57FE5F81FEC6AEE8F4C171
SHA-256	E1DD38DC66A44126B420260A1C8CBD7FC5A5E66FCA9097FBACB6645B53215EC9

Key	Value
MD5	23A2568318B998663D8436AEEFBE42CB
PackageArch	noarch
PackageDescription	The PKI Framework contains the common and client libraries and utilities written in Java. This package is a part of the PKI Core used by the Certificate System. 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	CentOS BuildSystem <http://bugs.centos.org>
PackageName	pki-base-java
PackageRelease	12.el7_9
PackageVersion	10.5.18
SHA-1	13F00F6F8BFAA594C41C0CB943832FB454888777
SHA-256	B97CA8437CA8DDD548433B4E5244B6B95C3C06FABEBEE6A67B64E0183FF83641

Key	Value
MD5	582246B82157C8662A83E5807E83C627
PackageArch	noarch
PackageDescription	The Certificate Authority (CA) is a required PKI subsystem which issues, renews, revokes, and publishes certificates as well as compiling and publishing Certificate Revocation Lists (CRLs). The Certificate Authority can be configured as a self-signing Certificate Authority, where it is the root CA, or it can act as a subordinate CA, where it obtains its own signing certificate from a public CA.
PackageMaintainer	CentOS Buildsys <bugs@centos.org>
PackageName	pki-ca
PackageRelease	3.module_el8.4.0+816+beb6e9a3
PackageVersion	10.10.5
SHA-1	147506EFD482926E20D4BA2D3383E4500FC45FA4
SHA-256	4B99A7F8792F17ED71EE1B38039E369888965ABE7AE9430F51C523E5AD843E93