Free elliptic curve cryptography 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.

seccure toolset implements a selection of asymmetric algorithms based on elliptic curve cryptography (ECC). In particular it offers public key encryption / decryption and signature generation / verification.
ECC schemes offer a much better key size to security ratio than classical systems (RSA, DSA). Keys are short enough to make direct specification of keys on the command line possible (sometimes this is more convenient than the management of PGP-like key rings).
seccure builds on this feature and therefore is the tool of choice whenever lightweight asymmetric cryptography -- independent of key servers, revocation certificates, the Web of Trust or even configuration files -- is required.
Where can I download seccure?
seccure is GPL software. First download seccure from the following link. Then, after having made sure that libgcrypt is properly installed, run make and make install as usual.
How is seccure used?
First we give an example for key generation:
$ seccure-key
Assuming curve p160.
Enter private key: my private key
The public key is: 8W;>i^H0qi|J&$coR5MFpR*Vn
Then we do some public key encryption / decryption:
$ seccure-encrypt -o private.msg 8W;>i^H0qi|J&$coR5MFpR*Vn
Assuming MAC length of 80 bits.
Go ahead and type your message ...
This is a very very secret message!
^D
$ seccure-decrypt -i private.msg
Assuming MAC length of 80 bits.
Assuming curve p160.
Enter private key: my private key
This is a very very secret message!
Integrity check successful, message unforged!
At last we try out the signature generation / verification:
$ seccure-sign
Assuming curve p160.
Enter private key: my private key
Go ahead and type your message ...
This message will be signed
^D
Signature: !JI1%Luh6mu:@)S3wS.go(u1z,b.NhXIUI)/p@$*ONA+)+G}}_
$ seccure-verify 8W;>i^H0qi|J&$coR5MFpR*Vn !JI1%Luh6mu:@)S3wS.go(u1z,b.NhXIUI)/p@$*ONA+)+G}}_
Go ahead and type your message ...
This message will be signed
^D
Signature successfully verified!
Enhancements:
- This release adds signcryption and inline signatures.

trfcrypt is an add-on package to the tcl-extension trf. It provides the encryption functionality which was removed from the base package to allow its inclusion on the Tcl/Tk CDROM without violating US export control laws on cryptography.
The C API is layered on top of the trf C API and provides a set of commands for the management, implementation and usage of blockciphers and stream.
Although it is possible to implement ciphers using only the trf C API the code in this package makes it much easier, as general things like the handling of blockcipher modes are done here, thus obviating the need to reimplement them every time. A new cipher just has to provide some information about itself (key sizes) and functions to:
- generate the internal keyschedule from the specified key
- encrypt/decrypt a character or a block of data

FlexiCrypt is a universal cryptography toolkit for managing certificates and symmetric keys. FlexiCrypt can perform many kinds of encryption, decryption, signing, and several related tasks.
Main features:
- key managing (asymmetric and symmetric)
- generate certificates
- symmetric encryption
- asymmetric encryption
- hybrid encryption
- decryption
- XML-signatures
- message digest computation
- secure file deletion (wipe files)
- performance comparison

Fast Secure File System exports existing directories securely over the network, letting users store and retrieve encrypted data in a scalable and transparent way. FSFS is written in C and works on GNU/Linux systems on x86 and PPC architectures, with help from FUSE and OpenSSL.
File systems are easily the most evident, from the point of view of users, component of an operating system. Through file systems it is possible to organize data in a wide variety of ways, and access resources through a common interface.
Users can nowadays not only store and retrieve documents, but also find information on running processes and system settings (through ProcFS), access and manipulate e-mail (for example with GmailFS), or perform several other operations.
In several circumstances and scenarios it is desirable to protect stored files and directories from manipulation by unknown or malicious users: financial or health-related data, confidential documents, or any kind of personal or sensitive data may need to be stored securely, in such a way that it can not be examined or modified freely by third parties.
Most file systems do not take action in this sense, and external cryptographic utilities are sometimes employed to secure data before storage. While this can be a perfectly secure solution, it is not transparent to users.
Distributed file systems propose efficient ways of accessing data remotely as if it resided on the local machine; when it comes to dealing with securely stored data as in the examples above, care must be taken to preserve confidentiality and integrity also during network transfer.
Not all distributed file systems accomplish this task, weakening the overall security of the system, or do so inefficiently, making it inconvenient for users.
FSFS is a secure, distributed file system in users space, written in C with much help from FUSE and OpenSSL. It lets users store and retrieve data securely and transparently, knowing that it is protected both on permanent storage devices and while in transit over the network.
It is also concerned with scalability, therefore separates data cryptography from the server, leaving it to the clients; this approach is similar to the one used in CFS, and opposite to those taken on by other secure file system solutions (like NFS on top of IPsec).
FSFS is written as a pair of user space daemons that act as client and server. Because of this, it needs no kernel support (unlike NFS over IPsec), save the FUSE loadable kernel module on clients, included in Linux since 2.6.14; servers dont use FUSE and depend only on user space OpenSSL libraries.
Servers export an existing file system (of virtually any kind) to clients over the network through two separate channels: a TLS connection set up with OpenSSL, and a clear channel. Requests from the clients to the servers are sent via the TLS socket, thus they are encrypted and authenticated, according to TLS v1 specifications, by the channel itself and decrypted on receipt, as they are usually very short and the relevant cryptography does not constitute a great overhead; simple server replies undergo the same process.
Cryptography in this case happens at both ends of the transmission.
In a distributed file system, large amounts of data may be transferred between clients and servers, thus encrypting and decrypting everything may become too cumbersome for both parties, and as more clients are added to the system the server may severely lose performance; moreover, file data should be stored encrypted anyway, so the cryptography could be moved to the clients, in such a way that each encrypts data before a write operation sends it over the network to the server, and decrypts it after a read retrieves it.
This way servers only deal with TLS details and can concentrate on serving client requests by doing the relevant I/O on the underlying, "physical" file system. As the data is already encrypted, it does not need to go through the TLS channel and the corresponding overhead, but can be sent via the clear channel, provided the messages are authenticated.
Enhancements:
- This release fixes two bugs. One bug related to socket creation and would cause problems on some systems (namely OpenSUSE 10.2). The other bug related to server configuration creation when using the Python configuration utilities. Users dont need to upgrade to this release if theyre not experiencing problems or are not using the Python configuration utilities.

Self-certifying File System provides a secure, global network file system with decentralized control.

SFS is a secure, global network file system with completely decentralized control. SFS lets you access your files from anywhere and share them with anyone, anywhere.

Anyone can set up an SFS server, and any user can access any server from any client.

At the same time, SFS uses strong cryptography to provide security over untrusted networks.

Thus, you can safely share files across administrative realms without involving administrators or certification authorities.

TaoCrypt project is a portable, fast, cryptographic library for most needs.
Main features:
- one way hash functions: SHA-1, MD2, MD4, MD5, RIPEMD-160;
- message authentication codes: HMAC;
- block ciphers: DES, Triple-DES, AES, Blowfish, Twofish;
- stream ciphers: ARC4;
- public key cryptography: RSA, DSA, Diffie-Hellman;
- password based key derivation: PBKDF2 from PKCS #5;
- a pseudo random number generator and large integer support.
There is also support for Base 16/64 encoding/decoding, DER encoding/decoding, and X.509 processing.
To build:
./configure
make
To test the build, from the ./test directory run ./test
Enhancements:
- This release includes bugfixes, portability enhancements, and some optimizations.