Result for 2FB65B00790F99903F76F9D068709488D53D938E

Query result

Key Value
CRC32B2F670BF
FileName./usr/share/pki/kra/conf/workers.properties
FileSize5658
MD57824A6E972FAAE3D9EC7B06A47B70105
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '924', 'OpSystemCode': '479', 'ProductCode': '919', 'ProductName': 'SuSE Linux Professional 8.2', 'ProductVersion': '8.2'}
RDS:package_id182052
SHA-12FB65B00790F99903F76F9D068709488D53D938E
SHA-256E1F16DFC4891EFBC5F8B12D38381041F75AEEF95DDA09A3C728BAC964A8660A1
SSDEEP96:hAxhGP4CyIaZXPa6ZfNRNTgbh5zG9vOmKpkM3+cb+3sK3zeiSKtIz4lB2:hDPHdSPLZFRNiHamBifiJ
SpecialCode
TLSHT1BEC1862BAF5E742111F3C3117045F37EDE56215A83A098B87C18CC183BE3CAA627F596
dbnsrl_legacy
insert-timestamp1679423362.175144
sourceRDS.db
tar:gnamebin
tar:unameroot
hashlookup:parent-total110
hashlookup:trust100

Network graph view

Parents (Total: 110)

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

Key Value
MD5D87210B1FB44562840CC140E71532427
PackageArchnoarch
PackageDescriptionThe 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.
PackageMaintainerFedora Project
PackageNamepki-kra
PackageRelease2.fc19
PackageVersion10.0.3
SHA-101EAFF6B30AD5DFE57092BFFAFFE127A0D595FAE
SHA-25687689A1F9842760B2A57A93FDB8006F3BC35FBE3EB46337415A0E819C74A465F
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD//3.7//packages//alpha//mod_jk-1.2.8p0.tgz
MD52719631CCB5913C224FE3C023000AC0C
SHA-105F7033DB08421D917355F35328D13C0AA50DBF7
SHA-256CFDEB12D7575845A4E4ABEC15E006EE2FCB83E3DF7BDCAA86E2644CBA48F1462
SSDEEP1536:FDRBdeyWmzvbrNrXs9jqcLGZioD5O9OzLIGU70fVPFA3HEKoZ:FZVrHtXg+GGMG4+VPakKE
TLSHT13683121365D90AD04807004BEBDC3ABD1A2CC8F32DD9D6EA7B999E5CD37D7012F16949
Key Value
MD541F196F4608B391CEA8CCCA5CA6FDB00
PackageArchnoarch
PackageDescriptionThe 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. 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)
PackageMaintainerKoji
PackageNamepki-ca
PackageRelease1.fc15
PackageVersion9.0.7
SHA-10CD3A2F5C6E9432693E6100848303D879A4F5001
SHA-256A6A2E3D82693194A9489C6B23A76A08001574701A6F359C3AC1AC66C551C7E37
Key Value
MD5236ED2A9604CD7E8AC0ED35AB7D70858
PackageArchnoarch
PackageDescriptionThe 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. 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)
PackageMaintainerFedora Project
PackageNamepki-ca
PackageRelease1.fc16
PackageVersion9.0.15
SHA-1118FCF9944B45218668F01F70AF80A6E46DD5C38
SHA-256297B99FD7463158B103165AC3FD144452BC2C8B646BC215764DF49A4780E04CE
Key Value
MD5AE25CAED0E9003E50064796F005D5198
PackageArchnoarch
PackageDescriptionThe 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. 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.
PackageMaintainerFedora Project
PackageNamepki-ca
PackageRelease1.fc20
PackageVersion10.1.0
SHA-112D4A12D187A1884D64CB1512D57A8BF24311F26
SHA-256194DCD133378CA4637802C7A9C9F38B17406F92836AC6F425B0D30D39D9F451B
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD//3.9//packages//alpha//mod_jk-1.2.15.tgz
MD58FFC22778250B6948835321E10910CF3
SHA-11494226CE94BA60965F688A80283597F82D5BF69
SHA-256EE09DF3C0870E600CC1533B19AA12FBF765702EE8E83C9521DCF5281EE761B6B
SSDEEP1536:qPXwanMo46gd6BBmyozosB702f9an9HgkBVdQoAYrnIeM0nTCxumzV+I4CoyzM10:3aXfgdyjaBYUAhfXFAtF0n6F4CvM1N83
TLSHT1CE93128D7CCF51F04AF032363053A853B86AAEE09DA21543EA68084E7DD119FAD55BB7
Key Value
MD520457829536FBC76DED8841F2FB682CE
PackageArchnoarch
PackageDescriptionThe 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.
PackageMaintainerCentOS BuildSystem <http://bugs.centos.org>
PackageNamepki-kra
PackageRelease14.el7_9
PackageVersion10.5.18
SHA-114F4334157B8B18C03CAAC67F973002CF31A20A8
SHA-256FA1AD496790644BCCAB3140B7F585DD72D55F3D0B242EC69CF7C2939B91B468B
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD//3.7//packages//sparc//mod_jk-1.2.8p0.tgz
MD562BBCCF38AB6C195A5B9B651E43A2DC3
SHA-118D800FAF1E4ABE3B20D98A513C7E049B557DC6B
SHA-256E26AD966DD1C1B9149C1C92D843CDAC3BD30564B0AF27EFE396A0CD0EBA378F6
SSDEEP1536:dcgtFo9xtXymDtDZgAZgDNav55xLE9xcpbu5WRfDkGogN7qg3GSUoYzoP9mMRvAv:dc2FoUCJnZENmPF7uUfwG/bGHoqUleXh
TLSHT1238302EE55FE6FBBC89E98F59E7716C2087F18940991B11027827C6DBF528A3B826104
Key Value
FileNamehttps://ftp.lysator.liu.se/pub/OpenBSD//4.0//packages//sparc//mod_jk-1.2.15.tgz
MD5ED516FDAA9CCEB9B9B8D56BC092AAB19
SHA-11A857E4DB0903019104F31D0D568E506CFF25E95
SHA-256A721F20D1AFAF2C84B16788CEA02F310ACB4D70D2745C18C7D40085570A6882E
SSDEEP1536:hO05vP55AbhHd8se0T8C9pUINga1//EefDNEDIAO3P8NoWEprgKhm9nZ/jZjEQQ9:hl5Z50nTUINgm/EebNEE8N/4wWNGWjl
TLSHT175A312691E224C47E3D2A05EE4BA00013C7D179641E68C97AFBF76625B8531C876F1DF
Key Value
MD5B99AAB0524A935867295C7A6438B40D2
PackageArchnoarch
PackageDescriptionThe 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. 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.
PackageMaintainerFedora Project
PackageNamepki-ca
PackageRelease7.fc23
PackageVersion10.2.6
SHA-11D62C9E34713BADC6391C3BCB86AE4AFF561B69B
SHA-256CB19068AF418B20F7F8E622708501CA19BD2A0C6B0B23993A23315B6F3FB8866