# packages

pkgId: 13cecb5216456d42cfe7b5e8fabab62c6c6ea189902bbf95de8fac1fe2c5d133
name: dogtag-pki
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Dogtag Public Key Infrastructure (PKI) Suite
url: http://pki.fedoraproject.org/
rpm_license: GPLv2 and LGPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1c
rpm_sourcerpm: dogtag-pki-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/dogtag-pki-10.2.0-1.fc21/dogtag-pki-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  The Dogtag Public Key Infrastructure (PKI) Suite is comprised of the following
  six subsystems and a client (for use by a Token Management System):

    * Certificate Authority (CA)
    * Data Recovery Manager (DRM)
    * Online Certificate Status Protocol (OCSP) Manager
    * Registration Authority (RA)
    * Token Key Service (TKS)
    * Token Processing System (TPS)
    * Enterprise Security Client (ESC)

  Additionally, it provides a console GUI application used for server and
  user/group administration of CA, DRM, OCSP, and TKS, javadocs on portions
  of the Dogtag API, as well as various command-line tools used to assist with
  a PKI deployment.

  To successfully deploy instances of a CA, DRM, OCSP, or TKS,
  a Tomcat Web Server must be up and running locally on this machine.

  To successfully deploy instances of an RA, or TPS,
  an Apache Web Server must be up and running locally on this machine.

  To meet the database storage requirements of each CA, DRM, OCSP, TKS, or TPS
  instance, a 389 Directory Server must be up and running either locally on
  this machine, or remotely over the attached network connection.

  To meet the database storage requirements of an RA, an SQLite database will
  be created locally on this machine each time a new RA instance is created.

  After installation of this package, use the 'pkicreate' and 'pkiremove'
  utilities to respectively create and remove PKI instances.


pkgId: f8223324e2b5aca95a94a4d512710b4f7e7247d13d61af55080ecbdc5b4b359a
name: dogtag-pki-console-theme
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Console User Interface
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-00014a1d
rpm_sourcerpm: dogtag-pki-theme-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/dogtag-pki-theme-10.2.0-1.fc21/dogtag-pki-console-theme-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  This PKI Console User Interface contains
  the Dogtag textual and graphical user interface for the PKI Console.

  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.


pkgId: b539153e5163caf22fef0c6eac8a626dcd5016e299a4ebc05dec2858a20c5579
name: dogtag-pki-server-theme
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Server Framework User Interface
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-00014a1d
rpm_sourcerpm: dogtag-pki-theme-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/dogtag-pki-theme-10.2.0-1.fc21/dogtag-pki-server-theme-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  This PKI Server Framework User Interface contains
  the Dogtag textual and graphical user interface for the PKI Server Framework.

  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.


pkgId: 7fba4418f1ea3fc52de33b88213f035055d15a511cb437bcd25360b025ddfef6
name: dogtag-pki-theme
arch: src
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - Dogtag PKI Theme Components
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-00014a1d
location_href: fedora-21-x86_64/dogtag-pki-theme-10.2.0-1.fc21/dogtag-pki-theme-10.2.0-1.fc21.src.rpm
checksum_type: sha256
description:
  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.


pkgId: bfc08c72671bbc68467bf2c72be58c38350510317fe02e794372fde3cc92a49c
name: pki-base
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - PKI Framework
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-base-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  The PKI Framework contains the common and client libraries and utilities.
  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 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.


pkgId: f2f67e115e602fda6083b796d41d60c1daaa6f0a717642c00f375358c38025b5
name: pki-base
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Framework
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-base-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  The PKI Framework contains the common and client libraries and utilities.
  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 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.


pkgId: 1561da1c44fd04ce06612c6a2ee017eb967ac215ff5c888c92859f1323b74275
name: pki-ca
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - Certificate Authority
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-ca-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  The 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.


pkgId: a7e998de2fe71246984eeb3c00e4b37d8c3149144b5dea9a7b5e7844e75a6da7
name: pki-ca
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - Certificate Authority
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-ca-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  The 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.


pkgId: 74b7679c2c34a16409ae6869c92335f2cb404295832dfc8a7f164b9e5390c78b
name: pki-core
arch: src
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - PKI Core Components
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-0001517c
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-core-10.1.1-2.fc20.src.rpm
checksum_type: sha256
description:
  ==================================
  ||  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.


pkgId: c05acf5f95166f2d5ddfd07eeafffbbd0b4f06439fc13a32eeee406cf373cc24
name: pki-core
arch: src
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Core Components
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1f
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-core-10.2.0-1.fc21.src.rpm
checksum_type: sha256
description:
  ==================================
  ||  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.


pkgId: 5657d38b9f3a7499c9be96dc8be8c5cb8f88f55845814a9b9433875320473a07
name: pki-core-debuginfo
arch: x86_64
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Debug information for package pki-core
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: Development/Debug
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-core-debuginfo-10.1.1-2.fc20.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package pki-core.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 99732579452553d53ff76540bccb1194c61c2f66f6df09574f4f51f492bf60df
name: pki-javadoc
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - PKI Framework Javadocs
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: Documentation
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-javadoc-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  This documentation pertains exclusively to version 10.1.1 of
  the PKI Framework and Tools.

  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 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.


pkgId: 60e5b1f408dd8a5661cb61f18717cd28e559119af2385e7d716be8cb86f35fd7
name: pki-javadoc
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Framework Javadocs
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: Documentation
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-javadoc-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  This documentation pertains exclusively to version 10.2.0 of
  the PKI Framework and Tools.

  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 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.


pkgId: ffe3fa9cd51bae0ae5f9f74e5716421751771900cce284e579c4b804a0c6800b
name: pki-kra
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - Data Recovery Manager
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-kra-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  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.


pkgId: c843f19f7b3c8ecb4da325f676d84d36f85b85a5f685482d9f6dbf436573fe92
name: pki-kra
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - Data Recovery Manager
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-kra-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  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.


pkgId: 5997cc746640b72a851fecbf74c58578523f589646915255f84d97b0dbfa3942
name: pki-ocsp
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - Online Certificate Status Protocol Manager
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-ocsp-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  The Online Certificate Status Protocol (OCSP) Manager is an optional PKI
  subsystem that can act as a stand-alone OCSP service.  The OCSP Manager
  performs the task of an online certificate validation authority by enabling
  OCSP-compliant clients to do real-time verification of certificates.  Note
  that an online certificate-validation authority is often referred to as an
  OCSP Responder.

  Although the Certificate Authority (CA) is already configured with an
  internal OCSP service.  An external OCSP Responder is offered as a separate
  subsystem in case the user wants the OCSP service provided outside of a
  firewall while the CA resides inside of a firewall, or to take the load of
  requests off of the CA.

  The OCSP Manager can receive Certificate Revocation Lists (CRLs) from
  multiple CA servers, and clients can query the OCSP Manager for the
  revocation status of certificates issued by all of these CA servers.

  When an instance of OCSP Manager is set up with an instance of CA, and
  publishing is set up to this OCSP Manager, CRLs are published to it
  whenever they are issued or updated.

  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.


pkgId: 491a29f14a1e04ef9b1a39042d660bcebe9d5328b42f29a66402e60fe12d346b
name: pki-ocsp
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - Online Certificate Status Protocol Manager
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-ocsp-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  The Online Certificate Status Protocol (OCSP) Manager is an optional PKI
  subsystem that can act as a stand-alone OCSP service.  The OCSP Manager
  performs the task of an online certificate validation authority by enabling
  OCSP-compliant clients to do real-time verification of certificates.  Note
  that an online certificate-validation authority is often referred to as an
  OCSP Responder.

  Although the Certificate Authority (CA) is already configured with an
  internal OCSP service.  An external OCSP Responder is offered as a separate
  subsystem in case the user wants the OCSP service provided outside of a
  firewall while the CA resides inside of a firewall, or to take the load of
  requests off of the CA.

  The OCSP Manager can receive Certificate Revocation Lists (CRLs) from
  multiple CA servers, and clients can query the OCSP Manager for the
  revocation status of certificates issued by all of these CA servers.

  When an instance of OCSP Manager is set up with an instance of CA, and
  publishing is set up to this OCSP Manager, CRLs are published to it
  whenever they are issued or updated.

  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.


pkgId: ea05786824b2c2f4403c5c75250bfc020177c3fdd82b01cbcf65be95e342d37c
name: pki-server
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - PKI Server Framework
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-server-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  The PKI Server Framework is required by the following four PKI subsystems:

      the Certificate Authority (CA),
      the Data Recovery Manager (DRM),
      the Online Certificate Status Protocol (OCSP) Manager,
      the Token Key Service (TKS), and
      the Token Processing Service (TPS).

  This package is a part of the PKI Core used by the Certificate System.
  The package contains scripts to create and remove PKI subsystems.


  ==================================
  ||  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.


pkgId: 37187e609e63af979f54e05b50bd1a588fea9340c98aa5e3d4094acadd8796db
name: pki-server
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Server Framework
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-server-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  The PKI Server Framework is required by the following four PKI subsystems:

      the Certificate Authority (CA),
      the Data Recovery Manager (DRM),
      the Online Certificate Status Protocol (OCSP) Manager,
      the Token Key Service (TKS), and
      the Token Processing Service (TPS).

  This package is a part of the PKI Core used by the Certificate System.
  The package contains scripts to create and remove PKI subsystems.


  ==================================
  ||  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.


pkgId: a9194f65da7fbc90668735f574be06a182e3128842de909f2845eeb2c46500e7
name: pki-symkey
arch: x86_64
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Symmetric Key JNI Package
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Libraries
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-symkey-10.1.1-2.fc20.x86_64.rpm
checksum_type: sha256
description:
  The Symmetric Key Java Native Interface (JNI) package supplies various native
  symmetric key operations to Java programs.

  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 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.


pkgId: 6901b8ae1f2cbea69d9a10450d0896a83354c11b14c210c9ce858b877347e1d5
name: pki-symkey
arch: x86_64
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Symmetric Key JNI Package
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Libraries
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-symkey-10.2.0-1.fc21.x86_64.rpm
checksum_type: sha256
description:
  The Symmetric Key Java Native Interface (JNI) package supplies various native
  symmetric key operations to Java programs.

  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 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.


pkgId: f45a048b01edd5b9f1c4916123c0bbaf930897702504fe934d5e4828b26c018a
name: pki-tks
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - Token Key Service
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-tks-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  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.

  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.


pkgId: 6a246456df410387b90181484b5a29f0b5d6f5b6f288f0436879e20a4297cd1e
name: pki-tks
arch: noarch
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - Token Key Service
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-tks-10.2.0-1.fc21.noarch.rpm
checksum_type: sha256
description:
  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.

  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.


pkgId: 17f7b647439d7608185100629792dd22e11729a2c1946ae67f685a74de0fd6b3
name: pki-tools
arch: x86_64
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - PKI Tools
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-tools-10.1.1-2.fc20.x86_64.rpm
checksum_type: sha256
description:
  This package contains PKI executables that can be used to help make
  Certificate System into a more complete and robust PKI solution.

  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 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.


pkgId: 6e542c06d8668f35f030c5d877af1601cb0836a38e5f37f8fdffa7416cf1fd19
name: pki-tools
arch: x86_64
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - PKI Tools
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Base
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-tools-10.2.0-1.fc21.x86_64.rpm
checksum_type: sha256
description:
  This package contains PKI executables that can be used to help make
  Certificate System into a more complete and robust PKI solution.

  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 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.


pkgId: d1e2a001c92ebf82d366e1a4c540e67d6d9d00aff35add5a87b5924d54708269
name: pki-tps
arch: x86_64
version: 10.2.0
epoch: 0
release: 1.fc21
summary: Certificate System - Token Processing Service
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-00014a1f
rpm_sourcerpm: pki-core-10.2.0-1.fc21.src.rpm
location_href: fedora-21-x86_64/pki-core-10.2.0-1.fc21/pki-tps-10.2.0-1.fc21.x86_64.rpm
checksum_type: sha256
description:
  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.

  The utility "tpsclient" is a test tool that interacts with TPS.  This
  tool is useful to test TPS server configs without risking an actual
  smart card.


  ==================================
  ||  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.


pkgId: 0b8b52564f7ca4d2c34d8e38fb72ae258e811716ad2d5a33c4a215328b400da7
name: pki-tps-tomcat
arch: noarch
version: 10.1.1
epoch: 0
release: 2.fc20
summary: Certificate System - Token Processing Service
url: http://pki.fedoraproject.org/
rpm_license: GPLv2
rpm_vendor: Fedora Project COPR (mharmsen/dogtag)
rpm_group: System Environment/Daemons
rpm_buildhost: i-0001517c
rpm_sourcerpm: pki-core-10.1.1-2.fc20.src.rpm
location_href: fedora-20-x86_64/pki-core-10.1.1-2.fc20/pki-tps-tomcat-10.1.1-2.fc20.noarch.rpm
checksum_type: sha256
description:
  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.


  ==================================
  ||  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.


