Parents (Total: 8)

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

Key	Value
MD5	E37A2BA1A621238533BBFE49A91DB3FF
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc15
PackageVersion	9.0.1
SHA-1	0FEFD5EA44674F2B7A83D46187B1998F7079A49A
SHA-256	D6E0A50DF2FA87C1A318D59E96ADD0D850F0F7386A64A2FF12FECBB10888C750

Key	Value
MD5	754868E91E6914E19118F70821E62EDA
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc17
PackageVersion	9.0.10
SHA-1	DAF45588ACF73925C7555383CF7E685E3417B01F
SHA-256	47E7082FB3960A062148747CE03A6B8D2AEB9FEDFC4A98D7289785276FCA3CD7

Key	Value
MD5	B1F606802B47B1A7CBB4033F279180E6
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc16
PackageVersion	9.0.7
SHA-1	6237F492B95A047A45FFD93C87E6549B0D031757
SHA-256	D947A5541B4FDA13ABDD6355C6C8C2947379BB65C53382E648F711437E912086

Key	Value
MD5	E3A34DFA0177220C25AD2112F538F596
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc17
PackageVersion	9.0.10
SHA-1	602BADA126B57DD3D01ED2BAE0DE567405A875D3
SHA-256	B3A67758C97C16CC9A6AD48E84E1D6AF20DEC9B397A5D90ABCB5B5A4F4B03B2D

Key	Value
MD5	75221CDED62269A4322125058FECBE03
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc17
PackageVersion	9.0.10
SHA-1	A83E230499128E6B5ED22F82C361E48E00D44665
SHA-256	D710EE6B3969331696414024D3337BFEECDF8EFB9874C004FD7CC600709F7DBD

Key	Value
MD5	2AFA401AF298A05F12A03C3ABAB842C2
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc15
PackageVersion	9.0.2
SHA-1	CF4960A54E4620808D38EECE87102D813CE26C9D
SHA-256	41EF2AEA784B148A87402BF4D5B9FDC112821D3AD20FE61EB4EE0D6CDBE6FA03

Key	Value
MD5	ADA2CAEC81F3CF4A1950B8BAF35509FB
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc15
PackageVersion	9.0.2
SHA-1	E7CF8A1EDD4704457DC88C9429908073817D4497
SHA-256	3BEBC36B56864BD628653A6B747A48448C3EB09C88C3D58E725C4964A982745D

Key	Value
MD5	DF23E1B78DADEEB84B0637C8D817EA2E
PackageArch	noarch
PackageDescription	Certificate System (CS) is an enterprise software system designed to manage enterprise Public Key Infrastructure (PKI) deployments. The Token Key Service (TKS) is an optional PKI subsystem that manages the master key(s) and the transport key(s) required to generate and distribute keys for hardware tokens. TKS provides the security between tokens and an instance of Token Processing System (TPS), where the security relies upon the relationship between the master key and the token keys. A TPS communicates with a TKS over SSL using client authentication. TKS helps establish a secure channel (signed and encrypted) between the token and the TPS, provides proof of presence of the security token during enrollment, and supports key changeover when the master key changes on the TKS. Tokens with older keys will get new token keys. Because of the sensitivity of the data that TKS manages, TKS should be set up behind the firewall with restricted access. For deployment purposes, a TKS requires the following components from the PKI Core package: * pki-setup * pki-native-tools * pki-util * pki-java-tools * pki-common * pki-selinux and can also make use of the following optional components from the PKI Core package: * pki-util-javadoc * pki-java-tools-javadoc * pki-common-javadoc * 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)
PackageMaintainer	Fedora Project
PackageName	pki-tks
PackageRelease	1.fc16
PackageVersion	9.0.7
SHA-1	B8547E6271FF974927781222AAC34BB5D1E5AE83
SHA-256	B92744E1C37A7AF83F9DC06D4D427A45FA71114FCAC29CC67637C9E894E66D38