cf
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 41
Cft 0.2.1
Cft project watches a system administrator as she makes changes to a system. more>>
Its basic principle is heavily influenced by Gnomes Sabayon. Instead of the desktop though, cft is focused on traditional system administrators and how they maintain machines, mostly with command line tools.
Cft uses puppet as its backbone for expressing the configuration of a system, and for understanding in greater detail what changes the admin has made to the system. Sites that already use puppet to manage their configuration can easily integrate cfts output into the overall site configuration; for sites that use some other means of configuration management, cfts output provides a complete record of changes made and serves as a good starting point of integrating the changes back into the sites configuration.
Example:
In lieu of colorful screenshots, a simple example will explain in more detail how cft works: cft organizes changes in sessions to let the user better indicate what aspect of the system they are fixing (the webserver, the mailserver etc.) A simple session to fix the configuration of postfix and to start and enable the service might entail root running the following commands:
tux:1# cft begin postfix
tux:2# yum -y install postfix
tux:3# vi /etc/postfix/main.cf
tux:4# chkconfig postfix on
tux:5# service postfix start
tux:6# cft finish postfix
Note that the user only had to issue two additonal commands to begin and finish the session, everything else in the session is exactly the same as if the changes had been made without cft. The command cft begin postfix tells cft to start a session called postfix, and the last command cft finish postfix tells it to do the final bookkeeping necessary for analysing the results.
Once the commands above have been issued, running cft manifest postfix will print the changes in the form of a puppet manifest:
tux:6# cft manifest postfix
class postfix {
package { postfix.i386:
ensure => 2:2.3.3-2
}
service { postfix:
enable => true,
pattern => postfix,
ensure => running
}
file { /etc/aliases.db:
group => smmsp,
owner => root,
mode => 0640,
source => /tmp/cft/postfix/after/etc/aliases.db
}
file { /etc/postfix/main.cf:
group => root,
owner => root,
mode => 0644,
source => /tmp/cft/postfix/after/etc/postfix/main.cf
}
}
This manifest tells puppet that puppet should enable and start the postfix service, and that the two files should be copied from the location mentioned as the source and receive the given owner, group, and mode. cft takes care of copying all modified files into a safe location so that they can be copied off the machine into a central location. The mention of the file aliases.db is somewhat spurious: it gets automatically recreated by the init script for postfix, and cft treats it exactly as if the user had created the file.
To facilitate moving the changes onto a central serevr, cft can also convert a session into a tarball that contains both the puppet manifest and all the files that are mentioned in it, in this case aliases.db and main.cf. Fancier, more convenient methods of integrating changes back into a central puppet server are planned for the future.
<<lessCft uses puppet as its backbone for expressing the configuration of a system, and for understanding in greater detail what changes the admin has made to the system. Sites that already use puppet to manage their configuration can easily integrate cfts output into the overall site configuration; for sites that use some other means of configuration management, cfts output provides a complete record of changes made and serves as a good starting point of integrating the changes back into the sites configuration.
Example:
In lieu of colorful screenshots, a simple example will explain in more detail how cft works: cft organizes changes in sessions to let the user better indicate what aspect of the system they are fixing (the webserver, the mailserver etc.) A simple session to fix the configuration of postfix and to start and enable the service might entail root running the following commands:
tux:1# cft begin postfix
tux:2# yum -y install postfix
tux:3# vi /etc/postfix/main.cf
tux:4# chkconfig postfix on
tux:5# service postfix start
tux:6# cft finish postfix
Note that the user only had to issue two additonal commands to begin and finish the session, everything else in the session is exactly the same as if the changes had been made without cft. The command cft begin postfix tells cft to start a session called postfix, and the last command cft finish postfix tells it to do the final bookkeeping necessary for analysing the results.
Once the commands above have been issued, running cft manifest postfix will print the changes in the form of a puppet manifest:
tux:6# cft manifest postfix
class postfix {
package { postfix.i386:
ensure => 2:2.3.3-2
}
service { postfix:
enable => true,
pattern => postfix,
ensure => running
}
file { /etc/aliases.db:
group => smmsp,
owner => root,
mode => 0640,
source => /tmp/cft/postfix/after/etc/aliases.db
}
file { /etc/postfix/main.cf:
group => root,
owner => root,
mode => 0644,
source => /tmp/cft/postfix/after/etc/postfix/main.cf
}
}
This manifest tells puppet that puppet should enable and start the postfix service, and that the two files should be copied from the location mentioned as the source and receive the given owner, group, and mode. cft takes care of copying all modified files into a safe location so that they can be copied off the machine into a central location. The mention of the file aliases.db is somewhat spurious: it gets automatically recreated by the init script for postfix, and cft treats it exactly as if the user had created the file.
To facilitate moving the changes onto a central serevr, cft can also convert a session into a tarball that contains both the puppet manifest and all the files that are mentioned in it, in this case aliases.db and main.cf. Fancier, more convenient methods of integrating changes back into a central puppet server are planned for the future.
Download (3.1MB)
Added: 2007-05-09 License: GPL (GNU General Public License) Price:
901 downloads
CFPlus 0.95
CFPlus is a modern client for Crossfire+ and Crossfire MMORPG game servers. more>>
CFPlus is a modern client for Crossfire+ and Crossfire MMORPG game servers.
It offers a large map, an elaborate menu and help system, dialog-based character setup, and an innovative command completer and macros, and supports all CF+ extensions: dialog-based NPC interaction, enhanced map protocol (health and dialogue information), and the graphical minimap.
It is based on Perl, SDL, and OpenGL for high performance on modern systems, and works on both Unix and Windows. Ports to other platforms should be very easy and are underway.
Main features:
- Death is not permanent, and you can get back all lost stats and experience by playing a game in a special place named Nimbus. You are teleported there when you die and you have to play a game (currently minesweeper) to get out.
- Friendly fire is disabled and playerkilling is also modified. You can only kill another player when you and the other player are hostile. To become hostile, you have to visit the church of Gorokh in Scorn and talk to the priest. To become peaceful again, visit the curch of Valriel and talk to its priest.
- Invitation of other players to where you are is possible with the invite command. You have to solve the invitor quest (see below in maps) to be able to use the command.
- You can follow other players with the follow command when you stand next to the player you want to follow.
- Pet monsters and summoned creatures will not stand in the way of other party members, making it bearable to play with summoning skills in a party.
- Map and graphics artists are working on improved graphics and new maps and quests.
- A new currency: the Royalty. Its worth 100 Platinum and is made of paper. (The bank script was completly rewritten in Perl)
- The communication commands have been rewritten in Perl and an ignore command was added.
- Trade shops have been implemented in Perl, which allows the player to trade items when they are offline.
<<lessIt offers a large map, an elaborate menu and help system, dialog-based character setup, and an innovative command completer and macros, and supports all CF+ extensions: dialog-based NPC interaction, enhanced map protocol (health and dialogue information), and the graphical minimap.
It is based on Perl, SDL, and OpenGL for high performance on modern systems, and works on both Unix and Windows. Ports to other platforms should be very easy and are underway.
Main features:
- Death is not permanent, and you can get back all lost stats and experience by playing a game in a special place named Nimbus. You are teleported there when you die and you have to play a game (currently minesweeper) to get out.
- Friendly fire is disabled and playerkilling is also modified. You can only kill another player when you and the other player are hostile. To become hostile, you have to visit the church of Gorokh in Scorn and talk to the priest. To become peaceful again, visit the curch of Valriel and talk to its priest.
- Invitation of other players to where you are is possible with the invite command. You have to solve the invitor quest (see below in maps) to be able to use the command.
- You can follow other players with the follow command when you stand next to the player you want to follow.
- Pet monsters and summoned creatures will not stand in the way of other party members, making it bearable to play with summoning skills in a party.
- Map and graphics artists are working on improved graphics and new maps and quests.
- A new currency: the Royalty. Its worth 100 Platinum and is made of paper. (The bank script was completly rewritten in Perl)
- The communication commands have been rewritten in Perl and an ignore command was added.
- Trade shops have been implemented in Perl, which allows the player to trade items when they are offline.
Download (9.4MB)
Added: 2006-11-09 License: GPL (GNU General Public License) Price:
1140 downloads
RTx::RT34::Bulk::CF::Edit 0.001
RTx::RT34::Bulk::CF::Edit is a Perl module to allow bulk editing of custom fields. more>>
RTx::RT34::Bulk::CF::Edit is a Perl module to allow bulk editing of custom fields.
<<less Download (0.014MB)
Added: 2007-01-23 License: Perl Artistic License Price:
1006 downloads
Asterisk Live CF card b-01
Asterisk Live CF card is, clearly, a compact flash install of asterisk. more>>
Asterisk Live CF card is, clearly, a compact flash install of asterisk that will give you a complete, running system similar to that of the asterisk live CD.
Indeed most things are the same although there have been some additions and changes.
To install the CF you will need some way of getting the image onto the card. Generally this can be done with a USB CF card reader using
dd if=asterisk-cf-b01 of=/dev/sda bs=1k count=64000
Useful things to know
1. The cf install currently assumes its hda (1 2 and 3) so youll need to put it in as your primary master using your CF->IDE adaptor, this will be more automagical in the future
2. example configs are stored on hda3 along with a new feature script called remoteconfig. This will allow you to update the configuration/OS automatically on boot from a remote webserver. More detail on how to use this feature will appear at http://www.automated.it/asterisk be sure to read any notes there first.
3. At the minimum youll need a 64mb CF card but you can use a larger one if you wish and create futher partitions. Currenly when you create the CF from the image the following partitions exist
Disk /dev/hda: 8 heads, 32 sectors, 490 cylinders
Units = cylinders of 256 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 33 4208 83 Linux
/dev/hda2 34 354 41088 83 Linux
/dev/hda3 355 490 17408 83 Linux
4. Once booted you will need to make changes to the files in /dev/hda3/astlive-example, particularly networking and the zapata/zaptel configs. Note, if you rename the astlive-example directory to astlive then on the next boot the files will be copied and activated on the running system automatically. Using the example astlive directory includes a PASSWORD CHANGE for root from EPPING to epping (without quotes) as a demonstration. At the minimum you MUST change the networking to suit your environment, since they will change to what is in this directory too.
5. All partitions on the CF are unmounted after boot so if you need to work on them, you will need to specifically mount them.
6. Ive tested E100P, X100P and TDM40B cards using this install, and would be interested to hear of other cards proven to be working.
<<lessIndeed most things are the same although there have been some additions and changes.
To install the CF you will need some way of getting the image onto the card. Generally this can be done with a USB CF card reader using
dd if=asterisk-cf-b01 of=/dev/sda bs=1k count=64000
Useful things to know
1. The cf install currently assumes its hda (1 2 and 3) so youll need to put it in as your primary master using your CF->IDE adaptor, this will be more automagical in the future
2. example configs are stored on hda3 along with a new feature script called remoteconfig. This will allow you to update the configuration/OS automatically on boot from a remote webserver. More detail on how to use this feature will appear at http://www.automated.it/asterisk be sure to read any notes there first.
3. At the minimum youll need a 64mb CF card but you can use a larger one if you wish and create futher partitions. Currenly when you create the CF from the image the following partitions exist
Disk /dev/hda: 8 heads, 32 sectors, 490 cylinders
Units = cylinders of 256 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 33 4208 83 Linux
/dev/hda2 34 354 41088 83 Linux
/dev/hda3 355 490 17408 83 Linux
4. Once booted you will need to make changes to the files in /dev/hda3/astlive-example, particularly networking and the zapata/zaptel configs. Note, if you rename the astlive-example directory to astlive then on the next boot the files will be copied and activated on the running system automatically. Using the example astlive directory includes a PASSWORD CHANGE for root from EPPING to epping (without quotes) as a demonstration. At the minimum you MUST change the networking to suit your environment, since they will change to what is in this directory too.
5. All partitions on the CF are unmounted after boot so if you need to work on them, you will need to specifically mount them.
6. Ive tested E100P, X100P and TDM40B cards using this install, and would be interested to hear of other cards proven to be working.
Download (45.3MB)
Added: 2006-06-20 License: GPL (GNU General Public License) Price:
1224 downloads
Config::Fast 1.07
Config::Fast is an extremely fast configuration file parser. more>>
Config::Fast is an extremely fast configuration file parser.
SYNOPSIS
# default config format is a space-separated file
company "Supercool, Inc."
support nobody@nowhere.com
# and then in Perl
use Config::Fast;
%cf = fastconfig;
print "Thanks for visiting $cf{company}!n";
print "Please contact $cf{support} for support.n";
This module is designed to provide an extremely lightweight way to parse moderately complex configuration files. As such, it exports a single function - fastconfig() - and does not provide any OO access methods. Still, it is fairly full-featured.
Heres how it works:
%cf = fastconfig($file, $delim);
Basically, the fastconfig() function returns a hash of keys and values based on the directives in your configuration file. By default, directives and values are separated by whitespace in the config file, but this can be easily changed with the delimiter argument (see below).
When the configuration file is read, its modification time is first checked and the results cached. On each call to fastconfig(), if the config file has been changed, then the file is reread. Otherwise, the cached results are returned automatically. This makes this module great for mod_perl modules and scripts, one of the primary reasons I wrote it. Simply include this at the top of your script or inside of your constructor function:
my %cf = fastconfig(/path/to/config/file.conf);
If the file argument is omitted, then fastconfig() looks for a file named $0.conf in the ../etc directory relative to the executable. For example, if you ran:
/usr/local/bin/myapp
Then fastconfig() will automatically look for:
/usr/local/etc/myapp.conf
This is great if youre really lazy and always in a hurry, like I am.
If this doesnt work for you, simply supply a filename manually. Note that filename generation does not work in mod_perl, so youll need to supply a filename manually.
<<lessSYNOPSIS
# default config format is a space-separated file
company "Supercool, Inc."
support nobody@nowhere.com
# and then in Perl
use Config::Fast;
%cf = fastconfig;
print "Thanks for visiting $cf{company}!n";
print "Please contact $cf{support} for support.n";
This module is designed to provide an extremely lightweight way to parse moderately complex configuration files. As such, it exports a single function - fastconfig() - and does not provide any OO access methods. Still, it is fairly full-featured.
Heres how it works:
%cf = fastconfig($file, $delim);
Basically, the fastconfig() function returns a hash of keys and values based on the directives in your configuration file. By default, directives and values are separated by whitespace in the config file, but this can be easily changed with the delimiter argument (see below).
When the configuration file is read, its modification time is first checked and the results cached. On each call to fastconfig(), if the config file has been changed, then the file is reread. Otherwise, the cached results are returned automatically. This makes this module great for mod_perl modules and scripts, one of the primary reasons I wrote it. Simply include this at the top of your script or inside of your constructor function:
my %cf = fastconfig(/path/to/config/file.conf);
If the file argument is omitted, then fastconfig() looks for a file named $0.conf in the ../etc directory relative to the executable. For example, if you ran:
/usr/local/bin/myapp
Then fastconfig() will automatically look for:
/usr/local/etc/myapp.conf
This is great if youre really lazy and always in a hurry, like I am.
If this doesnt work for you, simply supply a filename manually. Note that filename generation does not work in mod_perl, so youll need to supply a filename manually.
Download (0.010MB)
Added: 2007-08-11 License: Perl Artistic License Price:
805 downloads
Compact Filter 0.3
Compact Filter is a network packet filter for Linux. more>>
Compact Filter is a network packet filter for Linux. It features an easy-to-use compact filter representation and high performance.
The main features are: easy to use interface, compact filter representation (memory efficient), and very high performance.
A difference between CF and other firewalls, such as Netfilter, is its representation of the ruleset. In CF the user writes a filter which is then compiled and optimized in user-space. The optimized filter is then loaded into the kernel (using netlink). Consequently the in kernel packet filtering code only needs funtionality for setting up a filter and filtering packets, while the more complex code of optimizing the filter remains in user-space.
Because of the continuous increase of the bandwidth and the security threats, firewalls have to evolve towards more efficient filtering schemes. The truth is that the existing scheme does not scale so well with the combined growth of bandwidth and rulesets.
Our aim is to try another approach to perform packet filtering where we minimize the complexity of the filtering process. This result in, both, a reduction of the required CPU power to filter packets and a simpler (and smaller) kernel code. Of course, we are pushing all the smart and complex part out to the user-space, but, developing in user-space is much simpler and safer.
Enhancements:
- changed -d option to delete all filters
- added -D option to delete a specific filter
- changed default policy to permit rather than deny
- added -l option on flex to support --yylineno on older versions of flex
- new and improved install guide
<<lessThe main features are: easy to use interface, compact filter representation (memory efficient), and very high performance.
A difference between CF and other firewalls, such as Netfilter, is its representation of the ruleset. In CF the user writes a filter which is then compiled and optimized in user-space. The optimized filter is then loaded into the kernel (using netlink). Consequently the in kernel packet filtering code only needs funtionality for setting up a filter and filtering packets, while the more complex code of optimizing the filter remains in user-space.
Because of the continuous increase of the bandwidth and the security threats, firewalls have to evolve towards more efficient filtering schemes. The truth is that the existing scheme does not scale so well with the combined growth of bandwidth and rulesets.
Our aim is to try another approach to perform packet filtering where we minimize the complexity of the filtering process. This result in, both, a reduction of the required CPU power to filter packets and a simpler (and smaller) kernel code. Of course, we are pushing all the smart and complex part out to the user-space, but, developing in user-space is much simpler and safer.
Enhancements:
- changed -d option to delete all filters
- added -D option to delete a specific filter
- changed default policy to permit rather than deny
- added -l option on flex to support --yylineno on older versions of flex
- new and improved install guide
Download (0.092MB)
Added: 2006-06-30 License: GPL (GNU General Public License) Price:
1211 downloads
jCSP 1.0
jCSP is the java-based successor to CSP. more>>
jCSP is the java-based successor to CSP.
jCSP is a java-toolkit for building PKI services. Culturally based on the perl CSP toolkit (cf elsewhere on this site) jCSP is built with different goals in mind and the perl toolkit will be maintained in parallell.
Currently the jcsp project contains a single subproject: jcsp-engine - the core of the jcsp toolkit - which is a xml-driven certificate generator. Using jcsp-engine it is easy to create (sign) certificates tailored to specific needs.
The svn repository for jcsp (including jcsp-engine) is svn://anonsvn.it.su.se/jcsp/trunk. Builds are done using maven2 and wind up in the maven repository.
<<lessjCSP is a java-toolkit for building PKI services. Culturally based on the perl CSP toolkit (cf elsewhere on this site) jCSP is built with different goals in mind and the perl toolkit will be maintained in parallell.
Currently the jcsp project contains a single subproject: jcsp-engine - the core of the jcsp toolkit - which is a xml-driven certificate generator. Using jcsp-engine it is easy to create (sign) certificates tailored to specific needs.
The svn repository for jcsp (including jcsp-engine) is svn://anonsvn.it.su.se/jcsp/trunk. Builds are done using maven2 and wind up in the maven repository.
Download (0.038MB)
Added: 2006-10-18 License: GPL (GNU General Public License) Price:
1103 downloads
compFUSEd 200712321
compFUSEd is a simple compressed overlay fs that supports both READ and WRITE operations. more>>
Since there are none right now for Linux [well there still is ext2comp, but ext2 is getting a bit old and the patches are NOT compatible with ext3] I wrote this thing. Thanks to FUSE and using compFUSEd you can have a compressed FS on top of any fancy must have FS on Linux.
Simple? This fs is not suited for large files! Files are compressed as a whole. No clever strategy was used to split the files in chunks of fixed. Later maybe.
Overlay? Files are compressed an decompressed on the fly but the actual storage is done in the directory of an underlying fs. This underlying fs takes care of space allocation, fragmention, etc...
Main features:
- Transparant read and write compression (again, I know ;)
- Configuration file (very simple one)
- Can use ZLIB, LZO or BZIP2, set in config file. You can not change the compression once the files are created!
- User defined blacklist of file extensions that should not be compressed, set in config file. So that we do not try to compress jpeg or Xvid files. Common file types are included by default in the blacklist (see cf_file.c).
- Files smaller that 4096 bytes are not compressed. First because bzip2 has problems with that! And second because I _think_ that the underlying fs will allocate a block of 4096 bytes anyway to store the compressed data anyway (no?).
- Any cleverness? Not really, uncompressible files are not compressed. Unchanged files are not recompressed (whoaa!...:( ).
- Since version 0.04 (cf-200528614.tgz) threading works (after 12 October 2005).
Enhancements:
- A new "minimum size for compression" parameter has been added.
- Incorrectly marked uncompressable chunks have been fixed.
- The code to persist the filesystem info between mounts has been fixed.
- This release has graceful handling of compression lib failure.
- It has dynamically sized file mapping (internal mapping).
<<lessSimple? This fs is not suited for large files! Files are compressed as a whole. No clever strategy was used to split the files in chunks of fixed. Later maybe.
Overlay? Files are compressed an decompressed on the fly but the actual storage is done in the directory of an underlying fs. This underlying fs takes care of space allocation, fragmention, etc...
Main features:
- Transparant read and write compression (again, I know ;)
- Configuration file (very simple one)
- Can use ZLIB, LZO or BZIP2, set in config file. You can not change the compression once the files are created!
- User defined blacklist of file extensions that should not be compressed, set in config file. So that we do not try to compress jpeg or Xvid files. Common file types are included by default in the blacklist (see cf_file.c).
- Files smaller that 4096 bytes are not compressed. First because bzip2 has problems with that! And second because I _think_ that the underlying fs will allocate a block of 4096 bytes anyway to store the compressed data anyway (no?).
- Any cleverness? Not really, uncompressible files are not compressed. Unchanged files are not recompressed (whoaa!...:( ).
- Since version 0.04 (cf-200528614.tgz) threading works (after 12 October 2005).
Enhancements:
- A new "minimum size for compression" parameter has been added.
- Incorrectly marked uncompressable chunks have been fixed.
- The code to persist the filesystem info between mounts has been fixed.
- This release has graceful handling of compression lib failure.
- It has dynamically sized file mapping (internal mapping).
Download (0.099MB)
Added: 2007-05-03 License: Public Domain Price:
905 downloads
LEAF 2.4.2
LEAF is an easy-to-use embedded Linux system that is meant for creating network appliances. more>>
LEAF Bering-uClibc is based on the well-known Bering distribution from Jacques Nilo and Erik Wolzak and provide the same features and functionality in the base. Anyway there are some differences with the original Bering release.
The biggest difference is that all binaries have been compiled with uClibc instead of glibc 2.0.7; but Bering-uClibc also supports ipv6, is based on a newer kernel, uses the latest sources, has some improvements and bugfixes and is significantly smaller.
LEAF Bering-uClibc is available for download as a single-floppy-based firewall or as an ISO-image. Additionally booting from HD, CF or an USB device is supported.
The floppy image supports dhcp, ppp and pppoe connections out of the box and fits for a SOHO network demanding a stable and secure router/Internet connection. With dropbear, a small sshd replacement, it is even ready for secure remote administration.
With the ISO image, or using an USB/CF/HD boot device, you can add about 100 packages to extend LEAF Bering-uClibc with capabilities like SNMP, IPV6 (and shorewall-like IPV6 firewall setup utility), VPN, Intrusion Detection, Traffic Accounting, Quagga Routing Suite, bandwith management and wireless connections, just to name a few.
Enhancements:
- dnsmasq applied
- an extra stability patch to version 2.27
- shorewall updated to version 3.0.7
<<lessThe biggest difference is that all binaries have been compiled with uClibc instead of glibc 2.0.7; but Bering-uClibc also supports ipv6, is based on a newer kernel, uses the latest sources, has some improvements and bugfixes and is significantly smaller.
LEAF Bering-uClibc is available for download as a single-floppy-based firewall or as an ISO-image. Additionally booting from HD, CF or an USB device is supported.
The floppy image supports dhcp, ppp and pppoe connections out of the box and fits for a SOHO network demanding a stable and secure router/Internet connection. With dropbear, a small sshd replacement, it is even ready for secure remote administration.
With the ISO image, or using an USB/CF/HD boot device, you can add about 100 packages to extend LEAF Bering-uClibc with capabilities like SNMP, IPV6 (and shorewall-like IPV6 firewall setup utility), VPN, Intrusion Detection, Traffic Accounting, Quagga Routing Suite, bandwith management and wireless connections, just to name a few.
Enhancements:
- dnsmasq applied
- an extra stability patch to version 2.27
- shorewall updated to version 3.0.7
Download (0.40MB)
Added: 2006-06-02 License: GPL (GNU General Public License) Price:
1240 downloads
RFDump 1.4
RFDump is a backend GPL tool to directly interoperate with any RFID ISO-Reader to make the contents stored on RFID tags. more>>
RFDump is a backend GPL tool to directly interoperate with any RFID ISO-Reader to make the contents stored on RFID tags accessible. This makes the following types of audits possible:
Test robustness of data-structures on the reader and the backend-application
Proof-of-concept manipulations of RFID tag contents
Clone / copy & paste User-Data stored on RFID tags
Audit tag-security features
Due to the overwhelming feedback we received since presenting RFDump at the Blackhat Conference 2004 in Las Vegas (check out the slides from our presentation) we are working on making his Web Site a portal for information exchange regarding RFID technology. The intention is to build a forum where all people interested or concerned about RFID technolgy can discuss and exchange their opinion in an open environment.
RFDump is a tool to detect RFID-Tags and show their meta information: Tag ID, Tag Type, manufacturer etc. The User-Data of a tag can be displayed and modified using either a Hex or an ASCII editor. In addition, the integrated cookie feature demonstrates how easy it is for a company to abuse RFID technology to spy on their customers. RFDump works with the ACG Multi-Tag Reader or similar card reader hardware.
Main features:
- Runs on Linux, Windows
- Supports ACGs PCMCIA/CF Multi-Tag Readers
- Decodes the tag type, tag ID and manufacturer
- Displays tag memory in Hex and ASCII encoding
- Allows to write memory using Hex or ASCII editor
- NEW: Full 14443 a/b Support
- NEW: Support for Mifare sector keys
- NEW: Cookie feature using arbitrary cookie ID and automatically incrementing counter
- NEW: Brute-Force cracking of access control cards (sector keys)
- NEW: Audit of encrypted RFID tags check for "default" Shipping Keys
- NEW: Save and restore of Mifare Cards incl. Sector-Keys
- NEW: Multi baudrate reader support, RFDump can set boud rate
- NEW: Scan-Option
- NEW: Config-Menus
Supported Tag Types:
ISO 15693: Tag-it ISO, My-d, I-Code SLI, LRI512, TempSense
ISO 14443 A: Mifare Standard(1,2), Mifare UltraLight(1,2)
ISO 14443 B: SR176(1,2)
Tag-it
I-Code
Recommended Hardware:
Linux/Windows PC or HP iPAQ PDA with Linux
ACG Multi-Tag Reader, in a CF-Flash Socket or PCMCIA Adapter
13.56 MHz Tags for testing
Enhancements:
- Support was added for access control cards, ISO 14443 a/b.
- Support for brute force cracking of sector keys on encrypted rfid tags was added.
- Support for multi-baud rate readers was added.
- Support for cloning access cards was added.
- Minor bugs were fixed.
<<lessTest robustness of data-structures on the reader and the backend-application
Proof-of-concept manipulations of RFID tag contents
Clone / copy & paste User-Data stored on RFID tags
Audit tag-security features
Due to the overwhelming feedback we received since presenting RFDump at the Blackhat Conference 2004 in Las Vegas (check out the slides from our presentation) we are working on making his Web Site a portal for information exchange regarding RFID technology. The intention is to build a forum where all people interested or concerned about RFID technolgy can discuss and exchange their opinion in an open environment.
RFDump is a tool to detect RFID-Tags and show their meta information: Tag ID, Tag Type, manufacturer etc. The User-Data of a tag can be displayed and modified using either a Hex or an ASCII editor. In addition, the integrated cookie feature demonstrates how easy it is for a company to abuse RFID technology to spy on their customers. RFDump works with the ACG Multi-Tag Reader or similar card reader hardware.
Main features:
- Runs on Linux, Windows
- Supports ACGs PCMCIA/CF Multi-Tag Readers
- Decodes the tag type, tag ID and manufacturer
- Displays tag memory in Hex and ASCII encoding
- Allows to write memory using Hex or ASCII editor
- NEW: Full 14443 a/b Support
- NEW: Support for Mifare sector keys
- NEW: Cookie feature using arbitrary cookie ID and automatically incrementing counter
- NEW: Brute-Force cracking of access control cards (sector keys)
- NEW: Audit of encrypted RFID tags check for "default" Shipping Keys
- NEW: Save and restore of Mifare Cards incl. Sector-Keys
- NEW: Multi baudrate reader support, RFDump can set boud rate
- NEW: Scan-Option
- NEW: Config-Menus
Supported Tag Types:
ISO 15693: Tag-it ISO, My-d, I-Code SLI, LRI512, TempSense
ISO 14443 A: Mifare Standard(1,2), Mifare UltraLight(1,2)
ISO 14443 B: SR176(1,2)
Tag-it
I-Code
Recommended Hardware:
Linux/Windows PC or HP iPAQ PDA with Linux
ACG Multi-Tag Reader, in a CF-Flash Socket or PCMCIA Adapter
13.56 MHz Tags for testing
Enhancements:
- Support was added for access control cards, ISO 14443 a/b.
- Support for brute force cracking of sector keys on encrypted rfid tags was added.
- Support for multi-baud rate readers was added.
- Support for cloning access cards was added.
- Minor bugs were fixed.
Download (0.22MB)
Added: 2006-09-14 License: GPL (GNU General Public License) Price:
1162 downloads
The Ace Of Pinguins 1.2
The Ace of Penguins is a set of Unix/X solitaire games based on the ones available for Windows. more>>
The Ace of Penguins is a set of Unix/X solitaire games based on the ones available for Windows(tm) but with a number of enhancements that my wife says make my versions better.
The latest version includes clones of freecell, golf, mastermind, merlin, minesweeper, pegged, solitaire, taipei (with editor!), and thornq (by Martin Thornquist).
Installation:
To install the binaries tar, do this as user root (other platforms are similar):
cd /usr/bin/X11
tar xvfz /tmp/ace-1.2.linux.tar.gz
tar cf - libcards.so* | (cd /usr/local/lib ; tar xf -)
rm libcards.so*
You will need to run ldconfig to notice the new shared libraries.
Then you can open a new shell window and type the name of the program you want at the command line to run it.
<<lessThe latest version includes clones of freecell, golf, mastermind, merlin, minesweeper, pegged, solitaire, taipei (with editor!), and thornq (by Martin Thornquist).
Installation:
To install the binaries tar, do this as user root (other platforms are similar):
cd /usr/bin/X11
tar xvfz /tmp/ace-1.2.linux.tar.gz
tar cf - libcards.so* | (cd /usr/local/lib ; tar xf -)
rm libcards.so*
You will need to run ldconfig to notice the new shared libraries.
Then you can open a new shell window and type the name of the program you want at the command line to run it.
Download (0.30MB)
Added: 2005-08-17 License: GPL (GNU General Public License) Price:
1529 downloads
retawq 0.2.6c
retawq is an interactive, multi-threaded network client (web browser) for text terminals on computers with Unix-like operating s more>>
retawq is an interactive, multi-threaded network client (web browser) for text terminals on computers with Unix-like operating systems. It is written in C, fast, small, nicely configurable, and comfortable; e.g. the low-level network communications are performed in a non-blocking way, and you can open many "virtual windows" as you want and work simultaneously in two of them in a split-screen mode.
Main features:
- multi-window - you can open as many "virtual windows" as you like and work simultaneously in two of them in a split-screen mode
- multi-view - you can view a long series of documents within each browser window and easily go back and forth
- internationalization (i18n) - optional support for several natural languages (currently English, French, German, Spanish, Brazilian Portuguese and Japanese); cf. the compile-time configuration option OPTION_I18N
- mouse - optional mouse support for higher comfort; cf. the compile-time configuration option OPTION_TEXTMODEMOUSE
- contextual menus - so you need not remember all those boring keyboard commands :-)
- sessions - you can save current sessions and resume them at any later time
- keymaps - for the flexible association of keys with program actions
- incremental display - content is displayed as soon as it is received from the server; you need not twiddle thumbs until the whole document (or a large portion of it) has been received
- resizable terminals - retawq tries to utilize the extents of your terminal optimally; and when you resize it, the visible documents are immediately re-layouted within the new boundaries (if the libraries on your computer support this); any terminal size from 30x10 to 250x250 characters (width x height) is supported.
- several interfaces - theres more than just a web browser: you can start the program in different runmodes, e.g. to download a file "in the background" or to get a shell-like FTP client
- configurability - many compile-time, command-line and run-time configuration options are provided; additionally, you can choose the classical-style Makefile or the more modern/portable configure script
- multi-threading - retawq optionally uses (moderate) multi-threading in order to make fast, responsive use possible
- network protocols - several access methods are supported: HTTP/1.1 and 1.0 (including proxies and cookies), https (ditto), FTP, ftps, news/NNTP, finger, local files and directories, local CGI scripts; cf. URL Schemes for more information; other protocols will follow
- HTML renderer - more than 60 tags are known; the form support is quite complete (except file upload); more than 130 character entities are known, many others can be guessed; preliminary (little) support for tables and framesets exists
- IPv6 - optional support for the "next generation" Internet Protocol version; cf. the compile-time configuration option OPTION_IPV6
- fast, small, portable and stable - a special emphasis is put on keeping the program very fast and small but making it comfortable, nicely configurable and standards-compliant nevertheless
- low requirements - runs nicely even on slow computers with little memory; also doesnt require much from its environment: only a standard C library with rather little functionality is needed, anything else can be either disabled or configured to use existing libraries or to fall back on built-in replacements
<<lessMain features:
- multi-window - you can open as many "virtual windows" as you like and work simultaneously in two of them in a split-screen mode
- multi-view - you can view a long series of documents within each browser window and easily go back and forth
- internationalization (i18n) - optional support for several natural languages (currently English, French, German, Spanish, Brazilian Portuguese and Japanese); cf. the compile-time configuration option OPTION_I18N
- mouse - optional mouse support for higher comfort; cf. the compile-time configuration option OPTION_TEXTMODEMOUSE
- contextual menus - so you need not remember all those boring keyboard commands :-)
- sessions - you can save current sessions and resume them at any later time
- keymaps - for the flexible association of keys with program actions
- incremental display - content is displayed as soon as it is received from the server; you need not twiddle thumbs until the whole document (or a large portion of it) has been received
- resizable terminals - retawq tries to utilize the extents of your terminal optimally; and when you resize it, the visible documents are immediately re-layouted within the new boundaries (if the libraries on your computer support this); any terminal size from 30x10 to 250x250 characters (width x height) is supported.
- several interfaces - theres more than just a web browser: you can start the program in different runmodes, e.g. to download a file "in the background" or to get a shell-like FTP client
- configurability - many compile-time, command-line and run-time configuration options are provided; additionally, you can choose the classical-style Makefile or the more modern/portable configure script
- multi-threading - retawq optionally uses (moderate) multi-threading in order to make fast, responsive use possible
- network protocols - several access methods are supported: HTTP/1.1 and 1.0 (including proxies and cookies), https (ditto), FTP, ftps, news/NNTP, finger, local files and directories, local CGI scripts; cf. URL Schemes for more information; other protocols will follow
- HTML renderer - more than 60 tags are known; the form support is quite complete (except file upload); more than 130 character entities are known, many others can be guessed; preliminary (little) support for tables and framesets exists
- IPv6 - optional support for the "next generation" Internet Protocol version; cf. the compile-time configuration option OPTION_IPV6
- fast, small, portable and stable - a special emphasis is put on keeping the program very fast and small but making it comfortable, nicely configurable and standards-compliant nevertheless
- low requirements - runs nicely even on slow computers with little memory; also doesnt require much from its environment: only a standard C library with rather little functionality is needed, anything else can be either disabled or configured to use existing libraries or to fall back on built-in replacements
Download (0.384MB)
Added: 2006-06-15 License: GPL (GNU General Public License) Price:
1229 downloads
CSS::SAC::ConditionFactory 0.06
CSS::SAC::ConditionFactory Perl module contains the default ConditionFactory. more>>
CSS::SAC::ConditionFactory Perl module contains the default ConditionFactory.
SYNOPSIS
my $cf = CSS::SAC::ConditionFactory->new;
my $cond1 = $cf->create_foo_condition;
my $cond2 = $cf->create_bar_condition;
This is the default ConditionFactory for CSS::SAC. It creates conditions of all types defined in SAC. You may wish to subclass or replace the default ConditionFactory in order to get your own condition objects.
I plan on adding more flexibility to this factory so that one could tell it the classes to use for various conditions, that would avoid enforcing subclassing/recoding for people that only want to replace a family of factory methods.
I know that some of the method names are quite lengthy, but given the great number of possible conditions it helps to have descriptive names.
METHODS
These define the interface that must be adhered to by ConditionFactories. The Java names (given in parens) work too, though the Perl ones are recommended.
CSS::SAC::ConditionFactory->new or $cf->new
Creates a new condition factory object.
$cf->create_and_condition($first,$second) (createAndCondition)
creates a combinator condition of type and
$cf->create_attribute_condition($lname,$ns,$specified,$value) (createAttributeCondition)
creates an attr condition
$cf->create_begin_hyphen_attribute_condition($lname,$ns,$specified,$value) (createBeginHyphenAttributeCondition)
creates a attr condition of type bh
$cf->create_class_condition($ns,$value) (createClassCondition)
creates a attr condition of type class
$cf->create_content_condition($data) (createContentCondition)
creates a content condition
$cf->create_id_condition($value) (createIdCondition)
creates a attr condition of type id
$cf->create_lang_condition($lang) (createLangCondition)
creates a lang condition
$cf->create_negative_condition($cond) (createNegativeCondition)
creates a negative condition
$cf->create_one_of_attribute_condition($lname,$ns,$specified,$value) (createOneOfAttributeCondition)
creates a attr condition of type id
$cf->create_only_child_condition() (createOnlyChildCondition)
creates a only-child condition
$cf->create_only_type_condition() (createOnlyTypeCondition)
creates a only-type condition
$cf->create_or_condition($first,$second) (createOrCondition)
creates a combinator condition of type or
$cf->create_positional_condition($position,$type_node,$same_type) (createPositionalCondition)
creates a positional condition
$cf->create_pseudo_class_condition($ns,$value) (createPseudoClassCondition)
creates a attr condition of type pseudo class
<<lessSYNOPSIS
my $cf = CSS::SAC::ConditionFactory->new;
my $cond1 = $cf->create_foo_condition;
my $cond2 = $cf->create_bar_condition;
This is the default ConditionFactory for CSS::SAC. It creates conditions of all types defined in SAC. You may wish to subclass or replace the default ConditionFactory in order to get your own condition objects.
I plan on adding more flexibility to this factory so that one could tell it the classes to use for various conditions, that would avoid enforcing subclassing/recoding for people that only want to replace a family of factory methods.
I know that some of the method names are quite lengthy, but given the great number of possible conditions it helps to have descriptive names.
METHODS
These define the interface that must be adhered to by ConditionFactories. The Java names (given in parens) work too, though the Perl ones are recommended.
CSS::SAC::ConditionFactory->new or $cf->new
Creates a new condition factory object.
$cf->create_and_condition($first,$second) (createAndCondition)
creates a combinator condition of type and
$cf->create_attribute_condition($lname,$ns,$specified,$value) (createAttributeCondition)
creates an attr condition
$cf->create_begin_hyphen_attribute_condition($lname,$ns,$specified,$value) (createBeginHyphenAttributeCondition)
creates a attr condition of type bh
$cf->create_class_condition($ns,$value) (createClassCondition)
creates a attr condition of type class
$cf->create_content_condition($data) (createContentCondition)
creates a content condition
$cf->create_id_condition($value) (createIdCondition)
creates a attr condition of type id
$cf->create_lang_condition($lang) (createLangCondition)
creates a lang condition
$cf->create_negative_condition($cond) (createNegativeCondition)
creates a negative condition
$cf->create_one_of_attribute_condition($lname,$ns,$specified,$value) (createOneOfAttributeCondition)
creates a attr condition of type id
$cf->create_only_child_condition() (createOnlyChildCondition)
creates a only-child condition
$cf->create_only_type_condition() (createOnlyTypeCondition)
creates a only-type condition
$cf->create_or_condition($first,$second) (createOrCondition)
creates a combinator condition of type or
$cf->create_positional_condition($position,$type_node,$same_type) (createPositionalCondition)
creates a positional condition
$cf->create_pseudo_class_condition($ns,$value) (createPseudoClassCondition)
creates a attr condition of type pseudo class
Download (0.037MB)
Added: 2007-06-20 License: Perl Artistic License Price:
856 downloads
multican 0.0.4
multican is a Canon EOS class camera remote control utility. more>>
multican is a Canon EOS class camera remote control utility.
multican is able to remote control 300D, 350D, 30D, 20D, and 5D cameras and can be scripted to control up to six attached cameras.
Which functions are supported?
Several remote control functions are available in scripts, they are:
- setting shutter release speed (Tv)
- setting aperture size (Av)
- setting ISO sensitivity
- releasing shutter (currently only allows to store the image on CF)
Known Bugs:
The timing in the script strongly depends on the camera type and CF card which is used to do shooting. This is to be tested by multican user himself. If too short times are described in the script, the communication may hang, may skip some commands. Thanks to camera image caching, the shooting rate could be set under 1s if only several images are takes since the most of the EOS camera models contains an image cache, so that the images are stored into a queue and written to the CF lately.
The known bug in this multican release is that cameras need to be switched off and on again when a scripted sequence is finished and a new one is to be done. This is likely caused by the fact that the communication is not correcly terminated in the actual multicam release.
Enhancements:
- fix typos, update docs
- fix warnings
<<lessmultican is able to remote control 300D, 350D, 30D, 20D, and 5D cameras and can be scripted to control up to six attached cameras.
Which functions are supported?
Several remote control functions are available in scripts, they are:
- setting shutter release speed (Tv)
- setting aperture size (Av)
- setting ISO sensitivity
- releasing shutter (currently only allows to store the image on CF)
Known Bugs:
The timing in the script strongly depends on the camera type and CF card which is used to do shooting. This is to be tested by multican user himself. If too short times are described in the script, the communication may hang, may skip some commands. Thanks to camera image caching, the shooting rate could be set under 1s if only several images are takes since the most of the EOS camera models contains an image cache, so that the images are stored into a queue and written to the CF lately.
The known bug in this multican release is that cameras need to be switched off and on again when a scripted sequence is finished and a new one is to be done. This is likely caused by the fact that the communication is not correcly terminated in the actual multicam release.
Enhancements:
- fix typos, update docs
- fix warnings
Download (0.020MB)
Added: 2006-11-07 License: GPL (GNU General Public License) Price:
1084 downloads
ACL Policy Daemon for Postfix 0.60
ACL Policy Daemon is a program that communicates with the Postfix MTA using the Policy Delegation Protocol implementing an ACL. more>>
ACL Policy Daemon is a program that communicates with the Postfix MTA using the Policy Delegation Protocol implementing an ACL (Access Control List) system, making very easy to improve and create nice controls on your e-mail traffic. You can use it to verify SPF records to.
The project is developed using Python and has no other dependencies and licensed by GPL version 2.
The rules are loaded from a regular text file. It is planned to load the rules from a SQL database or LDAP directory in the future.
Greylisting functionality will be implemented soon.
For news and updated information about ACL Policy Daemon, you can always check the project page at GNA: https://gna.org/projects/apolicy/
Installation:
You must have Python installed, version 2.3 or above. Run python to check:
miguel@debian:~$ python
Python 2.4.4c0 (#2, Jul 30 2006, 15:43:58)
[GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
It is very easy to install apolicy. In some distributions, Postfixs daemons are located in /usr/libexec/postfix, check your distribution.
The following commands should do just fine, you must be root:
debian:~# tar zcf apolicy-0.3.tar.gz
debian:~# cp apolicy-0.3/src/apolicy.py /usr/lib/postfix/
debian:~# chmod 755 /usr/lib/postfix/apolicy.py
debian:~# mkdir /etc/apolicy/
debian:~# cp apolicy.conf /etc/apolicy/
debian:~# chmod 644 /etc/apolicy/apolicy.conf
debian:~# echo "apolicy unix - n n - - spawn" >> /etc/postfix/master.cf
debian:~# echo " user=nobody argv=/usr/lib/postfix/apolicy.py" >> /etc/postfix/master.cf
The apolicy.conf is a sample file with examples, you must edit it to fit your needs.
Install the complementary modules for apolicy. We will install 3 packages: apolicy, pyspf and pydns. Note that the directory that contains Python libraries is not the same on all operating systems. Sometimes it is inside /usr/lib or /usr/libexec, and may be named python or python< version >:
debian:~# mkdir /usr/lib/ /site-packages/apolicy
debian:~# mkdir /usr/lib/ /site-packages/spf
debian:~# mkdir /usr/lib/ /site-packages/DNS
debian:~# cp apolicy-0.3/src/apolicy/* /usr/lib/ /site-packages/apolicy
debian:~# cp apolicy-0.3/src/spf/* /usr/lib/ /site-packages/spf
debian:~# cp apolicy-0.3/src/DNS/* /usr/lib/ /site-packages/DNS
debian:~# echo apolicy > /usr/lib/ /site-packages/apolicy.pth
debian:~# echo spf > /usr/lib/ /site-packages/spf.pth
debian:~# echo DNS > /usr/lib/ /site-packages/DNS.pth
Before setting Postfix, it is wise to test apolicy and check if everything is right. The configuration file is loaded by default from /etc/apolicy/apolicy.conf, you can use -c parameter to change to point where your configuration file is. It is possible to debug your configuration using the parameter -d, it will send a lot of output to syslog mail facility:
debian:~# /usr/lib/postfix/apolicy.py -d
The program must keep running and waiting input from stdin. Take a look at mail.log for any problem. You can press ctrl+c to finish it. If no errors happened, then lets move forward.
Finally, add to your main.cf:
smtpd_recipient_restrictions =
reject_unlisted_recipient
...
reject_unauth_destination
check_policy_service unix:private/apolicy
For the size acl works, apolicy need to be called this way:
smtpd_end_of_data_restrictions = check_policy_service unix:private/apolicy
<<lessThe project is developed using Python and has no other dependencies and licensed by GPL version 2.
The rules are loaded from a regular text file. It is planned to load the rules from a SQL database or LDAP directory in the future.
Greylisting functionality will be implemented soon.
For news and updated information about ACL Policy Daemon, you can always check the project page at GNA: https://gna.org/projects/apolicy/
Installation:
You must have Python installed, version 2.3 or above. Run python to check:
miguel@debian:~$ python
Python 2.4.4c0 (#2, Jul 30 2006, 15:43:58)
[GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
It is very easy to install apolicy. In some distributions, Postfixs daemons are located in /usr/libexec/postfix, check your distribution.
The following commands should do just fine, you must be root:
debian:~# tar zcf apolicy-0.3.tar.gz
debian:~# cp apolicy-0.3/src/apolicy.py /usr/lib/postfix/
debian:~# chmod 755 /usr/lib/postfix/apolicy.py
debian:~# mkdir /etc/apolicy/
debian:~# cp apolicy.conf /etc/apolicy/
debian:~# chmod 644 /etc/apolicy/apolicy.conf
debian:~# echo "apolicy unix - n n - - spawn" >> /etc/postfix/master.cf
debian:~# echo " user=nobody argv=/usr/lib/postfix/apolicy.py" >> /etc/postfix/master.cf
The apolicy.conf is a sample file with examples, you must edit it to fit your needs.
Install the complementary modules for apolicy. We will install 3 packages: apolicy, pyspf and pydns. Note that the directory that contains Python libraries is not the same on all operating systems. Sometimes it is inside /usr/lib or /usr/libexec, and may be named python or python< version >:
debian:~# mkdir /usr/lib/ /site-packages/apolicy
debian:~# mkdir /usr/lib/ /site-packages/spf
debian:~# mkdir /usr/lib/ /site-packages/DNS
debian:~# cp apolicy-0.3/src/apolicy/* /usr/lib/ /site-packages/apolicy
debian:~# cp apolicy-0.3/src/spf/* /usr/lib/ /site-packages/spf
debian:~# cp apolicy-0.3/src/DNS/* /usr/lib/ /site-packages/DNS
debian:~# echo apolicy > /usr/lib/ /site-packages/apolicy.pth
debian:~# echo spf > /usr/lib/ /site-packages/spf.pth
debian:~# echo DNS > /usr/lib/ /site-packages/DNS.pth
Before setting Postfix, it is wise to test apolicy and check if everything is right. The configuration file is loaded by default from /etc/apolicy/apolicy.conf, you can use -c parameter to change to point where your configuration file is. It is possible to debug your configuration using the parameter -d, it will send a lot of output to syslog mail facility:
debian:~# /usr/lib/postfix/apolicy.py -d
The program must keep running and waiting input from stdin. Take a look at mail.log for any problem. You can press ctrl+c to finish it. If no errors happened, then lets move forward.
Finally, add to your main.cf:
smtpd_recipient_restrictions =
reject_unlisted_recipient
...
reject_unauth_destination
check_policy_service unix:private/apolicy
For the size acl works, apolicy need to be called this way:
smtpd_end_of_data_restrictions = check_policy_service unix:private/apolicy
Download (0.034MB)
Added: 2006-12-27 License: GPL (GNU General Public License) Price:
1032 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above cf search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
