Free cryptography api software for linux

The Legion of the Bouncy Castle Java Cryptography API provides a lightweight cryptography API in Java. A provider for the JCE and JCA, a clean-room implementation of the JCE 1.2.1, generators for Version 1 and Version 3 X.509 certificates, generators for Version 2 X.509 attribute certificates, PKCS12 support, and APIs for dealing with S/MIME, CMS, OCSP, TSP, and OpenPGP. Versions are provided for the J2ME, and JDK 1.0-1.5.
Main features:
- A lightweight cryptography API in Java.
- A provider for the JCE and JCA.
- A clean room implementation of the JCE 1.2.1.
- A library for reading and writing encoded ASN.1 objects.
- Generators for Version 1 and Version 3 X.509 certificates, Version 2 CRLs, and PKCS12 files.
- Generators for Version 2 X.509 attribute certificates.
- Generators/Processors for S/MIME and CMS (PKCS7).
- Generators/Processors for OCSP (RFC 2560).
- Generators/Processors for TSP (RFC 3161).
- Generators/Processors for OpenPGP (RFC 2440).
- A signed jar version suitable for JDK 1.4/1.5 and the Sun JCE.

libbasiccard is a library to access BasicCards (programmable smart cards). It closely follows the official APIs defined by ZeitControl (Cri, Bci, and zccrypt), extending them where needed. The project also includes support for the MultiApplication BasicCard and the BasicCard cryptography functions.
Enhancements:
- A port of the BasicCard cryptographic API (zccrypt) in the form of a new library called libbccrypto was added (elliptic curve cryptography support is available on request.)
- Support for all the commands of the MultiApplication BasicCard was added.

CryptoServer is OpenSource Server-side cryptography tool and run as daemon.

It is already tested in very busy environment and can support over one million transaction an hour.

CryptoServer accept the GPL License and can use it for any purpose as is.

RSA-Haskell is a collection of command-line cryptography tools and a cryptography library written in Haskell. The project is intended to be useful to anyone who wants to secure files or communications or who wants to incorporate cryptography in their Haskell application.
The libraries include Haskell implementations of SHA1, EME-OAEP, EMSA-PSS, MGF, RSAES-OAEP, and RSA-PSS. These standards implement signature/verification, strong cryptography, and hashing.
Enhancements:
- Documentation is now available for the command line utilities.
- An easy-to-use Windows binary release is available.

WWW::Facebook::API::REST::Client::Events is a Perl module with events for Client.

SYNOPSIS

use WWW::Facebook::API::REST::Client;

Methods for accessing events with WWW::Facebook::API::REST::Client

SUBROUTINES/METHODS

base

The WWW::Facebook::API::REST::Client::Base object to use to make calls to the REST server

get_in_window

The events.getInWindow method of the Facebook API

DIAGNOSTICS

This module is used by WWW::Facebook::API::REST::Client and right now does not have any unique error messages.

Gtk2::api is a mapping the Gtk+ C API to perl.

ABSTRACT
The Gtk2 module attempts to stick as close as is reasonable to the C API, to minimize the need to maintain documentation which is nearly a copy of the C API reference documentation. However, the world is not perfect, and the mappings between C and perl are not as clean and predictable as you might wish. Thus, this page described the basics of how to map the C API to the perl API, and lists various points in the API which follow neither the C API documentation nor the mapping principles.

The canonical documentation is the C API reference at http://developer.gnome.org/doc/API/gtk/ and http://developer.gnome.org/doc/API/gdk/
There are two main sections: BINDING BASICS describes the principles on which the bindings work; understanding these can lead you to guess the proper syntax to use for any given function described in the C API reference.

The second section lists various specific points of difference which dont necessarily correspond with what you expect; this section is in three main parts: missing methods, renamed methods, and different call signatures.

eBay::API is a Perl SDK for eBay Web services Interface.

SYNOPSIS

# 1. GeteBayOfficialTime use eBay::API::XML::Call::GeteBayOfficialTime;
my $pCall = eBay::API::XML::Call::GeteBayOfficialTime->new();
$pCall->execute();
my $sOfficialTime = $pCall->getEBayOfficialTime();
# 2. GetUser use eBay::API::XML::Call::GetUser; use eBay::API::XML::DataType::Enum::DetailLevelCodeType;
my $pCall = eBay::API::XML::Call::GetUser->new();
$pCall->setDetailLevel( [eBay::API::XML::DataType::Enum::DetailLevelCodeType::ReturnAll] );
$pCall->setUserID(userId);
$pCall->execute();

my $pUser = $pCall->getUser();
my $sStatusCode = $pUser->getStatus();
my $sSiteCode = $pUser->getSite();
# 3. VerifyAddItem use eBay::API::XML::Call::VerifyAddItem; use eBay::API::XML::DataType::ItemType; use eBay::API::XML::DataType::CategoryType; use eBay::API::XML::DataType::Enum::CountryCodeType; use eBay::API::XML::DataType::Enum::CurrencyCodeType; use eBay::API::XML::DataType::Enum::ListingTypeCodeType; use eBay::API::XML::DataType::Enum::BuyerPaymentMethodCodeType;
my $pItem = eBay::API::XML::DataType::ItemType->new();
$pItem->setCountry(eBay::API::XML::DataType::Enum::CountryCodeType::US);
$pItem->setCurrency(eBay::API::XML::DataType::Enum::CurrencyCodeType::USD);
$pItem->setDescription(item description.);
$pItem->setListingDuration(eBay::API::XML::DataType::Enum::ListingTypeCodeType::Days_1);
$pItem->setLocation(San Jose, CA);
$pItem->setPaymentMethods(eBay::API::XML::DataType::Enum::BuyerPaymentMethodCodeType::PaymentSeeDescription);
$pItem->setQuantity(1);
$pItem->getStartPrice()->setValue(1.0);
$pItem->setTitle(item title);

my $pCat = eBay::API::XML::DataType::CategoryType->new();
$pCat->setCategoryID(357);
$pItem->setPrimaryCategory($pCat);

my $pCall = eBay::API::XML::Call::VerifyAddItem->new();

$pCall->setItem($pItem);
$pCall->execute();

$sItemId = $pCall->getItemID()->getValue();