Free managed secure file transfer software for linux

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.

Secure Data Manager project is a manager for passwords and other private data.
Secure Data Manager (SDM) is a full-featured password manager application written entirely in Java (so it can run on Unix or Windows). It encrypts logins and other private information for Web sites, computers, credit cards, etc.
Main features:
- Many great features and more coming each month based on user feedback!
- No limit to how you use the product or how often!
- Trusted since you and everyone else can see the code that protects your passwords -- keeping the application clear of any trojans or bad business practices.
- Open source -- so if you know how to write code, you can add any feature you want!
- Free.

Remote Secure Command System project is a remote asynchronous and secure command system based on a file configuration.

A standalone server sends and receives commands through files, and a batch system launch ssh and scp commands.

Orion Secure Message Gateway (OrionSMG) is a secure message gateway for transporting ebXML, SOAP, and custom message formats. It complies with the OASIS ebXML 2.0 specification, and can act in both intermediary and processing MHS roles to provide end-to-end reliable messaging.
Orion Secure Message Gateway software runs natively on Linux, OS X, and Windows with ODBC/PostgreSQL database support.
Enhancements:
- OrionSvnInfo.h now in correct directory.
- Old documentation temporarily added.
- Minimal README.txt file added.

Apple Disk Transfer ProDOS (or ADTPro for short) transfers diskettes and logical disk images between Apple ][-era computers and the modern world. If youre familiar with the original ADT, ADTPro extends ADTs reach by working with more logical disk formats, drive types, communications devices, and host operating systems.
Main features:
- Compatibility with any device ProDOS can read
- Compatibility with any Apple ][ (or clone) computer with 64k memory
- Compatibility with many logical disk image formats: .DSK, .PO, .NIB, 2IMG
- Server compatibility with original ADT client program
- Server compatibility with Windows, Mac OSX, Linux, and probably Solaris
- Ability to bootstrap an Apple ][ from bare metal over serial or cassette ports
- Ability to send floppies in "batch" mode without having to name each one
Server
The server program runs on a computer capable of running Java. Depending on how you want to connect to your Apple, you might also need a serial port and cables, an Uthernet card for your apple, or a couple of audio patch cables. The server offers a compact user interface that shows what communications are taking place between the host and the Apple ][.
The servers primary role is to send and receive disk images as requested from the client. But if you have recently acquired an Apple and a disk drive, and you have no software for it - youre in a bit of a tricky situation if you want to move software from the Internet all the way to your shiny new Apple. ADTPros server can help get you get bootstrapped.
Client
The client side runs on the Apple ][. It handles most of the user interaction. When choosing disks/volumes to transfer, anything that ProDOS can see is fair game. Transferring data occurs with a 20k buffer on the Apple, so all transfers are broken up into 20k chunks. A progress indicator shows how far it is into the current chunk, as well as a running count of the total progress.
Enhancements:
- This release has been enhanced with Jean-Marc Boutillon (Deckard)s FASTDSK fast Disk II reading routines.
- This results in a speed boost of 25%-33% for Disk II to host transfers.
- Bootstrapping operations have been reduced, as there is no longer a dependency on ProDOS BASIC.

Secure Login provides a login extension similar to Operas Wand login.

It uses the built-in password manager, but deactivates the prefilling of login forms.
Instead, you are now able to login with one click or a keyboard shortcut (ALT+N).
Just add the Secure Login toolbar button to your toolbar, or use the provided statusbar icon.
If you hover over one of the icons, a tooltip is shown, displaying the login url and the number of available logins (users).
For more than one user or login forms on the current page a selection prompt is displayed on login.
You have the option to play sound notifications (*.wav) for found login data on the current page or when logging in.
All the options can be changed using the Secure Login settings menu or the statusbar icon context menu.

Secure Login provides you with a number of Security enhancements and helps protecting you from phishing:

Disabling the prefilling of login forms prevents malicious JavaScript code to automatically steal your login data.
This is due to the fact that no login data is inserted in form fields before the user clicks on the login button or logs in using the keyboard shortcut.
To make sure you login to the right website, the second level domain of the login url is compared to the second level domain of the current page.
If they do not match a dialog prompt is displayed before login.

SecureLogin provides you with an optional setting to protect you from all JavaScript code during login.
This can prevent cross-site scripting (XSS) attacks without having to deactivate JavaScript completely.
If you enable this option, your login data will never be inserted in any form fields nor will the login form be submitted.
Instead your credentials will be sent to the login page using internal Firefox methods.
Not all login forms will work this way, e.g. not those using JavaScript routines.
Therefore, you can add such websites to an exception list.