Free export ldap entries software for linux

Apache LDAP vhost driver project lets you put vhost with all possible information in an LDAP database for both Apache 1.x and 2.x.

Bug report system

With the new maintainence, there is now also a bug report system at the URL http://bugs.bayour.com/ (project mod_ldap_cfg).

Schemas

A schema called mod_ldap_cfg is used.

Apache config

To setup Apache to use this module, the httpd.conf is used.

Perl6::Export::Attrs - the Perl 6 is export(...) trait as a Perl 5 attribute.
SYNOPSIS
package Some::Module;
use Perl6::Export::Attrs;
# Export &foo by default, when explicitly requested,
# or when the :ALL export set is requested...
sub foo :Export(:DEFAULT) {
print "phooo!";
}
# Export &var by default, when explicitly requested,
# or when the :bees, :pubs, or :ALL export set is requested...
# the parens after is export are like the parens of a qw(...)
sub bar :Export(:DEFAULT :bees :pubs) {
print "baaa!";
}
# Export &baz when explicitly requested
# or when the :bees or :ALL export set is requested...
sub baz :Export(:bees) {
print "baassss!";
}
# Always export &qux
# (no matter what else is explicitly or implicitly requested)
sub qux :Export(:MANDATORY) {
print "quuuuuuuuux!";
}
IMPORT {
# This block is called when the module is used (as usual),
# but it is called after any export requests have been handled.
# Those requests will have been stripped from its @_ argument list
}
Implements a Perl 5 native version of what the Perl 6 symbol export mechanism will look like.
Its very straightforward:
- If you want a subroutine to be capable of being exported (when explicitly requested in the use arguments), you mark it with the :Export attribute.
- If you want a subroutine to be automatically exported when the module is used (without specific overriding arguments), you mark it with the :Export(:DEFAULT) attribute.
- If you want a subroutine to be automatically exported when the module is used (even if the user specifies overriding arguments), you mark it with the :Export(:MANDATORY) attribute.
- If the subroutine should also be exported when particular export groups are requested, you add the names of those export groups to the attributes argument list.

ProFTPD Quota LDAP module provides a ProFTPD module that imposes quotas based on LDAP user accounts.
This module is designed to impose quotas, on FTP accounts, based on user accounts. It is based on the ideas contained in Eric Estabrooks mod_quota and TJ Saunders mod_quotatab; however, this module has been written from scratch to implement quotas in a very different manner.
Installation
To install mod_quota_ldap, follow these instructions. After unpacking the tarball, copy the mod_quota_ldap.c file into:
{proftpd-dir}/contrib/
after unpacking the latest proftpd-1.2 source code. Follow the usual steps for using third-party modules in proftpd:
$ ./configure --with-modules=mod_quota_ldap make make install
Enhancements:
- Release works with proFTPd-1.2.8 or higher
- Bug#679338 & Bug#679343 - quota_ldap_getconf() bug solved

Python-LDAP provides an object-oriented API to access LDAP directory servers from Python programs. Mainly it wraps the OpenLDAP 2.x libs for that purpose.

Additionally the package contains modules for other LDAP-related stuff (e.g. processing LDIF, LDAPURLs, LDAPv3 schema, etc.).

Net::LDAP::Control::VLV is an LDAPv3 Virtual List View control object.

SYNOPSIS

use Net::LDAP;
use Net::LDAP::Control::VLV;
use Net::LDAP::Constant qw( LDAP_CONTROL_VLVRESPONSE );

$ldap = Net::LDAP->new( "ldap.mydomain.eg" );

# Get the first 20 entries
$vlv = Net::LDAP::Control::VLV->new(
before => 0, # No entries from before target entry
after => 19, # 19 entries after target entry
content => 0, # List size unknown
offset => 1, # Target entry is the first
);
$sort = Net::LDAP::Control::Sort->new( order => cn );

@args = ( base => "o=Ace Industry, c=us",
scope => "subtree",
filter => "(objectClass=inetOrgPerson)",
callback => &process_entry, # Call this sub for each entry
control => [ $vlv, $sort ],
);

$mesg = $ldap->search( @args );

# Get VLV response control
($resp) = $mesg->control( LDAP_CONTROL_VLVRESPONSE ) or die;
$vlv->response( $resp );

# Set the control to get the last 20 entries
$vlv->end;

$mesg = $ldap->search( @args );

# Get VLV response control
($resp) = $mesg->control( LDAP_CONTROL_VLVRESPONSE ) or die;
$vlv->response( $resp );

# Now get the previous page
$vlv->scroll_page( -1 );

$mesg = $ldap->search( @args );

# Get VLV response control
($resp) = $mesg->control( LDAP_CONTROL_VLVRESPONSE ) or die;
$vlv->response( $resp );

# Now page with first entry starting with "B" in the middle
$vlv->before(9); # Change page to show 9 before
$vlv->after(10); # Change page to show 10 after
$vlv->assert("B"); # assert "B"

$mesg = $ldap->search( @args );

BBDB::Export is a Perl module to export data from The Insidious Big Brother Database.

SYNOPSIS

use BBDB::Export;

# export to LDIF
my $exporter = BBDB::Export::LDIF->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => "export.ldif",
dc => "dc=geekfarm, dc=org",
}
);
$exporter->export();

# sync with ldap via ldapadd and ldapdelete
my $exporter = BBDB::Export::LDAP->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => "/tmp/tempfile",
dc => "dc=geekfarm, dc=org",
ldappass => "supersecret",
}
);

$exporter->export();

# export to vcards
my $exporter = BBDB::Export::vCard->new(
{
bbdb_file => "/path/to/.bbdb",
output_dir => "/some/path/",
}
);

$exporter->export();

# create .mail_aliases
my $exporter = BBDB::Export::MailAliases->new(
{
bbdb_file => "/path/to/.bbdb",
output_file => ".mail_aliases",
}
);

$exporter->export();

This module was designed to export to your bbdb data to a wide array of formats, and also to make it easy to write new modules to export to new formats. Current export options include building an LDIF, vCard, or .mail_aliases, and automatically updating an ldap server.
For a fully functional command line converter, see the bbdb-export script that comes with this module.

BBDB::Export should not be used directly. Use any of the available subclasses using the examples above. For more examples of using BBDB::Export, see the test cases.

NetDirector is an open and extensible management framework for managing configurations of common open source network services.
NetDirector offers both form driven and fine-grained control of server configuration files with many added benefits including rollback and policy-based access. It can manage both Linux and most any flavor of Unix. However, the preferred platform to host NetDirector Server Manager on is Linux.
What can you manage with NetDirector?
Today you can manage the following configurations through an easy-to-use form based web console. Or you can edit the entire configuration file in an editor manually but with the added advantage of automated version control.
- HTTP (Apache)
- DNS (BIND)
- DHCP
- File and Print Services (Samba, NFS)
- Email (Postfix, Sendmail)
- FTP (VSFTP)
- Users and Groups (mass add users to multiple servers at once.
- Network Interfaces
- Numerous System files
What else can NetDirector do beyond configuration management?
NetDirector is more than just a configuration tool, NetDirector has additional features including the following:
- Rollbacks (Revision Control) of each change made to a service accross any number of servers
- Troubleshooting/Logs
- Schedule Changes to occur anytime in the future
- Server configuration cloning.
- Intuitive integrated support for managing clustered servers and disaster recovery configurations.
- Track Past or Scheduled Changes to be done
- Track who made what changes and when
- Granular Role based user management
These capabilities can be applied to other server functions. For example, you could adapt NetDirector to schedule and run shell scripts on servers under management. Or, you could develop a module to provide system backups using Amanda as or simply use NetDirector as a way to front-end access to all servers, giving you the ability to tighten the points of authentication to servers and add an additional layer of security.