Parents (Total: 36)

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

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	D9AC86106E33CDE3D0C19135E819B31B
PackageArch	noarch
PackageDescription	This Data Recovery Manager (DRM) User Interface contains the Dogtag textual and graphical user interface for the DRM. 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-kra-theme
PackageRelease	1.fc16
PackageVersion	9.0.8
SHA-1	1310AA1649D1D1EE781C34B1B21882EA6EF95EE4
SHA-256	6443ACA22F5159BD4ACAB30B9E4E6A166A9FE264F073188FA3F3E28C28C38C96

Key	Value
MD5	851FE383620773F9A06EB69990BC5E03
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-server * pki-ca * pki-kra * pki-ocsp * pki-tks * pki-tps-tomcat * 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-kra
PackageRelease	1.fc20
PackageVersion	10.1.0
SHA-1	21E9FE25BE19C03690E9738DF897427F7D0D75CE
SHA-256	4AA15C85F9C95D87CE54783FA3DC5FEAD057044CF8D21FCC5B23C3066DD38C46

Key	Value
FileSize	168794
MD5	90D8298C20524EEA63EA54A9C4F3C31E
PackageDescription	Certificate System - Data Recovery Manager Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	pki-kra
PackageSection	java
PackageVersion	10.2.6-1
SHA-1	2B4295E3802632960D51137AB2E4B7FB743DCF75
SHA-256	A76A42FA8F43CBC5A817CEB04A912CC9D9C88B31B160ED552C415B45E260F6BD

Key	Value
MD5	F7247EDF5EC4FCEE2FAD18CD45F8F302
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-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-kra
PackageRelease	7.fc23
PackageVersion	10.2.6
SHA-1	363F90F8DE7393BED179CAEA0A11D780F6F730E4
SHA-256	FD777C3DDBEAA18BB4B6546035EC7CD31037605C87DBA2E8EC9F13EF26223550

Key	Value
MD5	728B5F3725F5800A8BE376E892D72D7B
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-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-kra
PackageRelease	2.fc22
PackageVersion	10.2.3
SHA-1	3D75A8DB1D23789F7B77FAD1262653035306CE49
SHA-256	80FF680CBC9BBB2241DBEEDDFBD1594157741A88EE9BBD8D8191D352875B3859

Key	Value
MD5	857201652B6882C54CE993E8B67C4EA6
PackageArch	noarch
PackageDescription	This Data Recovery Manager (DRM) User Interface contains the Dogtag textual and graphical user interface for the DRM. 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-kra-theme
PackageRelease	1.fc15
PackageVersion	9.0.4
SHA-1	41BFF8874C61BE6F5D11A234174B4FF01D1A50D9
SHA-256	63FF510DFFE8B577EDAC95F706959C2D940AFBB3B1FA4A8C77619FCCF7F3BD80

Key	Value
MD5	EE4DEEB0C3D9B376D99D41346CDC5DAE
PackageArch	noarch
PackageDescription	This Data Recovery Manager (DRM) User Interface contains the Dogtag textual and graphical user interface for the DRM. 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-kra-theme
PackageRelease	1.fc16
PackageVersion	9.0.6
SHA-1	48BE65A117C382C21C76629ADA82097F159D3F1E
SHA-256	90CC32EB222FE3C43E6151D45E239484B263B5E5A695E3A979158A880A9D0F2E

Key	Value
FileName	15322
FileSize	169772
MD5	289EC01F0EE2A7F09F01E3996FF30ED3
PackageDescription	Certificate System - Data Recovery Manager Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	pki-kra
PackageSection	java
PackageVersion	10.3.5+12-3ubuntu1
RDS:package_id	182052
SHA-1	49481D7CBDBB4C845357895DE5745167E527F2AB
SHA-256	0600352F2E20DAB4327E389AEF4B06F96218123C28F74DDA42F0E8D79B5906A6
insert-timestamp	1679408377.2533708
source	RDS.db

Key	Value
MD5	A7BF52FEF90E233909A2A8B4DA7877F4
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. 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-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-kra
PackageRelease	1.fc24
PackageVersion	10.3.1
SHA-1	4EA391267CA503654F5151C5778784657A1ACA7F
SHA-256	95516A7E6347C9CCEA98CEDDF624F2DAC34E0451720BDA3A366677669391A0C2