Modified items

All recently modified items, latest first.

ecj-4.2.1-7.fc19.armv6hl: ECJ is the Java bytecode compiler of the Eclipse Platform. It is also known as the JDT Core batch compiler.

ecj-4.2.1-7.fc19.x86_64: ECJ is the Java bytecode compiler of the Eclipse Platform. It is also known as the JDT Core batch compiler.

ecj-4.2.1-7.fc19.x86_64: ECJ is the Java bytecode compiler of the Eclipse Platform. It is also known as the JDT Core batch compiler.

dogtag-pki-console-theme-10.0.7-1.fc19.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-10.0.7-1.fc19.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.

curl-openssl-7.43.0-1.1.lbn19.x86_64: cURL package built with openssl instead of NSS.

cnmonitor-2.1.1-1.lbn19.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.lbn19.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.

certbot-0.6.0-0.0dev0git8e742fa.lbn19.noarch: Certbot is a free, automated certificate authority that aims to lower the barriers to entry for encrypting all HTTP traffic on the internet.

bastion-monit-ds389-19.0.0-3.lbn19.noarch: 389 Directory Server start/stop/control

bastion-ldapschemas-openldap-1.0.1-1.lbn19.noarch: LDAP schemas for LBN infrastructure

bastion-ldapschemas-389-1.0.1-1.lbn19.noarch: LDAP schemas for LBN infrastructure

apache-commons-validator-1.4.0-4.fc19.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.

apache-commons-pool-1.6-5.fc19.noarch: The goal of Pool package is it to create and maintain an object (instance) pooling package to be distributed under the ASF license. The package should support a variety of pool implementations, but encourage support of an interface that makes these implementations interchangeable.

apache-commons-parent-34-3.fc21.noarch: The Project Object Model files for the apache-commons packages.

apache-commons-digester-1.8.1-14.fc19.noarch: Many projects read XML configuration files to provide initialization of various Java objects within the system. There are several ways of doing this, and the Digester component was designed to provide a common implementation that can be used in many different projects

apache-commons-dbcp-1.4-12.fc19.noarch: Many Apache projects support interaction with a relational database. Creating a new connection for each user can be time consuming (often requiring multiple seconds of clock time), in order to perform a database transaction that might take milliseconds. Opening a connection per user can be unfeasible in a publicly-hosted Internet application where the number of simultaneous users can be very large. Accordingly, developers often wish to share a "pool" of open connections between all of the application's current users. The number of users actually performing a request at any given time is usually a very small percentage of the total number of active users, and during request processing is the only time that a database connection is required. The application itself logs into the DBMS, and handles any user account issues internally.


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