/usr/share/doc/kde/HTML/en/kwatchgnupg/index.docbook is in kleopatra 4:4.14.1-1+deb8u1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 | <?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
<!ENTITY gnupg "<acronym>GnuPG</acronym>">
<!ENTITY gpgconf "<application>GPGConf</application>">
<!ENTITY watchgnupg "<application>WatchGnuPG</application>">
<!ENTITY kwatchgnupg "<application>KWatchGnuPG</application>">
<!ENTITY kappname "&kwatchgnupg;">
<!ENTITY package "kdepim">
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE">
]>
<book id="kwatchgnupg" lang="&language;">
<bookinfo id="kwatchgnupginfo">
<title>The &kwatchgnupg; Handbook</title>
<authorgroup>
<author>
<firstname>Marc</firstname>
<surname>Mutz</surname>
<affiliation>
<address>&Marc.Mutz.mail;</address>
</affiliation>
</author>
<othercredit role="developer">
<firstname>Steffen</firstname>
<surname>Hansen</surname>
<contrib>Developer</contrib>
<affiliation>
<address>&Steffen.Hansen.mail;</address>
</affiliation>
</othercredit>
<othercredit role="developer">
<firstname>David</firstname>
<surname>Faure</surname>
<affiliation>
<address>&David.Faure.mail;</address>
</affiliation>
<contrib>Developer</contrib>
</othercredit>
<!-- TRANS:ROLES_OF_TRANSLATORS -->
</authorgroup>
<legalnotice>&GPLNotice;</legalnotice>
<date>2013-07-03</date>
<releaseinfo>1.0 (&kde; 4.11)</releaseinfo>
<abstract>
<para>
&kwatchgnupg; is a simple &gnupg; log viewer.
</para>
</abstract>
<keywordset>
<keyword>KDE</keyword>
<keyword>Kapp</keyword>
<keyword>gpg</keyword>
<keyword>gpgsm</keyword>
<keyword>GnuPG</keyword>
<keyword>Log viewer</keyword>
</keywordset>
</bookinfo>
<chapter id="introduction"> <title>Introduction</title>
<para>&kwatchgnupg; is simple &gnupg; log viewer for the
&gnupg; versions 1.4 and 2.0. It works as a &GUI;
wrapper around the command line tool &watchgnupg;, which listens on a
socket for log lines from the &gnupg; backend applications. See
<userinput>info watchgnupg</userinput> for more information about
&watchgnupg;.</para>
<para>&kwatchgnupg; can be started from the
<menuchoice><guimenu>Tools</guimenu><guimenuitem>GnuPG Log Viewer</guimenuitem></menuchoice> menu of both
&kleopatra; and &kmail;, as well as from the command
line. The &kwatchgnupg; executable is named
<userinput>kwatchgnupg</userinput>.
</para>
</chapter>
<chapter id="mainfunc"><title>Main Functions</title>
<sect1 id="mainfunc.viewing"><title>Viewing the Log</title>
<para>
&kwatchgnupg;'s main function is of course to present the &gnupg;
debugging and logging information to the user. The main window is
divided into a large text viewing area, where &gnupg; messages will
appear as they are generated, a toolbar giving quick access to the most
often needed functions, as well as the obligatory menu bar.
</para>
<para>
Each line in the text view is normally prefixed with a
<acronym>FD</acronym> identifier and a time stamp in ISO format. The
<acronym>FD</acronym> identifier can be used to distinguish between
output from different &gnupg; instances running in parallel. Following
the timestamp is the name of the component that is the source of the
log line, together with some internal information in sqare brackets,
followed by the original debugging or log output as printed by the
component.
</para>
<para>
By default, the number of log lines that are kept in the history is
limited to 10000 lines. You can configure the history size in the
configuration dialog.
</para>
</sect1>
<sect1 id="mainfunc.saving">
<title>Saving the Contents of the Log Window to a File</title>
<para>
Sometimes it might be convenient to save the current log window
contents to a file, ⪚ to mail it to the developers as part of a bug
report. There are two ways to achieve this in &kwatchgnupg;:
</para>
<para>
First, you can choose
<menuchoice><guilabel>File</guilabel><guimenuitem>Save
As...</guimenuitem></menuchoice> (or the corresponding toolbar icon)
to save the complete log window contents to a file. You will be
prompted to specify a save file location.
</para>
<para>
Second, you can select the interesting lines with normal left-mouse
selection and paste them into a word processor or mail user agent,
just like any other text. You should make sure, though, that lines are
not broken, since this reduces the readability of the log.
</para>
</sect1>
<sect1 id="mainfunc.clear"><title>Clearing the Log Window</title>
<para>
For convenience, you can instruct &kwatchgnupg; to clear the log
window using <menuchoice><guimenu>File</guimenu><guimenuitem>Clear
History</guimenuitem></menuchoice> (or the corresponding toolbar
icon).
</para>
<para>
Use this prior to starting the crypto operation that you want to
monitor to get only the output from that operation. You can then save
the log using <menuchoice><guimenu>File</guimenu><guimenuitem>Save
As...</guimenuitem></menuchoice> as described above.
</para>
<para>
Clearing the log discards any previous log window contents. If you are
unsure about whether you'll need the current contents afterwards, you
should save them to a file (see above) before clearing.
</para>
</sect1>
</chapter>
<chapter id="configure"><title>Configuring &kwatchgnupg;</title>
<para>
To configure &kwatchgnupg;, select
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
&kwatchgnupg;</guimenuitem></menuchoice>, or the corresponding toolbar
icon. &kwatchgnupg;'s configure dialog is divided into two parts, each
of which will be described below.
</para>
<sect1 id="configure.watchgnupg"><title>&watchgnupg; Settings</title>
<para>
&watchgnupg; is the process that actually monitors the logging socket
for activity and formats the lines as seen in the &kwatchgnupg; text
view. Settings in this group are passed down to the backend using
the &gpgconf; mechanism.
</para>
<para>
<guilabel>Executable</guilabel> contains the path to the &watchgnupg;
application. If &watchgnupg; is in your <varname>$PATH</varname>, you
can keep the default <userinput>watchgnupg</userinput>. If
&watchgnupg; is not in your <varname>$PATH</varname>, or if you have
more than one version installed, enter the absolute filename of the
watchgnupg executable here.
</para>
<para>
<guilabel>Socket</guilabel> contains the socket that &watchgnupg;
should listen on. A change here is distributed to all &gnupg; backend
modules using &gpgconf;, so you don't need to change this setting if
your &gnupg; config files have another <varname>log-file</varname>
set.
</para>
<para>
<guilabel>Default log level</guilabel> determines the amount of
logging information returned by the backend modules. See the
&watchgnupg; documentation for what level includes which
information. A change here is distributed to all &gnupg; backend
modules using &gpgconf;, so you don't need to change this setting if
your &gnupg; config files have another <varname>log-level</varname>
set.
</para>
</sect1>
<sect1 id="configure.logwindow"><title>Log Window Settings</title>
<para>
Here, you can configure the size of the history buffer, &ie; the
number of log lines that is kept. If more lines have been emitted by
the &gnupg; backend since the last clearance of the history, then the
oldest lines are discarded until there is enough room for the new
lines again.
</para>
<para>
You can disable the history size limit by clicking <guibutton>Set
Unlimited</guibutton>. Note, however, that &kwatchgnupg;'s memory
consumption will grow with the number of lines it currently
displays. If you use an unlimited history size, then make sure to run
&kwatchgnupg; only for short operations, or regularly clear the
history manually.
</para>
</sect1>
</chapter>
<chapter id="credits-and-license">
<title>Credits and License</title>
<para>&kwatchgnupg; copyright 2004 Klarälvdalens Datakonsult AB</para>
<para>Documentation copyright 2004 Klarälvdalens Datakonsult AB</para>
<itemizedlist>
<title>Contributors</title>
<listitem>
<para>&Steffen.Hansen; <email>hansen@kde.org</email></para>
</listitem>
<listitem>
<para>&Marc.Mutz; &Marc.Mutz.mail;</para>
</listitem>
<listitem>
<para>&David.Faure; &David.Faure.mail;</para>
</listitem>
</itemizedlist>
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
&underFDL;
&underGPL;
</chapter>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
// vim:ts=2:sw=2:tw=78:noet
-->
|