Free passphrases software for linux

JPasswords is a password management program with encrypted databases. JPasswords project allows you to securely store passwords or passphrases, together with related management data like username, entry title, dates and textual notes, on an encrypted disk file. Access to such a file is protected by a single secret key that you define resp. can change at any time.
Password entries may be ordered within groups (which can be nested) and displayed in tree or in table view. Upon retrieval of a password, the program assists you by a "copy to clipboard" function to make password or username quickly available in other applications. Several useful service functions around file management, like copy, merge, backup and restore, make this program a pleasure to use.
The format and encryption method for the database file is compatible with "Password Safe" (Version 2) files as created by CounterPanes (Bruce Schneier) program of the same name.
Main features:
- Maximum passphrase length: undefined
- Text and passphrase formatting: Unicode, platform- and locale-independent (not for file access key which is formatted on the local charset)
- Maximum number of records: limited by given user environment space (main memory or disk space)
- Encryption algorithm: Blowfish CBC (Bruce Schneier), 8-byte block modification scheme; complete regeneration with every save action
- File access shield: SHA-1, Blowfish EBC
- Data security: automatic backup, manual backup and restore
- Data communication: can export and import records over CSV format (RFC-4180 or spreadsheet)
- Application security: automatic program locking (idle time and minimize), manual program locking, covered text storage
- Passwords: automatic random password generation under various aspects
- GUI Languages: English, German, Russian, French

pam_passwdqc is a simple password strength checking module for PAM-aware password changing programs, such as passwd.

In addition to checking regular passwords, it offers support for passphrases and can provide randomly generated ones. All features are optional and can be (re-)configured without rebuilding.

This module should be stacked before your usual password changing module (such as pam_unix or pam_pwdb) in the password management group (the "password" lines in /etc/pam.d/passwd or /etc/pam.conf). The password changing module should then be told to use the provided new authentication token (new password) rather than request it from the user.

Theres usually the "use_authtok" option to do that. If your password changing module lacks the "use_authtok" option or its prompts are inconsistent with pam_passwdqcs, you may tell pam_passwdqc to ask for the old password as well, with "ask_oldauthtok". In that case the option to use with the password changing module is "use_first_pass".

Theres a number of supported options which can be used to modify the behavior of pam_passwdqc (defaults are given in square brackets):

min=N0,N1,N2,N3,N4 [min=disabled,24,12,8,7]

The minimum allowed password lengths for different kinds of passwords and passphrases. The keyword "disabled" can be used to disallow passwords of a given kind regardless of their length. Each subsequent number is required to be no larger than the preceding one.

N0 is used for passwords consisting of characters from one character class only. The character classes are: digits, lower-case letters, upper-case letters, and other characters. There is also a special class for non-ASCII characters which could not be classified, but are assumed to be non-digits.

N1 is used for passwords consisting of characters from two character classes which do not meet the requirements for a passphrase.

N2 is used for passphrases. A passphrase must consist of sufficient words (see the "passphrase" option below).

N3 and N4 are used for passwords consisting of characters from three and four character classes, respectively.

When calculating the number of character classes, upper-case letters used as the first character and digits used as the last character of a password are not counted.

In addition to being sufficiently long, passwords are required to contain enough different characters for the character classes and the minimum length they have been checked against.

max=N [max=40]

The maximum allowed password length. This can be used to prevent users from setting passwords which may be too long for some system services.

The value 8 is treated specially: with max=8, passwords longer than 8 characters will not be rejected, but will be truncated to 8 characters for the strength checks and the user will be warned. This is to be used with the traditional DES-based password hashes, which truncate the password at 8 characters.

It is important that you do set max=8 if you are using the traditional hashes, or some weak passwords will pass the checks.

passphrase=N [passphrase=3]

The number of words required for a passphrase, or 0 to disable the support for user-chosen passphrases.

match=N [match=4]

The length of common substring required to conclude that a password is at least partially based on information found in a character string, or 0 to disable the substring search. Note that the password will not be rejected once a weak substring is found; it will instead be subjected to the usual strength requirements with the weak substring removed.

The substring search is case-insensitive and is able to detect and remove a common substring spelled backwards.

similar=permit|deny [similar=deny]

Whether a new password is allowed to be similar to the old one. The passwords are considered to be similar when there is a sufficiently long common substring and the new password with the substring removed would be weak.

random=N[,only] [random=42]

The size of randomly-generated passphrases in bits (24 to 72), or 0 to disable this feature. Any passphrase that contains the offered randomly-generated string will be allowed regardless of other possible restrictions.

The "only" modifier can be used to disallow user-chosen passwords.

enforce=none|users|everyone [enforce=everyone]

The module can be configured to warn of weak passwords only, but not actually enforce strong passwords. The "users" setting will enforce strong passwords for invocations by non-root users only.

non-unix []

Normally, the module uses getpwnam(3) to obtain the users personal login information and use that during the password strength checks. This behavior can be disabled with the "non-unix" option.

retry=N [retry=3]

The number of times the module will ask for a new password if the user fails to provide a sufficiently strong password and enter it twice the first time.

ask_oldauthtok[=update] []

Ask for the old password as well. Normally, pam_passwdqc leaves this task for subsequent modules. With no argument, the "ask_oldauthtok" option will cause pam_passwdqc to ask for the old password during the preliminary check phase. With "ask_oldauthtok=update", pam_passwdqc will do that during the update phase.

check_oldauthtok []

This tells pam_passwdqc to validate the old password before giving a new password prompt. Normally, this task is left for subsequent modules.

The primary use for this option is when "ask_oldauthtok=update" is also specified, in which case no other module gets a chance to ask for and validate the password. Of course, this will only work with Unix passwords.

use_first_pass []
use_authtok []

Use the new password obtained by modules stacked before pam_passwdqc. This disables user interaction within pam_passwdqc. With this module, the only difference between "use_first_pass" and "use_authtok" is that the former is incompatible with "ask_oldauthtok".

Psi is the truly open messaging application.
Psi is the premiere Instant Messaging application designed for Microsoft Windows, Apple Mac OS X and GNU/Linux. Built upon an open protocol named Jabber, Psi is a fast and lightweight messaging client that utilises the best in open source technologies.
The goal of the Psi project is to create a powerful, yet easy-to-use Jabber/XMPP client that tries to strictly adhere to the XMPP drafts.and Jabber JEPs. This means that in most cases, Psi will not implement a feature unless there is an accepted standard for it in the Jabber community. Doing so ensures that Psi will be compatible, stable, and predictable, both from an end-user and developer standpoint.
This does not mean that Psi will never have "cool new features". The dev team and community are power-users who look to Psi to keep up with the times. We always want to hear what the users of Psi would like, and if a feature that the dev team wishes to implement does not have an accepted standard, or would diverge from an existing one, we can work together to see the standards changed to accomodate everyone.
Perhaps you have been considering Jabber, but dont want to abandon your friends? Jabber technologies are highly extensible, so Psi is able to interoperate with other, proprietory messaging systems such as AOLs ICQ and Microsofts Messenger. You can keep in contact with your friends, regardless of whether they use AIM, ICQ, MSNM or YahooM. Its even possible to use Internet Relay Chat! *
Unlike other IM clients, Psi is small, fast and responsive. It uses a graphical toolkit called Qt, which takes on the appearance of whichever operating system you run it on. For this reason, Psi doesnt use skins. Wed rather it blend with your desktop like any other application.
Psi has full support for Unicode. Unicode allows Psi to send and receive messages in other languages, even ones that arent based upon the English letterset. In fact, you are able to use Psi in your choice of eight different languages, with more on the way!
Cross-platform compatibility is important to the Psi development team; we believe that you should be able to use whichever operating system you wish. In keeping with this belief, we have a version for each of the three major OSs. The images on this page show Psi running on Microsoft Windows XP, Apple MacOS X and GNU/Linux/KDE3.
Whats New in 0.10 Stable Release:
- The default text input line in the chat dialogs starts at one line tall, and grows as necessary.
- The Roster can now be automatically resized to fit all contacts.
- The menu bar is now available on the roster.
- Tabbed chat windows were implemented.
- On Windows and Mac OS X, selected text may be automatically copied to the clipboard.
- Mac OS X builds now enjoy Growl(.info) support.
- Photos are now available in the VCard dialog.
- Roster and chat dialog now support transparency.
- GPG passphrases are now cached during the entire Psi session.

The ELF-Encrypter program suite is a collection of programs to encrypt ELF binaries using various algorithms, including the ones provided by GPG.
One can choose a lot of methods to obtain the encryption key, such as hashing a list of PCI peripheals, MAC addresses of ethernet cards, file inode numbers, passphrases and passwords.
Here is the complete list:
8-bit fixed mask (used only for testing)
32-bit user selectable mask (used only for testing)
Password
Cast5 (using GPG)
GPG - Encrypt (using GPG)
GPG - Sign (using GPG)
Ethernet MAC
Ethernet MAC and file inode
File inode
PCI binding
Executable files can be encrypted using the crypt-7lib program, then decrypted at runtime by a shared library (libdecrypt), directly linked to the binary or listed in LD_PRELOAD.
Users are strongly encouraged to use gpg-agent; however a special support for quintuple-agent is available at compilation time.
The suite also contains programs to manipulate and inject plain or encrypted code into ELF binaries.
This project is written in C and assembly for the x86 platform.
Enhancements:
- changed the data segment infection technique
- added the code to correct section table offsets