1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Man page of RSYNCRYPTO</TITLE>
</HEAD><BODY>
<H1>RSYNCRYPTO</H1>
Section: Rsyncrypto User Manual (1)<BR>Updated: July 22, 2008<BR><A HREF="#index">Index</A>
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
<A NAME="lbAB"> </A>
<H2>NAME</H2>
rsyncrypto - rsync friendly encryption
<A NAME="lbAC"> </A>
<H2>SYNOPSIS</H2>
<B>rsyncrypto</B>
[<I>options</I>]<I> srcfile dstfile keyfile key</I>
<BR>
<B>rsyncrypto</B>
[<I>options</I>]<I> </I><B>-r</B><I> srcdir dstdir keysdir key</I>
<A NAME="lbAD"> </A>
<H2>DESCRIPTION</H2>
This manual page documents the <B>rsyncrypto</B> command.
<P>
<B>rsyncrypto</B> is a utility that encrypts a file (or a directory structure)
in a way that ensures that local changes to the plain text file will result in
local changes to the cipher text file. This, in turn, ensures that doing
<B>rsync</B> to synchronize the encrypted files to another machine will have
only a small impact on <B>rsync</B>'s efficiency.
<P>
<B>rsyncrypto</B> will encrypt files using a symmetric block cipher (AES). Each
file is encrypted using a unique key. The file key is stored in two locations.
One is the "<I>key</I>" file, and the second is inside the encrypted file
itself. The second copy is encrypted using a RSA public key, which can be
shared for all encrypted files.
<P>
Decrypting the file can take place in one of two forms:
<DL COMPACT>
<DT><B>Warm Decryption</B>
<DD>
<I>keyfile</I> is used to decrypt <I>srcfile</I> into <I>dstfile</I>.
<DT><B>Cold Decryption</B>
<DD>
If <I>keyfile</I> is lost and <I>key</I> is the <B>private</B> key for the RSA
encryption, extract and create <I>keyfile</I> from the encrypted <I>srcfile</I>,
and create both <I>keyfile</I> and <I>dstfile</I>.
</DL>
<P>
If both <I>keyfile</I> and the private key are not available, decryption cannot
take place. Typically, this means that you would either want to transfer the
encrypted files in whatever way (secure or insecure, but probably <B>rsync</B>
:), and keep the plain text file, as well as the key file, secure. As long as
you saved the RSA private key, you can reconstruct them both.
<A NAME="lbAE"> </A>
<H2>PARAMETERS</H2>
The parameters meaning depend on the existence of the <I>-r</I> and <I>-d</I>
flags.
<DL COMPACT>
<DT><I>srcfile</I> or <I>srcdir</I><DD>
This is the source for the operation. This will be the plain text file for
encryption, and the cipher text file for decryption. If the <I>-r</I> option is
given, <I>srcdir</I> is the directory from which files are to be
encrypted/decrypted. Otherwise, <I>srcfile</I> is the file to be
encrypted/decrypted. In any case, <I>src</I> must exist prior to running
<B>rsyncrypto</B>.
<DT><I>dstfile</I> or <I>dstdir</I><DD>
Similar to <I>src</I>, this is the destination of the operation. It will be
the plain text to be created if <I>-d</I> was given, or the encrypted file
otherwise.
<DT><I>keyfile</I> or <I>keydir</I><DD>
The file holding the symmetric key for the encryption, or a directory in which
symmetric key files reside. If the later, the key files will have the same name
as the plain text files.
<DT><I>key</I><DD>
This file can either be a X509 certificate holding a public key, or a PEM format
private key. The private key is never needed unless a cold decryption is
required. See the
<B><A HREF="/cgi-bin/man/man2html?1+req">req</A></B>(1)
or
<B><A HREF="/cgi-bin/man/man2html?1+x509">x509</A></B>(1)
manual pages for more info.
</DL>
<P>
If <I>dst</I> does not exist, it will be created. The directory in which it
is to be created must exist prior to running <B>rsyncrypto</B>.
<P>
If encrypting, and a symmetric key for the file is found, the same parameters
will be used for the encryption unless the <I>--fr</I> or <I>--fk</I> options
are used. If that's the case, the key file is going to be replaced with the
correct parameters.
<A NAME="lbAF"> </A>
<H2>OPTIONS</H2>
These programs follow the usual GNU command line syntax, with long options
starting with two dashes (`-').
<DL COMPACT>
<DT><B>-h</B>, <B>--help</B>
<DD>
Show summary of options.
<DT><B>-V</B>, <B>--version</B>
<DD>
Print out the current version number.
<DT><B>-d</B>, <B>--decrypt</B>
<DD>
Decrypt <I>src</I> into <I>dst</I>. The default behavior is to encrypt <I>src</I>
into <I>dst</I>, and create <I>keyfile</I> if it does not exist.
<DT><B>-r</B>, <B>--recurse</B>
<DD>
Recursively encrypt/decrypt an entire directory structure. All files under
<I>srcdir</I> will be encrypted to files of the same name and path (almost, see
<I>--trim</I>) under <I>dstdir</I>. If not already there, a key file will be
created for each file under <I>keydir</I>.
<DT><B>--filelist</B>
<DD>
The first argument is a pointer to a file (or "-" for stdin) that has a list
of files to process. Any name ending with a "/" is taken to be a directory in
recursive mode, and any other name is a file name. The second argument is a
directory where the files are encrypted to. --filelist and -r are mutually
exclusive.
<DT><B>-c</B>, <B>--changed</B>
<DD>
Check the src and destination modified time (see --modify-window) prior
to performing the operation. If the modified time is the same, assume that the
files are also the same, and skip the operation. Notice that unlike <B>rsync</B>,
file sizes are not compared. This is because the file size is expected to change
during the encryption (and thus decryption) operation.
<DT><B>--risky-writes</B>
<DD>
Usually, when rsyncrypto writes a file, it uses a temporary name and moves the
file to its final name when successfully done. This serves two purposes. During
encryption, this prevents the false sense of security that may arise in case of
an rsyncrypto interruption by preventing a partial file from being present (and
in case of an update, by keeping the old backup). This also ensures that restarting
rsyncrypto will enable it to correctly detect whether the operation needs to be
repeated. During decryption, this prevents overwriting a file until we are certain
we can decrypt its source.
<P>
The main problem with this approach is that, if the file being written is large,
the file system needs to have enough space for two copies of it for the duration of
the operation. Also, if hard links are maintained, the default rsyncrypto behavior
will break the link.
<P>
Specify <B>--risky-writes</B> to make rsyncrypto directly overwrite the existing file
using the final name.
<DT><B>--modify-window=</B><I>num</I>
<DD>
Only applicable when <B>-c</B> is in effect. When comparing file modification times,
treat as equal modification times that are <I>num</I> seconds apart. Default value is
zero.
<P>
This option is most useful when the encrypted file is stored on a FAT file system.
FAT can only store modification time with a 2 seconds accuracy. This may result in
the modification time changing between original and encrypted file. In such a case,
<B>--modify-window=1</B> should be used.
<DT><B>--export-changes=</B><I>logfile</I>
<DD>
Whenever encrypting or deleting a file, write the file's name to <I>logfile</I>. This
allows passing <I>logfile</I> to <B><A HREF="/cgi-bin/man/man2html?1+rsync">rsync</A></B>(1) using the <B>--include-from</B>
rsync option.
<P>
This option is mostly useful if <B>rsyncrypto</B> is used to repeatedly encrypt a huge
directory tree, and then using rsync to synchronize it remotely. The use of this
option allows focusing <B>rsync</B> on only those files that are known to have
changed, rather than have it send the entire file list to the remote machine, making
the rsync operation faster. It should be noted that rsync version 3 starts the
actual file transfer while it is still transferring the file list, making the
performance gain from this option less noticeable.
<P>
When using this option in conjunction with rsync, keep in mind that <I>logfile</I>
is zeroed out before being written into. This means that unless there is at least
one completely successful rsync operation for each rsyncrypto invocation, it is
possible to have files that have been changed on disk by a previous invocation
of rsyncrypto, but were over written by a later invocation and do not show up
in the latest version of <I>logfile</I>. In other words, if rsyncrypto is run
more than once between two completely successful invocations of rsync, it is
possible for <I>logfile</I> not to be complete. <B>Use this option at your own risk!</B>
<P>
It is highly recommended that you upgrade to rsync version 3 or higher rather than
rely on this option.
<DT><B>-n</B>, <B>--name-encrypt=</B><I>translation_file</I>
<DD>
Encrypt the file name. If this option is specified, this means that file
names are encrypted as well. This is done by changing the name of the encrypted
file to a random string of characters, and storing the translation in the file
given as parameter.
If working in recursive mode, this file is automatically also included in the
encryption, and is given the fixed name "filemap". This is done so that
decryption of the file names is possible when the symmetric keys are lost.
<DT><B>--ne-nesting=</B><I>num</I>
<DD>
When the --name-encrypt option is used, by default all mangled file names
are stored in a single directory. When encrypting large directory trees, this
can result in rather big directories. Using "--ne-nesting" will split the
files to sub directories, according to random bits that are part of the
encrypted file name. "n" is the number of directories to nest.
<DT><B>--trim=</B><I>num</I>
<DD>
Determine how many directory levels to trim from the beginning of the <I>srcdir</I>
path when creating directories under <I>dstdir</I>. The default value is 1. See
<B>THE TRIM OPTION</B>
for more details.
<DT><B>--delete</B>
<DD>
When in recursive mode, delete files and directories under <I>dstdir</I> that do
not exist under <I>srcdir</I>.
<DT><B>--delete-keys</B>
<DD>
When deleting files, also delete their symmetric key and file name mapping (if
applicable). When only <B>--delete</B> is used, the symmetric key and file
mapping are kept, so that if the file is recreated, it will be rsyncable with
the original file. This option implies <B>--delete</B>.
<DT><B>-b</B><I>num</I><B> --keybits=</B><I>num</I>
<DD>
Specify the block cipher's key size. For AES, these can be 128, 192 or 256.
Note that unless the <I>--fr</I> or <I>--fkP options are also specified, this
will only affect files for which no keyfile</I> exists.
<DT><B>--noatime=</B><I>num</I>
<DD>
(Only on some platforms, most notably Linux). The platform usually keeps track of when
files were last being accessed. Since <B>rsyncrypto</B> is typically used for backup, it
opens the files it encrypts with the O_NOATIME option, which is a Linux specific
extension that tells the system not to update the file's access time. When opening a
file where the opening process is not owned by the file owner, an attempt to open the
file with O_NOATIME will cause the open to fail with "permission denied".
<BR>
<I>num</I> can be one of these options:
<B>0</B> means do not use O_NOATIME at all.
<B>1</B> (the default) means attempt to only use O_NOATIME if <B>rsyncrypto</B> thinks it
will not cause a permission denied error.
<B>2</B> means to use O_NOATIME always.
<DT><B>--no-archive-mode</B>
<DD>
Do not try to preserve timestamps. This option is incompatible with <B>-c</B>.
<DT><B>--gzip=</B><I>path</I>
<DD>
By default, <B>rsyncrypto</B> will compress the plain text prior to encrypting
it. In order not to become rsync unfriendly due to the compression,
<B>rsyncrypto</B> will search the path for an instance of
<B><A HREF="/cgi-bin/man/man2html?1+gzip">gzip</A></B>(1)
that supports the <I>--rsyncable</I> option. If the system's default gzip does
not support this option (all Debian and derivatives, as well as some others, support it), use
this option to tell <B>rsyncrypto</B> to use a different instance of gzip. The
tests directory of rsyncrypto's source has a file called "gzip", that does NULL
compression by redirecting the input and output to
<B><A HREF="/cgi-bin/man/man2html?1+cat">cat</A></B>(1).
<DT><B>--roll-win=</B><I>num</I>, <B>--roll-min=</B><I>num</I>, <B>--roll-sensitivity=</B><I>num</I>
<DD>
Affects the rolling block algorithm. See <B>NOTES</B>.
<DT><B>--fk</B>, <B>--fr</B>
<DD>
If command line, or a version with different defaults, dictate different
values for the <I>--roll-*</I> options or the <I>-b</I> option, these will only
affect files for which <I>keyfile</I> does not yet exist. specifying the
<I>--fk</I> or <I>--fr</I> will recreate <I>keyfile</I> if it has values different
than those in the previous key file.
<DT><B>-v</B>, <B>--verbose</B>
<DD>
Increase verbosity level. Specify several times to be more verbose.
</DL>
<A NAME="lbAG"> </A>
<H2>NOTES</H2>
<B>encrypting stdin</B>
<P>
If <I>srcfile</I> is given as `-', the plain text data will be read fro stdin.
This does not yet work for decompression (see <B>BUGS</B>).
<P>
<B>--roll-win</B>=num, <B>--roll-min</B>=num, <B>--roll-sensitivity</B>=num
<P>
These values affect some of the inner workings of <B>rsyncrypto</B>'s decision
making. In particular, these affect how <B>rsyncrypto</B> decides when to
revert to the IV.
<P>
These options should not be played with unless you understand what you are
doing. They are not dangerous, in that they will never cause data loss. Any
value should still allow decryption of the file. They do have an affect on
<B>rsync</B>'s efficiency.
<P>
These options are only there to allow quick response in case a security problem
pops up with their default values. If that happens, an advisory may come out
giving new values to fill in as a workaround. Until that happens, most users
are advised to leave these options alone.
<A NAME="lbAH"> </A>
<H2>THE TRIM OPTION</H2>
When running <B>rsyncrypto</B> in recursive mode, the directory structure under
<I>srcdir</I> is re-created under <I>dstdir</I>, with one directory stripped from
the path. In other words, if we have a directory structure which has:
<P>
a/b/c/file
<P>
running <B>rsyncrypto</B> with <I>srcdir</I> of "a/b", and <I>dstdir</I> of "f"
will create "f/b/c/file".
<P>
The <I>--trim</I> options lets the user say how many parts to trim from
<I>srcdir</I> when creating directories under <I>dstdir</I> and <I>keydir</I>. If, in the
above example, we said
<I>--trim</I>=0
then "f/a/b/c/file" would have been created. Likewise, if we said
<I>--trim</I>=2
then "f/c/file" would have been created.
<P>
It is an error to give a trim value which is higher than the number of
directory parts actually in <I>srcdir</I>. In the above example,
<I>--trim</I>=3
would result in an error.
<A NAME="lbAI"> </A>
<H2>SECURITY</H2>
The roll values affect, to a not totally known degree, how much information
is "leaked" between plain text and cipher text. The default values are supposed
to leak less than 20 bits of aggregated information about the plain text file
for every 8KB, in the worst case. These values, we hope, will be considered
secure enough for most usages. However, if your country's fate is at stake, use
a non-rsync optimized encryption, such as the one provided by
<B><A HREF="/cgi-bin/man/man2html?1+openssl">openssl</A></B>(1).
<A NAME="lbAJ"> </A>
<H2>EXAMPLES AND TUTORIAL</H2>
<P>
Before starting to use rsyncrypto you will need a public key in X509
certificate format. The quickest way to generate one of these is using the
<A HREF="/cgi-bin/man/man2html?1+openssl">openssl</A>(1) package. To generate a new 1536 bit RSA key as "backup.key", and
store the corresponding unencrypted public key in "backup.crt", use the
following command:
<P>
<DL COMPACT><DT><DD>
<TT>openssl req -nodes -newkey rsa:1536 -x509 -keyout backup.key -out backup.crt</TT>
</DL>
<P>
It does not matter what you answer for the certificate details, or when you set
it to expire. Rsyncrypto ignores everything in the certificate but the actual
key.
<P>
To encrypt file "data" into "data.enc", storing the file's specific key at "data.key", run:
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto data data.enc data.key backup.crt</TT>
</DL>
<P>
Anywhere in these examples that "backup.crt" is used, "backup.key" can be used
as well. The above could also have "backup.key" as the last argument. If these
examples list "backup.key" specifically, then it means that "backup.crt"
<B>cannot</B>
be used instead.
<P>
"data.enc" will be created. If "data.key" exists from a previous run, then the
newly created "data.enc" will have the same symmetric key and other attributes,
thus maintaining the rsync friendliness of the encryption. It is therefor
important to provide any previous key file for the data if one is available.
<P>
The command line to decrypt the file depends on whether you have the key file
used when the file was encrypted. If you do, then decryption can take place
using only the public key, with the following command:
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto -d data.enc data.dec data.key backup.crt</TT>
</DL>
<P>
If the key file was lost, the private key must be used to recover it from the
encrypted file using the following command:
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto -d data.enc data.dec data.key backup.key</TT>
</DL>
<P>
"data.key" will be created by the above command, as well as "data.dec".
<P>
Use of rsyncrypto to encrypt whole directories is similar, with directory names
replacing file names in the above example. To encrypt the content of a
directory called "data" to a directory called "enc", storing the symmetric keys
in a directory called "keys", run the following command:
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto -r data enc keys backup.crt</TT>
</DL>
<P>
As before the directories "enc" and "keys" will be created if they do not
already exist. The directory structure under "plain" will be duplicated under
"enc" and under "keys". That is, if there is a file called "foo" under "data",
an encrypted files called "foo" will be created under "enc", and a key file
named "foo" will be created under "keys". In other words, the first part of the
path to "data/foo" (the part that says "data") is eliminated from the path, and
this determines the name of the files under "enc" and "keys".
<P>
If a different trimming is required, the --trim option can be used. To have
rsyncrypto create "enc/data/foo" instead of the above, use the following
command:
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto -r --trim=0 data enc keys backup.crt</TT>
</DL>
<P>
Instead of taking all files from a single directory, it is possible to supply
rsyncrypto with a list of files and directories which to encrypt. This is done
using the --filelist option, like so:
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto --filelist --trim=0 list enc keys backup.crt</TT>
</DL>
<P>
"enc" and "keys" retain the same meaning as before. "list" is a text file with
a list, one per line, of files to encrypt. The --trim=0 option says that if
list contains a line saying "/home/foo/bar" which states the name of a file,
then an encrypted file called "enc/home/foo/bar" will be created. Without it,
the file will be called "enc/foo/bar". Likewise, with --trim=2, the file
would be created as "enc/bar".
<P>
It is often a problem that the file names are not encrypted. If that is the
case, we can ask rsyncrypto to encrypt the file names, as well as the actual
files. Rsyncrypto does not actually encrypt the file names. Instead, it
replaces the actual file name with a random series of characters. The mapping
between the actual file name and the garbled name is stored in a mapping file.
<P>
<DL COMPACT><DT><DD>
<TT>rsyncrypto --name-encrypt=map --trim=0 -r plain enc keys backup.crt</TT>
</DL>
<P>
This will encrypt the "plain" directory structure into enc, exactly as before.
Unlike before, all files will be directly under the "enc" directory, and will
be named as a meaningless garble. A file called "map" will be created under the
current directory that contains a map between the gabled and the real name of
the file. In addition, two files, called "enc/filemap" and "keys/filemap", will
also be created. These are the encrypted and key file corresponding to the "map"
file mentioned above. During decryption, if "map" does not exist, it will be
created by decrypting "enc/filemap".
<P>
<B>Important note:</B>
When performing file name encryption, it is vitally important to give the correct
--trim values, both during encryption and during decryption. Failing to do so
will cause rsyncrypto to search for non-existing file names, and to fail to
locate the files to decrypt.
<A NAME="lbAK"> </A>
<H2>BUGS</H2>
It is not yet possible to decrypt using password protected private key.
<P>
Decrypting from stdin is not yet supported.
<A NAME="lbAL"> </A>
<H2>SEE ALSO</H2>
<B><A HREF="/cgi-bin/man/man2html?1+rsync">rsync</A></B>(1),
<B><A HREF="/cgi-bin/man/man2html?1+gzip">gzip</A></B>(1),
<B><A HREF="/cgi-bin/man/man2html?1+openssl">openssl</A></B>(1),
<B><A HREF="/cgi-bin/man/man2html?1+x509">x509</A></B>(1),
<B><A HREF="/cgi-bin/man/man2html?1+req">req</A></B>(1).
<BR>
<A NAME="lbAM"> </A>
<H2>AUTHOR</H2>
rsyncrypto was written by Shachar Shemesh for Lingnu Open Source Consulting ltd.
<A HREF="http://www.lingnu.com">http://www.lingnu.com</A>
<P>
This manual page was written by Shachar Shemesh <<A HREF="mailto:shachar@debian.org">shachar@debian.org</A>>
<A NAME="lbAN"> </A>
<H2>PROJECT HOMEPAGE</H2>
<A HREF="http://rsyncrypto.lingnu.com">http://rsyncrypto.lingnu.com</A>
<P>
<HR>
<A NAME="index"> </A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">PARAMETERS</A><DD>
<DT><A HREF="#lbAF">OPTIONS</A><DD>
<DT><A HREF="#lbAG">NOTES</A><DD>
<DT><A HREF="#lbAH">THE TRIM OPTION</A><DD>
<DT><A HREF="#lbAI">SECURITY</A><DD>
<DT><A HREF="#lbAJ">EXAMPLES AND TUTORIAL</A><DD>
<DT><A HREF="#lbAK">BUGS</A><DD>
<DT><A HREF="#lbAL">SEE ALSO</A><DD>
<DT><A HREF="#lbAM">AUTHOR</A><DD>
<DT><A HREF="#lbAN">PROJECT HOMEPAGE</A><DD>
</DL>
<HR>
This document was created by
<A HREF="/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 19:43:39 GMT, July 23, 2008
</BODY>
</HTML>
|
