Release Notes: This release fixes a major error in cull processing, implements a major security enhancement on most systems, performs cyphertite configuration file generation with "cyphertitectl config generate", generates a crypto secrets file during configuration file generation, adds ctctl secrets uploading/downloading to store a user's secrets file on the server, changes the cyphertitectl command to change the secrets password to "ctctl secrets passwd", fixes an error in the cyphertite file browser related to rooted backups (-cP), and includes other minor cleanup and bugfixes.
Release Notes: User names were normalized to match Web accounts. Support for latest version of libevent was provided. Man pages were improved and cleaned up.A cyphertitectl (ctctl) man page was included in the packages. Build versioning was implemented on Linux to match support on BSD. Man pages can now be accessed by their short names on Linux. Usage clarity was improved. Error reporting when loading file certificates was improved. An issue regarding listing the contents of an incremental backup was fixed. There were other minor bugfixes, miscellaneous code cleanups, and improvements.
Release Notes: This release handles files truncated or growing during backup; a best effort will be made to archive the files. It reports useful error message when a user runs out of space on a limited space account. It adds a method to implement backups instead of archives; for more information see the man page 'BACKUP vs ARCHIVE' section. It changes the internal encoding of filenames as ct archives are backed up on the server to provide better internationalization support. Cyphertite file browser usage changes and operation improvements. Minor fixes and improvements.
Release Notes: The file browser utility, cyphertitefb, was improved. .ct is now recommended as the extension for metadata archive files. Debug trace filtering with '-D flagname' was implemented. The local database revision is now negotiated and synced with the server. Other miscellaneous code cleanups and improvements were made.
Release Notes: This release enables UTF-8 support for filenames. It adds a new file browser utility (cyphertitefb). It implements logic to validate the specified 'ctfile'. It fixes an issue when all specified files are excluded via the -E option. It corrects -P behavior, adds a change log in the root directory, and has general code cleanup and improvements.
Release Notes: This release fixes certain scenarios where extracting incremental backups could cause files to be restored to the wrong directory. It has been updated to use OpenSSL 1.0.0e. It consolidates the configuration and operational files into a single directory by default. There are other miscellaneous code cleanup and improvements.
Release Notes: Infrastructure was added for automatic feature negotiation. Metadata tag list output was fixed to allow copy/pasting with special characters. The latest versions of several dependency libraries are now used. Build versioning was added and code portability was improved. There were other minor cleanups and bugfixes.
Release Notes: This release fixes the -E flag when used with the -0 flag and non-differential backups (FS#169). It makes the -C flag work as intended in all modes. It fixes local database initialization (FS#164). The correct reduction ratio is displayed in stats (FS#167). Debug print has been added for scheduled files (FS#161). There are other minor cleanup and bugfixes.
Release Notes: This release handles the case where none of the specified backup objects exist. It modifies inclusion/exclusion processing to use full paths instead of only the filename on Linux. It properly restores suid bits with and without the -p option. It stores the basename of the backup file in remote mode incremental backups. It fixes an error when a symlink exists in the backup prefix. It adds a framework for upcoming features. There are general improvements and bugfixes.
Release Notes: Due to a bug, it was possible that a configuration file selected with -F was not processed correctly or entirely. This could result in configuration parameters (e.g. compression, metadata cache directory, etc.) that were set incorrectly. This is an emergency release, and users should update ASAP.