Free large public computing facility software for linux

Eureka Public Key was created due to numerous requests for a public key application using our strong encryption techniques. The basic principle for its use is one creates their own public key and distributes the key to whomever they will be transferring encrypted files with.

When one receives a key, they import it into their key database. You can create and import as many keys as you wish. Both public keys are used in the cryption process. You select your particular public key to use and the public key of the person who will receive it.

When a file has been received you put in your public key that matches the one they used and select their public key that was used in the encryption. See the Encryption, Decryption and Import/Export sections for more information on these topics. To create a public key, click on Keys then Create Public Key or click on the gold key icon under the menu items.

All you have to do is define a name for the public key and click on Create. All encrypted files will be written to the Encryptions folder. Likewise, all decrypted files will go to the Decryptions folder. If a file already exists with the same name, it will be overwritten.

Encryption:

To Encrypt a file, click on File then Encrypt.

All you have to do is select Your public key, their public key and click on Encrypt or press enter then select the file you want to process.

The file selected will be encrypted and then placed in your Encryptions folder. Now you can send this file in the manner you prefer.

Note that this application encrypts in a binary format. In other words, it uses the full 256 character set and is not a text file. You will need to send it as an attachment if you are using email to transmit it.

Decryption:

To Decrypt a file, click on File then Decrypt.

All you have to do is select Your public key, their public key then click on Decrypt and select the file you want to process.

The file selected will be decrypted and then placed in your Decryptions folder.

Public Fox cleans stuff after downloading.

Tired of cleaning stuff people download? Use this to limit file downloading.
Prevent browser changes.

Public Fox blocks users from downloading unwanted files.
Locks down Add-ons.
Locks down Preferences.
Locks down about:config
All with a central password.

Los Alamos Message Passing Interface is an implementation of the Message Passing Interface (MPI) motivated by a growing need for fault tolerance at the software level in large high-performance computing (HPC) systems.
This need is caused by the vast number of components present in modern HPC systems, particularly clusters. The individual components -- processors, memory modules, network interface cards (NICs), etc. -- are typically manufactured to tolerances adequate for small or desktop systems.
When aggregated into a large HPC system, however, system-wide error rates may be too great to successfully complete a long application run. For example, a network device may have an error rate which is perfectly acceptable for a desktop system, but not in a cluster of thousands of nodes, which must run error free for many hours or even days to complete a scientific calculation.
LA-MPI has two primary goals: network fault tolerance and high performance.
Network fault tolerance is acheived by implementing a highly efficient checksum/retransmission protocol. The integrity of delivered data is (optionally) verified at the user-level using a checksum or CRC. Data that is corrupt (or never delivered) is retransmitted.
As for high performance, LA-MPIs lightweight checksum/retransmission protocol allows us to achieve low latency messaging. Furthermore, the flexible approach taken to the use of redundant data paths in a network-device-rich system leads to high network bandwidth since different messages and/or message-fragments can be sent in parallel along different paths. Also, since LA-MPI is developed for use on the the large systems at Los Alamos National Laboratory we have verified that LA-MPI is scalable to over 3,500 processes.
An alternative solution to the network fault tolerance problem is to use the TCP/IP protocol. We believe, however, that this protocol -- developed to handle unreliable, inhomogeneous and oversubscribed networks -- performs poorly and is overly complex for HPC system messaging, and that LA-MPIs lightweight checksum/retransmission protocol is a more appropriate choice.
Main features:
- Standard compliant (MPI version 1.2 integrated with ROMIO for MPI-IO)
- Highly portable
- Open source (LGPL)
- Thread safe
- Optimized for SMP systems, including NUMA architectures
- Network fault tolerant (data integrity checked at user level)
- Message-fragment striping across multiple network devices
Enhancements:
- Namespace conflicts have been fixed.
- Error detection and handling of fragments has been improved.
- Bugs in memory barriers and spinlocks for x86 and x86_64 architectures have been fixed.
- Profiling and backtracing support have been added.
- Asynchronous I/O has been disabled by default as a workaround for problems with some filesystems.
- Minor timeout bugs have been fixed.

If youve had your music collection for a while, youve probably noticed that some (or most) of your tracks are mislabeled, skip, are duplicates, or have low bitrates. Depending on how long youve had your collection, this could be thousands of redundant, poping, or mislabled tracks. Parakeet Brainz is a tool to correct this, with a little user intervention as possible.

Parakeet Brainz analyzes the acoustic properties of music and looks it up in a large, public database. Using this information Parakeet Brainz sorts and organizes your collection.

Parakeet Brainz also intelegently detects duplicate tracks waisting disk space and removes them, so your collection can grow even larger.

Parakeet Brainz also supports plugins. these plugins can be used to decode and encode music for analysis and convertion.

ParakeetBrainz is completely free and open source under the GNU Public Licence.

Mumps is a general purpose programming language that supports a native hierarchical data base facility. It is supported by a large user community (mainly biomedical), and a diversified installed application software base. The language originated in the mid-60s at the Massachusetts General Hospital and it became widely used in both clinical and commercial settings. A dwindling number of implementations exist for the language. There are both ANSI, ISO (ISO/IEC 11756:1992) and DOD approved standards for Mumps.

As originally conceived, Mumps differed from other mini-computer based languages of the late 1960s by providing: 1) an easily manipulated hierarchical (multi-dimensional) data base that was well suited to representing medical records; 2) flexible string handling support; and (3) multiple concurrent tasks in limited memory on very small machines. Syntactically, Mumps is based on an earlier language named JOSS and has an appearance that is similar to early versions of Basic that were also based on JOSS.

This translator implements much of the most recent Mumps standard (see the manual). Mumps programs are translated to standard C++ programs and subsequently compiled to binary executables. This distribution contains the compiler source code, the manual, the run-time functions source code, all written in C/C++, and examples, written in Mumps. Also included is a stand-alone Mumps Interpreter for Windows XP and Linux. Click here for additional details.

The MDH (Multi-Dimensional and Hierarchical Data Base Toolkit) is a Linux-based, open sourced, toolkit of portable software that supports very fast, flexible, multi-dimensional and hierarchical storage, retrieval and manipulation of data bases ranging in size up to 256 terabytes. The package is written in C and C++ and is available under the GNU GPL/LGPL licenses in source code form. You must install the Mumps Compiler in order to use the MDH.

OpenSSH LDAP Public Key patch provides an easy way of centralizing strong user authentication by using an LDAP server for retrieving public keys instead of ~/.ssh/authorized_keys.
It uses the standard core.schema/nis.schema and strongAuthenticationUser object class, which can simplify login centralization but could introduce serious security flaws if the LDAP server is not correctly configured.
Enhancements:
- A memory leak has been fixed.
- A potential LDAP filter injection if a username has strange characters in it [()*] has been fixed.