This document describes how to use the utilities dcrypt and ecrypt.

Publishing with ecrypt

They assume that you have a directory for creating urls in.  To create a
url, you copy in the files you want to submit and give them extensions
".html" regardless of whether they are actual html documents or not.

Then you create a file with the same base name, but with extension ".flags",
and in this file you put all the eternity options you want to apply to this
file.  (For example:

URL: http://something.eternity/censored/
Option: directory
Cache: yes

).

Next extract the key you want to sign the documents with into a file with
pgp -kxa <userid>.  Copy this file and give the copied file the same
basename as your submitted document, but with extension .key.

Then run "ecrypt basename" it will look at basename.html, basename.key and
basename.flags.  It will create the subject field with the sha1 hash of the
url (it extracts the url from the .flags file).

Ecrypt can take a list of files on the command line.  If you use numbers for
the files (like USENET article numbers), you can copy them into your test
news spool for testing with: 

cp [0-9]* /XX/news/alt/anonymous/messages

where XX is the directory where you have installed eternity.

You'll have to run eternity -u to update the article database.  If things
get messed up, try running eternity -r to clean everything out, and then
running eternity -u to re-create the article databse from scratch.

Naturally when creating new documents, it would make sense to choose article
numbers that are not already taken in the test news spool, or you'll
overwrite them.

When you are satisfied with the results of the documents in the test spool,
you can post them (optionally via an anonymous remailers which knows how to
post to newsgroups, or via a remailer and a mail-to-news gateway).


Fixing bugs in eternity documents in the test news spool

The dcrypt utility does the opposite of the ecrypt utility.  You give it the
basename of the article, and it creates files with extensions .post, .html,
.key, .flags.

.post is just for your information and is overwritten by ecrypt when you
package the document back up again.

.html, .key and .flags can be modified.

Probably the most useful to be able to modify are .flags and .html.  After
you've edited them re-run ecrypt.  It will prompt you for your passphrase
to sign the document.  Then re-copy the newly created eternity post into
your test news spool.

To update the eternity article database correctly, and flush the cash, you
*must* first clear all state from the eternity database by running 
"eternity -r".  Then run "eternity -u" to re-create the database from
scratch.

Removing everything is necessary because eternity doesn't normally parse the
same article twice.  It will ignore your changes and work from the cache,
and/or from the old article values for key, and flag options.
