Free distributed rsa key generation software for linux

Distributed RSA Key Generation is a software to generate shared RSA keys. Currently, only keys for two parties using Gilboas protocol are supported. But the protocol stack is extensible, so in the future there may be other protocols supported.

Work has begun on Straubs protocol but is not finished yet, multi-party protocols like Boneh-Franklins may also be added in the far future.

Distributed Aide Runtime Controller is a multi-threaded Python application designed for managing AIDE installations in large heterogeneous networks.
AIDE is an open-source improvement upon the academic release of Tripwire. It can be used to detect filesystem changes in unix environments, which is useful for forensics on compromised systems and tracing illicit system configuration changes.
Darc provides a mechanism to run AIDE integrity checks across many unix systems from a single management station. It has the following features not available in a traditional AIDE installation:
- Maintaining read-only media databases on each system - not a trivial task! - is not required for day to day operations.
- Unified reporting - the admin doesnt have to read individual reports for each system.
- Integrated syslog support to notify admins when a system may have been compromised.
- Databases and configs are never written to the filesystems on the monitored hosts.
Enhancements:
- Better error handling and reporting
- HTML reports for easier navigation within the report
- Configurable timeout values for all relevant metrics - TCP connection timeouts, SFTP transfer time, AIDE run time
- Built-in support for aide database maintenance tasks (init, update) so the manual file manipulation required in 0.2 is completely eliminated.

Distributed Concurrent Versioning System (DCVS) project extends the well-known version control system CVS and the file distribution and synchronization program CVSup with functionality to distribute CVS repositories with local lines of development and handle synchronization of the distributed repositories automatically in the background.
Development lines (branches) are owned by a repository server, repository servers efficiently update each other via CVSup, and CVS ensures correct server use on checkin and branch creation.
Enhancements:
- This release adds miscellaneous bugfixes and the security patches of CVS 1.12.13.
- There are now installation packages for Windows to be installed on Cygwin, for SUSE Linux 10, for FreeBSD 4, 5, and 6, and for Fedora Core 4.

Distributed FTP is a distributed FTP daemon written in java. Instead of usual and well-known serversclient transfer it uses masterclient for control connections and slaveclient for (most) data transfers, the master must tell the slave to initiate/respond to a transfer.

Distributed Checksum Clearinghouse, in short DCC, is a system of clients and servers that collect and count checksums related to mail messages. The counts can be used by SMTP servers and mail user agents to detect and reject bulk mail.
DCC servers can exchange common checksums. The checksums include values that are "fuzzy", or constant across common variations in bulk messages.
Enhancements:
- This release improves the dccifd per-user whitelist default.
- It fixes the server database size estimate.
- Old installations really should upgrade to get the MIME decoding fix.

Distributed Network John The Ripper is a client/server framework that wraps around a slightly modified version of John The Ripper.
In contrast to the MPI version of John, dnetj allows the use of nodes which are of differing speeds and for nodes which do not run 24/7.
This tool was written for a number of reasons, firstly the MPI version requires an MPI installation on each node, and for the nodes to be configured together and be roughly the same speed. Also, although other distributed password crackers exist (such as djohn or medussa) they all have their own limitations.
The server loads a set of password hashes, and splits the available keyspace into "work units" of a configurable size. The clients connect and retrieve the hashes, as well as a set of work units to process. Once a client has processed some work units, it connects back to the server to submit the completed units as well as any passwords which have been cracked.
Possible uses include eg, running as a background task on all the workstations in an office.
Note, this tool is at an early stage of development and is likely to be very buggy, although it is functional. Bug reports and/or patches are strongly encouraged.
Main features:
- Distributed client/server model, any number of clients can be supported and can be brought up and down at will
- Support for any cipher supported by John 1.7.2 (additional cipher patches should be able to be applied normally)
- Keep the changes to John to a minimum, so that patches/updates can still be applied without too much fuss
- Uses the same optimized encryption routines as John
- Cracked hashes are stored in the standard john.pot format, so they can be displayed with john -show
- Passwd files sent to clients are sanitised (only the hash is sent, other fields from the passwd file are removed)
- Capability for auto client registration
- Code is intentionally kept clean to aid porting
Supported Platforms
Dnetj has been tested on the following systems:
- Linux/x86
- Linux/amd64
- Linux/sparc
- MacOSX/PPC
- MacOSX/Intel
- Solaris/x86
Version restrictions:
- Clients will sometimes crash if unable to connect to the server for a long period of time.
- Work unit size is limited to a 32bit integer number of crypts (ie: 4294967296)
- Node performance calculations wrap once the node has performed more than 4294967296 crypts, so nodes may appear to be much slower than they truly are.
- Doesnt work with NTLM, as the NTLM hash is stored in a different field of the passwd file.
- Traffic is sent in plain text (this makes debugging easier at this early stage of development)
- Makefile is very basic, and has no configure script, compilation on Solaris requires adding -lnsl -lsocket to the compile command.
Enhancements:
- Basic functionality is implemented, and dnetj is usable, but there are many things still to be implemented and a lot more testing is needed.

The Distributed Replicated Blob Server Project (drbs) is a young project, not mature enough to handle production data.

You still might take a look and report any feedback from build problemss or bugs to ideas what problems drbs might solve for you.

How to keep a large set of blobs available under the following circumstances:

Coda is an advanced networked filesystem. The project has been developed at CMU since 1987 by the systems group of M. Satyanarayanan. in the SCS department.
Coda is a distributed filesystem with its origin in AFS2. It has many features that are very desirable for network filesystems. Currently, Coda has several features not found elsewhere.
1. disconnected operation for mobile computing
2. is freely available under a liberal license
3. high performance through client side persistent caching
4. server replication
5. security model for authentication, encryption and access control
6. continued operation during partial network failures in server network
7. network bandwith adaptation
8. good scalability
9. well defined semantics of sharing, even in the presence of network failures
Enhancements:
- Coda now works on 64-bit systems.
- The client and server were successfully built and used on a machine with em64t extensions with a 64-bit Linux kernel.
- The new RVM-1.14 and RPC2-2.5 releases also incorporate some essential 64-bit fixes.
- Another welcome change is that venus now tries to keep cached access rights available for users even across system reboots or client restarts, which should improve life for people who frequently shut down or dual boot their machines.