MAN page from Other cruft-0.2.0-1.i386.rpm

CRUFT

Section: Misc. Reference Manual Pages (1)
Updated: Version 0.2
Index

NAME

cruft- Encrypt files locally

SYNOPSIS

cruftReplacement for the UNIXcryptcommand.

DESCRIPTION

cruftis intended as a drop-in replacement for the UNIXcryptcommand, being equivalent in functionality and even easier to use thanthe original.

cruftruns either as a filter,

cruft < infile > outfile

or in file mode.

cruft infile outfile

cruft infile > outfile

cruftwill autodetect whether the target file needs to be encrypted ordecrypted. A file encrypted by cruft always has at its start a sequenceof exactly 9 marker characters, which happen to be defined as as253 (0xFD).This makes it unnecessary to specify whether the target file is to beencrypted or decrypted, and indeed there is no provision for doing so.

OPTIONS

None.

FILES

~/.key

The "key" file of random numbers generated by thekeygenutility that is part of this package.

ENVIRONMENT

$HOME

The$HOMEenvironment variable, referenced by this utility, is normally set toeach user's home directory in any standard Linux or generic UNIX system.No changes should be necessary.

AUTHOR

Mendel Cooper - <thegrendelAATTtheriver.com>

BUGS

Encrypted files have nine special marker characters (0xFD) at their head,and this makes it easy to recognize that a) these files are encrypted,and b) the type of encryption done. Fortunately, this scarcely compromisesthe security of this method.

The~/.keyfile for every encrypted file must be maintainedsomewhere,either in the user's home directory or on backup media. Regular changes of the~/.keyfile, necessary for strictest security, can become an administrativenightmare.

This document was created byman2html,using the manual pages.