Free gmac rfc software for linux

This Tcl script may be used to extract MIB, PIB and ASN.1 modules from an RFC document.

Unlike most extractors, this script is smart enough to recognize ASN.1-style comments prior to or within the module header, use of the "TagDefaults" part of the module header (not used by MIB modules), module headers that are broken across multiple lines, and macros.

SAP::Rfc is a Perl module that contains RFC Function calls against an SAP R/3 System.

SYNOPSIS

# WARNING - as of SAP::Rfc 1.40 USER and PASSWD are case sensitive ready for
# R3 7.x
use SAP::Rfc;
$rfc = new SAP::Rfc(
ASHOST => myhost,
USER => ME,
PASSWD => secret,
LANG => EN,
CLIENT => 200,
SYSNR => 00,
TRACE => 1 );

my $it = $rfc->discover("RFC_READ_TABLE");

$it->QUERY_TABLE(TRDIR);
$it->ROWCOUNT( 2000 );
$it->OPTIONS( ["NAME LIKE RS%"] );

# or pass a list of hash refs like so:
$it->OPTIONS( [ { TEXT => "NAME LIKE RS%" } ] );

$rfc->callrfc( $it );

print "NO. PROGS: ".$it->tab(DATA)->rowCount()." n";
print join("n",( $it->DATA ));

$rfc->close();

SAP::Rfc - is a Perl extension for performing RFC Function calls against an SAP R/3 System. Please refer to the README file found with this distribution. This Distribution also allows the creation of registered RFCs so that an SAP system can call arbitrary Perl code created in assigned callbacks.

The best way to describe this package is to give a brief over view, and then launch into several examples. The SAP::Rfc package works in concert with several other packages that also come with same distribution, these are SAP::Iface, SAP::Parm, SAP::Tab, and SAP::Struc. These come together to give you an object oriented programming interface to performing RFC function calls to SAP from a UNIX based platform with your favourite programming language - Perl. A SAP::Rfc object holds together one ( and only one ) connection to an SAP system at a time. The SAP::Rfc object can hold one or many SAP::Iface objects, each of which equate to the definition of an RFC Function in SAP ( trans SE37 ). Each SAP::Iface object holds one or many SAP::Parm, and/or SAP::Tab objects, corresponding to the RFC Interface definition in SAP ( SE37 ).

For all SAP::Tab objects, and for complex SAP::Parm objects, a SAP::Struc object can be defined. This equates to a structure definition in the data dictionary ( SE11 ). Because the manual definition of interfaces and structures is a boring and tiresome exercise, there are specific methods provided to automatically discover, and add the appropriate interface definitions for an RFC Function module to the SAP::Rfc object ( see methods discover, and structure of SAP::Rfc ).

Please note that USER and PASSWD are now case sensitive - this change has the potential to break backward compatibility.

RFC (Remote Filesystem Checker) is a set of scripts that aims to help System-Administrators run a filesystem-checker (like tripwire, aide and so on...) from a "master-node" to several "slave-nodes" using ssh, scp, sudo and few other common shell commands.
Main features:
- crate/update FileSystem-Checkers (FSC) database
- execute FSC and create a log-report
- allow parallel execution, mass-check and mass-upgrade!
- support non-interactive operations
- use scp/ssh for all connections
- use an arbitrary port for ssh/scp connections (may be different for each host!)
- send (ONE) email to administrator(s)
- rotate logs, databases and other files
- support for AFICK, AIDE and INTEGRIT FileSystem-Checkers
- check users creation/removal
- check group creation/removal
- check if someone changes UID, GID or shell
- check for groups members or ID changes
- check for SUID/SGID on remote host via a separate PERL script
- check if remote-host is up before run checks on it (via nmap)
- kill the processes that take too long (you can set an arbitrary timeout value)

babel-ircd is a small IRC server aimed for small communities. It supports a subset of RFC1459.
It extends the RFC by providing automatic encoding translation. The project only works in stand-alone on one server.
Exemple of lacks : modes (like operator)
new server command : /encoding
- /encoding iso-8859-1 set the encoding of the client to iso 8859-1. The server then convert all the message from and to this client to the right encoding. With this several clients can have different encoding and see their accents. All encoding provided by iconv are available
- /encoding list returns the list of supported encodings
- /encoding shows the current encoding
This software is under the GPLv2 License.
Enhancements:
- Tested with: xchat gaim ChatZilla Zircon KSirc LostIrc ircII BitchX tirc epic4 TinyIRC

libmhash is a free library which provides a uniform interface to a large number of hash algorithms. These algorithms can be used to compute checksums, message digests, and other signatures.
The HMAC support implements the basics for message authentication, following RFC 2104. In the later versions some key generation algorithms, which use hash algorithms, have been added.
At the time of writing this, the library supports the algorithms:
SHA1, SHA160, SHA192, SHA224, SHA384, SHA512, HAVAL128, HAVAL160, HAVAL192, HAVAL224, HAVAL256, RIPEMD128, RIPEMD256, RIPEMD320, MD4, MD5, TIGER, TIGER128, TIGER160, ALDER32, CRC32, CRC32b, WHIRLPOOL, GOST, SNEFRU128, SNEFRU256.
Enhancements:
- A SIGBUS bug was fixed for unaligned data.

IMAPEngine provides an IMAP server which retrieves via POP3 and organizes mail in a database.
IMAPEngine is an IMAP server that uses a tdbengine database structure to store all accounts, messages, and mailboxes. This means it has nearly no limits in numbers, sizes, and performance, and it uses indexes to sort/find its data.
IMAPEngine is IMAP4Rev1 compatible and also has built-in support for the ACL, ID, IDLE, and UIDPLUS extensions. It is not (yet) an MTA, but it retrieves incoming messages from different POP3 servers. An simple integrated Web interface makes account configuration easy.
Enhancements:
- corrected imapfetch.mod
- included easyserver web server and developed index.mod for web based account configuration
- created imapconfig.mod for basic account setup on command line (better use the web frontend!)
- code cleanups, restructuring and some performance tweaking
- improved the table structure: bodies are stored as BLOB now. This raises the download performance significantly on big emails (more than ~2 MB)
- added the UIDPLUS extension as defined in RFC 2359. Mozilla Mail can handle it properly
- free client dependend flags now can be used (e.g. "Junk" sign of Mozilla Mail)
- the LIST and LSUB commands are now processed as defined in the IMAP4Rev1
- smaller semaphore scopes to each command that writes to the db, so table locks use only the minimum amount of time they need
- added the NAMESPACE extension as defined in RFC 2342
- added the ACL extension as defined in RFC 2086 (the commands are all implemented, but the rights are not yet mentioned by the server)
- added the IDLE extension as defined in RFC 2177 (though not sending any information when idle!)
- added the ID extension as defined in RFC 2971

Email::Find allows you to find RFC 822 email addresses in plain text.

Email::Find is a module for finding a subset of RFC 822 email addresses in arbitrary text (see "CAVEATS"). The addresses it finds are not guaranteed to exist or even actually be email addresses at all (see "CAVEATS"), but they will be valid RFC 822 syntax.

Email::Find will perform some heuristics to avoid some of the more obvious red herrings and false addresses, but theres only so much which can be done without a human.

Finds email addresses in the text and executes callback registered.

The callback is given two arguments. The first is a Mail::Address object representing the address found. The second is the actual original email as found in the text. Whatever the callback returns will replace the original text.

XPertMailer is a PHP class to send encoded MIME-type email messages like text, HTML, HTML embedded images, attachments, etc., to client, localhost, or relay SMTP servers with optional authorisation.
The class functions are optimised to execute in a very small time and to be easy to use. This reduces the size of the code and the time required to write it.
Data sending is done according to RFC 821 and RFC 2821, and the message type is in compliance with RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049, and RFC 2822.
Enhancements:
- Added the clear attachments functionality