Free rfc software for linux

Vortex Library is a BEEP Core protocol implementation, following the standard definitions in RFC 3080 and RFC 3081.
Vortex Library has a clean and easy-to-use API that allows you to write new protocols or user applications.
Vortex Library has been developed within the Af-Arch project, and it is being used at the data transport layer. However, Vortex Library can be used independently of Af-Arch.
Currently Vortex Library is supported in all Microsoft Windows Platforms as well as Linux.
Enhancements:
- A general update was done to make this release more usable on Microsoft Windows, using Visual Studio compilers.
- Missing support was added to enable getting error codes reported by peer at channel creation.
- Now xml-rpc-gen is able to include user code into the IDL definition that is placed at the resulting XML-RPC server.

strongSwan is an OpenSource IPsec implementation for the Linux operating system. strongSwan is an OpenSource IPsec implementation for the Linux operating system.
In order to have a stable IPsec platform to base our future extensions of the X.509 capability on, we decided to lauch the strongSwan project.
Main features:
- runs both on Linux 2.4 (KLIPS) and Linux 2.6 (native IPsec) kernels
- strong 3DES, AES, Serpent, Twofish, or Blowfish encryption
- Authentication based on X.509 certificates or preshared keys
- Powerful IPsec policies based on wildcards or intermediate CAs
- Retrieval and local caching of Certificate Revocation Lists via HTTP or LDAP
- Full support of the Online Certificate Status Protocol (OCSP, RCF 2560).
- Optional storage of RSA private keys on smartcards or USB crypto tokens
- Smartcard access via standardized PKCS #11 interface
- PKCS #11 proxy function offering RSA decryption services via whack
- NAT-Traversal (RFC 3947) and support of Virtual IPs and IKE Mode Config
- CA management (OCSP and CRL URIs, default LDAP server)
- Dead Peer Detection (DPD, RFC 3706)
- Group policies based on X.509 attribute certificates ( RFC 3281)
- Generation of default self-signed certificates during strongSwan setup
Enhancements:
- Source routes installed by the keying daemons are now in a separate routing table with ID 100 in order to avoid conflicts with the main table.
- Route lookup for IKEv2 traffic is done in userspace to ignore routes installed for IPsec, as IKE traffic shouldnt get encapsulated.
- The ipsec starter has become more tolerant to dynamic DNS lookup failures by keeping the last valid IP address.

k5n Desktop Calendar (k5nCal, for short) application is a calendar application for your desktop. It shares features with applications like Apple iCal and Microsoft Outlook, but it is open source.
This project is built upon Java Calendar Tools, and all data is stored in RFC 2445 iCalendar format.
Main features:
- Supports Mac OS X, Linux or Windows (requires Java 1.5)
- Saves all entries in iCalendar RFC 2445 format
- Simple and intuitive user interface similar
- Open source license so you can download and modify the source and use it free of charge.

Cornfed SIP User Agent is a Session Initiation Protocol (SIP) based softphone for your IBM-compatible Personal Computer running the Linux operating system.
The Cornfed SIP User Agent allows you to make Internet phone calls using an Advanced Linux Sound Architecture (ALSA) or Open Sound System (OSS) sound card with speakers and microphone as your telephone handset.
Main features:
- Supports SIP (RFC 3261), SDP (RFC 2327), and RTP (RFCs 3550 and 3551)
- Automated detection of Residential Gateways using Network Address Translation (NAT)
- Supports Digest authentications for registrations and outbound INVITEs
- Support for loose proxy routing using Record-Route and Route headers
- Handles forking of outbound INVITEs by proxies
- Supports re-INVITEs for changes to media transport
- Supports G.711 mu-Law and a-Law voice codecs
- Supports RFC 2833 DTMF tone generation
- Supports SIP compact header forms
- Gnome GUI and CLI clients
- Multi-threaded implementation
The Cornfed SIP User Agent is provided free of charge for personal use for users of the Linux operating system. The program is provided as a binary distribution only. The Cornfed SIP User Agent is specifically designed with embedded and mobile wireless devices in mind.
Development is under way to bring this client to other platforms. If you are interested in licensing this technology for your commercial application, please contact Cornfed Systems at 410-404-8790.
Enhancements:
- Minor bug fixes.
- Changed readline functionality to used raw input rather than cooked mode.
- Fixed bugs with display of status messages that caused client to hang.
- Disabled removal of registration on client exit.

HTTP extension for PHP allows building absolute URIs, RFC-compliant HTTP redirects, RFC-compliant HTTP date handling, parsing of HTTP headers and messages, caching by "Last-Modified" and/or ETag (with an on the fly option for ETag generation from buffered output), sending data/files/streams with (multiple) ranges, negotiating user-preferred language/charset, and convenient request functionality built upon libcurl.
PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, and HttpMessage.
Main features:
- Building absolute URIs
- RFC compliant HTTP redirects
- RFC compliant HTTP date handling
- Parsing of HTTP headers and messages
- Caching by "Last-Modified" and/or ETag (with on the fly option for ETag generation from buffered output)
- Sending data/files/streams with (multiple) ranges support
- Negotiating user preferred language/charset
- Convenient request functionality built upon libcurl
- PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, HttpMessage.
Enhancements:
- This release fixes bug #11359: HttpMessage::toMessageTypeObject() does not populate POST fields.

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.

X500::DN is a Perl module that can handle X.500 DNs (Distinguished Names), parse and format them.

SYNOPSIS

use X500::DN;

my $dn = X500::DN->ParseRFC2253 (cn=John Doe, o=Acme, Inc., c=US) or die;
print $dn->getRFC2253String(), "n";

$dn = new X500::DN (new X500::RDN (c=>US), new X500::RDN (cn=>John Doe));
my $rdn0 = $dn->getRDN (0);
my $c = $rdn0->getAttributeValue (c);

NOTE

The RFC 2253 syntax is explicitely backwards in relation to the ASN.1 SEQUENCE.

So the RFC 2253 string cn=John Doe, c=US has the same meaning as the X.500 string c=US, cn=John Doe. The X500::DN objects keep the RDNs in X.500 order!

This module handles X.500 DNs (Distinguished Names). Currently, it parses DN strings formatted according to RFC 2253 syntax into an internal format and produces RFC 2253 formatted string from it.

Methods

$object = new X500::DN (rdn, rdn, ...);

Creates a DN object from zero or more arguments of type X500::RDN.

$object = X500::DN->ParseRFC2253 (cn=John Doe, o=Acme, Inc., c=US);

Creates a DN object from an RFC 2253 formatted DN string notation.

$object->getRFC2253String();

Returns the DN as a string formatted according to RFC 2253 syntax.

$object->getOpenSSLString();

Returns the DN as a string formatted suitable for openssl req -subj and openssl ca -subj.

$object->getX500String();

Returns the DN as a string formatted according to X.500 syntax. NOTE: This is a hack, there is no definition for a X.500 string syntax!

$object->hasMultivaluedRDNs();

Returns whether the DN contains multi-valued RDNs.

$object->getRDN (num);

Returns the DNs RDN at position num as an X500::RDN object. num starts with 0, which will return the first RDN in ASN.1 SEQUENCE order.

$object->getRDNs();

Returns the DNs RDNs, a list of objects of type X500::RDN, in ASN.1 SEQUENCE order.

b64 is a very small and simple library that provides Base-64 encoding and decoding, according to RFC-1113, in C and C++.
The b64 project is released under the BSD license, which basically means its free for any use, but you cant claim its yours.
Enhancements:
- The code was updated to be fully compatible with STLSoft 1.9.1 (the special version released on Extended STL, volume 1: CD).