Modified items

All recently modified items, latest first.

dogtag-pki-tks-theme-9.0.13-1.lbn13.noarch: This Token Key Service (TKS) User Interface contains the Dogtag textual and graphical user interface for the TKS. 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.

dogtag-pki-ra-theme-9.0.13-1.lbn13.noarch: This Registration Authority (RA) User Interface contains the Dogtag textual and graphical user interface for the RA. 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.

dogtag-pki-ocsp-theme-9.0.13-1.lbn13.noarch: This Online Certificate Status Protocol (OCSP) Manager User Interface contains the Dogtag textual and graphical user interface for the OCSP Manager. 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.

dogtag-pki-kra-theme-9.0.13-1.lbn13.noarch: This Data Recovery Manager (DRM) User Interface contains the Dogtag textual and graphical user interface for the DRM. 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.

dogtag-pki-console-theme-9.0.13-1.lbn13.noarch: 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.

dogtag-pki-common-theme-9.0.13-1.lbn13.noarch: This PKI Common Framework User Interface contains the Dogtag textual and graphical user interface for the PKI Common 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.

dogtag-pki-ca-theme-9.0.13-1.lbn13.noarch: This Certificate Authority (CA) User Interface contains the Dogtag textual and graphical user interface for the CA. 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.

dogtag-pki-9.0.0-13.lbn13.noarch: 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.

cnmonitor-pgsql-2.1.1-1.lbn13.noarch: PostgreSQL backend for cnmonitor

cnmonitor-mysql-2.1.1-1.lbn13.noarch: MySQL backend for cnmonitor

cnmonitor-2.1.1-1.lbn13.noarch: Get full control over your LDAP environment! Directory Server, LDAP Monitoring application. Monitoring small to large scaled deployed directory server environments. Monitoring and viewing server status can be gathered from: Open LDAP RedHat / Fedora / 389 Directory Server Sun / Oracle Directory Server Enterprise Edition Novell eDirectory Server IBM Tivoli Directory Server General Monitoring such as response time, server availability (Any LDAP Server) Features: Environment and Server availability Monitoring Verify Replication Verify Cluster / Load Balancing View Schema Verify Cache Size View Trends Get email Alerts on server failures Get email Reports of weekly load Advance LDAP Query Servers recognized: Open LDAP, RedHat / Fedora / 389 Directory Server, Sun / Oracle, Novell / Suse eDirectory, IBM Tivoli Directory Server, Netscape iPlanet, Microsoft Active Directory and Oracle Internet Directory.

charge-1.3.0-6.lbn13.x86_64: Charge is a load testing software. It allows to test what can accept an LDAP directory. An XML configuration file allows to define operations to run, the ordre of these operations and eventually to generate LDAP operations from simples rules.

c-ares-1.10.0-1.lbn13.x86_64: c-ares is a C library that performs DNS requests and name resolves asynchronously. c-ares is a fork of the library named 'ares', written by Greg Hudson at MIT.

c-ares-1.9.1-2.fc18.armv6hl: c-ares is a C library that performs DNS requests and name resolves asynchronously. c-ares is a fork of the library named 'ares', written by Greg Hudson at MIT.

bcel-5.2-7.1.fc12.x86_64: The Byte Code Engineering Library (formerly known as JavaClass) is intended to give users a convenient possibility to analyze, create, and manipulate (binary) Java class files (those ending with .class). Classes are represented by objects which contain all the symbolic information of the given class: methods, fields and byte code instructions, in particular. Such objects can be read from an existing file, be transformed by a program (e.g. a class loader at run-time) and dumped to a file again. An even more interesting application is the creation of classes from scratch at run-time. The Byte Code Engineering Library (BCEL) may be also useful if you want to learn about the Java Virtual Machine (JVM) and the format of Java .class files. BCEL is already being used successfully in several projects such as compilers, optimizers, obsfuscators and analysis tools, the most popular probably being the Xalan XSLT processor at Apache.

bastion-monit-zenoss-ldap-4.2.4_4.0.2-1.lbn13.noarch: zenperfldap start/stop/control

bastion-monit-ds389-1.4.0-1.lbn13.noarch: 389 Directory Server start/stop/control

bastion-ldapschemas-openldap-1.0.0-2.lbn13.noarch: LDAP schemas for LBN infrastructure

bastion-ldapschemas-389-1.0.0-2.lbn13.noarch: LDAP schemas for LBN infrastructure

apache-commons-validator-1.3.1-5.lbn13.noarch: A common issue when receiving data either electronically or from user input is verifying the integrity of the data. This work is repetitive and becomes even more complicated when different sets of validation rules need to be applied to the same set of data based on locale for example. Error messages may also vary by locale. This package attempts to address some of these issues and speed development and maintenance of validation rules.

« Previous 20 items Next 20 items » 1 ... 2395 2396 2397 2398 2399 2400 2401 ... 2421


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items