Result for 0B0A988C513BCEF9382FE219D18040404686EB4F

Query result

Key Value
FileName./usr/share/pki/tps/conf/nss.conf
FileSize11474
MD5132DC365CE8B34E5B1612EAC99C42EDB
SHA-10B0A988C513BCEF9382FE219D18040404686EB4F
SHA-25678AD6229D5C1F5B541CF60D9C80AD848DEEEEDD019E353EAF1C459E2A6159F5C
SSDEEP192:wsnhRYd1X7Jj9fyCQcvtQmxZtz3FMyTGbqIhyaSEyCQcvtQmetz3FMyTGbqIhya4:3he1Nj9fyBM2mLBRGbqIhyaLyBM2meB7
TLSHT13932A6E63A88777625414683455D83C07328E07B266A0D37796DC6C903D1E6F87FF6E2
hashlookup:parent-total21
hashlookup:trust100

Network graph view

Parents (Total: 21)

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

Key Value
MD53D047D21E9EE31785933FC36FE692145
PackageArchs390x
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease2.fc17
PackageVersion9.0.7
SHA-1191CC1656371426E0C48DA3929B3EE252D5EA878
SHA-25687844975412D76EFA0DC77FD59CA364B166AA29733DFBA15E27FD716D2D91511
Key Value
MD5B5D3E03E53D721CDD8D1660048823DE6
PackageArchppc
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerKoji
PackageNamepki-tps
PackageRelease2.fc17
PackageVersion9.0.7
SHA-11C1699D450B24A5D88526FD1B348B0EF06EC35CB
SHA-256C8158C404000276BFB31C8202E61A9DEE85F85A8C6F526BD54A82CB96951FC24
Key Value
MD5F946295E6ABAE4C440724E2E6CA3A704
PackageArchppc
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS requires the following components from the PKI Core package: * pki-server * pki-tools * pki-selinux (f17 only) Additionally, Certificate System requires ONE AND ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages: * 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 ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease1.fc19
PackageVersion10.0.3
SHA-13F2DEDC1B7D20D2BAEC98DC913DEA203CFE07E50
SHA-2567BD0A86CC6245B0652C613D89A12A7C0F59F642D40CF0869C8E5B3179D1345B8
Key Value
MD56EC7F577F9C3ABC7EAD8E115914C096B
PackageArchs390x
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS requires the following components from the PKI Core package: * pki-server * pki-tools * pki-selinux (f17 only) Additionally, Certificate System requires ONE AND ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages: * 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 ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease1.fc19
PackageVersion10.0.3
SHA-14A80CDE10BFA2F0835B57A9A848B678493555515
SHA-256249D74765E3122A4E9E480FB4371B627CAFA7CED6A6EE75311156DAF3454D533
Key Value
MD58DBE1927E8EE64C6993ECBD261BA5856
PackageArchs390
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease2.fc17
PackageVersion9.0.7
SHA-150D00507CBF0E07D22C1E83E085AEF1A5B2A353B
SHA-256FF072A24FF6E67C137EBC72346FAAB34286987595C27B3EE29574866B4772897
Key Value
MD5AF20CBB47ADABD34B8E07C35FECB76FD
PackageArchs390x
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease1.fc16
PackageVersion9.0.7
SHA-15EAB1731F016147EB9D3E3F39D420E3E01257F73
SHA-2567DD5B2C4077B078E1D1109E25346FBFCC2BA03B5A82243FD3371B35F786A8262
Key Value
MD521C58995AF94055A1576804938CB650F
PackageArcharmv7hl
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS requires the following components from the PKI Core package: * pki-server * pki-tools * pki-selinux (f17 only) 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease1.fc18
PackageVersion10.0.0
SHA-166B9DB91EC5030C9E5B8095D5A5A8CCF8C0D1C8E
SHA-2563461510BCD6E6E3F1973DF68DA96808E011628D9A05D8BAB78902EBD9458FCFA
Key Value
MD5E10C1766420F40754280ED5C8E8026AE
PackageArchppc64
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerKoji
PackageNamepki-tps
PackageRelease2.fc17
PackageVersion9.0.7
SHA-166D1238ADB81EA0A14B740BD92AD01073F8F549A
SHA-256BAE31EF306475D785B9A549F11AFBD02B00C028E1511D28DF941D793B9487468
Key Value
MD5CE4E5B5B71C3150E4E8A844FF3F589D1
PackageArcharmv7hl
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS requires the following components from the PKI Core package: * pki-server * pki-tools * pki-selinux (f17 only) Additionally, Certificate System requires ONE AND ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages: * 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 ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease1.fc19
PackageVersion10.0.3
SHA-169034DD16CDDAE07B00274C78307C2BAFB9C9562
SHA-2566F551147E9B2206600561237D7F0039FFDD2E78480286167C46221BA07CC7AB0
Key Value
MD5E11EE4772D0FEDB41E214E402E881FC7
PackageArchs390
PackageDescriptionCertificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. 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 Data Recovery Manager (DRM), 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. For deployment purposes, a TPS 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) ================================== || ABOUT "CERTIFICATE SYSTEM" || ================================== ${overview}
PackageMaintainerFedora Project
PackageNamepki-tps
PackageRelease1.fc16
PackageVersion9.0.7
SHA-16D8089D5497F1471D102A2476720B0A41039FA19
SHA-2562BBE18F0F171305BC6A27D6375FC5C8623670DB14EEB56CC5D7EE2B9623ADFBC