| Key | Value |
|---|---|
| FileName | ./usr/share/pki/kra/webapps/kra/agent/kra/confirmRecover.html |
| FileSize | 458 |
| MD5 | 7095902D2BD1A186447B00C26438D52A |
| SHA-1 | 0DC5736C6980C687BEE0DF230AAB6A7AB6DA449E |
| SHA-256 | C6C9F7548E09DE4CEC6924E2CB4FEFB9DBBFA52369F7B1DE7D34889A27902467 |
| SSDEEP | 12:BMQbwuOOLU+PpqrVkAbp3VkAbY1A2nVkAbrVkAbqVkAbbV41i:WRVvFVvc1AAVv3VvWVvPV41i |
| TLSH | T12BF0A74FEE5DC0AA01D23E8D18B8E75C9AC8D589F5B2C9DD21F6920027E03DC0D45A45 |
| hashlookup:parent-total | 39 |
| hashlookup:trust | 100 |
The searched file hash is included in 39 parent files which include package known and seen by metalookup. A sample is included below:
| 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 | 20457829536FBC76DED8841F2FB682CE |
| 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 | CentOS BuildSystem <http://bugs.centos.org> |
| PackageName | pki-kra |
| PackageRelease | 14.el7_9 |
| PackageVersion | 10.5.18 |
| SHA-1 | 14F4334157B8B18C03CAAC67F973002CF31A20A8 |
| SHA-256 | FA1AD496790644BCCAB3140B7F585DD72D55F3D0B242EC69CF7C2939B91B468B |
| Key | Value |
|---|---|
| FileSize | 183072 |
| MD5 | 36DA275D8603592FF84753A0C2A3408A |
| 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.10.2-3build1 |
| SHA-1 | 1926E4A56D7410AA1BBDDB08510D0AA19B90CF64 |
| SHA-256 | 7ADF077285996572C3978E0049B232D37F4E07230F409873151E1EAED2AB4ED2 |
| Key | Value |
|---|---|
| FileSize | 192084 |
| MD5 | 6B672BEAF607831E7DBB928D3908F0FC |
| 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 | Debian FreeIPA Team <pkg-freeipa-devel@alioth-lists.debian.net> |
| PackageName | pki-kra |
| PackageSection | java |
| PackageVersion | 10.10.6-1 |
| SHA-1 | 1D53C585BAAE0346C29588BAA9DACA75C810F946 |
| SHA-256 | F668346574145E12CCD75E80D2C611137423087B7135E65EB3835CCCAE17A863 |
| Key | Value |
|---|---|
| MD5 | 9F335FBF1F44DD0E9FF72982272CE4E6 |
| 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 | CentOS BuildSystem <http://bugs.centos.org> |
| PackageName | pki-kra |
| PackageRelease | 7.el7 |
| PackageVersion | 10.5.18 |
| SHA-1 | 235BCC7CA0F2456BAD27798D24870D7BF693E529 |
| SHA-256 | 22643AC35A7FD3BE5A1FBCB1D16194CAE629E3FF9A0DC44B40532C89C9B54B97 |
| Key | Value |
|---|---|
| MD5 | C72BD98BC5F31B22D2FB0EAB31802CAC |
| 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 | CentOS Buildsys <bugs@centos.org> |
| PackageName | pki-kra |
| PackageRelease | 2.module_el8.5.0+945+a81e57da |
| PackageVersion | 10.11.2 |
| SHA-1 | 3DA48A68A947B316339A88C7555691979DA0F646 |
| SHA-256 | B48DA03EE2576FCA941DB89E6F1EF6C7D39E128A0E95BE6444CC3734A814C2BB |
| Key | Value |
|---|---|
| FileSize | 190924 |
| MD5 | 2285333F339D280B598BA1066E156BDD |
| 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 | Debian FreeIPA Team <pkg-freeipa-devel@alioth-lists.debian.net> |
| PackageName | pki-kra |
| PackageSection | java |
| PackageVersion | 10.10.2-3 |
| SHA-1 | 47FFBEC126F7632D2CBD52C3DF218D42ED69FD8E |
| SHA-256 | 8DEE054822C6949C3116D0DB699355622090D02C98BC72F08ACCDFC6A835E795 |
| Key | Value |
|---|---|
| MD5 | CF7E9FE8650659D0B1FC784158DA7514 |
| 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 | CentOS Buildsys <bugs@centos.org> |
| PackageName | pki-kra |
| PackageRelease | 1.module_el8.5.0+876+d4bb8aa6 |
| PackageVersion | 10.11.0 |
| SHA-1 | 4F59AECEAAB249EC31D3B5B16F2353CDA5E328EC |
| SHA-256 | ECD800A415DFDD1CC759DC3E0CE5F16F7C0E38EC5BDA7E464E66235BA3874E4F |
| Key | Value |
|---|---|
| MD5 | E1D592DA7F6884695B07304802BFFDBA |
| 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 | AlmaLinux Packaging Team <packager@almalinux.org> |
| PackageName | pki-kra |
| PackageRelease | 4.module_el8.5.0+2616+5b1d191d |
| PackageVersion | 10.11.2 |
| SHA-1 | 534EA7C85A07416FCF83A334C069EC09874964D6 |
| SHA-256 | 34481E6AD0DE2D548A72FB1FCCBD135105F83A2EB82DF6F12C7D011E881ED6C8 |
| Key | Value |
|---|---|
| FileSize | 190772 |
| MD5 | 212BFB86EF3D39C3A0749BDFA72B7E97 |
| 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 | Debian FreeIPA Team <pkg-freeipa-devel@alioth-lists.debian.net> |
| PackageName | pki-kra |
| PackageSection | java |
| PackageVersion | 10.9.4-1 |
| SHA-1 | 569220DF5674F2768EAAC854750FE002DF1A43B9 |
| SHA-256 | E97851D816694CF099265E724CA12FB70A0D3E796D7FAB91216CDEE72AB73FD9 |