[Pkg-privacy-commits] [nautilus-wipe] 81/224: Convert documentation draft to docbook
Ulrike Uhlig
u-guest at moszumanska.debian.org
Thu Jul 7 19:45:36 UTC 2016
This is an automated email from the git hooks/post-receive script.
u-guest pushed a commit to branch master
in repository nautilus-wipe.
commit b5f22c26dd55343d0e64d2fc521eae78d95ce2b6
Author: Colomban Wendling <ban at herbesfolles.org>
Date: Tue Mar 30 23:31:35 2010 +0200
Convert documentation draft to docbook
---
help/C/nautilus-srm.txt | 201 ------------------
help/C/nautilus-srm.xml | 527 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 527 insertions(+), 201 deletions(-)
diff --git a/help/C/nautilus-srm.txt b/help/C/nautilus-srm.txt
deleted file mode 100644
index c564211..0000000
--- a/help/C/nautilus-srm.txt
+++ /dev/null
@@ -1,201 +0,0 @@
-% nautilus-secure-delete Documentation
-
-
-# Short description
-
-`nautilus-secure-delete` allow to wipe files or free disk space from
-`nautilus`.
-
-Usually when you delete a file, even when bypassing the trash, it's
-not accessible anymore, but its content still exists on the media that
-contained it until a new file is written over it. Consequently, it can
-be quite easy to recover it.
-
-`nautilus-secure-delete` enables you to wipe files and available disk space
-from `nautilus` using the `secure-delete` program written by van Hauser /
-THC[1].
-
-[1]. Secure-delete, van Hauser / THC <vh at thc.org>, 1997-2003
- <http://www.thc.org>
-
-
-# An introduction to data deletion
-
-
-## Deleting doesn't affect data
-
-When you delete a file, even when bypassing or emptying the trash, you only
-tell your computer that you don't care anymore for the file. The file's
-entry is removed from the list of existing files but the content of the file
-remains on the storage medium. The data will remain there until the
-operating system reuses the space for new data.
-
-This could take weeks, months or years before this space is actually
-used for new data, actually overwriting the content of the deleted
-file. Until then, it's possible to recover it by reading directly the
-data on the storage media. That's a quite simple operation, automated
-by numerous softwares.
-
-
-## An answer : overwriting data several times
-
-If you want to make the content of a file really hard to recover, you
-have to overwrite it with other data. But that's not enough. On a
-magnetic hard disk, it's known[2] that the content can still be
-recovered by doing magnetic analysis of the hard disk surface. To
-address this issue, it's possible to overwrite several times the
-content to be deleted. That process is called "wiping".
-
-If some sensible files have been already deleted without paying
-attention to this issue, some of their data probably remains on the
-storage media. It's thus also useful to wipe all the available free
-space of a storage media.
-
-[2]. Peter Gutmann: Secure Deletion of Data from Magnetic and Solid-State
- Memory, 6th Usenix Security Symposium, 1996
- <http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html>
-
-
-## Limitations
-
-This section is quite technical. In a nutshell, there's a lot of limitations, so
-using this tool without setting up a complete security policy will probably be
-useless.
-
-- Temporary files and disks: lots of programs writes temporary and backup files.
- This means that the sensitive data you want do delete probably exists in an
- other form somewhere on your computer;
-- swap space: most operating systems could save data they are working on on a
- part of the hard disk called swap space. Your sensitive data could exist
- there;
-- storage media features: modern storage mediums often reorganize their content,
- e.g. to spread the writings over the media or to hide defective places to the
- operating system. Consequently, you can't be sure that the actual place
- occupied by your sensitive data was wiped;
-- journalized file systems: modern file systems log modifications of the files
- to ease recovering after a crash. This could make wiping inefficient. The same
- kind of problem exists with redundant file systems (e.g. RAID), file systems
- that make snapshots or that caches data (e.g. NFS). However, only the names of
- the files are logged if you use the default parameters of the standard Linux
- file system (ext3/ext4);
-- old algorithms: the wipe algorithms are old, and they are not guaranteed to
- work as expected on new storage medias.
-
-
-## The wipe algorithm
-
-nautilus-secure-delete enables you to wipe files and free disk space
-from `nautilus` using the `secure-delete` program written by van Hauser
-/ THC [3]
-
-
-> The deletion process is as follows:
->
-> 1. The overwriting procedure (in the secure mode) does a 38 times
-> overwriting. After each pass, the disk cache is flushed.
-> 2. truncating the file, so that an attacker don't know which
-> disk blocks belonged to the file.
-> 3. renaming of the file, so that an attacker can't draw any conclusion
-> from the filename on the contents of the deleted file.
-> 4. finally deleting the file (unlink).
->
-> (`secure-delete` documentation)
-
-[3]. Secure-delete, van Hauser / THC <vh at thc.org>, 1997-2003
- <http://www.thc.org>
-
-
-# Using `nautilus-secure-delete`
-
-
-## Launching nautilus-secure-delete
-
-
-### Wiping file(s) or directory(es)
-
-Select the file(s) you want to wipe, and right-click on them. If
-`nautilus-secure-delete` is able to wipe them, there will be a "Wipe" entry in
-the context menu.
-
-
-### Wiping available diskspace on storage media
-
-Select a file or a directory which is on the partition on which you want to wipe
-the available diskspace. If `nautilus-secure-delete` is able to wipe it, there
-will be a "Wipe available diskspace" entry in the context menu.
-
-
-## The confirmation dialog
-
-Once you click a menu item, a confirmation dialog will appear, where you can
-confirm or abort the wipe, and choose options (see next section).
-
-
-## The progress dialog
-
-If you confirm the wipe, a dialog will appear to let you see the progression of
-the deletion. For big files or partitions with a lot of available diskspace,
-wiping can take hours.
-
-It's possible, but discouraged, to cancel the wipe process. This would kill the
-underlaying `secure-delete` program and could lead to strange things like files
-partially overwritten but not deleted or big junk files.
-
-When the wipe is finished, a dialog should inform you of the success of the
-deletion.
-
-
-# Configuring `nautilus-secure-delete`
-
-In the confirmation dialog, you can click on the arrow left to the "Options"
-word to display options. To understand these options, you must have a good
-overview of the wipe process. If it's not already the case, please read [[An
-introduction to data deletion]].
-
-
-## Number of passes
-
-You can configure the number of times that the data to be wiped is overwritten
-by new data.
-
-
-38
-
-: Overwriting the data 38 times should prevent data recovery through
- magnetic analysis of the hard drive surface. This is achieved by the
- following procedure:
-
- - 1x overwrite with 0xff
- - 5x random passes
- - 27x overwriting with special values to make the recovery from MFM and
- RLL encoded hard disks hard/impossible - see Gutmann's paper on that
- which is also included.
- - 5x random passes
-
- This is the default value.
-
-2
-
-: Only two passes are written: one mode with 0xff and a final mode random
- values. [FIXME: implications]
-
-1
-
-: Only one random pass is written. Overwriting the data only one time should
- prevent from data recovery by analyzing raw data written on the storage
- media, but is useless against magnetic analysis of the hard drive surface.
-
-
-## Fast and insecure mode (no /dev/urandom, no sync)
-
-Fastens the wipe at the expense of security:
-
-- use a more predictable but faster pseudo-random number generator;
-- do not ensure that overwriting data is actually written on the storage media.
-
-
-## Last pass with zeros instead of random data
-
-Use zeros for the last overwrite, which is the data that will be actually easy
-to read. The default is to use pseudo random data.
-
diff --git a/help/C/nautilus-srm.xml b/help/C/nautilus-srm.xml
new file mode 100644
index 0000000..d2d66fc
--- /dev/null
+++ b/help/C/nautilus-srm.xml
@@ -0,0 +1,527 @@
+<?xml version="1.0"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
+ <!ENTITY legal SYSTEM "legal.xml">
+ <!ENTITY appversion "0.1">
+ <!ENTITY manrevision "0.1">
+ <!ENTITY date "March 2010">
+ <!ENTITY app "<application>Nautilus Secure Delete</application>">
+ <!-- Information about the entities
+ The legal.xml file contains legal information, there is no need to edit the file.
+ Use the appversion entity to specify the version of the application.
+ Use the manrevision entity to specify the revision number of this manual.
+ Use the date entity to specify the release date of this manual.
+ Use the app entity to specify the name of the application. -->
+]>
+<!--
+ (Do not remove this comment block.)
+ Maintained by the GNOME Documentation Project
+ http://developer.gnome.org/projects/gdp
+ Template version: 2.0 beta
+ Template last modified Apr 11, 2002
+-->
+<!-- =============Document Header ============================= -->
+<article id="index" lang="en">
+<!-- please do not change the id; for translations, change lang to -->
+<!-- appropriate code -->
+ <articleinfo>
+ <title>&app; Manual V&manrevision;</title>
+
+ <copyright>
+ <year>2010</year>
+ <holder>The Nautilus Secure Delete Team</holder>
+ </copyright>
+<!-- translators: uncomment this:
+
+ <copyright>
+ <year>2002</year>
+ <holder>ME-THE-TRANSLATOR (Latin translation)</holder>
+ </copyright>
+
+ -->
+<!-- An address can be added to the publisher information. If a role is
+ not specified, the publisher/author is the same for all versions of the
+ document. -->
+ <publisher>
+ <publishername> GNOME Documentation Project </publishername>
+ </publisher>
+
+ &legal;
+ <!-- This file contains link to license for the documentation (GNU FDL), and
+ other legal stuff such as "NO WARRANTY" statement. Please do not change
+ any of this. -->
+
+ <authorgroup>
+ <!-- XXX -->
+ <author>
+ <firstname>The Nautilus Secure Delete Team</firstname>
+ <!--
+ <surname>Writer 2</surname>
+ <affiliation>
+ <orgname>GNOME Documentation Project</orgname>
+ <address> <email>doc-writer2 at gnome.org</email> </address>
+ </affiliation>
+ -->
+ </author>
+ <!--
+ <author>
+ <firstname>Documentation</firstname>
+ <surname>Writer 1</surname>
+ <affiliation>
+ <orgname>GNOME Documentation Project</orgname>
+ <address> <email>doc-writer1 at gnome.org</email> </address>
+ </affiliation>
+ </author>
+ -->
+<!-- This is appropriate place for other contributors: translators,
+ maintainers, etc. Commented out by default.
+
+ <othercredit role="translator">
+ <firstname>Latin</firstname>
+ <surname>Translator 1</surname>
+ <affiliation>
+ <orgname>Latin Translation Team</orgname>
+ <address> <email>translator at gnome.org</email> </address>
+ </affiliation>
+ <contrib>Latin translation</contrib>
+ </othercredit>
+-->
+ </authorgroup>
+
+
+<!-- According to GNU FDL, revision history is mandatory if you are -->
+<!-- modifying/reusing someone else's document. If not, you can omit it. -->
+<!-- Remember to remove the &manrevision; entity from the revision entries other
+-->
+<!-- than the current revision. -->
+<!-- The revision numbering system for GNOME manuals is as follows: -->
+<!-- * the revision number consists of two components -->
+<!-- * the first component of the revision number reflects the release version of the GNOME desktop. -->
+<!-- * the second component of the revision number is a decimal unit that is incremented with each revision of the manual. -->
+<!-- For example, if the GNOME desktop release is V2.x, the first version of the manual that -->
+<!-- is written in that desktop timeframe is V2.0, the second version of the manual is V2.1, etc. -->
+<!-- When the desktop release version changes to V3.x, the revision number of the manual changes -->
+<!-- to V3.0, and so on. -->
+<!-- XXX
+ <revhistory>
+ <revision>
+ <revnumber>MY-GNOME-APPLICATION Manual V&manrevision;</revnumber>
+ <date>&date;</date>
+ <revdescription>
+ <para role="author">Documentation Writer 2
+ <email>docwriter2 at gnome.org</email>
+ </para>
+ <para role="publisher">GNOME Documentation Project</para>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>Full title of previous manual.</revnumber>
+ <date>Release date of previous manual.</date>
+ <revdescription>
+ <para role="author">Documentation Writer 1
+ <email>docwriter1 at gnome.org</email>
+ </para>
+ <para role="publisher">GNOME Documentation Project</para>
+ </revdescription>
+ </revision>
+ </revhistory>
+-->
+
+ <releaseinfo>This manual describes version &appversion; of Nautilus Secure Delete
+ </releaseinfo>
+ <legalnotice>
+ <title>Feedback</title>
+ <!-- XXX: FIXME -->
+ <para>To report a bug or make a suggestion regarding the &app; application or
+ this manual, follow the directions in the <ulink url="ghelp:gnome-feedback"
+ type="help">GNOME Feedback Page</ulink>.
+ </para>
+<!-- Translators may also add here feedback address for translations -->
+ </legalnotice>
+ </articleinfo>
+
+ <indexterm zone="index">
+ <primary>Nautilus Secure Delete</primary>
+ </indexterm>
+ <indexterm zone="index">
+ <primary>nautilus-secure-delete</primary>
+ </indexterm>
+
+<!-- ============= Document Body ============================= -->
+<!-- ============= Introduction ============================== -->
+<!-- Use the Introduction section to give a brief overview of what
+ the application is and what it does. -->
+ <sect1 id="nautilus-secure-delete-overview">
+ <title>Overview</title>
+ <para>
+ &app; allows you to wipe files or
+ available diskspace from <application>Nautilus</application>.
+ </para>
+ <para>
+ Usually when you delete a file, even when bypassing the trash, it's
+ not accessible anymore, but its content still exists on the media
+ that contained it until a new file is written over it.
+ Consequently, it can be quite easy to recover it.
+ </para>
+ <para>
+ &app; enables you to wipe files
+ and available disk space from <application>Nautilus</application> using the
+ <application>secure-delete</application> program written by van Hauser /
+ THC
+ <footnote>
+ <para>
+ [1]. Secure-delete, van Hauser / THC <email>vh at thc.org</email>,
+ 1997-2003
+ <ulink url="http://www.thc.org">
+ <literal>http://www.thc.org</literal>
+ </ulink>
+ </para>
+ </footnote>.
+ </para>
+ </sect1>
+
+ <sect1 id="nautilus-secure-delete-data-deletion-intro">
+ <title>An introduction to data deletion</title>
+ <sect2 id="nautilus-secure-delete-not-the-data">
+ <title>Deleting doesn't affect data</title>
+ <para>
+ When you delete a file, even when bypassing or emptying the trash,
+ you only tell your computer that you don't care anymore for the
+ file. The file's entry is removed from the list of existing files
+ but the content of the file remains on the storage medium. The data
+ will remain there until the operating system reuses the space for
+ new data.
+ </para>
+ <para>
+ This could take weeks, months or years before this space is
+ actually used for new data, actually overwriting the content of the
+ deleted file. Until then, it's possible to recover it by reading
+ directly the data on the storage media. That's a quite simple
+ operation, automated by numerous softwares.
+ </para>
+ </sect2>
+ <sect2 id="nautilus-secure-delete-an-answer">
+ <title>An answer : overwriting data several times</title>
+ <para>
+ If you want to make the content of a file really hard to recover,
+ you have to overwrite it with other data. But that's not enough. On
+ a magnetic hard disk, it's known
+ <footnote>
+ <para>
+ [2]. Peter Gutmann: Secure Deletion of Data from Magnetic and
+ Solid-State Memory, 6th Usenix Security Symposium, 1996
+ <ulink url="http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html">
+ <literal>http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html</literal>
+ </ulink>
+ </para>
+ </footnote>
+ that the content can still be
+ recovered by doing magnetic analysis of the hard disk surface. To
+ address this issue, it's possible to overwrite several times the
+ content to be deleted. That process is called "wiping".
+ </para>
+ <para>
+ If some sensible files have been already deleted without paying
+ attention to this issue, some of their data probably remains on the
+ storage media. It's thus also useful to wipe all the available free
+ space of a storage media.
+ </para>
+ </sect2>
+ <sect2 id="nautilus-secure-delete-limitations">
+ <title>Limitations</title>
+ <para>
+ This section is quite technical. In a nutshell, there's a lot of
+ limitations, so using this tool without setting up a complete
+ security policy will probably be useless.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Temporary files and disks: lots of programs writes temporary and
+ backup files. This means that the sensitive data you want do delete
+ probably exists in an other form somewhere on your computer;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ swap space: most operating systems could save data they are working
+ on on a part of the hard disk called swap space. Your sensitive
+ data could exist there;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ storage media features: modern storage mediums often reorganize
+ their content, e.g. to spread the writings over the media or to
+ hide defective places to the operating system. Consequently, you
+ can't be sure that the actual place occupied by your sensitive data
+ was wiped;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <!-- XXX: formatting -->
+ journalized file systems: modern file systems log modifications of
+ the files to ease recovering after a crash. This could make wiping
+ inefficient. The same kind of problem exists with redundant file
+ systems (e.g. RAID), file systems that make snapshots or that
+ caches data (e.g. NFS). However, only the names of the files are
+ logged if you use the default parameters of the standard Linux file
+ system (ext3/ext4);
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ old algorithms: the wipe algorithms are old, and they are not
+ guaranteed to work as expected on new storage medias.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+ <sect2>
+ <title>The wipe algorithm</title>
+ <para>
+ nautilus-secure-delete enables you to wipe files and free disk
+ space from <application>Nautilus</application> using the
+ <application>secure-delete</application> program written by van Hauser /
+ THC
+ <footnote>
+ <para>
+ Secure-delete, van Hauser / THC <email>vh at thc.org</email>,
+ 1997-2003
+ <ulink url="http://www.thc.org">
+ <literal>http://www.thc.org</literal>
+ </ulink>
+ </para>
+ </footnote>
+ </para>
+ <blockquote>
+ <attribution><application>secure-delete</application> documentation</attribution>
+ <para>The deletion process is as follows:</para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The overwriting procedure (in the secure mode) does a 38 times
+ overwriting. After each pass, the disk cache is flushed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ truncating the file, so that an attacker don't know which
+ disk blocks belonged to the file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ renaming of the file, so that an attacker can't draw any conclusion
+ from the filename on the contents of the deleted file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ finally deleting the file (unlink).
+ </para>
+ </listitem>
+ </orderedlist>
+ </blockquote>
+ </sect2>
+ </sect1>
+
+ <sect1 id="nautilus-secure-delete-usage">
+ <title>Using &app;</title>
+ <sect2 id="nautilus-secure-delete-start">
+ <title>Launching &app;</title>
+ <sect3 id="nautilus-secure-delete-srm">
+ <title>Wiping file(s) or directory(es)</title>
+ <para>
+ Select the file(s) you want to wipe, and right-click on them. If
+ &app; is able to wipe them,
+ there will be a <guimenuitem>Wipe</guimenuitem> entry in the context menu.
+ </para>
+ </sect3>
+ <sect3 id="nautilus-secure-delete-sfill">
+ <title>Wiping available diskspace on storage media</title>
+ <para>
+ Select a file or a directory which is on the partition on which you
+ want to wipe the available diskspace, and right-click on it. If
+ &app; is able to wipe it, there
+ will be a <guimenuitem>Wipe available diskspace</guimenuitem> entry in the context
+ menu.
+ </para>
+ </sect3>
+ </sect2>
+ <sect2 id="nautilus-secure-delete-confirmation-dialog">
+ <title>The confirmation dialog</title>
+ <para>
+ Once you click a menu item, a confirmation dialog will appear,
+ where you can confirm or abort the wipe, and choose options (see
+ <xref linkend="nautilus-secure-delete-config" />).
+ </para>
+ </sect2>
+ <sect2 id="nautilus-secure-delete-progress-dialog">
+ <title>The progress dialog</title>
+ <para>
+ If you confirm the wipe, a dialog will appear to let you see the
+ progression of the deletion. For big files or partitions with a lot
+ of available diskspace, wiping can take hours.
+ </para>
+ <para>
+ It's possible, but discouraged, to cancel the wipe process. This
+ would kill the underlaying <application>secure-delete</application> program
+ and could lead to strange things like files partially overwritten
+ but not deleted or big junk files.
+ </para>
+ <para>
+ When the wipe is finished, a dialog should inform you of the
+ success of the deletion.
+ </para>
+ </sect2>
+ </sect1>
+ <sect1 id="nautilus-secure-delete-config">
+ <title>Configuring &app;</title>
+ <para>
+ In the confirmation dialog, you can click on the arrow left to the
+ <guilabel>Options</guilabel> word to display options. To understand these
+ options, you must have a good overview of the wipe process. If it's
+ not already the case, please read <xref linkend="nautilus-secure-delete-data-deletion-intro" />.
+ </para>
+ <sect2 id="nautilus-secure-delete-passes">
+ <title>Number of passes</title>
+ <para>
+ You can configure the number of times that the data to be wiped is
+ overwritten by new data.
+ </para>
+
+ <variablelist>
+ <title>Number of passes</title>
+ <varlistentry>
+ <term>38</term>
+ <listitem>
+ <para>
+ Overwriting the data 38 times should prevent data recovery
+ through magnetic analysis of the hard drive surface. This is
+ achieved by the following procedure:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ 1x overwrite with 0xff
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 5x random passes
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 27x overwriting with special values to make the recovery from MFM
+ and RLL encoded hard disks hard/impossible - see Gutmann's paper on
+ that which is also included.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 5x random passes
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This is the default value.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>2</term>
+ <listitem>
+ <para>
+ Only two passes are written: one mode with 0xff and a final mode
+ random values. [FIXME: implications]
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>1</term>
+ <listitem>
+ <para>
+ Only one random pass is written. Overwriting the data only one
+ time should prevent from data recovery by analyzing raw data
+ written on the storage media, but is useless against magnetic
+ analysis of the hard drive surface.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect2>
+ <sect2 id="nautilus-secure-delete-fast-mode">
+ <title>Fast and insecure mode (no /dev/urandom, no sync)</title>
+ <para>
+ Fastens the wipe at the expense of security:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ use a more predictable but faster pseudo-random number generator;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ do not ensure that overwriting data is actually written on the
+ storage media.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+ <sect2 id="nautilus-secure-delete-zeros">
+ <title>Last pass with zeros instead of random data</title>
+ <para>
+ Use zeros for the last overwrite, which is the data that will be
+ actually easy to read. The default is to use pseudo random data.
+ </para>
+ </sect2>
+ </sect1>
+<!-- ============= Bugs ================================== -->
+<!-- This section is optional and is commented out by default.
+ You can use it to describe known bugs and limitations of the
+ program if there are any - please be frank and list all
+ problems you know of.
+
+ <sect1 id="mayapp-bugs">
+ <title>Known Bugs and Limitations</title>
+ <para> </para>
+ </sect1>
+-->
+<!-- ============= About ================================== -->
+<!-- This section contains info about the program (not docs), such as
+ author's name(s), web page, license, feedback address. This
+ section is optional: primary place for this info is "About.." box of
+ the program. However, if you do wish to include this info in the
+ manual, this is the place to put it. Alternatively, you can put this
+ information in the title page.-->
+ <sect1 id="nautilus-secure-delete-about">
+ <title>About &app;</title>
+ <para> &app; was written by The Nautilus Secure Delete Team
+ <!-- XXX
+ (<email>hacker at gnome.org</email>). To find more information about
+ &app;, please visit the
+ <ulink url="http://www.my-gnome-app.org" type="http">MY-GNOME-APP Web
+ page</ulink>.
+ -->
+ </para>
+ <!--
+ <para>
+ To report a bug or make a suggestion regarding this application or
+ this manual, follow the directions in this
+ <ulink url="ghelp:gnome-feedback" type="help">document</ulink>.
+ </para>
+ -->
+ <para>
+ This program is distributed under the terms of the GNU
+ General Public license as published by the Free Software
+ Foundation; either version 3 of the License, or (at your option)
+ any later version. A copy of this license can be found at this
+ <ulink url="ghelp:gpl" type="help">link</ulink>, or in the file
+ COPYING included with the source code of this program.
+ </para>
+ </sect1>
+</article>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/nautilus-wipe.git
More information about the Pkg-privacy-commits
mailing list