1 \input texinfo @c -*-texinfo-*-
3 @setfilename ../info/pgg
9 This file describes the PGG.
11 Copyright (C) 2003 Free Software Foundation, Inc.
12 Copyright (C) 2001 Daiki Ueno.
15 Permission is granted to copy, distribute and/or modify this document
16 under the terms of the GNU Free Documentation License, Version 1.1 or
17 any later version published by the Free Software Foundation; with no
18 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
19 Texts. A copy of the license is included in the section entitled ``GNU
20 Free Documentation License''.
26 * PGG: (pgg). Emacs interface to various PGP implementations.
29 @settitle PGG @value{VERSION}
38 @vskip 0pt plus 1filll
45 This manual describes PGG. PGG is an interface library between Emacs
46 and various tools for secure communication. PGG also provides a simple
47 user interface to encrypt, decrypt, sign, and verify MIME messages.
50 * Overview:: What PGG is.
51 * Prerequisites:: Complicated stuff you may have to do.
52 * How to use:: Getting started quickly.
54 * Parsing OpenPGP packets::
62 PGG is an interface library between Emacs and various tools for secure
63 communication. Even though Mailcrypt has similar feature, it does not
64 deal with detached PGP messages, normally used in PGP/MIME
65 infrastructure. This was the main reason why I wrote the new library.
67 PGP/MIME is an application of MIME Object Security Services (RFC1848).
68 The standard is documented in RFC2015.
71 @chapter Prerequisites
73 PGG requires at least one implementation of privacy guard system.
74 This document assumes that you have already obtained and installed them
75 and that you are familiar with its basic functions.
77 By default, PGG uses GnuPG, but Pretty Good Privacy version 2 or version
78 5 are also supported. If you are new to such a system, I recommend that
79 you should look over the GNU Privacy Handbook (GPH) which is available
80 at @uref{http://www.gnupg.org/gph/}.
85 The toplevel interface of this library is quite simple, and only
86 intended to use with public-key cryptographic operation.
88 To use PGG, evaluate following expression at the beginning of your
95 If you want to check existence of pgg.el at runtime, instead you can
96 list autoload setting for desired functions as follows.
99 (autoload 'pgg-encrypt-region "pgg"
100 "Encrypt the current region." t)
101 (autoload 'pgg-decrypt-region "pgg"
102 "Decrypt the current region." t)
103 (autoload 'pgg-sign-region "pgg"
104 "Sign the current region." t)
105 (autoload 'pgg-verify-region "pgg"
106 "Verify the current region." t)
107 (autoload 'pgg-insert-key "pgg"
108 "Insert the ASCII armored public key." t)
109 (autoload 'pgg-snarf-keys-region "pgg"
110 "Import public keys in the current region." t)
115 * Selecting an implementation::
116 * Caching passphrase::
117 * Default user identity::
121 @section User Commands
123 At this time you can use some cryptographic commands. The behavior of
124 these commands relies on a fashion of invocation because they are also
125 intended to be used as library functions. In case you don't have the
126 signer's public key, for example, the function @code{pgg-verify-region}
127 fails immediately, but if the function had been called interactively, it
128 would ask you to retrieve the signer's public key from the server.
130 @deffn Command pgg-encrypt-region start end recipients &optional sign
131 Encrypt the current region between @var{start} and @var{end} for
132 @var{recipients}. When the function were called interactively, you
133 would be asked about the recipients.
135 If encryption is successful, it replaces the current region contents (in
136 the accessible portion) with the resulting data.
138 If optional argument @var{sign} is non-@code{nil}, the function is
139 request to do a combined sign and encrypt. This currently only work
143 @deffn Command pgg-decrypt-region start end
144 Decrypt the current region between @var{start} and @var{end}. If
145 decryption is successful, it replaces the current region contents (in
146 the accessible portion) with the resulting data.
149 @deffn Command pgg-sign-region start end &optional cleartext
150 Make the signature from text between @var{start} and @var{end}. If the
151 optional third argument @var{cleartext} is non-@code{nil}, or the
152 function is called interactively, it does not create a detached
153 signature. In such a case, it replaces the current region contents (in
154 the accessible portion) with the resulting data.
157 @deffn Command pgg-verify-region start end &optional signature fetch
158 Verify the current region between @var{start} and @var{end}. If the
159 optional third argument @var{signature} is non-@code{nil}, or the function
160 is called interactively, it is treated as the detached signature of the
163 If the optional 4th argument @var{fetch} is non-@code{nil}, or the
164 function is called interactively, we attempt to fetch the signer's
165 public key from the key server.
168 @deffn Command pgg-insert-key
169 Retrieve the user's public key and insert it as ASCII-armored format.
172 @deffn Command pgg-snarf-keys-region start end
173 Collect public keys in the current region between @var{start} and
174 @var{end}, and add them into the user's keyring.
177 @node Selecting an implementation
178 @section Selecting an implementation
180 Since PGP has a long history and there are a number of PGP
181 implementations available today, the function which each one has differs
182 considerably. For example, if you are using GnuPG, you know you can
183 select cipher algorithm from 3DES, CAST5, BLOWFISH, and so on, but on
184 the other hand the version 2 of PGP only supports IDEA.
186 By default, if the variable @code{pgg-scheme} is not set, PGG searches the
187 registered scheme for an implementation of the requested service
188 associated with the named algorithm. If there are no match, PGG uses
189 @code{pgg-default-scheme}. In other words, there are two options to
190 control which command is used to process the incoming PGP armors. One
191 is for encrypting and signing, the other is for decrypting and
195 Force specify the scheme of PGP implementation for decrypting and verifying.
196 The value can be @code{gpg}, @code{pgp}, and @code{pgp5}.
199 @defvar pgg-default-scheme
200 Force specify the scheme of PGP implementation for encrypting and signing.
201 The value can be @code{gpg}, @code{pgp}, and @code{pgp5}.
204 @node Caching passphrase
205 @section Caching passphrase
207 PGG provides a simple passphrase caching mechanism. If you want to
208 arrange the interaction, set the variable @code{pgg-read-passphrase}.
210 @defvar pgg-cache-passphrase
211 If non-@code{nil}, store passphrases. The default value of this
212 variable is @code{t}. If you were worry about security issue, however,
213 you could stop caching with setting it @code{nil}.
216 @defvar pgg-passphrase-cache-expiry
217 Elapsed time for expiration in seconds.
220 @node Default user identity
221 @section Default user identity
223 The PGP implementation is usually able to select the proper key to use
224 for signing and decryption, but if you have more than one key, you may
225 need to specify the key id to use.
227 @defvar pgg-default-user-id
228 User ID of your default identity. It defaults to the value returned
229 by @samp{(user-login-name)}. You can customize this variable.
232 @defvar pgg-gpg-user-id
233 User ID of the GnuPG default identity. It defaults to @samp{nil}.
234 This overrides @samp{pgg-default-user-id}. You can customize this
238 @defvar pgg-pgp-user-id
239 User ID of the PGP 2.x/6.x default identity. It defaults to
240 @samp{nil}. This overrides @samp{pgg-default-user-id}. You can
241 customize this variable.
244 @defvar pgg-pgp5-user-id
245 User ID of the PGP 5.x default identity. It defaults to @samp{nil}.
246 This overrides @samp{pgg-default-user-id}. You can customize this
251 @chapter Architecture
253 PGG introduces the notion of a "scheme of PGP implementation" (used
254 interchangeably with "scheme" in this document). This term refers to a
255 singleton object wrapped with the luna object system.
257 Since PGG was designed for accessing and developing PGP functionality,
258 the architecture had to be designed not just for interoperability but
259 also for extensiblity. In this chapter we explore the architecture
260 while finding out how to write the PGG backend.
269 @section Initializing
271 A scheme must be initialized before it is used.
272 It had better guarantee to keep only one instance of a scheme.
274 The following code is snipped out of @file{pgg-gpg.el}. Once an
275 instance of @code{pgg-gpg} scheme is initialized, it's stored to the
276 variable @code{pgg-scheme-gpg-instance} and will be reused from now on.
279 (defvar pgg-scheme-gpg-instance nil)
281 (defun pgg-make-scheme-gpg ()
282 (or pgg-scheme-gpg-instance
283 (setq pgg-scheme-gpg-instance
284 (luna-make-entity 'pgg-scheme-gpg))))
287 The name of the function must follow the
288 regulation---@code{pgg-make-scheme-} follows the backend name.
290 @node Backend methods
291 @section Backend methods
293 In each backend, these methods must be present. The output of these
294 methods is stored in special buffers (@ref{Getting output}), so that
295 these methods must tell the status of the execution.
297 @deffn Method pgg-scheme-lookup-key scheme string &optional type
298 Return keys associated with @var{string}. If the optional third
299 argument @var{type} is non-@code{nil}, it searches from the secret
303 @deffn Method pgg-scheme-encrypt-region scheme start end recipients &optional sign
304 Encrypt the current region between @var{start} and @var{end} for
305 @var{recipients}. If @var{sign} is non-@code{nil}, do a combined sign
306 and encrypt. If encryption is successful, it returns @code{t},
307 otherwise @code{nil}.
310 @deffn Method pgg-scheme-decrypt-region scheme start end
311 Decrypt the current region between @var{start} and @var{end}. If
312 decryption is successful, it returns @code{t}, otherwise @code{nil}.
315 @deffn Method pgg-scheme-sign-region scheme start end &optional cleartext
316 Make the signature from text between @var{start} and @var{end}. If the
317 optional third argument @var{cleartext} is non-@code{nil}, it does not
318 create a detached signature. If signing is successful, it returns
319 @code{t}, otherwise @code{nil}.
322 @deffn Method pgg-scheme-verify-region scheme start end &optional signature
323 Verify the current region between @var{start} and @var{end}. If the
324 optional third argument @var{signature} is non-@code{nil}, it is treated
325 as the detached signature of the current region. If the signature is
326 successfully verified, it returns @code{t}, otherwise @code{nil}.
329 @deffn Method pgg-scheme-insert-key scheme
330 Retrieve the user's public key and insert it as ASCII-armored format.
331 On success, it returns @code{t}, otherwise @code{nil}.
334 @deffn Method pgg-scheme-snarf-keys-region scheme start end
335 Collect public keys in the current region between @var{start} and
336 @var{end}, and add them into the user's keyring.
337 On success, it returns @code{t}, otherwise @code{nil}.
341 @section Getting output
343 The output of the backend methods (@ref{Backend methods}) is stored in
344 special buffers, so that these methods must tell the status of the
347 @defvar pgg-errors-buffer
348 The standard error output of the execution of the PGP command is stored
352 @defvar pgg-output-buffer
353 The standard output of the execution of the PGP command is stored here.
356 @defvar pgg-status-buffer
357 The rest of status information of the execution of the PGP command is
361 @node Parsing OpenPGP packets
362 @chapter Parsing OpenPGP packets
364 The format of OpenPGP messages is maintained in order to publish all
365 necessary information needed to develop interoperable applications.
366 The standard is documented in RFC 2440.
368 PGG has its own parser for the OpenPGP packets.
370 @defun pgg-parse-armor string
371 List the sequence of packets in @var{string}.
374 @defun pgg-parse-armor-region start end
375 List the sequence of packets in the current region between @var{start}
379 @defvar pgg-ignore-packet-checksum
380 If non-@code{nil}, don't check the checksum of the packets.
384 @chapter Function Index
388 @chapter Variable Index
398 arch-tag: 0c205838-34b9-41a5-b9d7-49ae57ccac85