-
--- 2:2.1.6+ds1-1/lang/ar/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,87 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Message Composition</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using Enigmail when composing messages</h3>
-
- <dl>
- <dt>Enigmail menu in Mail/Compose window</dt>
-
- <dd>
- <dl>
- <dt>Sign message</dt>
-
- <dd>Enable/Disable sending signed mail. User is notified, if signing fails.</dd>
-
- <dt>Encrypt message</dt>
- <dd>
- <p>Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.</p>
-
- <p>If <em>Display selection when necessary</em> is set in <strong>Preferences -> Key Selection tab</strong>, a list of keys will pop up if there are addresses in the list of recipients for the message for whom you have no public key.</p>
-
- <p>If <em>Never display OpenPGP key selection dialog</em> is set in <strong>Preferences -> Key Selection tab</strong>, and there are addresses in the list of recipients for the message for whom you have no public key, the message will be sent unencrypted.</p>
- </dd>
-
- <dt>Use PGP/MIME for this message</dt>
-
- <dd>
- Enable/Disable the use of <a href="https://tools.ietf.org/html/rfc3156" target="_blank">PGP/MIME</a> for this message.
-
- <p>If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.</p>
-
- <p>This feature is dependent on the settings in <strong>Preferences -> PGP/MIME tab</strong> being set to <em>Allow to use PGP/MIME</em> or <em>Always use PGP/MIME</em>.</p>
- </dd>
-
- <dt>Default composition options</dt>
-
- <dd>
- <ul>
- <li><strong>Signing/Encryption Options...</strong>: shortcut to <strong>Account Settings -> OpenPGP Options.</strong></li>
-
- <li><strong>Send options...</strong>: shortcut to <strong>Preferences -> Send</strong> tab.</li>
-
- <li><strong>Key selection options...</strong>: shortcut to <strong>Preferences -> Key Selection</strong> tab.</li>
-
- <li><strong>PGP/MIME options...</strong>: shortcut to <strong>Preferences -> PGP/MIME</strong> tab.</li>
- </ul>
- </dd>
-
- <dt>Undo encryption</dt>
-
- <dd>
- <p>If there is a failure when actually sending mail, such as the POP server not accepting the request, Enigmail will not know about it, and the encrypted message will continue to be displayed in the Compose window. Choosing this menu item will undo the encryption/signing, reverting the Compose window back to its original text.</p>
-
- <p><em>As a temporary fix, this option may also be used to decrypt the quoted text when replying to encrypted messages. Enigmail should automatically decrypt the quoted message, but if that fails for some reason, you can use this menu item to force it.</em></p>
- </dd>
-
- <dt>Insert public key</dt>
-
- <dd>insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.</dd>
-
- <dt>Clear save passphrase</dt>
-
- <dd>Clears cached passphrase. Useful if you have multiple passphrases.</dd>
-
- <dt>Help</dt>
-
- <dd>Displays Help information from the website (this page).</dd>
- </dl>
- </dd>
- </dl>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/ar/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=خصوصية OpenPGP
+Not Found
\ No newline at end of file
-
--- 2:2.1.6+ds1-1/lang/ca/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,69 +0,0 @@
-<html>
-<head><title>Ajuda Enigmail: Editor de regles</title>
-</head>
-<body>
-<h1>Ajuda Enigmail</h1>
-
-<h3>Emprant l'editor de regles de l'Enigmail</h3>
-<p>En el editor de regles podeu indicar que, en funció del destinatari, s'activi el xifratge,
-la signatura i el PGP/MIME, i definir quina clau OpenPGP emprar. Cada regla consisteix
-en 5 camps que es representen en una línia individual:
-</p>
-<ul>
- <li><span style="font-weight: bold;">Correu electrònic</span>: l'adreça(es) dels camps
- A: (To), Còpia: (Cc) i Còpia invisible: (Bcc) a comprovar. La coincidència es basa en <span
- style="font-style: italic;">subcadenes</span> (es poden trobar més detalls al diàleg
- d'edició de regles)
- </li>
- <li><span style="font-weight: bold;">Clau(s) OpenPGP</span>: una llista de les identificacions
- de claus OpenPGP per a usar amb el destinatari
- </li>
- <li><span style="font-weight: bold;">Signatura</span>: activa o desactiva
- la signatura del missatge. Això preval sobre el que s'ha indicat a la
- finestra de redacció del missatge. El valors són:
- <ul>
- <li><i>Mai</i>: desactiva la signatura, inclòs si s'ha activat a la finestra
- de redacció del missatge (preval sobre els altres valors)<br>
- </li>
- <li><i>Possible</i>: deixa la signatura
- tal com s'ha indicat a la finestra de redacció del missatge
- </li>
- <li><i>Sempre</i>: activa la signatura, inclòs si <span
- style="font-style: italic;">no</span> s'ha activat a la finestra de redacció del
- missatge
- </li>
- </ul>
- </li>
-</ul>
-<div style="margin-left: 40px;">Aquests paràmetres de signatura s'aplicaran a totes les
-regles que coincideixin. Si una de les regles desactiva la signatura, el missatge no es
-signarà, a menys que altres regles indiquin <i>Sempre</i>.<br>
-</div>
-<ul>
- <li><span style="font-weight: bold;">Xifratge</span>: activa o desactiva
- el xifratge del missatge. Els paràmetres permesos i els seu significat són
- els mateixos que per la signatura de missatge.</li>
- <li><span style="font-weight: bold;">PGP/MIME</span>: activa o desactiva
- l'ús de la codificació PGP/MIME (RFC 3156) del missatge.
- Si el el PGP/MIME està desactivat, els missatges es codifiquen amb el
- "PGP inserit". Els paràmetres permesos i els seu significat són
- els mateixos que per la signatura de missatge.
- </li>
-</ul>
-<p>Les regles es processen segons l'ordre mostrat a la llista. Quan una regla
-coincideix amb un destinatari i conté un identificador de clau OpenPGP, a més d'emprar
-l'dentificador de clau indicat, el destinatari no es tornarà a considerar en processar les
-regles seguents.</p>
-<p><i>Nota:</i> L'editor de regles encara no està acabat. És posible escriure les regles
-més avançades editant directament el fitxer de regles (aquestes regles no hauríen
-de tornar-se a editar en el editor de regles).
-<a
-href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Més informació</a>
-per editar directament el fitxer a la pàgina web de l'Enigmail</p>
-<hr/>
-<p>
-Teniu més ajuda a la vostra disposició a la
-<a href="https://www.enigmail.net/support/" target="_blank">pàgina web d'ajuda de l'Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/el/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=Ασφάλεια OpenPGP
+Not Found
\ No newline at end of file
-
--- 2:2.1.6+ds1-1/lang/da/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=OpenPGP-sikkerhed
+Not Found
\ No newline at end of file
-
--- 2:2.1.6+ds1-1/lang/ar/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Message Reading</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using Enigmail when reading messages</h3>
-
- <dl>
- <dt>Decrypt button in main Mail window</dt>
-
- <dd>This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.</dd>
-
- <dt>Pen and Key icons in Message Header display</dt>
-
- <dd>
- The <em>Pen</em> and <em>Key</em> icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the <em>Pen</em> icon will change to a <em>Broken Pen</em> to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
-
- <ul>
- <li><em>OpenPGP Security info</em>: allows you to view the output status from GnuPG for the message.</li>
-
- <li><em>Copy OpenPGP Security info</em>: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.</li>
-
- <li><em>View OpenPGP Photo ID</em>: allows you to view the <em>Photo ID</em> of the person who sent the message, if they have a photo embedded in their Public Key. (<em>This option will only be enabled if a Photo ID exists in their key.)</em></li>
-
- <li><em>S/MIME Security info</em>: allows you to view the S/MIME Security Info for the message.</li>
- </ul>
-
- <p>If you do not have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and you read a message which is signed or encrypted, you will see a <em>Pen</em> icon in the headers display area with a <em>Question mark</em> on it, the Enigmail status line in the headers area will say <em>Part of the message signed; click pen icon for details</em> and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.</p>
-
- <p>You may also see this if you have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and the OpenPGP key is not available on the default keyserver.</p>
-
- <p>Clicking on the <em>Pen and Question mark</em> icon will bring up a window advising that the key is unavailable in your keyring. Clicking on OK will bring up another window with a list of keyservers from which you can select to download the sender's public key from.</p>
-
- <p>To configure the list of keyservers you wish to use, go to <strong>Enigmail -> Preferences -> Basic</strong> tab and enter the keyserver addresses in the <em>Keyserver(s):</em> box, separated by a comma. <em>The first keyserver in the list will be used as the default.</em></p>
- </dd>
-
- <dt>Opening encrypted attachments / importing attached OpenPGP keys</dt>
-
- <dd>Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: <em>Decrypt and Open</em> and <em>Decrypt and Save</em>. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.</dd>
- </dl>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/es-AR/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-AR/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="utf8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta name="author" content="EduLeo" />
-<title>Ayuda de Enigmail: Redacción de mensajes</title>
-</head>
-
-<body>
-<h1>Ayuda de Enigmail</h1>
-<h3>Usando Enigmail para redactar mensajes</h3>
-<ul>
-<li><strong>Menú Enigmail en la ventana de redacción de mensajes</strong>
-<ul>
-<li><strong>Firmar mensaje</strong>: Activa/desactiva el envío de correo firmado. El usuario recibe una notificación si hay un fallo en la firma.</li>
-<li><strong>Cifrar mensaje</strong>: Activa/desactiva el cifrado para todos los destinatarios antes de enviarlo. El usuario recibe una notificación si hay un fallo al cifrar.
-<p>Si está activada la opción <em>Mostrar la selección si es necesario</em> en <strong>Preferencias -> pestaña Selección de clave</strong>, se abrirá una ventana con una lista de claves si hay direcciones en la lista de destinatarios del mensaje de las que no se tiene la clave pública.</p>
-<p>Si está activada la opción <em>Nunca mostrar el diálogo de selección de clave OpenPGP</em> en <strong>Preferencias -> pestaña Selección de clave</strong>, y hay direcciones en la lista de destinatarios del mensaje de las que no se tiene la clave pública, el mensaje se enviará sin cifrar.</p>
-</ul></li>
-<li><strong>Usar PGP/MIME en este mensaje</strong>: Activa/desactiva el uso de <a href="https://tools.ietf.org/html/rfc3156" onclick="window.open('https://tools.ietf.org/html/rfc3156');return false">PGP/MIME</a> en este mensaje.
-<p>Si sabe con certeza que los destinatarios pueden leer el correo usando el formato PGP/MIME, entonces se debe usar.</p>
-<p>Esta característica depende de la configuración en <strong>Preferencias -> pestaña PGP/MIME</strong> si está establecida en <em>Usar PGP/MIME si es posible</em> o <em>Siempre usar PGP/MIME</em>.</p>
-<ul>
-<li><strong>Opciones predeterminadas de redacción</strong>: Submenú</li>
-<li><strong>Opciones de firmado/cifrado...</strong>: acceder a <strong>Configuración de cuentas... -> Seguridad OpenPGP</strong>.</li>
-<li><strong>Opciones de envío...</strong>: acceder a <strong>Preferencias -> pestaña Enviar</strong>.</li>
-<li><strong>Opciones de selección de clave...</strong>: acceder a <strong>Preferencias -> pestaña Selección de clave</strong>.</li>
-<li><strong>Opciones PGP/MIME...</strong>: acceder a <strong>Preferencias -> pestaña PGP/MIME</strong>.</li>
-</ul></li>
-<li><strong>Deshacer cifrado</strong>: Si hay algún problema al enviar el correo, como un fallo en el servidor POP que no acepta la solicitud, Enigmail no lo sabrá, y el mensaje cifrado seguirá mostrándose en la ventana de redacción. Con esta opción de menú, se deshacerá el cifrado/firma, volviendo a la ventana de redacción con su texto original.<br />
-<em>Como solución temporal, también se puede usar para descifrar el texto citado al contestar a mensajes cifrados. Enigmail debe descifrar automáticamente el mensaje citado, pero si se produce un fallo por cualquier motivo, se puede usar esta opción del menú para forzarlo</em>.</li>
-<li><strong>Adjuntar clave pública...</strong>: Adjunta el bloque de la clave pública al mensaje, en un archivo con armadura ASCII. Se le preguntará el ID de usuario de las claves que se van a adjuntar.</li>
-<li><strong>Borrar frase contraseña guardada</strong>: Elimina de la caché las frases contraseñas introducidas manualmente. Esto es útil si se tienen varias frases contraseñas.</li>
-<li><strong>Ayuda</strong>: Muestra información de ayuda (esta página).</li>
-</ul><hr/>
-<p>Más ayuda disponible en la <a href="https://www.enigmail.net/support/" onclick="window.open('https://www.enigmail.net/support/');return false">página Web de ayuda de Enigmail</a></p>
-</body></html>
-
--- 2:2.1.6+ds1-1/lang/bg/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: How to Resolve Problems with Initializing OpenPGP</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>How to Resolve Problems with Initializing OpenPGP</h3>
-
- <p>There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below;
- for more information please visit the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Support page.</a></p>
-
- <dl>
- <dt>GnuPG could not be found</dt>
- <dd>
- <p>
- In order for OpenPGP to work, the tool <a href="https://www.gnupg.org/" target="_blank">GnuPG</a> needs to be installed.
- If GnuPG cannot be found, then first make sure that the executable <tt>gpg.exe</tt> (on Windows; <tt>gpg</tt> on other platforms) is installed on your computer.
- If GnuPG is installed, and OpenPGP cannot find it, then you need to manually set the path to GnuPG in the OpenPGP Preferences (menu <i>OpenPGP</i> > <i>Preferences</i>)
- </p>
-
- <dt>Enigmime failed to initialize</dt>
-
- <dd>
- <p>
- OpenPGP works only if it is built using the same build environment as Thunderbird or SeaMonkey was built. This means that you can use the official Enigmail releases only if you use the official releases of Thunderbird or SeaMonkey provided by <a href="www.mozilla.org">mozilla.org</a>.
- </p>
- <p>
- If you use a Thunderbird or SeaMonkey version coming from some other source (e.g. the provider of your Linux distribution), or if you built the application yourself, you should either use an Enigmail version built by the same source, or build Enigmail yourself. For building Enigmail, refer to the <a href="https://www.enigmail.net/download/source.php">Source Code section</a> on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
- </p>
- </dd>
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/troubles.php" target="_blank">Enigmail Support Web Site</a>.</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/ipc/tests/.eslintrc.js 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/ipc/tests/.eslintrc.js 2020-10-01 13:32:58.000000000 +0000
@@ -1,5 +1,5 @@
module.exports = {
"rules": {
- "strict": 0,
+ "strict": 0
}
}
-
--- 2:2.1.6+ds1-1/debian/tests/control 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/tests/control 1970-01-01 00:00:00.000000000 +0000
@@ -1,16 +0,0 @@
-Tests: tbird-sqlite
-Depends:
- jsunit (>= 0.2.2),
- sqlite3,
- thunderbird (>= 1:68.0),
-Restrictions: allow-stderr
-
-Tests: unit-tests
-Depends:
- enigmail,
- jsunit (>= 0.2.2),
- make,
- perl,
- python3,
- sqlite3,
-Restrictions: allow-stderr
-
--- 2:2.1.6+ds1-1/debian/patches/0013-fix-eslint-errors.patch 1970-01-01 00:00:00.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0013-fix-eslint-errors.patch 2020-10-07 15:48:06.000000000 +0000
@@ -0,0 +1,52 @@
+Description: fix problems raised by eslint when running tests
+Author: Olivier Tilloy <olivier.tilloy@canonical.com>
+
+--- a/ipc/tests/subprocess-test.js
++++ b/ipc/tests/subprocess-test.js
+@@ -352,7 +352,7 @@ function run_test() {
+ '--pinentry-mode=loopback',
+ '--passphrase-fd=4',
+ '--status-fd=5',
+- '--symmetric',
++ '--symmetric'
+ ],
+ environment: envList,
+ stdin: function(pipe) {
+@@ -377,7 +377,7 @@ function run_test() {
+ p.wait();
+
+ statusdata="";
+- let decrypt_status_re = /\[GNUPG:\] NEED_PASSPHRASE_SYM \d+ \d+ \d+\n\[GNUPG:] BEGIN_DECRYPTION\n(\[GNUPG:\] DECRYPTION_COMPLIANCE_MODE \d+\n)?\[GNUPG:\] DECRYPTION_INFO \d+ \d+\n\[GNUPG:\] PLAINTEXT \d+ \d+ *\n(\[GNUPG:\] PLAINTEXT_LENGTH (\d+)\n)?\[GNUPG:\] DECRYPTION_OKAY\n(\[GNUPG:\] GOODMDC\n)?\[GNUPG:\] END_DECRYPTION\n/m
++ let decrypt_status_re = /\[GNUPG:\] NEED_PASSPHRASE_SYM \d+ \d+ \d+\n\[GNUPG:] BEGIN_DECRYPTION\n(\[GNUPG:\] DECRYPTION_COMPLIANCE_MODE \d+\n)?\[GNUPG:\] DECRYPTION_INFO \d+ \d+\n\[GNUPG:\] PLAINTEXT \d+ \d+ *\n(\[GNUPG:\] PLAINTEXT_LENGTH (\d+)\n)?\[GNUPG:\] DECRYPTION_OKAY\n(\[GNUPG:\] GOODMDC\n)?\[GNUPG:\] END_DECRYPTION\n/m;
+
+ try {
+ p = subprocess.call({
+@@ -392,7 +392,7 @@ function run_test() {
+ '--pinentry-mode=loopback',
+ '--passphrase-fd=4',
+ '--status-fd=5',
+- '--decrypt',
++ '--decrypt'
+ ],
+ environment: envList,
+ stdin: function(pipe) {
+--- a/package/webextension.js
++++ b/package/webextension.js
+@@ -71,7 +71,7 @@ var enigmailApi = class extends Extensio
+ this.chromeHandle.destruct();
+ this.chromeHandle = null;
+
+- console.debug("webextension.js: Enigmail shutdown");
++ Services.console.logStringMessage("webextension.js: Enigmail shutdown");
+ }
+
+ getAPI(context) {
+@@ -85,7 +85,7 @@ var enigmailApi = class extends Extensio
+ }
+
+ close() {
+- console.debug("webextension.js: close");
++ Services.console.logStringMessage("webextension.js: close");
+ ExtensionSupport.unregisterWindowListener(EXTENSION_NAME);
+ }
+ };
-
--- 2:2.1.6+ds1-1/lang/cs/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/cs/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,84 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Nápověda pro Enigmail - úprava pravidel OpenPGP</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Nápověda pro Enigmail</h1>
-
- <h3>Používání editoru pravidel v Enigmailu: úprava pravidel OpenPGP</h3>
-
- <p>V editoru pravidel můžete pro každého příjemce nastavit výchozí chování Enigmailu tak, že povolíte šifrování, podpis, PGP/MIME a určíte klíč(e) OpenPGP, který se bude pro daného příjemce používat. Zde můžete určit pravidla pro jednotlivé příjemce a pro skupiny příjemců s podobnými charfakteristikami.</p>
-
- <dl>
- <dt>Nastavit OpenPGP pravidla pro</dt>
-
- <dd>Pole obsahuje emailové adresy příjemců (bez jmen, t.j. pouze adresu ve tvaru <tt>jmeno@domena.cz</tt>). Můžete uvést několik emailových adres oddělených mezerami. Adresy mohou obsahovat pouze doménovou část, takže pravidlo odpovídá všem adresátům dané domény, např.<tt>@domena.cz</tt> zahrnuje adresy <tt>jmeno@domena.cz</tt>, <tt>jine_jmeno@domena.cz</tt>, atd.</dd>
-
- <dt>Použij pravidlo jestliže adresát ...</dt>
-
- <dd>
- Upravuje hledání emailových adres, na které se budou v pravidlech používat. Pokud zapíšete více adres, nastavení se aplikuje na všechny. Následující příklady vycházejí z příkladu adresy <tt>jmeno@domena.cz</tt>.
-
- <ul>
- <li><em>Je přesně</em>: s tímto nastavením bude pravidlo použito, pokud email adresáta je přesně <tt>jmeno@domena.cz</tt> (nezávisí na použití velkých a malých písmen v emailové adrese).</li>
-
- <li><em>Obsahuje</em>: s tímto nastavením bude pravidlo použito pro každou emailovou adresu, která obsahuje zadaný text, t.j. <tt>moje-jmeno@domena.cz</tt> nebo <tt>jmeno@domena.cz.com</tt>.</li>
-
- <li><em>Začíná s</em>: s tímto nastavením bude pravidlo použito pro každou emailovou adresu, která začíná zadaným textem t.j. <tt>jmeno@domena.cz</tt>, <tt>jmeno@domena.cz.com</tt>.</li>
-
- <li><em>Končí s</em>: s tímto nastavením bude pravidlo použito pro každou emailovou adresu, která končí zadaným textem t.j. <tt>moje-jmeno@domena.cz</tt> , <tt>jmeno@domena.cz</tt>.</li>
- </ul>
- </dd>
-
- <dt>Pokračovat s dalším pravidlem k daným adresám</dt>
-
- <dd>Tato akce umožní definovat pravidlo a nezadat ID klíče ve vstupním poli <em>Použít následující klíče OpenPGP:</em>. Odpovídající klíč bude podle emailové adresy určen při odesílání zprávy. Pro určenou(é) adresu(y) se také zpracují další pravidla.</dd>
-
- <dt>Nekontrolovat dále pravidla k dané adrese</dt>
-
- <dd>Ukončí zpracování dalších pravidel pro zvolenou adresu, začne se zpracovávat další adresa příjemce.</dd>
-
- <dt>Použít následující OpenPGP klíče:</dt>
-
- <dd>Pomocí tlačítka <em>Vybrat klíč(e)...</em> vyberte klíče, které budou použity k šifrování. Stejně jako v předchozím případě se již nepoužijí pro odpovídající adresu další pravidla.</dd>
-
- <dt>Výchozí pro podepisování</dt>
-
- <dd>
- Povolit / zakázat
- podepsání zprávy. To, zda dojde k podepsání zprávy, závisí na nastavení podepisovámí v okně Psání zprávy a na vybrané hodnotě z těchto možností:
-
- <ul>
- <li><em>Nikdy</em>: zakáže podepsání zprávy bez ohledu na to, jaká volba je v okně psaní zprávy. Tato volba potlačuje ostatní.</li>
-
- <li><em>Ano, jestliže je to povoleno při vytváření zprávy:</em> podepisování zprávy je povoleno a závisí na další volbě, která bude nastavena v okně psaní zprávy.</li>
-
- <li><em>Vždy</em>: zpráva bude podepsána bez ohledu na to, jaká je volba v okně psaní zprávy</li>
- </ul>Toto nastavení podpisu bude použito pro všechna odpovídající pravidla. Jestliže jedno z pravidel zakáže podepsání, zpráva nebude podepsána bez ohledu na to, zda v ostatních pravidlech je nastavena volba <em>Vždy</em>.
- </dd>
-
- <dt>Šifrování</dt>
-
- <dd>Povolit / zakázat šifrování zprávy. Nastavení šifrování a jeho význam jsou podobné jako nastavení podepisování.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd> Povolit / zakázat kódování zprávy pomocí PGP/MIME (RFC 3156). Pokud je PGP/MIME zakázáno, zpráva je kódována použitím "vkládaného PGP" ("inline PGP"). Nastavení a jeho význam jsou podobné jako nastavení podepisování.</dd>
- </dl>
-
-<p>Pravidla jsou zpracována v pořadí podle uvedeného seznamu. Vždy, když pravidlo odpovídá příjemci a obsahuje ID klíče OpenPGP, příjemce se již kromě použití určeného klíče v dalších pravidlech nezpracovává.</p>
- <hr />
-
- <p>Další nápověda je dostupná na stránkách <a href="https://www.enigmail.net/support/">dokumentace Enigmailu</a> (anglicky).</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/ca/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,99 +0,0 @@
-<html>
-<head><title>Ajuda Enigmail: Editar regla OpenPGP</title>
-</head>
-<body>
-<h1>Ajuda Enigmail</h1>
-
-<h3>Emprant l'editor de regles de l'Enigmail: Edició d'una regla OpenPGP</h3>
-<p>A l'editor de regles, podeu indicar, per cada destinatari, el xifratge, la signatura i PGP/MIME i quines claus OpenPGP emprar de manera predeterminada. En aquest diàleg, podeu indicar les regles per un destinatari individual i per un grup de destinataris amb atributs força similars.
-</p>
-<ul>
- <li><span style="font-weight: bold;">Estableix les regles OpenPGP per a</span>: Conté l'adreça de
- correu dels destinataris (sense noms, p.ex. només una adreça com
- <tt>algu@correu.domini</tt>). Podeu indicar algunes adreces de correu, separades per espais.
- L'adreça indicada aquí pot consistir de només la secció del domini, així el correu a qualsevol adreça del domini coincidirà (p.ex.
- <tt>@correu.domini</tt> coincideix amb <tt>algu@correu.domini</tt>,
- <tt>algualtre@correu.domini</tt>, <tt>qualsevol@correu.domini</tt>, etc.)
- </li>
- <li><span style="font-weight: bold;">Aplica la regla si el destinatari ...</span>:
- Això modifica la coincidència de les adreces de correu.
- Si s'ha introduït múltiples adreces de correu, el paràmetre s'aplicarà a totes.
-
- Els exemples següents estan basats en les <i>Regles OpenPGP</i> introduïdes més amunt <tt>algu@correu.domini</tt>.
- <ul>
- <li><i>És exacta</i>: amb aquest paràmetre, la regla només s'activarà amb adreces de correus
- a <tt>algu@correu.domini</tt> (exacta, coincidència sense distinció de majúscules).
- </li>
- <li><i>Conté</i>: amb aquest paràmetre, qualsevol adreça de correu que contingui la cadena
- coincidirà (p.ex. <tt>tambealgu@correu.domini</tt> o <tt>algu@correu.domini.net</tt>)
- </li>
- <li><i>Comença amb</i>: amb aquest paràmetre, qualsevol adreça de correu que comenci amb la
- cadena coincidirà (p.ex. <tt>algu@correu.domini.net</tt>, <tt>algu@correu.domini-nom.com</tt>)
- </li>
- <li><i>Acaba amb</i>: amb aquest paràmetre, qualsevol adreça de correu que acabi amb la cadena coincidirà (p.ex. <tt>algu@correu.domini</tt>,
- <tt>algualtre@correu.domini</tt>).
- </li>
- </ul>
-
- </li>
- <li><span style="font-weight: bold;">Continua amb la següent regla per l'adreça coincident</span><br>
- L'activació d'aquesta funció us permet definir una regla sense
- haver d'indicar una identificació de clau en el camp <em>Empra les
- claus OpenPGP següents:</em>, així que l'adreça de correu s'usa per
- comprovar la clau en el moment d'enviar. També es processaran les
- regles posteriors per a la mateixa adreça(es).
- </li>
- <li><span style="font-weight: bold;">No comprovis més regles per l'adreça coincident</span><br>
- L'activació d'aquesta funció atura el procés d'altres regles per a
- l'adreça(es) coincident amb aquesta regla. El procés de regles
- continua amb el següent destinatari.
- </li>
- <li><span style="font-weight: bold;">Empra les següents claus OpenPGP:</span><br>
- Empreu el botó <em>Selecciona clau(s)..</em> per seleccionar les claus
- dels destinataris que s'usaran per a xifrar. De la mateixa manera que
- amb l'acció anterior, no es processen més regles amb l'adreça coincident.
- </li>
- <li><span style="font-weight: bold;">Signatura per omissió</span>: activa o desactiva
- la signatura del missatge, en funció del que s'ha indicat a la finestra de redacció
- del missatge. El valors són:
- <ul>
- <li><i>Mai</i>: desactiva la signatura, inclòs si s'ha activat a la finestra
- de redacció del missatge (preval sobre els altres valors)<br>
- </li>
- <li><i>Sí, si s'ha seleccionat a la redacció del missatge</i>: deixa la signatura
- tal com s'ha indicat a la finestra de redacció del missatge
- </li>
- <li><i>Sempre</i>: activa la signatura, inclòs si <span
- style="font-style: italic;">no</span> s'ha activat a la finestra de redacció del
- missatge
- </li>
- </ul>
- </li>
-</ul>
-<div style="margin-left: 40px;">Aquests paràmtres de signatura s'apliquen a totes les
-regles que coincideixen. Si una de les regles desactiva la signatura, el missatge
-no es signarà, a menys que altres regles indiquin <i>Sempre</i>.<br>
-</div>
-<ul>
- <li><span style="font-weight: bold;">Xifratge</span>: activa o desactiva
- el xifratge del missatge. Els paràmetres admesos i el seu significat són
- els mateixos que per la signatura de missatge.</li>
- <li><span style="font-weight: bold;">PGP/MIME</span>: activa o desactiva
- l'ús de la codificació PGP/MIME (RFC 3156) del missatge.
- Si el PGP/MIME està desactivat, els missatges es codifiquen usant el "PGP inserit".
- Els paràmetres admesos i el seu significat són
- els mateixos que per la signatura de missatge.
- </li>
-</ul>
-<p>Les regles es processen segons l'ordre mostrat a la llista de
-l'<em>editor de regles OpenPGP</em>. Quan una regla coincideix amb un destinatari i
-conté una identificació de clau OpenPGP, a més d'usar la identificació de clau
-indicada, el destinatari ja no es té en compte al processar més regles.
-</p>
-<hr/>
-<p>
-Teniu més ajuda a la vostra disposició a la
-<a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank"> pàgina de paràmetres per destinatari de l'Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/da/help/help.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/help.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
-<title>Enigmail Help</title>
-</head>
-
-<body>
-<h1>Enigmail Help</h1>
-<h3>Using Enigmail when reading messages</h3>
-<ul>
- <li><b>Decrypt button in main Mail window</b><br />
- This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command. </li>
- <li><b>Pen and Key icons in Message Header display</b><br />
- The <em>Pen</em> and <em>Key</em> icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the <em>Pen</em> icon will change to a <em>Broken Pen</em> to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
- <ul>
- <li><em>Enigmail Security info</em>: allows you to view the output status from GnuPG for the message.</li>
- <li><em>Copy Enigmail Security info</em>: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.</li>
- <li><em>View OpenPGP Photo ID</em>: allows you to view the <em>Photo ID</em> of the person who sent the message, if they have a photo embedded in their Public Key. (<em>This option will only be enabled if a Photo ID exists in their key.)</em></li>
- <li><em>S/MIME Security info</em>: allows you to view the S/MIME Security Info for the message.</li>
- </ul>
- <p>If you do not have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and you read a message which is signed or encrypted, you will see a <em>Pen</em> icon in the headers display area with a <em>Question mark</em> on it, the Enigmail status line in the headers area will say <em>Part of the message signed; click pen icon for details</em> and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.</p>
- <p>You may also see this if you have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and the OpenPGP key is not available on the default keyserver.</p>
- <p>Clicking on the <em>Pen and Question mark</em> icon will bring up a window advising that the key is unavailable in your keyring. Clicking on OK will bring up another window with a list of keyservers from which you can select to download the sender's public key from.</p>
- <p>To configure the list of keyservers you wish to use, go to <b>Enigmail -> Preferences -> Basic</b> tab and enter the keyserver addresses in the <em>Keyserver(s):</em> box, separated by a comma. <em>The first keyserver in the list will be used as the default.</em></p>
- </li>
- <li><b>Opening encrypted attachments / importing attached OpenPGP keys</b><br />
- Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: <em>Decrypt and Open</em> and <em>Decrypt and Save</em>. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings. </li>
-</ul>
-<hr />
-<p> Further help is available on the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Help web page</a> <br />
-If you have questions or comments about enigmail, please send a message to the <a href="https://www.enigmail.net/support/list.php" target="_blank">Enigmail mailing list</a></p>
-<p>Enigmail is open source and licensed under the <a href="https://www.mozilla.org/MPL/2.0" target="_blank">Mozilla Public License 2.0</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/es-AR/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-AR/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta name="author" content="EduLeo" />
-<title>Ayuda de Enigmail: Editor de reglas</title>
-</head>
-
-<body>
-<h1>Ayuda de Enigmail</h1>
-<h3>Usando el editor de reglas de Enigmail</h3>
-<p>En el editor de reglas, se pueden especificar opciones predeterminadas por destinatario para activar el cifrado, firma y PGP/MIME, así como definir qué clave(s) OpenPGP usar. Cada regla consiste de 5 campos y se representa en una sola línea:</p>
-<ul>
-<li><strong>Correo electrónico</strong>: Las direcciones de correo en los campos Para:, Cc: y Cco: tienen que coincidir. La coincidencia funciona en <em>subcadenas</em> (Más detalles en el diálogo de Editar regla)</li>
-<li><strong>Clave(s) OpenPGP</strong>: Una lista de IDs de claves OpenPGP para usar con el destinatario.</li>
-<li><strong>Firmar</strong>: Activar o desactivar el firmado de mensajes. Esta opción usa o ignora lo que se haya especificado en la ventana de redacción de mensajes. Los valores son:
-<br/><ul>
-<li><em>Nunca</em>: Desactiva la firma, incluso si estaba activada en la ventana de redacción del mensaje (tiene preferencia sobre los otros valores).</li>
-<li><em>Posible</em>: Deja la firma como se haya especificado en la ventana de redacción de mensajes.</li>
-<li><em>Siempre</em>: Activar la firma, incluso si <em>no</em> está activada en la ventana de redacción de mensajes.</li>
-</ul>
-</li>
-</ul>
-<div style="margin-left: 40px;">Estas opciones de firma se aplican a todas las reglas que las cumplan. Si una de las reglas desactiva la firma, el mensaje no se firmará, independientemente de otras reglas que especifiquen <em>Siempre</em>.</div>
-<ul>
-<li><strong>Cifrar</strong>: Activa o desactiva el cifrado del mensaje. Las opciones permitidas y su significado son las mismas que para la firma.</li>
-<li><strong>PGP/MIME</strong>: Activa o desactiva el uso de la codificación del mensaje PGP/MIME (RFC 3156). Si PGP/MIME está desactivado, los mensajes se codifican usando "PGP integrado". Los valores permitidos y su significado son los mismos que para la firma de mensajes.</li>
-</ul>
-<p>Las reglas se procesan en el orden mostrado en la lista. Cuando una regla coincida con un destinatario y contenga un ID de clave OpenPGP, además de usar el ID de clave especificado, el destinatario no se tendrá en consideración al procesar más reglas.</p>
-<p><em>NOTA:</em> El editor de reglas aún no está completo. Es posible escribir algunas reglas más avanzadas editando directamente el archivo de reglas (en cuyo caso, éstas no se deben volver a editar mediante el editor). <a href="https://www.enigmail.net/documentation/pgprules_file.php" onclick="window.open('https://www.enigmail.net/documentation/pgprules_file.php');return false">Más información</a> para editar el archivo directamente se encuentra disponible en la página Web de Enigmail.</p>
-<hr /><p>Más ayuda disponible en la <a href="https://www.enigmail.net/support/" onclick="window.open('https://www.enigmail.net/support/');return false">página Web de ayuda de Enigmail</a></p>
-</body></html>
-
--- 2:2.1.6+ds1-1/lang/cs/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/cs/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Nápověda pro Enigmail - čtení zpráv</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Nápověda pro Enigmail</h1>
-
- <h3>Používání Enigmailu při čtení zpráv</h3>
-
- <dl>
- <dt>Tlačítko "Dešifrovat" v hlavním okně</dt>
-
- <dd>Toto tlačítko má několik funkcí: dešifrování, ověřování nebo import veřejných klíčů. Normálně probíhá dešifrování/ověřování automaticky, ovšem tato funkce může být v předvolbách zakázána. Pokud nastane chyba, zobrazí se krátká zpráva ve stavovém řádku Enigmailu. Pokud klepnete na tlačítko "Dešifrovat", zobrazí se podrobnější výpis chyb včetně GnuPG příkazů.</dd>
-
- <dt>Ikony pera a klíče zobrazené v hlavičce zprávy</dt>
-
- <dd>
- Ikony <em>Pera</em> a <em>Klíče</em> ikony pera a klíče v hlavičce zprávy indikují zda zpráva, kterou čtete, je podepsána a/nebo šifrována a zda je podpis platný, tj., že zpráva nebyla od okamžiku podpisu změněna. Ikona <em>zlomného pera</em> indikuje, že zpráva má neplatný podpis nebo byla změněna. Pokud klepnete pravým tlačítkem na ikonu pera nebo klíče zobrazí se menu s následujícími možnostmi:
-
- <ul>
- <li><em>Bezpečnostní informace:</em> zobrazí výstup GnuPG pro tuto zprávu.</li>
-
- <li><em>Kopírovat bezpečnostní informace OpenPGP:</em> zkopíruje výstup z GnuPG do schránky; umožní například vložení do odpovědi na zprávu.</li>
-
- <li><em>Zobrazit Foto ID</em>: zobrazí <em>Photo ID</em> osoby, která zprávu poslala, jestliže jej veřejný klíč obsahuje. (<em>Tato volba je dostupná pouze pokud je fotografie ve veřejném klíči uložena.)</em></li>
-
- <li><em>Bezpečnostní informace S/MIME:</em> zobrazí bezpečnostní informace S/MIME.</li>
- </ul>
-
- <p>Jestliže v souboru <tt>gpg.conf</tt> nemáte nastaveno automatické načítání klíčů z keyserveru a čtete elektronicky podepsáné nebo šifrováné zprávy, uvidíte panelu zprávy ikonku <em>pera s otazníkem</em> a v horní části se zobrazí: <em>Část zprávy byla podepsána; klepněte na ikonku pera nebo klíče pro více informací</em>. Ve zprávě se zobrazí značky úseku textu OpenPGP a blok podpisu.</p>
-
- <p>Může se to stát i v případě, že máte nastaveno automatické načítání klíčů z keyserveru, ale klíč není na serveru k dispozici.</p>
-
- <p>Klepnutím na ikonku <em>pera a otazníku</em> se Vám zobrazí hlášení že klíč, kterým byla zpráva podepsána, není dostupný. Klepnutím na tlačítko OK se dostanete k dalšímu oknu, kde si můžete ze seznamu keyserverů vybrat odkud veřejný klíč odesílatele stáhnout.</p>
-
- <p>Seznam keyserverů, které chcete používat, nastavíte v menu <strong>OpenPGP -> Předvolby... -> Určete Váš/Vaše keyservery</strong>, adresy napište do řádku <em>Keyserver(y):</em>. Více adres <em>oddělte čárkou</em>. Jako výchozí bude použit první keyserver.</p>
- </dd>
-
- <dt>Otevření šifrovaných příloh / import přiložených klíčů OpenPGP</dt>
-
- <dd>Přílohy pojmenované *.pgp, *,asc a *.gpg je OpenPGP schopno rozeznat a zpracovat. Kliknutím pravým tlačítkem myši na přílohu dostanete dvě specifické položky kontextového menu: <em>Dešifrovat a otevřít</em> a <em>Dešifrovat a uložit jako ...</em>. Tyto možnosti využijete, když budete chtít, aby Enigmail přílohy před otevřením nebo uložením dešifroval. Jestliže je příloha zprávy rozpoznána jako soubor obsahující s klíčem OpenPGP, bude Vám nabídnuta možnost importovat klíč do Vašeho úložiště.</dd>
- </dl>
- <hr />
-
- <p>Další nápověda je dostupná na stránkách <a href="https://www.enigmail.net/support/">dokumentace Enigmailu</a> (anglicky).</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/cs/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/cs/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=OpenPGP/Enigmail
+Not Found
\ No newline at end of file
-
--- 2:2.1.6+ds1-1/lang/ca/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=Seguretat OpenPGP
+Not Found
\ No newline at end of file
-
lang/ar/enigmail.dtd
-
--- 2:2.1.6+ds1-1/debian/tests/tbird-sqlite 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/tests/tbird-sqlite 1970-01-01 00:00:00.000000000 +0000
@@ -1,29 +0,0 @@
-#!/bin/bash
-
-# Author: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
-
-# just trying to ensure that thunderbird can work with sqlite:
-mkdir -m 0700 -p tbird-sqlite.profile/extensions
-printf /usr/share/xul-ext/jsunit/ > tbird-sqlite.profile/extensions/jsunit@enigmail.net
-cat > tbird-sqlite.profile/prefs.js <<EOF
-user_pref("extensions.autoDisableScopes", 14);
-user_pref("extensions.update.enabled", false);
-user_pref("lightweightThemes.update.enabled", false);
-user_pref("extensions.blocklist.enabled", false);
-user_pref("browser.search.update", false);
-user_pref("app.update.auto", false);
-user_pref("browser.dom.window.dump.enabled", true);
-user_pref("toolkit.telemetry.prompted", false);
-user_pref("toolkit.telemetry.rejected", true);
-user_pref("toolkit.telemetry.enabled", false);
-EOF
-printf '{"created":%d000}' "$(date '+%s')" >tbird-sqlite.profile/times.json
-
-# set up a profile cleanly, ignoring messages to stderr
-ln -sf debian/tests/no-test.js main.js
-/usr/bin/thunderbird --headless --profile "$(pwd)/tbird-sqlite.profile" 2>&1
-
-ln -sf debian/tests/tbird-sqlite.js main.js
-/usr/bin/thunderbird --headless --profile "$(pwd)/tbird-sqlite.profile"
-rm -rf main.js
-echo .dump | sqlite3 tbird-sqlite.profile/testing.sqlite
-
--- 2:2.1.6+ds1-1/debian/rules 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/rules 2020-10-07 15:48:06.000000000 +0000
@@ -12,11 +12,6 @@ override_dh_auto_configure:
ln -sf /usr/share/misc/config.guess /usr/share/misc/config.sub ./
dh_auto_configure -- --with-tb-path=/usr/bin/thunderbird --with-tb-args='--headless --profile $(shell pwd)/test-profile'
-override_dh_auto_test:
-ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
- debian/run-tests
-endif
-
override_dh_auto_clean:
# if config/autoconf.mk is not present, create stub of it, such that make distclean works
if [ ! -f config/autoconf.mk ]; then \
-
lang/de/enigmail.dtd
-
lang/el/enigmail.properties
-
--- 2:2.1.6+ds1-1/lang/ca/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Ajuda de l'Enigmail: Com resoldre els problemes en inicialitzar l'OpenPGP</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Ajuda de l'Enigmail</h1>
-
- <h3>Com resoldre els problemes en inicialitzar l'OpenPGP</h3>
-
- <p>Hi ha diversos motius pels que la inicialització de l'OpenPGP no funciona. Els més normals es descriuen tot seguit. Per a més informació visiteu la <a href="https://www.enigmail.net/support/" target="_blank">pàgina d'ajuda de l'Enigmail.</a></p>
-
- <dl>
- <dt>No s'ha trobat el GnuPG</dt>
- <dd>
- <p>
- Per a que funcioni l'OpenPGP, cal instal·lar l'eina <a href="https://www.gnupg.org/" target="_blank">GnuPG</a>.
- Si no es pot trobar el GnuPG, primer assegureu-vos que l'executable <tt>gpg.exe</tt> (a Windows, <tt>gpg</tt> en altres platformes) està instal·lat a l'ordinador.
- Si el GnuPG està instal·lat, i l'OpenPGP no pot trobar-lo, aleshores necessitareu definir manualment el camí al GnuPG en les preferències de l'OpenPGP (menú <i>OpenPGP</i> > <i>Preferències</i>)
- </p>
- </dd>
-
- <dt>L'Enigmime falla en iniciar-se</dt>
-
- <dd>
- <p>
- L'OpenPGP funciona només si està construït utilitzant el mateix entorn de construcció amb el que s'ha construït el Thunderbird o el SeaMonkey. Aixó vol dir que només podeu utilitzar la versió oficial de l'Enigmail si utilitzeu les versions oficials del Thunderbird o el SeaMonkey proporcionats per <a href="www.mozilla.org">mozilla.org</a>.
- </p>
- <p>
- Si utilitzeu una versió del Thunderbird o del SeaMonkey provinent d'alguna altra font (p.ex. el proveïdor de la vostra distribució de Linux), o si vós mateix heu construït l'aplicació, heu d'utilitzar una versió de l'Enigmail construïda per la mateixa font, o heu de construir l'Enigmail vós mateix. Per a construir l'Enigmail, dirigiu-vos a la <a href="https://www.enigmail.net/download/source.php">secció de codi font</a> de la pàgina inicial de l'Enigmail. Si us plau, no presenteu cap informe d'error respecte a aquest problema, no es pot solucionar.
- </p>
- </dd>
-
- </dl>
- <p>Hi ha més ajuda disponible en el <a href="https://www.enigmail.net/support/troubles.php" target="_blank">lloc web d'ajuda de l'Enigmail</a>.</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/de/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit Enigmail Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail-Hilfe</h1>
-
- <h3>Optionen zum Verschlüsselten Senden</h3>
-
- <p>In den Senden Einstellungen kann man prinzipiell das Modell und die prinzipiellen Einstellungen zum Verschlüsseln einstellen. </p>
- <dl>
-<dt>Bequeme Verschlüsselung</dt>
- <dd>Mit diesen Einstellungen wird möglichst immer ohne Rückfragen verschlüsselt.
- <p>Diese Einstellungen sind vor allem dann angemessen, wenn man einfach nur seine Privatsphäre erhöhen will, indem man Emails möglichst verschlüsselt statt unverschlüsselt verschickt.</p>
- <p>Der Effekt ist wie wenn man Emails statt als Postkarten als Briefe versendet. Im Gegensatz zu Postkarten kann damit unterwegs nicht mehr jeder den Inhalt der Email einfach so mitlesen.</p>
- <p>Wie bei Briefen bietet das aber keine absolute Garantie, dass die Emails unterwegs nicht von anderen gelesen werden können (auch wenn dazu ein gewisser technischer Aufwand notwendig ist).</p>
- <p>Ein ganz konkretes Risiko besteht darin, aus Versehen "gefälschte Schlüssel" zu verwenden, die man von irgendjemanden oder irgendwo bekommen hat und nur behauptet wurde, dass der Schlüssel zur angegebenen Email-Adresse gehört. Um dieses Risiko zu vermeiden, sollte man nur Schlüssel akzeptieren, denen man vertrauen kann (siehe unten), oder immer selbst einen Schlüssel anhand des Fingerabdrucks mit dem Eigentümer abgleichen (und unterschreiben).</p></dd>
-
- <dt>Manuelle Verschlüsselung</dt>
- <dd>Mit dieser Option kann man die verschiedenen Einstellungen zur Verschlüsselung nach den eigenen Vorstellungen anpassen. Man kann festlegen
- <ul>
- <li>ob auf verschlüsselte/signierte Emails automatisch verschlüsselt/signiert geantwortet werden soll.</li>
- <li>ob man nur Schlüssel akzeptieren will, denen man auch vertrauen kann (dies aktiviert das OpenPGP Vertrauensmodell, durch das man nur Schlüsseln vertraut, die von einem selbst oder Personen, denen man trauen kann, unterschrieben wurden).</li>
- <li>ob man möglichst immer automatisch verschlüsseln will.</li>
- <li>ob und unter welchen Umständen eine ausgehende Email (und deren Verschlüsselung) final bestätigt werden muss.</li>
- </ul>
- </dd>
-
- Falls es wichtig ist, dass der Inhalt von verschlüsselten Emails nicht von anderen Personen oder Organisationen gelesen werden können, sollte man zumindest bei den manuellen Einstellungen die Option einschalten, mit der nur vertrauenswürdige Schlüssel akzeptiert werden. Während dies das Risiko der Verwendung von "gefälschten Schlüsseln" reduziert, muss man dazu aber in der Schlüsselverwaltung Schlüssel aktiv unterschreiben und/oder aktiv bestätigen, welchen Email-Adressen (Personen/Organisationen) man trauen kann, wenn diese die Gültigkeit von Schlüssel bestätigen.</p>
-
-<hr/>
-<p>Weitere Hilfe ist verfügbar auf der <a href="https://www.enigmail.net/support/" target="_blank">Enigmail-Hilfeseite</a></p>
-
-</body>
-</html>
-
lang/de/enigmail.properties
-
--- 2:2.1.6+ds1-1/lang/bg/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/bg/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=OpenPGP Security
+Not Found
\ No newline at end of file
-
--- 2:2.1.6+ds1-1/debian/patches/0010-fixed-bug-1057-Hockeypuck-keyservers-reject-uploads-.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0010-fixed-bug-1057-Hockeypuck-keyservers-reject-uploads-.patch 1970-01-01 00:00:00.000000000 +0000
@@ -1,64 +0,0 @@
-From: Patrick Brunschwig <patrick@enigmail.net>
-Date: Fri, 3 Apr 2020 20:23:14 +0200
-Subject: fixed bug 1057: Hockeypuck keyservers reject uploads that use
- Content-Type: text/plain
-
-(cherry picked from commit 997095d61d2a388c65ec65f9ffd1516390910d03)
----
- package/keyserver.jsm | 10 ++++++++--
- 1 file changed, 8 insertions(+), 2 deletions(-)
-
-diff --git a/package/keyserver.jsm b/package/keyserver.jsm
-index c0d1e53..38f57ee 100644
---- a/package/keyserver.jsm
-+++ b/package/keyserver.jsm
-@@ -173,6 +173,7 @@ const accessHkpInternal = {
-
- let method = "GET";
- let protocol;
-+ let contentType = "text/plain;charset=UTF-8";
-
- switch (keySrv.protocol) {
- case "hkp":
-@@ -189,6 +190,7 @@ const accessHkpInternal = {
- if (actionFlag === EnigmailConstants.UPLOAD_KEY) {
- url += "/pks/add";
- method = "POST";
-+ contentType = "application/x-www-form-urlencoded";
- }
- else if (actionFlag === EnigmailConstants.DOWNLOAD_KEY) {
- if (searchTerm.indexOf("0x") !== 0) {
-@@ -206,6 +208,7 @@ const accessHkpInternal = {
- return {
- url: url,
- host: keySrv.host,
-+ contentType: contentType,
- method: method
- };
- },
-@@ -328,20 +331,23 @@ const accessHkpInternal = {
- let {
- url,
- host,
-- method
-+ method,
-+ contentType
- } = this.createRequestUrl(keyserver, actionFlag, keyId);
-
- if (host === HKPS_POOL_HOST && actionFlag !== EnigmailConstants.GET_SKS_CACERT) {
- this.getSksCACert().then(r => {
- EnigmailLog.DEBUG(`keyserver.jsm: accessHkpInternal.accessKeyServer: getting ${url}\n`);
- xmlReq.open(method, url);
-+ xmlReq.setRequestHeader("Content-Type", contentType);
- xmlReq.send(payLoad);
- });
- }
- else {
- EnigmailLog.DEBUG(`keyserver.jsm: accessHkpInternal.accessKeyServer: requesting ${url}\n`);
- xmlReq.open(method, url);
-- xmlReq.send(payLoad);
-+ xmlReq.setRequestHeader("Content-Type", contentType);
-+ xmlReq.send(payLoad);
- }
- });
- },
-
lang/es-ES/enigmail.properties
-
--- 2:2.1.6+ds1-1/debian/control 2020-01-22 19:53:06.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/control 2020-10-07 15:48:06.000000000 +0000
@@ -8,6 +8,8 @@ Uploaders:
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Build-Depends:
debhelper-compat (= 12),
+ eslint,
+ node-text-table,
perl,
python3,
unzip,
@@ -23,7 +25,7 @@ Architecture: all
Depends:
gnupg (>= 2.2.8-2~),
gnupg-agent,
- thunderbird (>= 1:68.0) | icedove (>= 1:68.0),
+ thunderbird (>= 1:78.0) | icedove (>= 1:78.0),
${misc:Depends},
Recommends:
pinentry-x11,
@@ -35,8 +37,8 @@ Enhances:
icedove,
thunderbird,
Breaks:
- icedove (<< 1:68.0),
- thunderbird (<< 1:68.0),
+ icedove (<< 1:78.0),
+ thunderbird (<< 1:78.0),
Description: GPG support for Thunderbird and Debian Icedove
OpenPGP extension for Thunderbird. Enigmail allows users to access the
features provided by the popular GnuPG software from within Thunderbird.
-
--- 2:2.1.6+ds1-1/lang/ar/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Rules Editor</title>
- <style type="text/css" xml:space="preserve">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using the Enigmail Rules Editor</h3>
-
- <p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. Each rule consists of 5 fields and is represented on a single line:</p>
-
- <dl>
- <dt>Email</dt>
-
- <dd>The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on <span style="font-style: italic;">substrings</span> (Further details can be found in the Edit Rule dialog)</dd>
-
- <dt>OpenPGP Key(s)</dt>
-
- <dd>a list of OpenPGP Key ID's to use for the recipient</dd>
-
- <dt>Sign</dt>
-
- <dd>
- enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
-
- <ul>
- <li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
-
- <li><em>Possible</em>: leave signing as specified in the message composition window</li>
-
- <li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
- </ul>
-
- <p>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.</p>
- </dd>
-
- <dt>Encrypt</dt>
-
- <dd>enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.</dd>
- </dl>
-
- <p>The rules are processed in the order displayed in the list. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
-
- <p><em>Note:</em> The rule editor is not yet complete. It is possible to write some more advanced rules by directly editing the rules file (these rules should then not be edited anymore in the rule editor). <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Further information</a> for directly editing the file is available on the Enigmail Homepage</p>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/bg/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Rules Editor</title>
- <style type="text/css" xml:space="preserve">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using the Enigmail Rules Editor</h3>
-
- <p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. Each rule consists of 5 fields and is represented on a single line:</p>
-
- <dl>
- <dt>Email</dt>
-
- <dd>The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on <span style="font-style: italic;">substrings</span> (Further details can be found in the Edit Rule dialog)</dd>
-
- <dt>OpenPGP Key(s)</dt>
-
- <dd>a list of OpenPGP Key ID's to use for the recipient</dd>
-
- <dt>Sign</dt>
-
- <dd>
- enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
-
- <ul>
- <li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
-
- <li><em>Possible</em>: leave signing as specified in the message composition window</li>
-
- <li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
- </ul>
-
- <p>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.</p>
- </dd>
-
- <dt>Encrypt</dt>
-
- <dd>enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.</dd>
- </dl>
-
- <p>The rules are processed in the order displayed in the list. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
-
- <p><em>Note:</em> The rule editor is not yet complete. It is possible to write some more advanced rules by directly editing the rules file (these rules should then not be edited anymore in the rule editor). <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Further information</a> for directly editing the file is available on the Enigmail Homepage</p>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/bg/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Message Reading</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using Enigmail when reading messages</h3>
-
- <dl>
- <dt>Decrypt button in main Mail window</dt>
-
- <dd>This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.</dd>
-
- <dt>Pen and Key icons in Message Header display</dt>
-
- <dd>
- The <em>Pen</em> and <em>Key</em> icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the <em>Pen</em> icon will change to a <em>Broken Pen</em> to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
-
- <ul>
- <li><em>OpenPGP Security info</em>: allows you to view the output status from GnuPG for the message.</li>
-
- <li><em>Copy OpenPGP Security info</em>: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.</li>
-
- <li><em>View OpenPGP Photo ID</em>: allows you to view the <em>Photo ID</em> of the person who sent the message, if they have a photo embedded in their Public Key. (<em>This option will only be enabled if a Photo ID exists in their key.)</em></li>
-
- <li><em>S/MIME Security info</em>: allows you to view the S/MIME Security Info for the message.</li>
- </ul>
-
- <p>If you do not have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and you read a message which is signed or encrypted, you will see a <em>Pen</em> icon in the headers display area with a <em>Question mark</em> on it, the Enigmail status line in the headers area will say <em>Part of the message signed; click pen icon for details</em> and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.</p>
-
- <p>You may also see this if you have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and the OpenPGP key is not available on the default keyserver.</p>
-
- <p>Clicking on the <em>Pen and Question mark</em> icon will bring up a window advising that the key is unavailable in your keyring. Clicking on OK will bring up another window with a list of keyservers from which you can select to download the sender's public key from.</p>
-
- <p>To configure the list of keyservers you wish to use, go to <strong>Enigmail -> Preferences -> Basic</strong> tab and enter the keyserver addresses in the <em>Keyserver(s):</em> box, separated by a comma. <em>The first keyserver in the list will be used as the default.</em></p>
- </dd>
-
- <dt>Opening encrypted attachments / importing attached OpenPGP keys</dt>
-
- <dd>Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: <em>Decrypt and Open</em> and <em>Decrypt and Save</em>. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.</dd>
- </dl>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/configure.ac 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/configure.ac 2020-10-01 13:32:58.000000000 +0000
@@ -2,7 +2,7 @@
AC_PREREQ(2.61)
min_automake_version="1.10"
-AC_INIT([enigmail],[2.1.6], [https://www.enigmail.net])
+AC_INIT([enigmail],[2.2.4], [https://www.enigmail.net])
AC_PATH_PROG(PYTHON, "python3")
-
lang/el/enigmail.dtd
-
debian/patches/0006-enable-the-use-of-extra-file-descriptors-and-test-th.patch
--- 2:2.1.6+ds1-1/debian/patches/0006-enable-the-use-of-extra-file-descriptors-and-test-th.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0006-enable-the-use-of-extra-file-descriptors-and-test-th.patch 2020-10-07 15:48:06.000000000 +0000
@@ -18,8 +18,6 @@ Subject: enable the use of extra file de
ipc/tests/subprocess-test.js | 28 +++++++++++++++++
5 files changed, 136 insertions(+), 4 deletions(-)
-diff --git a/ipc/modules/enigmailprocess_common.jsm b/ipc/modules/enigmailprocess_common.jsm
-index 06859c3..4e64a42 100644
--- a/ipc/modules/enigmailprocess_common.jsm
+++ b/ipc/modules/enigmailprocess_common.jsm
@@ -598,12 +598,19 @@ class _BaseProcess {
@@ -88,8 +86,6 @@ index 06859c3..4e64a42 100644
});
}
-diff --git a/ipc/modules/enigmailprocess_main.jsm b/ipc/modules/enigmailprocess_main.jsm
-index 266bf14..2012428 100644
--- a/ipc/modules/enigmailprocess_main.jsm
+++ b/ipc/modules/enigmailprocess_main.jsm
@@ -87,6 +87,18 @@ var SubprocessMain = {
@@ -120,8 +116,6 @@ index 266bf14..2012428 100644
let environment = {};
if (!options.environment || options.environmentAppend) {
-diff --git a/ipc/modules/enigmailprocess_worker_unix.js b/ipc/modules/enigmailprocess_worker_unix.js
-index ebffdc9..ab4a792 100644
--- a/ipc/modules/enigmailprocess_worker_unix.js
+++ b/ipc/modules/enigmailprocess_worker_unix.js
@@ -392,6 +392,14 @@ class Process extends BaseProcess {
@@ -139,8 +133,6 @@ index ebffdc9..ab4a792 100644
this.pipes = our_pipes;
return their_pipes;
-diff --git a/ipc/modules/subprocess.jsm b/ipc/modules/subprocess.jsm
-index b62c676..d8ea4ab 100644
--- a/ipc/modules/subprocess.jsm
+++ b/ipc/modules/subprocess.jsm
@@ -25,6 +25,14 @@
@@ -226,11 +218,9 @@ index b62c676..d8ea4ab 100644
if (options.command instanceof Ci.nsIFile) {
opts.command = options.command.path;
} else {
-diff --git a/ipc/tests/subprocess-test.js b/ipc/tests/subprocess-test.js
-index 5e68b18..5e5f85b 100644
--- a/ipc/tests/subprocess-test.js
+++ b/ipc/tests/subprocess-test.js
-@@ -294,6 +294,34 @@ function run_test() {
+@@ -300,6 +300,34 @@ function run_test() {
p.wait();
@@ -264,4 +254,4 @@ index 5e68b18..5e5f85b 100644
+
/////////////////////////////////////////////////////////////////
- // Test many concurrent runs
+ // Test many subsequent runs
-
--- 2:2.1.6+ds1-1/debian/tests/tbird-sqlite.js 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/tests/tbird-sqlite.js 1970-01-01 00:00:00.000000000 +0000
@@ -1,80 +0,0 @@
-/* global ChromeUtils: false; Assert: false; dump: false; JSUnit: false */
-
-"use strict";
-
-const Sqlite = ChromeUtils.import("resource://gre/modules/Sqlite.jsm").Sqlite;
-const PromiseUtils = ChromeUtils.import("resource://gre/modules/PromiseUtils.jsm").PromiseUtils;
-
-function log(str) {
- /* how to log to stdout/stderr? */
- dump(str, str.length);
-}
-
-/**
- * Create the "simple" table and the corresponding index
- *
- * @param connection: Object - SQLite connection
- * @param deferred: Promise
- */
-function createTable(connection, deferred) {
- log("createTable()\n");
-
- connection.execute("create table simple (" +
- "foo text not null, " + // string
- "int text not null); "). // number
- then( function _ok() {
- log("createTable - index\n");
- connection.execute("create unique index xx on simple(foo)").
- then(function _f() {
- deferred.resolve();
- });
- });
-}
-
-function checkDatabaseStructure(connection) {
- log("checkDatabaseStructure\n");
-
- let deferred = PromiseUtils.defer();
-
- connection.tableExists("simple").then(
- function onSuccess(exists) {
- log("checkDatabaseStructure - success\n");
- if (!exists) {
- createTable(connection, deferred);
- }
- else {
- deferred.resolve();
- }
- },
- function onError(error) {
- log("checkDatabaseStructure - error\n");
- deferred.reject(error);
- }
- );
-
- return deferred.promise;
-}
-
-
-log("started sqlite test!!!\n");
-JSUnit.testPending();
-Sqlite.openConnection({
- path: "testing.sqlite",
- sharedMemoryCache: false
-}).then(
- function onConnection(connection) {
- log("success!!!\n");
- var conn = connection;
- checkDatabaseStructure(conn).
- then(function _x() {
- conn.close();
- JSUnit.testSucceeded();
- JSUnit.testFinished();
- });
- },
- function onError(error) {
- JSUnit.testFailed();
- JSUnit.testFinished();
- log("failure!!!\n");
- }
-);
-
--- 2:2.1.6+ds1-1/lang/de/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,63 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail-Hilfe: Enigmail-Empfägerregeln</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css" xml:space="preserve">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail-Hilfe</h1>
-
- <h3>Enigmail-Empfängerregeln</h3>
-
- <p>Mit dem Regel-Editor kann man Standards in Bezug auf Verschlüsselung, Unterschreiben und PGP/MIME für bestimmte Empfänger und die Benutzung von Schlüsseln einstellen. Jede Regel besteht aus 5 Feldern und ist in einer einzelnen Zeile zu finden:</p>
-
- <dl>
- <dt>E-Mail-Adresse</dt>
-
- <dd>Die E-Mail-Adressen der Felder "An:", "CC:" und "BCC:", die übereinstimmen sollen. Die Übereinstimmung arbeitet mit <span style="font-style: italic;">substrings</span> (Weitere Details im Dialog "Enigmail-Empfängerregel bearbeiten").</dd>
-
- <dt>OpenPGP-Schlüssel</dt>
-
- <dd>Eine Liste der OpenPGP-Schlüssel-IDs, die für den Empfänger verwendet werden sollen.</dd>
-
- <dt>Unterschreiben</dt>
-
- <dd>
- Unterschreiben von Nachrichten ermöglichen / nicht ermöglichen. Dies verwendet die Einstellungen, die im Fenster "Verfassen" angegeben sind oder setzt sich darüber hinweg. Es gibt folgende Optionen:
-
- <ul>
- <li><em>Nie</em>: Unterschreiben unmöglich, selbst wenn im Fenster "Verfassen" angegeben (setzt sich über andere Einstellungen hinweg).</li>
-
- <li><em>Ja, wenn beim Verfassen ausgewählt</em>: Einstellung aus dem Fenster "Verfassen" wird übernommen.</li>
-
- <li><em>Immer</em>: Unterschreiben, selbst wenn <span style="font-style: italic;">nicht</span> im Fenster "Verfassen" angegeben.</li>
- </ul>
-
- <p>Diese Unterschriftseinstellungen werden auf alle Regeln angewendet, die übereinstimmen. Wenn eine der Regeln das Unterschreiben unmöglich macht, dann wird die Nachricht nicht unterschrieben - auch wenn bei anderen Regeln <i>Immer</i> angegeben ist.</p>
- </dd>
-
- <dt>Verschlüsseln</dt>
-
- <dd>Verschlüsselung ermöglichen / nicht ermöglichen. Die möglichen Einstellungen und ihre Bedeutungen stimmen mit den oben genannten überein.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>Verwenden von PGP/MIME (RFC 3156) ermöglichen / nicht ermöglichen. Falls PGP/MIME nicht möglich ist, dann werden die Nachrichten per "Inline PGP" verschlüsselt. Die möglichen Einstellungen und ihre Bedeutungen stimmen mit den oben genannten überein.</dd>
- </dl>
-
- <p>Die Regeln werden in der Reihenfolge, wie sie in der Liste erscheinen, angewendet. Wann immer eine Regel auf einen Empfänger zutrifft und eine OpenPGP-Schlüssel-ID enthält, dann wird der Empfänger nach Verwendung der angegeben Schlüssel-ID bei den nachfolgenden Regeln nicht mehr beachtet.</p>
-
- <p><em>Hinweis:</em> Der Regel-Editor ist noch nicht komplett. Es ist möglich, weiter fortgeschrittene Regeln zu schreiben, indem man direkt die Regel-Datei bearbeitet (diese Regeln sollten danach nicht mehr mit dem Regel-Editor bearbeitet werden). <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Weitere Informationen</a>, wie die Datei bearbeitet werden muss, gibt es auf der Enigmail-Homepage</p>
- <hr/>
-
- <p>Weitere Hilfe ist verfügbar auf der <a href="https://www.enigmail.net/support/" target="_blank">Enigmail-Hilfeseite</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/patches/0011-drop-unnecessary-tests.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0011-drop-unnecessary-tests.patch 1970-01-01 00:00:00.000000000 +0000
@@ -1,37 +0,0 @@
-From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
-Date: Wed, 6 Nov 2019 01:42:24 -0500
-Subject: Drop unnecessary tests in keyObj-test.js
-
-See Message-ID: <8736f1nfsd.fsf@fifthhorseman.net> (and followup
-messages) on enigmail-users@enigmail.net for more discussion about why
-these tests are bogus and irrelevant for debian.
----
- package/tests/keyObj-test.js | 17 +----------------
- 1 file changed, 1 insertion(+), 16 deletions(-)
-
-diff --git a/package/tests/keyObj-test.js b/package/tests/keyObj-test.js
-index 0042e02..a82caa5 100644
---- a/package/tests/keyObj-test.js
-+++ b/package/tests/keyObj-test.js
-@@ -37,19 +37,4 @@ test(withTestGpgHome(withEnigmail(function shouldExportMinimalSubkey() {
- Assert.equal(minKey.keyData.substr(0, 50), "mQGNBFub08oBDACmb04i4u8xUV1ADbnbN5l83mpr70OyWVJb5E");
- Assert.equal(minKey.keyData.substr(-50, 50), "p9TFNKjguUrrGrVnmnmy/YoGTJWuGqrZy8kcC3LCjg0k2mV0M=");
- }
--
-- EnigmailGpg.agentVersion = "2.2.1";
-- Assert.ok(!EnigmailGpg.getGpgFeature("export-specific-uid"));
--
-- let minKey = keyObj.getMinimalPubKey("bob@somewhere.invalid");
-- Assert.equal(minKey.exitCode, 0);
-- Assert.equal(minKey.keyData.substr(3, 50), "NBFub08oBDACmb04i4u8xUV1ADbnbN5l83mpr70OyWVJb5ElIc");
-- Assert.ok(minKey.keyData.substr(-50, 50) == "1MU0qOC5SusatWeaebL9igZMla4aqtnLyRwLcsKODSTaZXQw==" ||
-- minKey.keyData.substr(-50, 50) == "p9TFNKjguUrrGrVnmnmy/YoGTJWuGqrZy8kcC3LCjg0k2mV0M=", "min key matches");
--
-- minKey = keyObj.getMinimalPubKey("does@not.exist");
-- Assert.equal(minKey.exitCode, 0);
--
-- Assert.equal(minKey.keyData.substr(0, 50), "xsDNBFub08oBDACmb04i4u8xUV1ADbnbN5l83mpr70OyWVJb5E");
-- Assert.equal(minKey.keyData.substr(-50, 50), "1MU0qOC5SusatWeaebL9igZMla4aqtnLyRwLcsKODSTaZXQw==");
--})));
-\ No newline at end of file
-+})));
-
--- 2:2.1.6+ds1-1/lang/ca/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,58 +0,0 @@
-<html>
-<head><title>Ajuda Enigmail: Lectura de missatges</title>
-</head>
-<body>
-<h1>Ajuda Enigmail</h1>
-
-<h3>Emprant l'Enigmail per llegir missatges</h3>
-<ul>
- <li><b>Botó Desxifra a la finestra principal de la Missatgeria</b><br>
- Aquest botó es pot emprar per a varies funcions: desxifrar, verificar o importar claus públiques.
- Normalment, el desxiframent/verificació és automàtic, encara que es pot desactivar amb una opció.
- Tanmateix, si això falla, es mostrarà un missatge curt d'error a la línia d'estat de l'Enigmail.
- Si feu un clic al botó Desxifra, podreu veure un missatge d'error més detallat, inclòsa la sortida de l'ordre GPG.
- </li>
- <li><b>Icones del llapis i la clau al visualitzador de capçaleres del missatge</b><br>
- Les icones del <em>llapis</em> i la <em>clau</em> al visualitzador de capçaleres del missatge indiquen
- si el missatge que esteu llegint ha estat signat i/o xifrat. Si el missatge ha estat modificat, la icona del
- <em>llapis</em> canviarà a un <em>llapis trencat</em> per a indicar que la signatura és dolenta.
- Fent un clic amb el botó dret a la icona del llapis o de la clau mostrarà un menú amb les següents opcions:
- <ul>
- <li><em>Informació de seguretat OpenPGP</em>: us permet veure l'estat de la sortida GPG del missatge.</li>
- <li><em>Copia la informació de seguretat OpenPGP</em>: copia l'estat de la sortida GPG al porta-retalls;
- enganxar-lo a un missatge de resposta, etc.</li>
- <li><em>Mostra l'identificador de foto OpenPGP</em>: us permet veure l'<em>identificador de foto</em> de la
- persona que envia el missatge, si ha incrustat una foto a la seva clau pública.
- (<em>Aquesta opció només s'activarà si existeix l'identificador de foto a la seva clau.)</em></li>
- <li><em>Informació de seguretat S/MIME</em>: us permet veure la informació de seguretat S/MIME del missatge.</li>
- </ul>
- <p>Si no heu establert l'opció <em>keyserver-options auto-key-retrieve</em> al vostre fitxer
- <tt>gpg.conf</tt> i llegiu un missatge que està signat o xifrat,
- veureu la icona d'un <em>llapis</em> a l'àrea de visualització de les capçaleres amb un <em>interrogant</em>,
- i la línia d'estat de l'Enigmail a l'àrea de capçaleres indicarà <em>Part
- del missatge signat; feu un clic a la icona del llapis pels detalls</em> i el missatge de la subfinestra
- de la Missatgeria mostrarà tots els indicadors del bloc PGP del missatge i el bloc de signatura.</p>
- <p>També podreu veure això si teniu establerta l'opció <em>keyserver-options auto-key-retrieve</em>
- al vostre fitxer <tt>gpg.conf</tt> i la clau PGP no es troba en el servidor de claus predeterminat.</p>
- <p>En fer un clic a la icona del <em>llapis amb interrogant</em> s'obrirà una finestra avisant que
- la clau no està al vostre anell de claus. Si feu un clic a D'acord s'obrirà una altra finestra amb una
- llista dels servidors de claus que podeu seleccionar per a baixar la clau pública del remitent.</p>
- <p>Per a configurar la llista dels servidors de claus que voleu usar, aneu a la pestanya <b>Enigmail ->
- Preferències -> Bàsic</b> i introduïu les adreces dels servidors de claus a la caixa
- <em>Servidor(s) de claus:</em>, separats per comes. <em>El primer servidor de claus serà el
- predeterminat.</em></p>
- </li>
- <li><b>Obrint fitxers adjunts xifrats / important claus PGP adjuntes</b><br>
- Els fitxers adjunts anomenats *.pgp, *.asc i *.gpg es reconeixen com adjunts que l'Enigmail pot gestionar de manera
- especial. Fent un clic amb el botó dret en aquests adjunts s'activen dos elements especials del menú contextual:
- <em>Desxifra i obre</em> i <em>Desxifra i desa</em>. Empreu aquests dos elements del menú si voleu que l'Enigmail
- desxifri un adjunt abans d'obrir-lo o desar-lo. Si un adjunt es reconeix com un fitxer de clau PGP,
- se us oferirà la possibilitat d'importar la clau al vostre anell de claus.
- </li>
-</ul><hr/>
-<p>
-Teniu més ajuda a la vostra disposició a la
-<a href="https://www.enigmail.net/support/" target="_blank">pàgina web de l'Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/patches/0004-copy-enums.armor-from-OpenPGP.js.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0004-copy-enums.armor-from-OpenPGP.js.patch 1970-01-01 00:00:00.000000000 +0000
@@ -1,61 +0,0 @@
-From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
-Date: Mon, 11 Jun 2018 00:08:04 -0400
-Subject: copy enums.armor from OpenPGP.js
-
-Since we use this in our own bytesToArmor(), we just copy the simple
-table in here.
----
- package/openpgp.jsm | 33 +++++++++++++++------------------
- 1 file changed, 15 insertions(+), 18 deletions(-)
-
-diff --git a/package/openpgp.jsm b/package/openpgp.jsm
-index 2982850..c6b8f99 100644
---- a/package/openpgp.jsm
-+++ b/package/openpgp.jsm
-@@ -35,31 +35,28 @@ var crc_table = [0x00000000, 0x00864cfb, 0x018ad50d, 0x010c99f6, 0x0393e6e1, 0x0
- 0x575bc9c3, 0x57dd8538
- ];
-
--var gOpenPGPLib;
--
- function initialize() {
- const EnigmailLog = ChromeUtils.import("chrome://enigmail/content/modules/log.jsm").EnigmailLog;
-- const getOpenPGPLibrary = ChromeUtils.import("chrome://enigmail/content/modules/stdlib/openpgp-lib.jsm").getOpenPGPLibrary;
--
- EnigmailLog.DEBUG("openpgp.jsm: initialize()\n");
--
-- try {
-- gOpenPGPLib = getOpenPGPLibrary();
--
-- EnigmailLog.DEBUG(`openpgp.jsm: openpgp: ${gOpenPGPLib}\n`);
-- }
-- catch (ex) {
-- EnigmailLog.ERROR("openpgp.jsm: initialize: error: " + ex.toString() + "\n");
-- }
- }
-
- var EnigmailOpenPGP = {
-- get openpgp() {
-- if (!gOpenPGPLib) {
-- initialize();
-+ openpgp: {
-+ enums: {
-+ /** Armor type
-+ * @enum {Integer}
-+ * @readonly
-+ */
-+ armor: {
-+ multipart_section: 0,
-+ multipart_last: 1,
-+ signed: 2,
-+ message: 3,
-+ public_key: 4,
-+ private_key: 5,
-+ signature: 6
-+ },
- }
--
-- return gOpenPGPLib;
- },
-
- enigmailFuncs: {
-
lang/da/enigmail.properties
-
lang/da/enigmail.dtd
-
--- 2:2.1.6+ds1-1/lang/el/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/el/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: How to Resolve Problems with Initializing OpenPGP</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>How to Resolve Problems with Initializing OpenPGP</h3>
-
- <p>There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below;
- for more information please visit the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Support page.</a></p>
-
- <dl>
- <dt>GnuPG could not be found</dt>
- <dd>
- <p>
- In order for OpenPGP to work, the tool <a href="https://www.gnupg.org/" target="_blank">GnuPG</a> needs to be installed.
- If GnuPG cannot be found, then first make sure that the executable <tt>gpg.exe</tt> (on Windows; <tt>gpg</tt> on other platforms) is installed on your computer.
- If GnuPG is installed, and OpenPGP cannot find it, then you need to manually set the path to GnuPG in the OpenPGP Preferences (menu <i>OpenPGP</i> > <i>Preferences</i>)
- </p>
-
- <dt>Enigmime failed to initialize</dt>
-
- <dd>
- <p>
- OpenPGP works only if it is built using the same build environment as Thunderbird or SeaMonkey was built. This means that you can use the official Enigmail releases only if you use the official releases of Thunderbird or SeaMonkey provided by <a href="www.mozilla.org">mozilla.org</a>.
- </p>
- <p>
- If you use a Thunderbird or SeaMonkey version coming from some other source (e.g. the provider of your Linux distribution), or if you built the application yourself, you should either use an Enigmail version built by the same source, or build Enigmail yourself. For building Enigmail, refer to the <a href="https://www.enigmail.net/download/source.php">Source Code section</a> on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
- </p>
- </dd>
- </dl>
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/troubles.php" target="_blank">Enigmail Support Web Site</a>.</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/da/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encrypted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of Enigmail to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/patches/0011-skip-record-if-nothing-found-broken-Find-keys-for-al.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0011-skip-record-if-nothing-found-broken-Find-keys-for-al.patch 1970-01-01 00:00:00.000000000 +0000
@@ -1,24 +0,0 @@
-From: Patrick Brunschwig <patrick@enigmail.net>
-Date: Sat, 11 Apr 2020 11:35:53 +0200
-Subject: skip record if nothing found (broken Find keys for all contacts)
- with vks keyservers
-
-(cherry picked from commit 048d65f1846683cd6a3e939b6e65e16e3db3c2c3)
----
- package/keyserver.jsm | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/package/keyserver.jsm b/package/keyserver.jsm
-index 38f57ee..d98b021 100644
---- a/package/keyserver.jsm
-+++ b/package/keyserver.jsm
-@@ -1546,6 +1546,9 @@ const accessVksServer = {
- for (let i in searchArr) {
- let r = await this.accessKeyServer(EnigmailConstants.SEARCH_KEY, keyserver, searchArr[i], listener);
-
-+ // try next item if nothing found
-+ if (!r || !r.length) continue;
-+
- const cApi = EnigmailCryptoAPI();
- let keyList = await cApi.getKeyListFromKeyBlock(r);
-
-
--- 2:2.1.6+ds1-1/lang/de/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail-Hilfe: Enigmail-Empfägerregel bearbeiten</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail-Hilfe</h1>
-
- <h3>Enigmail-Empfängerregeln bearbeiten</h3>
-
- <p>Es können Standards für einen Empfänger bezüglich Verschlüsselung, Unterschreiben und PGP/MIME sowie die Verwendung von OpenPGP-Schlüsseln festgelegt werden. In diesem Dialog können Sie Regeln für einen einzelnen Empfänger sowie Gruppen von Empfängern mit ähnlichen Eigenschaften festlegen.</p>
-
- <dl>
- <dt>Regel für</dt>
-
- <dd>Beinhaltet die E-Mail-Adressen der Empfänger (ohne Namen, also z.B. einfach <tt>somebody@email.domain</tt>). Sie können mehrere E-Mail-Adressen festlegen; die Adressen müssen mit Leerzeichen voneinander getrennt sein. Die eingegebenen Adressen können auch nur aus dem Domain-Namen bestehen, so dass die Regel auf alle Mails dieser Domain angewendet wird, also z.B. <tt>@email.domain</tt> bezieht ein <tt>body@email.domain</tt>, <tt>somebody@email.domain</tt>, <tt>anybody@email.domain</tt>, etc.</dd>
-
- <dt>Anwenden, wenn Empfänger...</dt>
-
- <dd>
- Dies modifiziert die Übereinstimmung der E-Mail-Adressen. Wenn mehrere E-Mail-Adressen eingegeben werden, dann wird diese Einstellung auf alle angewendet. Die folgenden Beispiele beziehen sich auf die Adresse <tt>body@email.domain</tt>, die im oberen Feld <em>Enigmail-Empfängerregel</em> eingegeben wurde.
-
- <ul>
- <li><em>ist exakt</em>: Mit dieser Einstellung wird die Regel nur angewendet, wenn die E-Mail-Adresse <tt>body@email.domain</tt> lautet (exakt, Gross-/Kleinschreibung wird nicht beachtet).</li>
-
- <li><em>enthält</em>: Regel wird angewendet, wenn die Zeichenfolge in der E-Mail-Adresse auftaucht, also z.B. <tt>anybody@email.domain</tt> oder <tt>body@email.domain.net</tt></li>
-
- <li><em>beginnt mit</em>: Regel wird angewendet, wenn die Zeichenfolge am Beginn der E-Mail-Adresse steht, also z.B. <tt>body@email.domain.net</tt>, <tt>body@email.domain-name.com</tt>.</li>
-
- <li><em>endet mit</em>: Regel wird angewendet, wenn die Zeichenfolge am Ende der E-Mail-Adresse steht, also z.B. <tt>anybody@email.domain</tt>, <tt>somebody@email.domain</tt>.</li>
- </ul>
- </dd>
-
- <dt>Weitere Regeln auf passende Adresse prüfen</dt>
-
- <dd>Diese Einstellung erlaubt Ihnen, eine Regel zu erstellen ohne eine spezielle Schlüssel-ID in <em>Verwende folgende OpenPGP-Schlüssel</em> angeben zu müssen. Die E-Mail-Adresse wird für die Auswahl des passenden Schlüssels beim Senden genutzt. Weitere Regeln für die gleiche E-Mail-Adresse werden auch ausgeführt.</dd>
-
- <dt>Weitere Regeln nicht auf passende Adresse prüfen</dt>
-
- <dd>Bei dieser Einstellung werden weitere Regeln nicht mehr ausgeführt, sobald eine passende Regel gefunden wurde.</dd>
-
- <dt>Verwende folgende OpenPGP-Schlüssel:</dt>
-
- <dd>Nutzen Sie die Schaltfläche <em>Auswählen...</em>, um die gewünschten Schlüssel auszuwählen. Auch hier werden keine weiteren Regeln ausgeführt.</dd>
-
- <dt>Unterschreiben</dt>
-
- <dd>
- Unterschreiben von Nachrichten ermöglichen / nicht ermöglichen. Diese Einstellung verwendet oder übergeht, was Sie im Fenster "Verfassen" angegeben haben. Die möglichen Einstellungen lauten:
-
- <ul>
- <li><em>Nie</em>: Unterschreiben nicht ermöglichen, auch wenn es im Fenster "Verfassen" möglich war (andere Einstellungen werden übergangen).</li>
-
- <li><em>Ja, wenn beim Verfassen ausgewählt</em>: Übernimmt die Einstellung, die beim Verfassen gewählt wurde.</li>
-
- <li><em>Immer</em>: Unterschreiben ermöglichen, selbst wenn es <span style="font-style: italic;">nicht</span> im Fenster "Verfassen" ermöglicht war.</li>
- </ul>Diese Unterschriftseinstellungen werden bei allen übereinstimmenden Regeln angewendet. Wenn eine der Regeln das Unterschreiben nicht ermöglicht, dann wird die Nachricht ungeachtet anderer Regeln, die <em>Immer </em>vorschreiben, nicht unterschrieben.
- </dd>
-
- <dt>Verschlüsselung</dt>
-
- <dd>Verschlüsselung ermöglichen / nicht ermöglichen. Die möglichen Einstellungen und Bedeutungen stimmen mit den oben genannten überein.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>Verschlüsselung mit PGP/MIME (RFC 3156) ermöglichen / nicht ermöglichen. Wenn nicht PGP/MIME abgestellt (nicht möglich) ist, dann wird die Nachricht per "Inline PGP" verschlüsselt. Die möglichen Einstellungen und Bedeutungen stimmen mit den oben genannten überein.</dd>
- </dl>
-
- <p>Die Regeln werden in der Reihenfolge, wie sie in der Liste im Dialog "Enigmail-Empfängerregeln" erscheinen, angewendet. Wann immer eine Regel auf einen Empfänger zutrifft und eine OpenPGP-Schlüssel-ID enthält, dann wird der Empfänger nach Verwendung der angegeben Schlüssel-ID bei den nachfolgenden Regeln nicht mehr beachtet.</p>
- <hr/>
-
- <p>Weitere Hilfe ist verfügbar auf der <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Enigmail Per-Recipient Settings Seite</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/bg/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using the Enigmail Rules Editor: Edit OpenPGP Rule</h3>
-
- <p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. In this dialog, you can specify the rules for a single recipient, and for a group of recipients with very similar attributes.</p>
-
- <dl>
- <dt>Set OpenPGP Rules for</dt>
-
- <dd>Contains the email addresses of the recipients (without names, i.e. just an address like <tt>somebody@email.domain</tt>). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. <tt>@email.domain will</tt> allow matching to <tt>body@email.domain</tt>, <tt>somebody@email.domain</tt>, <tt>anybody@email.domain</tt>, etc.</dd>
-
- <dt>Apply rule if recipient ...</dt>
-
- <dd>
- This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on <tt>body@email.domain</tt> entered in the <em>OpenPGP Rules</em> field above.
-
- <ul>
- <li><em>Is exactly</em>: with this setting, the rule will only trigger on emails to <tt>body@email.domain</tt> (exact, case insensitive matching).</li>
-
- <li><em>Contains</em>: with this setting, any email address containing the string is matched, e.g. <tt>anybody@email.domain</tt> or <tt>body@email.domain.net</tt></li>
-
- <li><em>Begins with</em>: with this setting, any email address starting with the string is matched, e.g. <tt>body@email.domain.net</tt>, <tt>body@email.domain-name.com</tt>.</li>
-
- <li><em>Ends with</em>: with this setting, any email address ending with the string is matched, e.g. <tt>anybody@email.domain</tt> , <tt>somebody@email.domain</tt>.</li>
- </ul>
- </dd>
-
- <dt>Continue with the next rule for the matching address</dt>
-
- <dd>Enabling this function will allow you to define a rule but not have to specify a KeyID in the <em>Use the following OpenPGP keys:</em> field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.</dd>
-
- <dt>Do not check further rules for the matching address</dt>
-
- <dd>Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.</dd>
-
- <dt>Use the following OpenPGP keys:</dt>
-
- <dd>Use the <em>Select Key(s)..</em> button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.</dd>
-
- <dt>Default for Signing</dt>
-
- <dd>
- Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
-
- <ul>
- <li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
-
- <li><em>Yes, if selected from in Message Composition</em>: leave signing as specified in the message composition window</li>
-
- <li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
- </ul>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.
- </dd>
-
- <dt>Encryption</dt>
-
- <dd>Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.</dd>
- </dl>
-
- <p>The rules are processed in the order displayed in the list in the <em>OpenPGP Rules Editor</em>. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Enigmail Per-Recipient Settings page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/de/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,47 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail-Hilfe: Beheben von Problemen bei der Enigmail-Initialisierung</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail-Hilfe</h1>
-
- <h3>Beheben von Problemen bei der Enigmail-Initialisierung</h3>
-
- <p>Es gibt verschiedene Ursachen für ein Fehlschlagen der Enigmail-Initialisierung. Die bekanntesten werden unten beschrieben&
- für weitere Informationen besuchen Sie bitte die <a href="https://www.enigmail.net/support/" target="_blank">Enigmail-Hilfe-Webseite</a>.</p>
-
- <dl>
- <dt>GnuPG konnte nicht gefunden werden</dt>
- <dd>
- <p>
- Damit Enigmail funktionieren kann, muss die Anwendung <a href="https://www.gnupg.org/" target="_blank">GnuPG</a> installiert sein.
- Wenn GnuPG nicht gefunden werden kann, stellen Sie als erstes sicher, dass die Anwendung <tt>gpg.exe</tt> (für Windows& <tt>gpg</tt> für andere Plattformen) auf Ihrem PC tatsächlich vorhanden ist.
- Wenn GnuPG (<tt>gpg.exe</tt> bzw. <tt>gpg</tt>) tatsächlich installiert ist, aber Enigmail kann es trotzdem nicht finden, müssen Sie den Pfad zu GnuPG manuell in den Enigmail-Einstellungen angeben (Menü <i>Enigmail</i> > <i>Einstellungen...</i>).
- </p>
-
- <dt>Initialisierung von EnigMIME ist fehlgeschlagen</dt>
-
- <dd>
- <p>
- Enigmail funktioniert nur, wenn es in der gleichen Entwicklungsumgebung wie Thunderbird bzw. Seamonkey erstellt (kompiliert) wurde. Sie können das offizielle Enigmail zusammen mit offiziellen Veröffentlichungen von Thunderbird bzw. Seamonkey von <a href="www.mozilla.org">mozilla.org</a> verwenden.
- </p>
- <p>
- Wenn Sie Thunderbird oder Seamonkey in einer Version/Variante von einer anderen Quelle verwenden (z.B. vom Anbieter einer Linux-Distribution), oder wenn Sie die Anwendung selbst kompiliert haben, müssen Sie auch Enigmail in einer Version verwenden, die in der gleichen Entwicklungsumgebung kompiliert wurde. Um Enigmail selbst zu kompilieren, beachten Sie bitte die Angaben auf der Enigmail-Webseite im <a href="https://www.enigmail.net/download/source.php">Bereich Source-Code</a>. Bitte erstellen Sie keine Fehlerhinweise (Bugs) zu diesem Problem, da es dazu keine andere Lösung gibt.
- </p>
- </dd>
- </dl>
- <hr>
-
- <p>Weitere Hilfe ist verfügbar unter <a href="https://www.enigmail.net/support/troubles.php" target="_blank">Enigmail-Hilfeseite</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/configure 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/configure 2020-10-01 13:32:58.000000000 +0000
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for enigmail 2.1.6.
+# Generated by GNU Autoconf 2.69 for enigmail 2.2.4.
#
# Report bugs to <https://www.enigmail.net>.
#
@@ -579,8 +579,8 @@ MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME='enigmail'
PACKAGE_TARNAME='enigmail'
-PACKAGE_VERSION='2.1.6'
-PACKAGE_STRING='enigmail 2.1.6'
+PACKAGE_VERSION='2.2.4'
+PACKAGE_STRING='enigmail 2.2.4'
PACKAGE_BUGREPORT='https://www.enigmail.net'
PACKAGE_URL=''
@@ -1208,7 +1208,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures enigmail 2.1.6 to adapt to many kinds of systems.
+\`configure' configures enigmail 2.2.4 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1275,7 +1275,7 @@ fi
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of enigmail 2.1.6:";;
+ short | recursive ) echo "Configuration of enigmail 2.2.4:";;
esac
cat <<\_ACEOF
@@ -1358,7 +1358,7 @@ fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-enigmail configure 2.1.6
+enigmail configure 2.2.4
generated by GNU Autoconf 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
@@ -1375,7 +1375,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by enigmail $as_me 2.1.6, which was
+It was created by enigmail $as_me 2.2.4, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ $0 $@
@@ -2615,7 +2615,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_wri
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by enigmail $as_me 2.1.6, which was
+This file was extended by enigmail $as_me 2.2.4, which was
generated by GNU Autoconf 2.69. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -2668,7 +2668,7 @@ _ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
ac_cs_version="\\
-enigmail config.status 2.1.6
+enigmail config.status 2.2.4
configured by $0, generated by GNU Autoconf 2.69,
with options \\"\$ac_cs_config\\"
-
--- 2:2.1.6+ds1-1/lang/de/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=OpenPGP-Sicherheit
+Not Found
\ No newline at end of file
-
--- 2:2.1.6+ds1-1/lang/da/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,88 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Message Composition</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using Enigmail when composing messages</h3>
-
- <dl>
- <dt>Enigmail menu in Mail/Compose window</dt>
-
- <dd>
- <dl>
- <dt>Sign message</dt>
-
- <dd>Enable/Disable sending signed mail. User is notified, if signing fails.</dd>
-
- <dt>Encrypt message</dt>
- <dd>
- <p>Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.</p>
-
- <p>If <em>Display selection when necessary</em> is set in <strong>Preferences -> Key Selection tab</strong>, a list of keys will pop up if there are addresses in the list of recipients for the message for whom you have no public key.</p>
-
- <p>If <em>Never display OpenPGP key selection dialog</em> is set in <strong>Preferences -> Key Selection tab</strong>, and there are addresses in the list of recipients for the message for whom you have no public key, the message will be sent unencrypted.</p>
- </dd>
-
- <dt>Use PGP/MIME for this message</dt>
-
- <dd>
- Enable/Disable the use of <a href="https://tools.ietf.org/html/rfc3156">PGP/MIME</a> for this message.
-
- <p>If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.</p>
-
- <p>This feature is dependent on the settings in <strong>Preferences -> PGP/MIME tab</strong> being set to <em>Allow to use PGP/MIME</em> or <em>Always use PGP/MIME</em>.</p>
- </dd>
-
- <dt>Default composition options</dt>
-
- <dd>
- <ul>
- <li><strong>Signing/Encryption Options...</strong>: shortcut to <strong>Account Settings -> OpenPGP Options.</strong></li>
-
- <li><strong>Send options...</strong>: shortcut to <strong>Preferences -> Send</strong> tab.</li>
-
- <li><strong>Key selection options...</strong>: shortcut to <strong>Preferences -> Key Selection</strong> tab.</li>
-
- <li><strong>PGP/MIME options...</strong>: shortcut to <strong>Preferences -> PGP/MIME</strong> tab.</li>
- </ul>
- </dd>
-
- <dt>Undo encryption</dt>
-
- <dd>
- <p>If there is a failure when actually sending mail, such as the POP server not accepting the request, Enigmail will not know about it, and the encrypted message will continue to be displayed in the Compose window. Choosing this menu item will undo the encryption/signing, reverting the Compose window back to its original text.</p>
-
- <p><em>As a temporary fix, this option may also be used to decrypt the quoted text when replying to encrypted messages. Enigmail should automatically decrypt the quoted message, but if that fails for some reason, you can use this menu item to force it.</em></p>
- </dd>
-
- <dt>Insert public key</dt>
-
- <dd>insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.</dd>
-
- <dt>Clear save passphrase</dt>
-
- <dd>Clears cached passphrase. Useful if you have multiple passphrases.</dd>
-
- <dt>Help</dt>
-
- <dd>Displays Help information from the website (this page).</dd>
- </dl>
- </dd>
- </dl>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/">Enigmail Help web page</a></p>
-</body>
-</html>
-
lang/ar/enigmail.properties
-
--- 2:2.1.6+ds1-1/.eslintrc.js 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/.eslintrc.js 2020-10-01 13:32:58.000000000 +0000
@@ -80,4 +80,4 @@ module.exports = {
"Cr": true,
"Ci": true
}
-};
\ No newline at end of file
+};
-
lang/es-ES/enigmail.dtd
-
--- 2:2.1.6+ds1-1/lang/ca/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,76 +0,0 @@
-<html>
-<head><title>Ajuda Enigmail: Redacció de missatge</title>
-</head>
-<body>
-<h1>Ajuda Enigmail</h1>
-
-<h3>Emprant l'Enigmail per redactar missatges</h3>
-
-<ul>
- <li><b>El menú Enigmail a la finestra de Redacció</b>
- <li><b>Signa missatge</b>: Activa/desactiva l'enviament de correu signat. S'avisa a l'usuari si falla
- la signatura.
- </li>
- <li><b>Xifra missatge</b>: Activa/desactiva el xifratge a tots els destinataris abans d'enviar.
- S'avisa a l'usuari si falla el xifratge.
- <p>Si s'ha activat <em>Mostra la selecció només quan es necessiti</em> a <b>Preferències
- -> Pestanya de selecció de claus</b>, s'obrirà una llista de claus si hi ha adreces a la llista de
- destinataris del missatge pels que no teniu una clau pública.</p>
- <p>Si s'ha activat <em>No mostris mai el diàleg de selecció de claus OpenPGP</em> a <b>Preferències
- -> Pestanya de selecció de claus</b>, i hi ha adreces a la llista de destinataris del missatge pels
- que no teniu una clau pública, el missatge s'enviarà sense xifrar.</p>
- </li>
- <li><b>Empra PGP/MIME en aquest missatge</b>: Activa/desactiva l'ús del
- <a href="https://tools.ietf.org/html/rfc3156">PGP/MIME</a>
- en aquest missatge.
- <p>Si teniu coneixement que el(s) destinatari(s) pot llegir el correu codificat amb el format PGP/MIME,
- hauríeu d'activar-lo.</p>
- <p>Aquesta funcionalitat depèn de si estan actius els paràmetres <em>Permet l'ús de PGP/MIME</em> o
- <em>Empra sempre PGP/MIME</em> a <b>Preferències -> Pestanya PGP/MIME</b>.</p>
- </li>
- <li><b>Opcions de redacció predeterminades</b>: Submenú.
- <ul>
- <li><b>Opcions de signatura/xifratge...</b>: drecera a <b>Paràmetres del compte ->
- Opcions OpenPGP.</b>
- </li>
- <li><b>Opcions d'enviament...</b>: drecera a la pestanya <b>Preferències ->
- Enviament</b>.
- </li>
- <li><b>Opcions de selecció de clau...</b>: drecera a la pestanya <b>Preferències ->
- Selecció de clau</b>.
- </li>
- <li><b>Opcions PGP/MIME...</b>: drecera a la pestanya <b>Preferències ->
- PGP/MIME</b>.
- </li>
- </ul>
- </li>
- <li><b>Desfés el xifratge</b>: Si hi ha una errada quan s'enviï el corrreu,
- p.ex. que el servidor POP no accepta la petició, l'Enigmail no se n'assabentarà,
- i el missatge xifrat continuarà mostrant-se a la finestra de redacció.
- Seleccionant aquesta opció del menú es desfarà el xifratge/signatura, i es revertirà
- la finestra de redacció al text original.<br>
- <em>Com a solució provisional, aquesta opció es pot emprar per a desxifrar el text
- citat en respondre a missatges xifrats. L'Enigmail hauria de desxifrar automàticament
- el missatge citat, però si això falla per alguna raó, podeu emprar aquesta opció del menú
- per a forçar-ho.</em>
- </li>
- <li><b>Insereix la clau pública</b>: insereix el bloc ASCII-cuirassat amb la clau pública a
- la posició actual del cursor de la finestra de redacció. Es sol·licitarà l'adreça de correu
- de la clau(s) a inserir. Les claus inserides d'aquesta manera es reconeixeran automàticament
- a la recepció per l'Enigmail. Després de l'inserció de la clau, encara podeu
- signar/xifrar el correu si us cal. No inseriu més d'un bloc de clau a un missatge; només indiqueu
- vàries adreces de correu, separades per comes o espais quan es sol·liciti.
- </li>
- <li><b>Neteja la contrasenya desada</b>: Neteja la contrasenya memoritzada. És útil
- si teniu vàries contrasenyes.
- </li>
- <li><b>Ajuda</b>: Mostra la informació d'ajuda del lloc web (aquesta pàgina).
- </li>
-</ul>
-<hr/>
-<p>
-Teniu més ajuda a la vostra disposició a la
-<a href="https://www.enigmail.net/support/" target="_blank">pàgina web de l'Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/patches/series 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/series 2020-10-07 15:48:06.000000000 +0000
@@ -1,11 +1,5 @@
-0001-avoid-eslint-during-buildtest.patch
0002-Avoid-auto-download-of-pEpEngine-Closes-891882.patch
-0003-avoid-OpenPGP.js-when-building.patch
-0004-copy-enums.armor-from-OpenPGP.js.patch
0006-enable-the-use-of-extra-file-descriptors-and-test-th.patch
0007-add-test-to-do-symmetric-encryption-decryption-with-.patch
-0008-use-GnuPG-instead-of-openpgp.js-for-symmetric-encryp.patch
-0011-drop-unnecessary-tests.patch
0012-Fix-parallel-build.patch
-0010-fixed-bug-1057-Hockeypuck-keyservers-reject-uploads-.patch
-0011-skip-record-if-nothing-found-broken-Find-keys-for-al.patch
+0013-fix-eslint-errors.patch
-
--- 2:2.1.6+ds1-1/debian/patches/0001-avoid-eslint-during-buildtest.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0001-avoid-eslint-during-buildtest.patch 1970-01-01 00:00:00.000000000 +0000
@@ -1,24 +0,0 @@
-From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
-Date: Mon, 25 Jan 2016 13:22:44 -0500
-Subject: avoid eslint during buildtest
-
-eslint is not yet in debian (see https://bugs.debian.org/743404).
-once it is packaged, we should remove this patch and allow the full
-testsuite to run on the debian buildd infrastructure.
----
- Makefile | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/Makefile b/Makefile
-index 308c34a..f74f9e5 100644
---- a/Makefile
-+++ b/Makefile
-@@ -43,7 +43,7 @@ unit:
- make -C ui/tests
- make -C ipc/tests
-
--test: eslint check unit
-+test: check unit
-
- clean:
- rm -f build/$(XPIFILE) .eslintcache
-
--- 2:2.1.6+ds1-1/lang/es-ES/am-enigprefs.properties 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-ES/am-enigprefs.properties 2020-10-01 13:32:58.000000000 +0000
@@ -1,2 +1 @@
-# Strings used in the Mozill AccountManager
-prefPanel-enigprefs=Seguridad de OpenPGP
+Not Found
\ No newline at end of file
-
lang/cs/enigmail.properties
-
--- 2:2.1.6+ds1-1/lang/es-AR/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-AR/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: How to Resolve Problems with Initializing OpenPGP</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head>
-
-<body>
- <h1>Ayuda de Enigmail</h1>
-
- <h3>Cómo Resolver Problemas al Iniciar OpenPGP</h3>
-
- <p>Hay varias razones por las que no se tiene éxito al inicializar OpenPGP. Las más comunes son descritas más abajo &
- para más información por favor visite la <a href="https://www.enigmail.net/support/" target="_blank">página de Soporte de Enigmail.</a></p>
-
- <dl>
- <dt>No se pudo encontrar GnuPG</dt>
- <dd>
- <p>
- Para que funcione OpenPGP, la herramienta <a href="https://www.gnupg.org/" target="_blank">GnuPG</a> debe ser instalada.
- Si GnuPG no puede ser encontrado, entonces primero asegúrese de que el ejecutable <tt>gpg.exe</tt> (en Windows& <tt>gpg</tt> en otras plataformas) esté instalado en su computador.
- Si GnuPG está instalado, y OpenPGP no puede encontrarlo, entonces usted necesitará configurar manualmente la ruta a GnuPG en las Preferencias de OpenPGP (menú <i>OpenPGP</i> > <i>Preferencias</i>) </p>
-
- <dt>Enigmime falló al inicilizarse</dt>
-
- <dd>
- <p>
- OpenPGP solamente funciona si es compilado usando el mismo ambiente de compilación en que Thunderbird o SeaMonkey fue compilado. Esto significa que usted sólo puede usar la versión oficial de Enigmail si utiliza las versiones oficiales de Thunderbird o SeaMonkey provistas por <a href="www.mozilla.org">mozilla.org</a>. </p>
- <p>
- Si usted utiliza una versión de Thunderbird o SeaMonkey provista por otra fuente (p.ej. el proveedor de su distribución de Linux), o si usted compiló la aplicación por si mismo, ustede debe, o bien usar una versión de Enigmail del mismo proveedor, o compilar Enigmail usted mismo. Para compilar Enigmail, refiérase a la <a href="https://www.enigmail.net/download/source.php">sección de Código Fuente</a> en la página de Enigmail. Por favor no envie reportes de bugs acerca de este problema, no puede ser solucionado.</p>
- </dd>
- </dl>
-
- <p>Más ayuda está disponible en el <a href="https://www.enigmail.net/support/troubles.php" target="_blank">Sitio Web de Soporte de Enigmail</a>.</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/el/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<title>Βοήθεια του Enigmail</title>
-</head>
-
-<body>
-<h1>Βοήθεια του Enigmail</h1>
-<h3>Ανάγνωση μηνυμάτων με το Enigmail</h3>
-<ul>
- <li><b>Το κουμπί Αποκρυπτογράφησης στο κύριο παράθυρο</b><br />
- Αυτό το κουμπί εξυπηρετεί πολλούς σκοπούς: αποκρυπτογράφηση, επαλήθευση ή εισαγωγή δημόσιων κλειδιών. Κανονικά η αποκρυπτογράφηση/επαλήθευση γίνεται αυτόματα, παρότι αυτό μπορεί να αλλαχτεί. Αν όμως παρουσιαστεί πρόβλημα, θα εμφανιστεί ένα περιληπτικό μήνυμα στη γραμμή κατάστασης του Enigmail. Αν κάνετε κλικ στο κουμπί Αποκρυπτογράφησης, θα μπορέσετε να δείτε ένα πιο λεπτομερές μήνυμα καθώς και την έξοδο της εντολής GnuPG. </li>
- <li><b>Τα εικονίδια Πένας και Κλειδιού στην Κεφαλίδα του μηνύματος</b><br />
- Τα εικονίδια <em>Πένας</em> και <em>Κλειδιού</em> στην Κεφαλίδα του μηνύματος δηλώνουν αν το μήνυμα που διαβάζετε είναι υπογεγραμμένο και/ή κρυπτογραφημένο και αν η υπογραφή είναι έγκυρη, το μήνυμα δεν αλλάχτηκε μετά την υπογραφή του. Αν το μήνυμα έχει αλλαχτεί, το εικονίδιο <em>Πένας</em> θα αντικατασταθεί από το εικονιδίου <em>Σπασμένου κλειδιού</em> το οποίο δηλώνει ότι η υπογραφή δεν είναι έγκυρη. Κάνοντας δεξί κλικ σε ένα από τα δύο εικονίδια θα εμφανιστεί ένα μενού με τις ακόλουθες επιλογές:
- <ul>
- <li><em>Πληροφορίες ασφαλείας OpenPGP</em>: σας εμφανίζει την κατάσταση εξόδου του GnuPG για το μήνυμα.</li>
- <li><em>Αντιγραφή πληροφοριών ασφαλείας OpenPGP</em>: αντιγράφει την κατάσταση εξόδου του GnuPG στο πρόχειρο· για να την επικολλήσετε σε κάποιο μήνυμα κλπ.</li>
- <li><em>Εμφάνιση ID φωτογραφίας OpenPGP</em>: σας εμφανίζει το <em>ID φωτογραφίας</em> του ατόμου που σας έστειλε το μήνυμα, αν βέβαια αυτή υπάρχει στο Δημόσιο Κλειδί του. (<em>Αυτή η επιλογή είναι διαθέσιμο μόνο αν το ID φωτογραφίας OpenPGP υπάρχει στο κλειδί.)</em></li>
- <li><em>Πληροφορίες ασφαλείας S/MIME</em>: σας εμφανίζει τις πληροφορίες ασφαλείας S/MIME για το μήνυμα.</li>
- </ul>
- <p>Αν δεν έχετε ενεργοποιημένη την επιλογή <em>keyserver-options auto-key-retrieve</em> στο αρχείο <tt>gpg.conf</tt> σας, και διαβάζετε ένα μήνυμα που είναι υπογεγραμμένο ή κρυπτογραφημένο, στην κεφαλίδα του μηνύματος θα εμφανιστεί το εικονίδιο <em>Πένας</em> με ένα <em>Ερωτηματικό</em> πάνω του, ενώ το μήνυμα στη γραμμή κατάστασης του Enigmail θα λέει <em>Τμήμα του μηνύματος υπογεγραμμένο· κάντε κλικ στο εικονίδιο Πένας για πληροφορίες</em> και στην περιοχή κειμένου του μηνύματος θα εμφανίζονται όλα τα OpenPGP μπλοκ και το μπλοκ της υπογραφής.</p>
- <p>Αυτό μπορεί επίσης να συμβεί όταν το κλειδί δεν υπάρχει στον προκαθορισμένο εξυπηρετητή κλειδιών, ακόμα κι αν έχετε ενεργοποιημένη την επιλογή<em>keyserver-options auto-key-retrieve</em> στο <tt>gpg.conf</tt> σας.</p>
- <p>Κάνοντας κλικ στο εικονίδιο <em>Πένας και Ερωτηματικού</em> θα εμφανιστεί ένα παράθυρο που θα σας πληροφορεί ότι το κλειδί δεν είναι διαθέσιμο στη λίστα κλειδιών σας. Πατώντας OK θα εμφανιστεί ένα άλλο παράθυρο με μία λίστα εξυπηρετητών κλειδιών για να επιλέξετε από ποιον θα γίνει λήψη του δημόσιου κλειδιού του αποστολέα.</p>
- <p>Για να ορίσετε τη λίστα των εξυπηρετητών κλειδιών που θέλετε να χρησιμοποιείτε, πηγαίνετε στην καρτέλα <b>Enigmail -> Προτιμήσεις -> Βασικές</b> και εισάγετε τις διευθύνσεις στο πεδίο <em>Εξυπηρετητής(ές) κλειδιών:</em>, χωρισμένες με κόμματα.<em> Ο πρώτος εξυπηρετητής στη λίστα θα χρησιμοποιηθεί ως ο προκαθορισμένος.</em></p>
- </li>
- <li><b>Άνοιγμα κρυπτογραφημένων επισυνάψεων / εισαγωγή ενσωματωμένων κλειδιών OpenPGP</b><br />
- Επισυνάψεις με όνομα *.pgp, *.asc και *.gpg αναγνωρίζονται ως επισυνάψεις που το Enigmail θα τις διαχειριστεί με ειδικό τρόπο. Κάνοντας δεξί κλικ σε μία τέτοια επισύναψη θα ενεργοποιήσει δύο ειδικές καταχωρήσεις στο μενού που θα εμφανιστεί: <em>Αποκρυπτογράφηση και Άνοιγμα</em> και <em>Αποκρυπτογράφηση και Αποθήκευση</em>. Χρησιμοποιήστε τις αν θέλετε το Enigmail αποκρυπτογραφήσει την επισυνάψεις πριν το άνοιγμα ή την αποθήκευσή της. Αν η επισύναψη αναγνωριστεί ως αρχείο κλειδιού OpenPGP, θα ερωτηθείτε αν θέλετε να γίνει εισαγωγή του κλειδιού στη λίστα κλειδιών σας. </li>
-</ul>
-<hr />
-<p> Περισσότερη βοήθεια είναι διαθέσιμη στο δικτυακό τόπο του <a href="https://www.enigmail.net/support/" target="_blank">Enigmail</a> <br />
-Αν έχετε ερωτήσεις ή σχόλια σχετικά με το enigmail, παρακαλώ στείλτε ένα μήνυμα στη λίστα του <a href="https://www.enigmail.net/support/list.php" target="_blank">Enigmail OpenPGP</a></p>
-<p>Το Enigmail OpenPGP είναι λογισμικό ανοικτού κώδικα και κυκλοφορεί υπό την <a href="https://mozilla.org/MPL/2.0/" target="_blank">Mozilla Public License 2.0</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/tests/unit-tests 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/tests/unit-tests 1970-01-01 00:00:00.000000000 +0000
@@ -1,21 +0,0 @@
-#!/bin/bash
-
-mkdir -p config
-cat > config/autoconf.mk <<EOF
-XPI_MODULE_VERS = $(dpkg-parsechangelog -S Version | sed s'/-[^-]*$//')
-
-PERL = /usr/bin/perl
-PYTHON = /usr/bin/python3
-
-TB_PATH = "/usr/bin/thunderbird"
-TB_ARGS = --headless --profile $(pwd)/test-profile
-
-JSUNIT = $(pwd)/util/run-jsunit /usr/bin/perl /usr/bin/thunderbird --headless --profile $(pwd)/test-profile
-EOF
-debian/run-tests autopkgtest
-test_ret=$?
-printf 'looking at filesystems:\n'
-cat /proc/mounts
-printf 'contents of %s/test-profile/enigmail.sqlite:\n' "$(pwd)"
-echo .dump | sqlite3 $(pwd)/test-profile/enigmail.sqlite
-exit "$test_ret"
-
--- 2:2.1.6+ds1-1/config/autoconf.mk.in 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/config/autoconf.mk.in 2020-10-01 13:32:58.000000000 +0000
@@ -11,20 +11,12 @@ TB_ARGS = @TB_ARGS@
TESTS = @enable_tests@
FIX_LANGUAGES = @enable_fix_lang@
ENABLE_LANG = @enable_lang@
-ENABLE_POSTBOX = @enable_postbox@
+ENABLE_POSTBOX =
srcdir = @srcdir@
-JSUNIT = $(DEPTH)/util/run-jsunit $(PERL) $(TB_PATH) $(TB_ARGS)
-
-ifeq ($(ENABLE_POSTBOX),yes)
-TARGET_TOOL=pbx
-INCLUDE = $(DEPTH)/include/postbox.h
-BUILD = $(DEPTH)/build-pbx
-else
TARGET_TOOL=tbird
INCLUDE = $(DEPTH)/include/tbird.h
BUILD = $(DEPTH)/build-tb
-endif
DIST = $(BUILD)/dist
-
--- 2:2.1.6+ds1-1/lang/ar/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/es-AR/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-AR/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/el/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,69 +0,0 @@
-<html>
-<head><title>Βοήθεια του Enigmail: Επεξεργασία κανόνων OpenPGP</title>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-</head>
-<body>
-<h1>Βοήθεια του Enigmail</h1>
-
-<h3>Χρήση του Επεξεργαστή κανόνων του Enigmail: Επεξεργασία κανόνων OpenPGP</h3>
-<p>Στον Επεξεργαστή κανόνων, μπορείτε να καθορίσετε τις προκαθορισμένες επιλογές για κάθε παραλήπτη για την ενεργοποίηση της κρυπτογράφησης, υπογραφής και χρήση PGP/MIME, και να επιλέξετε τα κλειδιά OpenPGP που θα χρησιμοποιηθούν. Σε αυτόν το διάλογο μπορείτε να καθορίσετε τους κανόνες για ένα συγκεκριμένο παραλήπτη, ή για μια ομάδα παραληπτών με παρόμοιες ιδιότητες.
-</p>
-<ul>
- <li><span style="font-weight: bold;">Ορισμός κανόνων OpenPGP για</span>: Περιέχει τις διευθύνσεις αλληλογραφίας των παραληπτών (χωρίς ονόματα, δηλ. απλώς τη διεύθυνση, όπως η <tt>somebody@email.domain</tt>). Μπορείτε να εισάγετε παραπάνω από μία διεύθυνση, χωρίζοντάς τες με κενά. Οι διευθύνσεις μπορούν να περιέχουν μόνο τον τομέα ώστε ο κανόνας να εφαρμόζεται σε όλες τις διευθύνσεις από αυτόν τον τομέα. Παράδειγμα: εισάγοντας το <tt>@email.domain</tt>, ο κανόνας να εφαρμοστεί στα <tt>body@email.domain</tt>,
- <tt>somebody@email.domain</tt>, <tt>anybody@email.domain</tt>, κλπ.
- </li>
- <li><span style="font-weight: bold;">Εφαρμογή κανόνα αν ο παραλήπτης ...</span>:
- Αυτό καθορίζει τον τρόπο ταιριάσματος της διεύθυνσης αλληλογραφίας.
- Αν έχουν εισαχθεί πολλαπλές διευθύνσεις, η ρύθμιση θα εφαρμοστεί σε όλες.
- Τα παρακάτω παράδειγμα βασίζονται στο ότι το <tt>body@email.domain</tt>
- έχει εισαχθεί στο παραπάνω πεδίο <i>Ορισμός κανόνων OpenPGP για</i>.
- <ul>
- <li><i>είναι ακριβώς</i>: με αυτήν την επιλογή, ο κανόνας θα εφαρμοστεί μόνο σε μηνύματα προς το <tt>body@email.domain</tt> (ακριβές ταίριασμα, χωρίς διάκριση πεζών/κεφαλαίων).
- </li>
- <li><i>περιέχει</i>: με αυτήν την επιλογή, ο κανόνας θα εφαρμοστεί σε οποιαδήποτε διεύθυνση περιέχει τη συμβολοσειρά,
- δηλ. <tt>anybody@email.domain</tt> ή <tt>body@email.domain.net</tt>
- </li>
- <li><i>αρχίζει με</i>: με αυτήν την επιλογή, ο κανόνας θα εφαρμοστεί σε οποιαδήποτε διεύθυνση αρχίζει με τη συμβολοσειρά, δηλ. <tt>body@email.domain.net</tt>, <tt>body@email.domain-name.com</tt> κλπ.
- </li>
- <li><i>τελειώνει με </i>: με αυτήν την επιλογή, ο κανόνας θα εφαρμοστεί σε οποιαδήποτε διεύθυνση τελειώνει με τη συμβολοσειρά, δηλ. <tt>anybody@email.domain</tt>, <tt>somebody@email.domain</tt> κλπ.
- </li>
- </ul>
-
- </li>
- <li><span style="font-weight: bold;">Συνέχιση με τον επόμενο κανόνα για τη διεύθυνση</span><br>
- Ενεργοποιώντας αυτήν την επιλογή μπορείτε να ορίσετε έναν κανόνα χωρίς να χρειαστεί να εισάγετε
- ένα ID κλειδιού στο πεδίο <em>Χρήση των ακόλουθων κλειδιών OpenPGP:</em>, ώστε η διεύθυνση να χρησιμοποιηθεί για τον έλεγχο του κλειδιού την ώρα της αποστολής. Επίσης, θα εφαρμοστούν οι επόμενοι κανόνες για τη διεύθυνση.
- </li>
- <li><span style="font-weight: bold;">Να μη γίνει έλεγχος άλλων κανόνων για τη διεύθυνση</span><br>
- Ενεργοποιώντας αυτήν την επιλογή μπορείτε να σταματήσετε τον έλεγχο της συγκεκριμένης διεύθυνσης, δηλ. ο έλεγχος κανόνων συνεχίζεται για την επόμενη διεύθυνσή
- </li>
- <li><span style="font-weight: bold;">Χρήση των ακόλουθων κλειδιών OpenPGP:</span><br>
- Χρησιμοποιήστε το κουμπί <em>Επιλογή κλειδιού(ών)...</em> για να επιλέξετε τα κλειδιά του παραλήπτη που θα χρησιμοποιηθούν για την κρυπτογράφηση. Όπως και στην παραπάνω ενέργεια, δε θα ελεγχθούν οι επόμενοι κανόνες για τη διεύθυνση.
- </li>
- <li><span style="font-weight: bold;">Εξ ορισμού για υπογραφή</span>: ενεργοποίηση ή απενεργοποίηση της υπογραφής του μηνύματος. Αυτό είτε χρησιμοποιεί ή παρακάμπτει την επιλογή που κάνατε στο παράθυρο Σύνταξης του μηνύματος. Διαθέσιμες τιμές είναι οι:
- <ul>
- <li><i>Ποτέ</i>: απενεργοποιεί την υπογραφή, ακόμα και αν έχει ενεργοποιηθεί στο παράθυρο Σύνταξης του μηνύματος<br>
- </li>
- <li><i>Ναι, αν επιλεγεί στη σύνταξη μηνύματος</i>: θα χρησιμοποιηθεί η επιλογή που έγινε στο παράθυρο Σύνταξης του μηνύματος
- </li>
- <li><i>Πάντα</i>: ενεργοποιεί την υπογραφή, ακόμα και αν <span
- style="font-style: italic;">δεν</span> έχει ενεργοποιηθεί στο παράθυρο Σύνταξης του μηνύματος
- </li>
- </ul>
- </li>
-</ul>
-<div style="margin-left: 40px;">Αυτές οι επιλογές εφαρμόζονται σε όσους κανόνες ταιριάζουν. Αν κάποιος κανόνας απενεργοποιεί την υπογραφή, το μήνυμα δε θα υπογραφεί, ανεξάρτητα από άλλους κανόνες που χρησιμοποιούν το <i>Πάντα</i>.<br>
-</div>
-<ul>
- <li><span style="font-weight: bold;">Κρυπτογράφηση</span>: ενεργοποιεί ή απενεργοποιεί την κρυπτογράφηση του μηνύματος. Οι επιτρεπόμενες τιμές και το νόημά τους είναι ίδιες με αυτές της υπογραφής.</li>
- <li><span style="font-weight: bold;">PGP/MIME</span>: ενεργοποιεί ή απενεργοποιεί τη χρήση της κωδικοποίησης PGP/MIME (RFC 3156) για το μήνυμα.
- Αν απενεργοποιηθεί, τα μηνύματα θα κωδικοποιούνται με "εμβόλιμο PGP". Οι επιτρεπόμενες τιμές και το νόημά τους είναι ίδιες με αυτές της υπογραφής.
-</ul>
-<p>Οι κανόνες εφαρμόζονται με τη σειρά που βρίσκονται στη λίστα του <em>Επεξεργαστή κανόνων OpenPGP</em>. Κάθε φορά που ένας κανόνας ταιριάζει με έναν παραλήπτη και περιέχει ένα ID κλειδιού OpenPGP, εκτός του ότι θα χρησιμοποιηθεί το καθορισμένο ID κλειδιού, ο παραλήπτης δε θα θεωρείται διαθέσιμος για τους υπόλοιπους κανόνες.
-</p>
-<hr/>
-<p>Περισσότερη βοήθεια είναι διαθέσιμη στο δικτυακό τόπο του
-<a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/de/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail-Hilfe: Lesen von Nachrichten</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
-<h1>Enigmail-Hilfe</h1>
-
-<h3>Verwenden von Enigmail beim Lesen von Nachrichten</h3>
-
- <dl>
- <dt>Schaltfläche "Entschlüsseln" im Hauptfenster</dt>
-
- <dd>Diese Schaltfläche kann für mehrere Zwecke verwendet werden: zum Entschlüsseln, Überprüfen, oder Importieren von öffentlichen Schlüsseln. Im Normalfall werden Nachrichten automatisch entschlüsselt und überprüft. Dies kann jedoch in den Einstellungen deaktiviert werden. Sollte das Entschlüsseln fehlschlagen, dann erscheint im Regelfall eine kurze Fehlermeldung in der Statuszeile von Enigmail. Sie werden dann, wenn Sie die Schaltfläche "Entschlüsseln" anklicken, eine detaillierte Fehlermeldung (inklusive der Meldung von der OpenPGP-Kommandozeile) erhalten.</dd>
-
- <dt>Schlüssel- und/oder Stift-Symbol in der Statusleiste einer Nachricht</dt>
-
- <dd>
- Das <em>Stift-</em> und das <em>Schlüssel-</em>Symbol in der Statusleiste geben an, ob die Nachricht unterschrieben und/oder verschlüsselt ist und ob die Unterschrift gültig ist, d.h. dass die Nachricht seit ihrem Senden nicht geändert wurde. Falls die Nachricht geändert wurde, wird der <em>Stift</em> rot dargestellt, um auf die Ungültigkeit der Unterschrift hinzuweisen. Nach einem Klick auf "Details" in der Enigmail-Zeile im Nachrichtenkopf wird ein Menü mit den folgenden Optionen angezeigt:
-
- <ul>
- <li><em>Schlüssel importieren</em>: importiert eventuell angehängte öffentliche Schlüssel in Ihren Schlüsselring in der Schlüsselverwaltung.</li>
-
- <li><em>Enigmail-Sichheitsinfo...</em>: ermöglicht Ihnen, die Statusmeldungen der Enigmail-Kommandozeile für die Nachricht anzusehen.</li>
-
- <li><em>Enigmail-Sicherheitsinfo kopieren</em>: kopiert die Statusmeldungen von Enigmail in die Zwischenablage, damit man sie z.B. in eine Antwortnachricht etc. einfügen kann.</li>
-
- <li><em>Foto-ID anzeigen</em>: ermöglicht Ihnen, die <em>Foto-ID</em> der Person, die die Nachricht gesendet hat, anzusehen, falls diese ein Foto in dem öffentlichen Schlüssel eingebettet hat. (<em>Diese Option is nur verfügbar wenn ein Foto in dem öffentlichen Schlüssel eingebettet ist.)</em></li>
-
- <li><em>Schlüssel unterschreiben</em>: lässt Sie den Schlüssel des Absenders unterschreiben.</li>
-
- <li><em>Besitzervertrauen des Absenders festlegen...</em>: lässt Sie das Besitzervertrauen des Absenders festlegen, falls dessen Schlüssel in Ihrem Schlüsselring vorhanden ist.</li>
-
- </ul>
-
- <p>Falls Sie <em>keyserver-options auto-key-retrieve</em> nicht in der Datei <tt>gpg.conf</tt> eingestellt haben, und Sie lesen eine Nachricht, die signiert oder verschlüsselt ist, dann erscheint ein <em>Stift-</em>Symbol mit einem <em>Fragezeichen</em>. Die Enigmail-Statuszeile im Kopfzeilenbereich der Nachricht wird melden: <em>Ein Teil der Nachricht ist signiert; klicken Sie auf das Stift-Symbol für Details</em>, und im Nachrichtentext werden alle PGP-Nachrichtenblockanzeiger und Signaturblöcke angezeigt.</p>
-
- <p>Dies kann außerdem angezeigt werden, wenn Sie <em>keyserver-options auto-key-retrieve</em> in der Datei <tt>gpg.conf</tt> eingestellt haben aber der OpenPGP-Schlüssel nicht auf dem voreingestellten Schlüssel-Server verfügbar ist.</p>
-
- <p>Wenn Sie auf das <em>Schlüssel mit Fragezeichen</em>-Symbol klicken, dann erhalten Sie die Meldung, dass der Schlüssel nicht in Ihrem Schlüsselring verfügbar ist. Wenn Sie OK klicken, dann öffnet sich ein Fenster mit einer Liste von Schlüssel-Servern, aus der Sie einen auswählen können, um den öffentlichen Schlüssel des Absenders herunterzuladen.</p>
-
- <p>Um die Liste der Schlüssel-Server, die Sie verwenden möchten, zu konfigurieren, gehen Sie zu <b>Enigmail -> Einstellungen... -> Allgemein</b> und geben die Adressen der Schlüssel-Server im Feld <em>Schlüssel-Server</em> ein (jeweils getrennt durch ein Komma). <em>Der erste Schlüssel-Server wird als voreingestellter Server verwendet.</em></p>
- </dd>
-
- <dt>Öffnen von verschlüsselten Dateianhängen / Importieren von angehängten OpenPGP-Schlüsseln</dt>
-
- <dd>Dateianhänge mit den Endungen *.pgp, *.asc und *.gpg werden von Enigmail als Anhänge erkannt, die speziell mit Enigmail bearbeitet werden können. Durch einen Rechtsklick auf solch einen Dateianhang werden zwei spezielle Menüeinträge im Kontextmenü angezeigt: <em>Entschlüsseln und Öffnen</em> und <em>Entschlüsseln und Speichern</em>. Verwenden Sie diese Menüeinträge, falls Enigmail einen Dateianhang entschlüsseln soll, bevor Sie ihn öffnen oder speichern. Wenn ein Anhang als PGP-Schlüsseldatei erkannt wird, dann werden Sie gefragt, ob sie diese(n) Schlüssel in ihren Schlüsselring importieren möchten.</dd>
- </dl>
- <hr />
-
- <p>Weitere Hilfe ist verfügbar unter <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Hilfeseite</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/da/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: How to Resolve Problems with Initializing Enigmail</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>How to Resolve Problems with Initializing Enigmail</h3>
-
- <p>There are several reasons why initializing Enigmail does not succeed. The most common ones are described below;
- for more information please visit the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Support page.</a></p>
-
- <dl>
- <dt>GnuPG could not be found</dt>
- <dd>
- <p>
- In order for Enigmail to work, the tool <a href="https://www.gnupg.org/" target="_blank">GnuPG</a> needs to be installed.
- If GnuPG cannot be found, then first make sure that the executable <tt>gpg.exe</tt> (on Windows; <tt>gpg</tt> on other platforms) is installed on your computer.
- If GnuPG is installed, and Enigmail cannot find it, then you need to manually set the path to GnuPG in the Enigmail Preferences (menu <i>Enigmail</i> > <i>Preferences</i>)
- </p>
-
- <dt>Enigmail Core Service failed to initialize</dt>
-
- <dd>
- <p>
- Enigmail works only if it is built using the same build environment as Thunderbird or SeaMonkey was built. This means that you can use the official Enigmail releases only if you use the official releases of Thunderbird or SeaMonkey provided by <a href="www.mozilla.org">mozilla.org</a>.
- </p>
- <p>
- If you use a Thunderbird or SeaMonkey version coming from some other source (e.g. the provider of your Linux distribution), or if you built the application yourself, you should either use an Enigmail version built by the same source, or build Enigmail yourself. For building Enigmail, refer to the <a href="https://www.enigmail.net/download/source.php">Source Code section</a> on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
- </p>
- </dd>
- </dl>
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/troubles.php" target="_blank">Enigmail Support Web Site</a>.</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/da/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit Per-Recipient Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using the Enigmail Rules Editor: Edit Per-Recipient Rule</h3>
-
- <p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. In this dialog, you can specify the rules for a single recipient, and for a group of recipients with very similar attributes.</p>
-
- <dl>
- <dt>Set Enigmail Rules for</dt>
-
- <dd>Contains the email addresses of the recipients (without names, i.e. just an address like <tt>somebody@email.domain</tt>). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. <tt>@email.domain will</tt> allow matching to <tt>body@email.domain</tt>, <tt>somebody@email.domain</tt>, <tt>anybody@email.domain</tt>, etc.</dd>
-
- <dt>Apply rule if recipient ...</dt>
-
- <dd>
- This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on <tt>body@email.domain</tt> entered in the <em>Enigmail Rules</em> field above.
-
- <ul>
- <li><em>Is exactly</em>: with this setting, the rule will only trigger on emails to <tt>body@email.domain</tt> (exact, case insensitive matching).</li>
-
- <li><em>Contains</em>: with this setting, any email address containing the string is matched, e.g. <tt>anybody@email.domain</tt> or <tt>body@email.domain.net</tt></li>
-
- <li><em>Begins with</em>: with this setting, any email address starting with the string is matched, e.g. <tt>body@email.domain.net</tt>, <tt>body@email.domain-name.com</tt>.</li>
-
- <li><em>Ends with</em>: with this setting, any email address ending with the string is matched, e.g. <tt>anybody@email.domain</tt> , <tt>somebody@email.domain</tt>.</li>
- </ul>
- </dd>
-
- <dt>Continue with the next rule for the matching address</dt>
-
- <dd>Enabling this function will allow you to define a rule but not have to specify a KeyID in the <em>Use the following OpenPGP keys:</em> field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.</dd>
-
- <dt>Do not check further rules for the matching address</dt>
-
- <dd>Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.</dd>
-
- <dt>Use the following OpenPGP keys:</dt>
-
- <dd>Use the <em>Select Key(s)..</em> button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.</dd>
-
- <dt>Default for Signing</dt>
-
- <dd>
- Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
-
- <ul>
- <li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
-
- <li><em>Yes, if selected from in Message Composition</em>: leave signing as specified in the message composition window</li>
-
- <li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
- </ul>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.
- </dd>
-
- <dt>Encryption</dt>
-
- <dd>Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.</dd>
- </dl>
-
- <p>The rules are processed in the order displayed in the list in the <em>Per-Recipient Rules Editor</em>. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Enigmail Per-Recipient Settings page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/current-languages.txt 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/current-languages.txt 2020-10-01 13:32:58.000000000 +0000
@@ -13,6 +13,7 @@ gd
gl
hr
hu
+hy
it
ja
ko
-
--- 2:2.1.6+ds1-1/lang/cs/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/cs/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Nápověda pro Enigmail: editor pravidel</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
- <style type="text/css" xml:space="preserve">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Nápověda pro Enigmail</h1>
-
-<h3>Použití editoru pravidel v Enigmailu</h3>
-<p>V editoru pravidel můžete pro každého příjemce nastavit výchozí chování Enigmailu tak, že povolíte
-šifrování, podpis, PGP/MIME a určíte klíč(e) OpenPGP, který se bude pro daného příjemce používat.
-Každé pravidlo se skládá z 5 položek a je reprezentováno jedním řádkem:
-</p>
-<dl>
- <dt>Email</dt>
- <dd>Určení emailové(ých) adresy (adres) z polí Komu:, Kopie: a Skrytá kopie:, pro kterou(é) se pravidlo použije. Určení probíhá podle <span style="font-style: italic;">podřetězců</span> (více podrobností najdete v dialogu při vytváření pravidla).</dd>
-
- <dt>Klíč(e) OpenPGP</dt>
- <dd>Seznam ID klíčů OpenPGP k použití pro zvoleného příjemce</dd>
-
- <dt>Podpis</dt>
- <dd>Povolit / zakázat podepsání zprávy. Použije se zadaná hodnota anebo bude přepsána hodnota nastavená v okně vytváření zprávy. Možnosti jsou:
-
- <ul>
- <li><em>Nikdy</em>: zakáže podepsání zprávy bez ohledu na to, jaká volba je v okně psaní zprávy. Tato volba potlačuje ostatní.</li>
- <li><em>Možný</em>: ponechá podepisování zprávy na nastavení v okně psaní zprávy.</li>
- <li><em>Vždy</em>: zprávy bude podepsána, i kdyby to v okně psaní zprávy povoleno nebylo.</li></ul>
-
-<p>Nastavení pro podepisování se použije pro všechna odpovídající pravidla. Jestliže jedno pravidlo podepsání zakazuje, zpráva nebude podepsána bez ohledu na to, zda ostatní pravidla mají nastavenou volbu <em>Vždy</em>.</p></dd>
-
- <dt>Šifrování</dt>
- <dd>Povolit / zakázat šifrování zprávy. Nastavení šifrování a jeho význam jsou podobné jako nastavení podepisování.</dd>
-
- <dt>PGP/MIME</dt>
- <dd> Povolit / zakázat kódování zprávy pomocí PGP/MIME (RFC 3156). Pokud je PGP/MIME zakázáno, zpráva je kódována použitím "vkládaného PGP" ("inline PGP"). Nastavení a jeho význam jsou podobné jako nastavení podepisování.</dd>
-
-</dl>
-
-<p>Pravidla jsou zpracována v pořadí podle uvedeného seznamu. Vždy, když pravidlo odpovídá příjemci a obsahuje ID klíče OpenPGP, příjemce se již kromě použití určeného klíče v dalších pravidlech nezpracovává.</p>
-
-<p><em>Poznámka:</em> Editor pravidel ještě není kompletní. Je možno napsat složitější pravidla přímou úpravou souboru pravidel, avšak tyto pravidla již pak nesmíte upravovat pomocí editoru
-pravidel. <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Další informace</a> o přímé úpravě souboru s pravidly si můžete přečíst na stránkách Enigmailu (anglicky).</p>
-<hr/>
-
- <p>Další nápověda je dostupná na stránkách <a href="https://www.enigmail.net/support/">dokumentace Enigmailu</a> (anglicky).</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/bg/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/bg/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,87 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Message Composition</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using Enigmail when composing messages</h3>
-
- <dl>
- <dt>Enigmail menu in Mail/Compose window</dt>
-
- <dd>
- <dl>
- <dt>Sign message</dt>
-
- <dd>Enable/Disable sending signed mail. User is notified, if signing fails.</dd>
-
- <dt>Encrypt message</dt>
- <dd>
- <p>Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.</p>
-
- <p>If <em>Display selection when necessary</em> is set in <strong>Preferences -> Key Selection tab</strong>, a list of keys will pop up if there are addresses in the list of recipients for the message for whom you have no public key.</p>
-
- <p>If <em>Never display OpenPGP key selection dialog</em> is set in <strong>Preferences -> Key Selection tab</strong>, and there are addresses in the list of recipients for the message for whom you have no public key, the message will be sent unencrypted.</p>
- </dd>
-
- <dt>Use PGP/MIME for this message</dt>
-
- <dd>
- Enable/Disable the use of <a href="https://tools.ietf.org/html/rfc3156">PGP/MIME</a> for this message.
-
- <p>If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.</p>
-
- <p>This feature is dependent on the settings in <strong>Preferences -> PGP/MIME tab</strong> being set to <em>Allow to use PGP/MIME</em> or <em>Always use PGP/MIME</em>.</p>
- </dd>
-
- <dt>Default composition options</dt>
-
- <dd>
- <ul>
- <li><strong>Signing/Encryption Options...</strong>: shortcut to <strong>Account Settings -> OpenPGP Options.</strong></li>
-
- <li><strong>Send options...</strong>: shortcut to <strong>Preferences -> Send</strong> tab.</li>
-
- <li><strong>Key selection options...</strong>: shortcut to <strong>Preferences -> Key Selection</strong> tab.</li>
-
- <li><strong>PGP/MIME options...</strong>: shortcut to <strong>Preferences -> PGP/MIME</strong> tab.</li>
- </ul>
- </dd>
-
- <dt>Undo encryption</dt>
-
- <dd>
- <p>If there is a failure when actually sending mail, such as the POP server not accepting the request, Enigmail will not know about it, and the encrypted message will continue to be displayed in the Compose window. Choosing this menu item will undo the encryption/signing, reverting the Compose window back to its original text.</p>
-
- <p><em>As a temporary fix, this option may also be used to decrypt the quoted text when replying to encrypted messages. Enigmail should automatically decrypt the quoted message, but if that fails for some reason, you can use this menu item to force it.</em></p>
- </dd>
-
- <dt>Insert public key</dt>
-
- <dd>insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.</dd>
-
- <dt>Clear save passphrase</dt>
-
- <dd>Clears cached passphrase. Useful if you have multiple passphrases.</dd>
-
- <dt>Help</dt>
-
- <dd>Displays Help information from the website (this page).</dd>
- </dl>
- </dd>
- </dl>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/cs/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/cs/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,88 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-
- <title>Nápověda pro Enigmail - psaní zpráv</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Nápověda pro Enigmail</h1>
-
- <h3>Použití Enigmailu při psaní zprávy</h3>
-
- <dl>
- <dt> menu OpenPGP v okně Zpráva/Nová zpráva </dt>
-
- <dd>
- <dl>
- <dt>Podepsat zprávu</dt>
-
- <dd>Povolit / zakázat podepsat odesílanou zprávu. Pokud digitální podpis selže, je o tom uživatel informován.</dd>
-
- <dt>Šifrovat zprávu</dt>
- <dd>
- <p>Povolit / zakázat šifrování zprávy pro všechny příjemce před zasláním. Pokud šifrování selže, je uživatel o této zkutečnosti informován.</p>
-
- <p>Při nastavené volbě <em>Zobraz výběr, když je třeba</em> v menu <strong>Předvolby-> záložka Výběr klíče</strong> se při odesílání pošty zobrazí seznam klíčů pro šifrování zprávy, pokud jsou v seznamu příjemců pošty adresáti, jejichž veřejný klíč nemáte.</p>
-
- <p>Při nastavené volbě <em>Nikdy nezobrazovat výběr OpenPGP klíče</em> v menu <strong>Předvolby -> záložka Výběr klíče</strong> se odešle zpráva nezašifrovaná, pokud jsou v seznamu příjemců pošty adresáti, jejichž veřejný klíč nemáte.</p>
- </dd>
-
- <dt>Použít PGP/MIME pro tuto zprávu</dt>
-
- <dd>
- Povolit / zakázat použití <a href="https://tools.ietf.org/html/rfc3156" target="_blank"title="Popis PGP/MIME (anglicky)">PGP/MIME</a> pro tuto zprávu..
-
- <p>Pokud víte, že příjemce dokáže přečíst poštu, která používá PGP/MIME formát, můžete tento formát použít.</p>
-
- <p>Tato volba je povolena, pokud na záložce <strong>Předvolby -> PGP/MIME tab</strong> je nastaveno <em>Povolit použití PGP/MIME</em> nebo<em> Vždy použít PGP/MIME</em>.</p>
- </dd>
-
- <dt>Výchozí nastavení tvorby zpráv</dt>
-
- <dd>
- <ul>
- <li><strong>Nastavení podepisování/šifrování...</strong>: menu <strong>Nástroje -> Nastavení účtu -> OpenPGP/Enigmail</strong></li>
-
- <li><strong>Nastavení odesílání...</strong>:-> záložky <strong>Předvolby -> Odesílání</strong> </li>
-
- <li><strong>Nastavení výběru klíče...</strong>:-> záložky <strong>Předvolby -> Výběr klíče</strong> </li>
-
- <li><strong>PGP/MIME nastavení...</strong>:-> záložky <strong>Předvolby -> PGP/MIME</strong> </li>
- </ul>
- </dd>
-
- <dt>Zpět šifrování</dt>
-
- <dd>
- <p>Pokud při zasílání pošty dojde k chybě, například když POP server nepřijme požadavek, Enigmail o tom nebude vědět, a zašifrovaná zpráva zůstane zobrazena v okně Psaní zprávy. Zvolením této položky menu dojde ke zrušení šifrování a podepsání, což se projeví zobrazením původního (nezašifrovaného) textu v okně psaní zprávy.</p>
-
- <p><em>Tato volba může být použita takě jako nouzová oprava, pokud odpovídáte na zašifrovanou zprávu. Enigmail dešifruje citovanou zprávu automaticky, ale pokud z nějakého důvodu dešifrování neproběhne, může být tato volba použita k vynucenému dešifrování zprávy.</em></p>
- </dd>
-
- <dt>Připojit veřejný klíč</dt>
-
- <dd>Zobrazí se seznam veřejných klíčů, které můžete připojit k vytvářené zprávě. Pokud zvolíte jediný klíč, připojí se ke zprávě soubor s názvem 0xkey_id.asc (kde key_id je číselný identifikátor zvoleného klíče ), který obsahuje <span title="Blok tisknutelných znaků, který vznikl použitím kódování Radix-64 na veřejný klíč v binárním tvaru" class="armored">ASCII-armored</span>y text zvolného klíče. Pokud vyberete více klíčů, připojí se soubor s názvem pgpkeys.asc, který obsahuje <span title="Blok tisknutelných znaků, který vznikl použitím kódování Radix-64 na veřejný klíč v binárním tvaru" class="armored">ASCII-armored</span> text se všemi klíči.</dd>
-
- <dt>Smazat uložené heslo</dt>
-
- <dd>Dojde k odstranění dočasně uloženého hesla k soukromému klíči. To je užitečné zejména pokud máte více hesel.</dd>
-
- <dt>Nápověda</dt>
-
- <dd>Zobrazí nápovědu jako webovou stránku (tato stránka).</dd>
- </dl>
- </dd>
- </dl>
- <hr />
-<p>Další nápověda je dostupná na stránkách <a href="https://www.enigmail.net/support/">dokumentace Enigmailu</a> (anglicky).</p>
-</body>
-</html>
-
lang/bg/enigmail.properties
-
--- 2:2.1.6+ds1-1/lang/ar/help/initError.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/help/initError.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: How to Resolve Problems with Initializing OpenPGP</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>How to Resolve Problems with Initializing OpenPGP</h3>
-
- <p>There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below;
- for more information please visit the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Support page.</a></p>
-
- <dl>
- <dt>GnuPG could not be found</dt>
- <dd>
- <p>
- In order for OpenPGP to work, the tool <a href="https://www.gnupg.org/" target="_blank">GnuPG</a> needs to be installed.
- If GnuPG cannot be found, then first make sure that the executable <tt>gpg.exe</tt> (on Windows; <tt>gpg</tt> on other platforms) is installed on your computer.
- If GnuPG is installed, and OpenPGP cannot find it, then you need to manually set the path to GnuPG in the OpenPGP Preferences (menu <i>OpenPGP</i> > <i>Preferences</i>)
- </p>
-
- <dt>Enigmime failed to initialize</dt>
-
- <dd>
- <p>
- OpenPGP works only if it is built using the same build environment as Thunderbird or SeaMonkey was built. This means that you can use the official Enigmail releases only if you use the official releases of Thunderbird or SeaMonkey provided by <a href="www.mozilla.org">mozilla.org</a>.
- </p>
- <p>
- If you use a Thunderbird or SeaMonkey version coming from some other source (e.g. the provider of your Linux distribution), or if you built the application yourself, you should either use an Enigmail version built by the same source, or build Enigmail yourself. For building Enigmail, refer to the <a href="https://www.enigmail.net/download/source.php">Source Code section</a> on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
- </p>
- </dd>
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/troubles.php" target="_blank">Enigmail Support Web Site</a>.</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/cs/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/cs/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/ca/help/sendingPrefs.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ca/help/sendingPrefs.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Defining Preferences to Send Encrypted</h3>
-
- <p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
- <dl>
-<dt>Convenient Encryption</dt>
- <dd>With these settings, emails are encrypted without confirmation whenever possible.
- <p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
- <p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
-<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
-<p>A concrete risk is that you accidentally use "faked keys" you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
-
- <dt>Manual Encryption</dt>
- <dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
- <ul>
- <li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
- <li>whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
- <li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
- <li>whether and when you want to finally confirm sending an email.</li>
- </ul>
- </dd>
-
- If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
-
-</body>
-</html>
-
lang/ca/enigmail.dtd
-
--- 2:2.1.6+ds1-1/lang/el/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,45 +0,0 @@
-<html>
-<head><title>Βοήθεια του Enigmail: Επεξεργασία κανόνων</title>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-</head>
-<body>
-<h1>Βοήθεια του Enigmail</h1>
-
-<h3>Χρήση του Επεξεργαστή κανόνων του Enigmail</h3>
-<p>Στον Επεξεργαστή κανόνων, μπορείτε να καθορίσετε τις προκαθορισμένες επιλογές για κάθε παραλήπτη για την ενεργοποίηση της κρυπτογράφησης, υπογραφής και χρήση PGP/MIME, και να επιλέξετε τα κλειδιά OpenPGP που θα χρησιμοποιηθούν. Κάθε κανόνας αποτελείται από πέντε πεδία:
-</p>
-<ul>
- <li><span style="font-weight: bold;">Email</span>: οι διευθύνσεις αλληλογραφίας που μπορούν να χρησιμοποιηθούν στα πεδία To:, Cc: και Bcc:. Ο έλεγχός τους γίνεται με χρήση <span
- style="font-style: italic;">υποσυμβολοσειρών</span> (Περισσότερες λεπτομέρειες υπάρχουν στο διάλογο του Επεξεργαστή κανόνων)
- </li>
- <li><span style="font-weight: bold;">Κλειδί(ιά) OpenPGP</span>: η λίστα ID κλειδιών OpenPGP
-για χρήση με τον αποστολέα</li>
- <li><span style="font-weight: bold;">Υπογραφή</span>: ενεργοποίηση ή απενεργοποίηση της υπογραφής του μηνύματος. Αυτό είτε χρησιμοποιεί ή παρακάμπτει την επιλογή που κάνατε στο παράθυρο Σύνταξης του μηνύματος. Διαθέσιμες τιμές είναι οι:
- <ul>
- <li><i>Ποτέ</i>: απενεργοποιεί την υπογραφή, ακόμα και αν έχει ενεργοποιηθεί στο παράθυρο Σύνταξης του μηνύματος<br>
- </li>
- <li><i>Πιθανή</i>: θα χρησιμοποιηθεί η επιλογή που έγινε στο παράθυρο Σύνταξης του μηνύματος</li>
- <li><i>Πάντα</i>: ενεργοποιεί την υπογραφή, ακόμα και αν <span
- style="font-style: italic;">δεν</span> έχει ενεργοποιηθεί στο παράθυρο Σύνταξης του μηνύματος
- </li>
- </ul>
- </li>
-</ul>
-<div style="margin-left: 40px;">Αυτές οι επιλογές εφαρμόζονται σε όσους κανόνες ταιριάζουν. Αν κάποιος κανόνας απενεργοποιεί την υπογραφή, το μήνυμα δε θα υπογραφεί, ανεξάρτητα από άλλους κανόνες που χρησιμοποιούν το <i>Πάντα</i>.<br>
-</div>
-<ul>
- <li><span style="font-weight: bold;">Κρυπτογράφηση</span>: ενεργοποιεί ή απενεργοποιεί την κρυπτογράφηση του μηνύματος. Οι επιτρεπόμενες τιμές και το νόημά τους είναι ίδιες με αυτές της υπογραφής.</li>
- <li><span style="font-weight: bold;">PGP/MIME</span>: ενεργοποιεί ή απενεργοποιεί τη χρήση της κωδικοποίησης PGP/MIME (RFC 3156) για το μήνυμα.
- Αν απενεργοποιηθεί, τα μηνύματα θα κωδικοποιούνται με "εμβόλιμο PGP". Οι επιτρεπόμενες τιμές και το νόημά τους είναι ίδιες με αυτές της υπογραφής.
- </li>
-</ul>
-<p>Οι κανόνες εφαρμόζονται με τη σειρά που βρίσκονται στη λίστα. Κάθε φορά που ένας κανόνας ταιριάζει με έναν παραλήπτη και περιέχει ένα ID κλειδιού OpenPGP, εκτός του ότι θα χρησιμοποιηθεί το καθορισμένο ID κλειδιού, ο παραλήπτης δε θα θεωρείται διαθέσιμος για τους υπόλοιπους κανόνες.</p>
-<p><i>Σημείωση:</i> Ο Επεξεργαστής κανόνων δεν είναι ακόμα ολοκληρωμένος. Είναι δυνατή η συγγραφή πιο προχωρημένων κανόνων με απευθείας επεξεργασία του αρχείου κανόνων (δε θα πρέπει να γίνει πλέον επεξεργασία αυτών των κανόνων με τον Επεξεργαστή). <a
-href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Περισσότερες πληροφορίες</a> για την απευθείας επεξεργασία του αρχείου κανόνων υπάρχουν στο δικτυακό τόπο του Enigmail</p>
-<hr/>
-<p>
-Περισσότερη βοήθεια είναι διαθέσιμη στο δικτυακό τόπο του
-<a href="https://www.enigmail.net/support/" target="_blank">Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/lang/el/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/el/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,61 +0,0 @@
-<html>
-<head><title>Βοήθεια του Enigmail: Σύνταξη μηνυμάτων</title>
-<meta http-equiv="content-type" content="text/html; charset=utf-8">
-</head>
-<body>
-<h1>Βοήθεια του Enigmail</h1>
-
-<h3>Χρήση του Enigmail στη σύνταξη μηνυμάτων</h3>
-
-<ul>
- <li><b>Μενού του Enigmail στο παράθυρο Σύνταξης μηνύματος</b>
- <ul>
- <li><b>Υπογραφή μηνύματος</b>: Ενεργοποίηση/Απενεργοποίηση της αποστολής υπογεγραμμένων μηνυμάτων. Ο χρήστης θα ειδοποιηθεί αν η υπογραφή αποτύχει.
- </li>
- <li><b>Κρυπτογράφηση μηνύματος</b>: Ενεργοποίηση/Απενεργοποίηση της κρυπτογράφησης για όλους τους παραλήπτες πριν την αποστολή. Ο χρήστης θα ειδοποιηθεί αν η κρυπτογράφηση αποτύχει.
- <p>Αν έχει ενεργοποιηθεί η επιλογή <em>Εμφάνιση επιλογών όταν είναι απαραίτητο</em> στην καρτέλα <b>Προτιμήσεις
- -> Επιλογή κλειδιού</b>, και υπάρχουν διευθύνσεις στη λίστα παραληπτών για τις οποίες δεν υπάρχει δημόσιο κλειδί, θα εμφανιστεί η λίστα κλειδιών για να επιλέξετε αυτό που θα χρησιμοποιηθεί.</p>
- <p>Αν έχει ενεργοποιηθεί η επιλογή <em>Να μην εμφανίζεται ποτέ ο διάλογος επιλογής κλειδί OpenPGP</em> στην καρτέλα <b>Προτιμήσεις
- -> Επιλογή κλειδιού</b>, και υπάρχουν διευθύνσεις στη λίστα παραληπτών για τις οποίες δεν υπάρχει δημόσιο κλειδί, το μήνυμα θα αποσταλεί χωρίς κρυπτογράφηση.</p>
- </li>
- </ul>
- </li>
- <li><b>Χρήση PGP/MIME για αυτό το μήνυμα</b>: Ενεργοποίηση/Απενεργοποίηση της χρήσης <a href="https://tools.ietf.org/html/rfc3156" target="_blank">PGP/MIME</a>
- για αυτό το μήνυμα.
- <p>Αν γνωρίζετε ότι οι παραλήπτες του μηνύματός σας μπορούν να διαβάσουν μηνύματα που χρησιμοποιούν PGP/MIME,
- καλό είναι να το ενεργοποιήσετε.</p>
- <p>Αυτό το χαρακτηριστικό εξαρτάται από το αν έχετε ενεργοποιήσει μία από τις επιλογές <em>Επιτρέπεται η χρήση PGP/MIME</em> ή <em>Να χρησιμοποιείται πάντα PGP/MIME</em>, στην καρτέλα <b>Προτιμήσεις -> PGP/MIME</b>.</p>
- </li>
- <li><b>Προκαθορισμένες επιλογές σύνταξης</b>: Υπομενού.
- <ul>
- <li><b>Επιλογές υπογραφής/κρυπτογράφησης...</b>: συντόμευση προς το <b>Ρυθμίσεις λογαριασμού ->
- Επιλογές OpenPGP.</b>
- </li>
- <li><b>Επιλογές αποστολής...</b>: συντόμευση προς την καρτέλα <b>Προτιμήσεις ->
- Βασικές ρυθμίσεις</b>.
- </li>
- <li><b>Ρυθμίσεις επιλογής κλειδιού...</b>: συντόμευση προς την καρτέλα <b>Προτιμήσεις ->
- Επιλογή κλειδιού</b>.
- </li>
- <li><b>Επιλογές PGP/MIME...</b>: συντόμευση προς την καρτέλα <b>Προτιμήσεις ->
- PGP/MIME</b>.
- </li>
- </ul>
- </li>
- <li><b>Αφαίρεση κρυπτογράφησης</b>: Αν παρουσιαστεί κάποιο σφάλμα κατά την αποστολή του μηνύματος, π.χ. ο διακομιστής POP δεν αποδεχτεί την αίτηση, το Enigmail δεν έχει τρόπο να το ανιχνεύσει, και το κρυπτογραφημένο μήνυμα θα εξακολουθήσει να εμφανίζεται στο παράθυρο Σύνταξης. Σε αυτήν την περίπτωση μπορείτε να ανακτήσετε το αρχικό σας κείμενο (χωρίς την υπογραφή/κρυπτογράφηση) με τη χρήση αυτού του μενού.<br>
- <em>Ως λύση ανάγκης, αυτή η επιλογή μπορεί να χρησιμοποιηθεί για την αποκρυπτογράφηση του κειμένου σε παράθεση, όταν απαντάτε σε κρυπτογραφημένα μηνύματα. Το Enigmail θα πρέπει να αποκρυπτογραφήσει αυτόματα το αρχικό μήνυμα, αλλά αν για κάποιο λόγο αυτό δε συμβεί, μπορείτε να το κάνετε εσείς με τη χρήση αυτού του μενού.</em>
- </li>
- <li> <b>Επισύναψη δημόσιου κλειδιού</b>: εισάγει το μπλοκ του δημόσιου κλειδιού σε μορφή ASCII-armored στην τρέχουσα θέση του δρομέα στο παράθυρο Σύνταξης. Θα σας ζητηθούν οι διευθύνσεις αλληλογραφίας του κλειδιού/ών που θα εισαχθεί. Κλειδιά που εισήχθησαν με αυτόν τον τρόπο θα αναγνωριστούν αυτόματα από το Enigmail του παραλήπτη. Μετά την εισαγωγή, μπορείτε να υπογράψετε/κρυπτογραφήσετε το μήνυμα ανάλογα με τις ανάγκες σας. Επίσης, δε θα πρέπει να εισάγετε πολλαπλά μπλοκ κλειδιών σε ένα μήνυμα· απλώς καθορίστε πολλαπλές διευθύνσεις αλληλογραφίας, χωρισμένες με κόμμα, όταν σας ζητηθεί.
- </li>
- <li><b>Εκκαθάριση αποθηκευμένης φράσης πρόσβασης</b>: Χρήσιμο αν έχετε πολλαπλές φράσης πρόσβασης.
- </li>
- <li><b>Βοήθεια</b>: Εμφανίζει τη Βοήθεια από το δικτυακό τόπο (αυτή η σελίδα).
- </li>
-</ul>
-<hr/>
-<p>
-Περισσότερη βοήθεια είναι διαθέσιμη στο δικτυακό τόπο του
-<a href="https://www.enigmail.net/support/" target="_blank">Enigmail</a>
-</p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/tests/no-test.js 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/tests/no-test.js 1970-01-01 00:00:00.000000000 +0000
@@ -1,3 +0,0 @@
-/* this runs no tests at all, just for the sake of setting up the profile. */
-/* global dump: false */
-dump("simple test to make sure logging works\n");
-
--- 2:2.1.6+ds1-1/debian/patches/0012-Fix-parallel-build.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0012-Fix-parallel-build.patch 2020-10-07 15:48:06.000000000 +0000
@@ -11,11 +11,9 @@ Signed-off-by: Daniel Kahn Gillmor <dkg@
ui/content/Makefile | 2 ++
1 file changed, 2 insertions(+)
-diff --git a/ui/content/Makefile b/ui/content/Makefile
-index 894db7d..93a6214 100644
--- a/ui/content/Makefile
+++ b/ui/content/Makefile
-@@ -136,9 +136,11 @@ UIFILES = \
+@@ -25,9 +25,11 @@ UIFILES = \
GENFILES = $(addprefix $(GENDIR)/,$(UIFILES))
$(GENDIR)/%.js: %.js
@@ -26,4 +24,4 @@ index 894db7d..93a6214 100644
+ mkdir -p $(GENDIR)
$(PERL) $(DEPTH)/util/plpp.pl -i $(INCLUDE) -o $@ $<
- $(GENDIR)/%.htm: %.htm
+ $(GENDIR)/%.xhtml: %.xhtml
-
debian/patches/0008-use-GnuPG-instead-of-openpgp.js-for-symmetric-encryp.patch
-
--- 2:2.1.6+ds1-1/lang/de/help/compose.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/de/help/compose.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,94 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail-Hilfe: Verfassen von Nachrichten</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail-Hilfe</h1>
-
- <h3>Verwenden von Enigmail beim Verfassen von Nachrichten</h3>
-
- <dl>
- <dt>Menü "Enigmail" im Fenster "Verfassen"</dt>
-
- <dd>
- <dl>
- <dt>Nachricht unterschreiben</dt>
-
- <dd>Unterschreiben von Nachrichten aktivieren / deaktivieren. Der Benutzer wird benachrichtigt, falls das Unterschreiben fehlschlägt.</dd>
-
- <dt>Nachricht verschlüsseln</dt>
- <dd>
- <p>Verschlüsselung an alle Adressaten aktivieren / deaktivieren. Der Benutzer wird benachrichtigt, falls die Verschlüsselung fehlschlägt.</p>
-
- <p>Falls <em>Auswahl anzeigen, wenn notwendig</em> im Menü <strong>Enigmail -> Einstellungen -> Schlüsselauswahl...</strong> eingestellt ist, dann wird eine Liste mit Schlüsseln erscheinen, wenn Sie keinen öffentlichen Schlüssel für einen oder mehrere Empfänger der Nachrichten besitzen.</p>
-
- <p>Falls <em>Auswahlfenster nie anzeigen</em> im Menü <strong>Enigmail -> Einstellungen -> Schlüsselauswahl...</strong> eingestellt ist, dann wird die Nachricht an die Empfänger unverschlüsselt gesendet, von denen Sie keinen öffentlichen Schlüssel besitzen.</p>
- </dd>
-
- <dt>PGP/MIME verwenden</dt>
-
- <dd>
- Verwenden von <a href="https://tools.ietf.org/html/rfc3156" target="_blank">PGP/MIME</a> für diese Nachricht ermöglichen / nicht ermöglichen.
-
- <p>Wenn Sie wissen, dass die Empfänger das PGP/MIME-Format verwenden können, dann sollten Sie dies benutzen.</p>
-
- <p>Diese Möglichkeit hängt von den Einstellungen unter <strong>Enigmail -> Einstellungen -> PGP/MIME...</strong> ab. Hier muss <em>PGP/MIME verwenden, wenn möglich</em> oder <em>Immer PGP/MIME verwenden</em> aktiviert sein.</p>
- </dd>
-
- <dt>Einstellungen (Untermenü)</dt>
-
- <dd>
- <ul>
- <li><strong>Unterschrift/Verschlüsselung...</strong>: Abkürzung zu den <strong>Konten-Einstellungen -> OpenPGP-Sicherheit.</strong></li>
-
- <li><strong>Senden...</strong>: Abkürzung zu <strong>Einstellungen -> Senden</strong>.</li>
-
- <li><strong>Schlüsselwauswahl...</strong>: Abkürzung zu <strong>Einstellungen -> Schlüsselauswahl</strong>.</li>
- </ul>
- </dd>
-
- <dt>Empfängerregeln</dt>
-
- <dd>Öffnet den Dialog mit den Empfängerregeln.</dd>
-
- <dt>Verschlüsselung rückgängig machen</dt>
-
- <dd>
- <p>Wenn es einen Fehler beim Senden der Nachricht gibt, also z.B. der POP-Server nicht erreichbar ist, dann wird Enigmail dies nicht wissen und die verschlüsselte Nachricht wird auch weiterhin im Fenster "Verfassen" angezeigt. Dieser Menüpunkt nimmt die Verschlüsselung / das Unterschreiben zurück und das Fenster "Verfassen" kehrt zum Originaltext zurück.</p>
-
- <p><em>Als vorläufige Maßnahme kann über diesen Menüpunkt auch eine verschlüsselte Nachricht, die man zitiert und auf die man antwortet, entschlüsselt angezeigt werden. Enigmail sollte zitierte Nachrichten automatisch entschlüsseln, was bisher jedoch fehlschlägt. Über diesen Menüeintrag kann Enigmail zur Entschlüsselung gezwungen werden.</em></p>
- </dd>
-
- <dt>Meinen öffentlichen Schlüssel anhängen</dt>
-
- <dd>Hägt an die Nachricht Ihren öffentlichen Schlüssel im ASCII-Format an.</dd>
-
- <dt>Öffentlichen Schlüssel anhängen</dt>
-
- <dd>Hägt an die Nachricht öffentliche Schlüssel im ASCII-Format an. Sie können die gewünschten Schlüssel dazu auswählen.</dd>
-
- <dt>Passphrase aus Zwischenspeicher löschen</dt>
-
- <dd>Löscht die gespeicherte Passphrase. Nützlich, falls Sie mehrere Passphrasen verwenden.</dd>
-
- <dt>Hilfe</dt>
-
- <dd>Zeigt die Hilfe an (diese Seite).</dd>
- </dl>
- </dd>
- </dl>
- <hr/>
-
- <p>Weitere Hilfe ist verfügbar auf der <a href="https://www.enigmail.net/support/" target="_blank">Enigmail-Hilfeseite</a></p>
-</body>
-</html>
-
lang/bg/enigmail.dtd
-
--- 2:2.1.6+ds1-1/lang/es-AR/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-AR/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,32 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta name="author" content="EduLeo" />
-<title>Ayuda de Enigmail: Lectura de mensajes</title>
-</head>
-
-<body>
-<h1>Ayuda de Enigmail</h1>
-<h3>Usando Enigmail para leer mensajes</h3><ul>
-<li><strong>Botón Descifrar en la ventana principal de correo</strong><br />
-Este botón se puede usar para varios propósitos: descifrar, verificar o importar claves públicas. Normalmente el descifrado/verificación se realiza automáticamente, aunque hay una opción para desactivar esto. Sin embargo, si esto falla, normalmente aparecerá un breve mensaje de error en la línea de estado de Enigmail. Si se pulsa el botón Descifrar, podrá ver un mensaje de error más detallado, incluyendo la salida del comando GnuPG.</li>
-<li><strong>Los iconos Lápiz y Llave mostrados en la cabecera del mensaje</strong><br />
-Los iconos <em>Lápiz</em> y <em>Llave</em> en la cabecera del mensaje indican si el mensaje que se está leyendo está firmado y/o cifrado y si la firma es buena, es decir; que el mensaje no se ha modificado desde el momento de su firma. Si el mensaje ha sido modificado, el icono del <em>Lápiz</em> cambiará a un <em>Lápiz roto</em> para indicar que la firma no es correcta. Al pulsar con el botón derecho del ratón en los iconos del Lápiz o Llave, se obtendrá un menú con las siguientes opciones:
-<br /><br /><ul>
-<li><em>Información de seguridad OpenPGP</em>: permite ver el estado de salida de GnuPG para el mensaje.</li>
-<li><em>Copiar información de seguridad OpenPGP</em>: copia el estado de salida de GnuPG al portapapeles; para pegarlo en un mensaje de respuesta, etc.</li>
-<li><em>Ver ID fotográfico OpenPGP</em>: permite ver la <em>Foto ID</em> de la persona que envió el mensaje, si tiene una foto incrustada en su clave pública (<em>Esta opción sólo se activará si existe un ID fotográfico en su clave)</em>.</li>
-<li><em>Información de seguridad S/MIME</em>: permite ver la información de seguridad S/MIME del mensaje.</li>
-</ul>
-<p>Si no tiene puesta la opción <em>keyserver-options auto-key-retrieve</em> en su archivo <tt>gpg.conf</tt> y lee un mensaje que está firmado o cifrado, verá un icono de un <em>Lápiz</em> en el área de visión de las cabeceras con un <em>Signo de interrogación</em> y, la línea de estado de Enigmail en el área de las cabeceras dirá: <em>Parte del mensaje firmado; pulse el icono del lápiz para más detalles</em> y el mensaje en el panel de mensajes mostrará todos los indicadores del bloque del mensaje OpenPGP y el bloque de la firma.</p>
-<p>También se puede ver esto si tiene activada la opción <em>keyserver-options auto-key-retrieve</em> en su archivo <tt>gpg.conf</tt> y la clave OpenPGP no está disponible en el servidor de claves predeterminado.</p>
-<p>Al pulsar en el icono del <em>Lápiz y Signo de interrogación</em> abrirá una ventana avisando que la clave no está disponible en el anillo de claves. Al pulsar en Aceptar abrirá otra ventana con una lista de servidores de claves en los que puede seleccionar para descargar la clave pública del remitente.</p>
-<p>Para configurar la lista de servidores de claves que desee usar, vaya a la pestaña <strong>Enigmail -> Preferencias -> Básicas</strong> e introduzca la dirección de los servidores de claves en el recuadro <em>Servidor(es) de claves:</em> separados por una coma. <em>El primer servidor de claves de la lista se usará como predeterminado.</em></p>
-</li>
-<li><strong>Abrir adjuntos cifrados / importar claves OpenPGP adjuntas</strong><br />
-Los adjuntos con el nombre *.pgp, *.asc y *.gpg se reconocen como adjuntos que se pueden manejar especialmente con Enigmail. Al pulsar con el botón derecho en un adjunto de este tipo se activan dos elementos especiales en el menú contextual: <em>Descifrar y Abrir</em> y <em>Descifrar y Guardar</em>. Use estos elementos si desea que Enigmail descifre un adjunto antes de abrirlo o guardarlo. Si se reconoce un adjunto como un archivo de clave OpenPGP, se le ofrece la posibilidad de importar las claves a sus anillos.</li>
-</ul><hr />
-<p>Más ayuda disponible en la <a href="https://www.enigmail.net/support/" onclick="window.open('https://www.enigmail.net/support/');return false">página Web de ayuda de Enigmail</a></p>
-</body></html>
-
--- 2:2.1.6+ds1-1/lang/da/help/rulesEditor.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/rulesEditor.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,63 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Rules Editor</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css" xml:space="preserve">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using the Enigmail Rules Editor</h3>
-
- <p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. Each rule consists of 5 fields and is represented on a single line:</p>
-
- <dl>
- <dt>Email</dt>
-
- <dd>The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on <span style="font-style: italic;">substrings</span> (Further details can be found in the Edit Rule dialog)</dd>
-
- <dt>OpenPGP Key(s)</dt>
-
- <dd>a list of OpenPGP Key ID's to use for the recipient</dd>
-
- <dt>Sign</dt>
-
- <dd>
- enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
-
- <ul>
- <li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
-
- <li><em>Possible</em>: leave signing as specified in the message composition window</li>
-
- <li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
- </ul>
-
- <p>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.</p>
- </dd>
-
- <dt>Encrypt</dt>
-
- <dd>enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.</dd>
- </dl>
-
- <p>The rules are processed in the order displayed in the list. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
-
- <p><em>Note:</em> The rule editor is not yet complete. It is possible to write some more advanced rules by directly editing the rules file (these rules should then not be edited anymore in the rule editor). <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Further information</a> for directly editing the file is available on the Enigmail Homepage</p>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/" target="_blank">Enigmail Help web page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/ipc/tests/subprocess-test.js 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/ipc/tests/subprocess-test.js 2020-10-01 13:32:58.000000000 +0000
@@ -83,6 +83,7 @@ function run_test() {
gResultStdErr += data;
},
done: function(result) {
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
},
mergeStderr: false
@@ -95,7 +96,7 @@ function run_test() {
"result matching"
);
- let len = gTestLines.join("").length;
+ let len = gTestLines.join("").replace(/\r\n/g, "\n").length;
Assert.equal(
"Starting dump\nDumped " + len + " bytes\n",
gResultStdErr.replace(/\r\n/g, "\n"),
@@ -122,13 +123,14 @@ function run_test() {
Assert.ok(false, "Got unexpected data '" + data + "' on stderr\n");
},
done: function(result) {
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
},
mergeStderr: true
});
p.wait();
- Assert.equal(gTestLines.join("").length + 30, gResultData.length, "comparing result");
+ Assert.equal(gTestLines.join("").replace(/\r\n/g, "\n").length + 30, gResultData.replace(/\r\n/g, "\n").length, "comparing result");
/////////////////////////////////////////////////////////////////
@@ -151,6 +153,7 @@ function run_test() {
},
done: function(result) {
gResultData = result.stdout;
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
},
mergeStderr: false
@@ -233,6 +236,7 @@ function run_test() {
gResultData = result.stdout;
gResultStdErr = result.stderr.replace(/\r\n/g, "\n");
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
Assert.equal(gTestLines.join(""), gResultData, "stdout");
Assert.equal(gResultStdErr.length, 28, "stderr");
@@ -258,6 +262,7 @@ function run_test() {
environment: envList,
done: function(result) {
gResultData = result.stdout;
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
},
mergeStderr: false
@@ -283,6 +288,7 @@ function run_test() {
gResultData += data;
},
done: function(result) {
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
Assert.equal("zbaxrl", gResultData, "transformed data");
},
@@ -296,7 +302,7 @@ function run_test() {
/////////////////////////////////////////////////////////////////
- // Test many concurrent runs
+ // Test many subsequent runs
/////////////////////////////////////////////////////////////////
do_print("mass test");
@@ -307,7 +313,8 @@ function run_test() {
arguments: [cmd.path, 'quick'],
environment: envList,
done: function(result) {
- Assert.equal("Hello\n", result.stdout, "stdout text");
+ Assert.equal("Hello\n", result.stdout.replace(/\r\n/g, "\n"), "stdout text");
+ if (result.exitCode === 255) result.exitCode = 0;
Assert.equal(0, result.exitCode, "exit code");
},
mergeStderr: false
@@ -315,4 +322,6 @@ function run_test() {
p.wait();
}
-}
\ No newline at end of file
+
+ dataFile.remove(false);
+}
-
--- 2:2.1.6+ds1-1/.gitlab-ci.yml 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/.gitlab-ci.yml 2020-10-01 13:32:58.000000000 +0000
@@ -18,42 +18,3 @@ check:
script:
- ./configure
- make check
-
-test:
- before_script:
- - export TBPROFILE="$(pwd)/tb-test-profile"
- - apt update -y -qq
- - apt install thunderbird gnupg zip unzip curl libgtk-3-0 -y -qq
- - mkdir -p $TBPROFILE/extensions tmp jsunit
- - printf '%s/build-tb/dist/' "$(pwd)" > "$TBPROFILE/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}"
- - printf 'user_pref("extensions.autoDisableScopes", 14);\n' > "$TBPROFILE/prefs.js"
- - printf 'user_pref("browser.dom.window.dump.enabled", true);\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("extensions.update.enabled", false);\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("extensions.update.autoUpdateDefault", false);\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("extensions.blocklist.enabled", false);\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("app.update.enabled", false);\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("app.update.auto", false);\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("extensions.enigmail.configuredVersion", "99.0");\n' >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("extensions.enigmail.logDirectory", "%s");\n' $(pwd)/tmp >> "$TBPROFILE/prefs.js"
- - printf 'user_pref("extensions.enigmail.pEpAutoDownload", false);\n' >> "$TBPROFILE/prefs.js"
- - curl -s -o "$TBPROFILE/extensions/jsunit@enigmail.net.xpi" https://www.enigmail.net/jsunit/jsunit-0.2.2.xpi
- #- export TBDOWNLOAD=$(curl -s 'https://download.mozilla.org/?product=thunderbird-beta-latest&os=linux64&lang=en-US' | sed -E 's/(.*href=")([^"]+)(".*)/\2/')
- - export TBDOWNLOAD=https://archive.mozilla.org/pub/thunderbird/releases/68.0/linux-x86_64/en-US/thunderbird-68.0.tar.bz2
- - curl -s -o thunderbird.tar.bz2 $TBDOWNLOAD
- - tar -xjvf thunderbird.tar.bz2
- - thunderbird/thunderbird --version
- script:
- - export TBPROFILE="$(pwd)/tb-test-profile"
- - export TMPDIR="$(pwd)/tmp"
- - export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
- - ./configure --enable-tests --with-tb-path=`printf '%s/thunderbird/thunderbird' "$(pwd)"` --with-tb-args="--headless --profile $TBPROFILE"
- - make dirs xpi
- - cat config/autoconf.mk
- - ls $TBPROFILE
- - cat $TBPROFILE/prefs.js
- - USER=root make unit
- artifacts:
- paths:
- - config
- - tmp
- - tb-test-profile
-
debian/patches/0003-avoid-OpenPGP.js-when-building.patch
-
--- 2:2.1.6+ds1-1/debian/run-tests 2019-11-19 07:25:37.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/run-tests 1970-01-01 00:00:00.000000000 +0000
@@ -1,34 +0,0 @@
-#!/bin/sh
-
-set -e
-
-if [ "$1" = autopkgtest ]; then
- extensionpath=/usr/share/xul-ext/enigmail/
-else
- extensionpath="$(printf '%s/build-tb/dist/' "$(pwd)")"
-fi
-
-mkdir -p test-profile/extensions tmp
-printf "%s" "$extensionpath" > 'test-profile/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}'
-printf /usr/share/xul-ext/jsunit/ > 'test-profile/extensions/jsunit@enigmail.net'
-cat > test-profile/prefs.js <<EOF
-user_pref("extensions.autoDisableScopes", 14);
-user_pref("extensions.update.enabled", false);
-user_pref("lightweightThemes.update.enabled", false);
-user_pref("extensions.blocklist.enabled", false);
-user_pref("browser.search.update", false);
-user_pref("app.update.auto", false);
-user_pref("browser.dom.window.dump.enabled", true);
-user_pref("toolkit.telemetry.prompted", false);
-user_pref("toolkit.telemetry.rejected", true);
-user_pref("toolkit.telemetry.enabled", false);
-EOF
-export TMPDIR="$(pwd)/tmp"
-
-make check
-# only run the test during autopkgtest, since it times out for some
-# reason i don't understand on the buildds:
-if [ "$1" = autopkgtest ]; then
- make unit
-fi
-head -n 200 -v test-profile/prefs.js
-
--- 2:2.1.6+ds1-1/lang/da/help/messenger.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/da/help/messenger.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Message Reading</title>
- <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using Enigmail when reading messages</h3>
-
- <dl>
- <dt>Decrypt button in main Mail window</dt>
-
- <dd>This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.</dd>
-
- <dt>Pen and Key icons in Message Header display</dt>
-
- <dd>
- The <em>Pen</em> and <em>Key</em> icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the <em>Pen</em> icon will change to a <em>Broken Pen</em> to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
-
- <ul>
- <li><em>Enigmail Security info</em>: allows you to view the output status from GnuPG for the message.</li>
-
- <li><em>Copy Enigmail Security info</em>: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.</li>
-
- <li><em>View OpenPGP Photo ID</em>: allows you to view the <em>Photo ID</em> of the person who sent the message, if they have a photo embedded in their Public Key. (<em>This option will only be enabled if a Photo ID exists in their key.)</em></li>
-
- <li><em>S/MIME Security info</em>: allows you to view the S/MIME Security Info for the message.</li>
- </ul>
-
- <p>If you do not have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and you read a message which is signed or encrypted, you will see a <em>Pen</em> icon in the headers display area with a <em>Question mark</em> on it, the Enigmail status line in the headers area will say <em>Part of the message signed; click pen icon for details</em> and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.</p>
-
- <p>You may also see this if you have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and the OpenPGP key is not available on the default keyserver.</p>
-
- <p>Clicking on the <em>Pen and Question mark</em> icon will bring up a window advising that the key is unavailable in your keyring. Clicking on OK will bring up another window with a list of keyservers from which you can select to download the sender's public key from.</p>
-
- <p>To configure the list of keyservers you wish to use, go to <strong>Enigmail -> Preferences -> Basic</strong> tab and enter the keyserver addresses in the <em>Keyserver(s):</em> box, separated by a comma. <em>The first keyserver in the list will be used as the default.</em></p>
- </dd>
-
- <dt>Opening encrypted attachments / importing attached OpenPGP keys</dt>
-
- <dd>Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: <em>Decrypt and Open</em> and <em>Decrypt and Save</em>. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.</dd>
- </dl>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/support/" target="_new">Enigmail Help web page</a></p>
-</body>
-</html>
-
lang/ca/enigmail.properties
-
--- 2:2.1.6+ds1-1/lang/ar/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/ar/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <title>Enigmail Help: Edit OpenPGP Rule</title>
- <style type="text/css">
- /*<![CDATA[*/
- dt { font-weight: bold; }
- /*]]>*/
- </style>
-</head>
-
-<body>
- <h1>Enigmail Help</h1>
-
- <h3>Using the Enigmail Rules Editor: Edit OpenPGP Rule</h3>
-
- <p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. In this dialog, you can specify the rules for a single recipient, and for a group of recipients with very similar attributes.</p>
-
- <dl>
- <dt>Set OpenPGP Rules for</dt>
-
- <dd>Contains the email addresses of the recipients (without names, i.e. just an address like <tt>somebody@email.domain</tt>). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. <tt>@email.domain will</tt> allow matching to <tt>body@email.domain</tt>, <tt>somebody@email.domain</tt>, <tt>anybody@email.domain</tt>, etc.</dd>
-
- <dt>Apply rule if recipient ...</dt>
-
- <dd>
- This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on <tt>body@email.domain</tt> entered in the <em>OpenPGP Rules</em> field above.
-
- <ul>
- <li><em>Is exactly</em>: with this setting, the rule will only trigger on emails to <tt>body@email.domain</tt> (exact, case insensitive matching).</li>
-
- <li><em>Contains</em>: with this setting, any email address containing the string is matched, e.g. <tt>anybody@email.domain</tt> or <tt>body@email.domain.net</tt></li>
-
- <li><em>Begins with</em>: with this setting, any email address starting with the string is matched, e.g. <tt>body@email.domain.net</tt>, <tt>body@email.domain-name.com</tt>.</li>
-
- <li><em>Ends with</em>: with this setting, any email address ending with the string is matched, e.g. <tt>anybody@email.domain</tt> , <tt>somebody@email.domain</tt>.</li>
- </ul>
- </dd>
-
- <dt>Continue with the next rule for the matching address</dt>
-
- <dd>Enabling this function will allow you to define a rule but not have to specify a KeyID in the <em>Use the following OpenPGP keys:</em> field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.</dd>
-
- <dt>Do not check further rules for the matching address</dt>
-
- <dd>Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.</dd>
-
- <dt>Use the following OpenPGP keys:</dt>
-
- <dd>Use the <em>Select Key(s)..</em> button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.</dd>
-
- <dt>Default for Signing</dt>
-
- <dd>
- Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
-
- <ul>
- <li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
-
- <li><em>Yes, if selected from in Message Composition</em>: leave signing as specified in the message composition window</li>
-
- <li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
- </ul>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.
- </dd>
-
- <dt>Encryption</dt>
-
- <dd>Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
-
- <dt>PGP/MIME</dt>
-
- <dd>Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.</dd>
- </dl>
-
- <p>The rules are processed in the order displayed in the list in the <em>OpenPGP Rules Editor</em>. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
- <hr />
-
- <p>Further help is available on the <a href="https://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Enigmail Per-Recipient Settings page</a></p>
-</body>
-</html>
-
--- 2:2.1.6+ds1-1/debian/patches/0007-add-test-to-do-symmetric-encryption-decryption-with-.patch 2020-04-12 01:42:58.000000000 +0000
+++ 2:2.2.4-0ubuntu1/debian/patches/0007-add-test-to-do-symmetric-encryption-decryption-with-.patch 2020-10-07 15:48:06.000000000 +0000
@@ -6,11 +6,9 @@ Subject: add test to do symmetric encryp
ipc/tests/subprocess-test.js | 95 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
-diff --git a/ipc/tests/subprocess-test.js b/ipc/tests/subprocess-test.js
-index 5e5f85b..f399cfa 100644
--- a/ipc/tests/subprocess-test.js
+++ b/ipc/tests/subprocess-test.js
-@@ -322,6 +322,101 @@ function run_test() {
+@@ -328,6 +328,101 @@ function run_test() {
p.wait();
@@ -111,4 +109,4 @@ index 5e5f85b..f399cfa 100644
+ p.wait();
/////////////////////////////////////////////////////////////////
- // Test many concurrent runs
+ // Test many subsequent runs
-
--- 2:2.1.6+ds1-1/lang/es-AR/help/editRcptRule.html 2020-03-28 09:44:53.000000000 +0000
+++ 2:2.2.4-0ubuntu1/lang/es-AR/help/editRcptRule.html 1970-01-01 00:00:00.000000000 +0000
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="author" content="EduLeo" />
-<title>Ayuda de Enigmail: Editar regla OpenPGP</title>
-</head>
-
-<body>
-<h1>Ayuda de Enigmail</h1>
-<h3>Usando el editor de reglas de Enigmail: Editar regla OpenPGP</h3>
-<p>En el editor de reglas, se pueden especificar opciones predeterminadas para cada destinatario, activando el cifrado, la firma y PGP/MIME; y para definir qué clave(s) OpenPGP va a usar. En este diálogo, se pueden especificar las reglas para un único destinatario, y para un grupo de destinatarios con atributos muy similares.</p>
-<ul>
-<li><strong>Definir reglas OpenPGP para</strong>: Contiene las direcciones de correo electrónico de los destinatarios (sin nombre, por ejemplo una dirección como <tt>alguien@correo.org</tt>). Se pueden especificar varias direcciones de correo, separadas por espacios. La dirección especificada aquí puede consistir de sólo la sección del dominio, para que se aplique al correo de cualquier dirección de ese dominio, como <tt>@correo.org</tt> se aplicará a <tt>alguien@correo.org</tt>, <tt>cualquiera@correo.org</tt>, <tt>otro@correo.org</tt>, etc.</li>
-<li><strong>Aplicar regla si el destinatario</strong>: Esto modifica si coinciden las direcciones de correo electrónico. Si se introducen varias direcciones, la opción se aplicará a todas. Los ejemplos de abajo están basados en que se ha introducido <tt>alguien@correo.org</tt> en el campo <em>Reglas openPGP</em> de arriba.<ul>
-<li><em>Es exactamente</em>: Con esta opción, la regla sólo se activará en los correos a <tt>alguien@correo.org</tt> (exacto, no se tienen en cuenta las mayúsculas).</li>
-<li><em>Contiene</em>: Con esta opción, cualquier dirección de correo que contenga la cadena, cumplirá la regla, como <tt>unnombre@correo.dominio</tt> o <tt>nombre@correo.dominio.org</tt></li>
-<li><em>Comienza con</em>: Con esta opción, cualquier dirección de correo que empiece por la cadena, cumplirá la regla, como <tt>alguien@correo.dominio.net</tt>, <tt>alguien@correo.nombre-dominio.com</tt>.</li>
-<li><em>Acaba en</em>: Con esta opción, cualquier dirección de correo que acabe en la cadena, cumplirá la regla, como <tt>otronombre@correo.org</tt>, <tt>alguien@correo.org</tt></li>
-</ul></li>
-<li><strong>Continuar con la regla siguiente para la dirección coincidente</strong><br />
-Activar esta función permitirá definir una regla pero no tener que especificar un ID de clave en el campo <em>Usar las siguientes claves OpenPGP:</em> para que se use la dirección de correo electrónico para comprobar una clave en el momento del envío. También se procesarán las reglas posteriores para la misma dirección.</li>
-<li><strong>No comprobar las reglas siguientes para la dirección coincidente</strong><br />
-Activar esta función detiene el procesamiento de cualquier otra regla para las direcciones que cumplan la regla. Es decir, las reglas se reanudan procesando el próximo destinatario.</li>
-<li><strong>Usar las siguientes claves OpenPGP:</strong><br />
-Use el botón <em>Seleccionar clave(s)...</em> para seleccionar las claves del destinatario que se usen para el cifrado. Al igual que la acción anterior, no se continúan procesando las reglas para las direcciones que cumplan la regla.</li>
-<li><strong>Predeterminada para firmar</strong>: Activa o desactiva la firma del mensaje. Esta opción usa o ignora lo especificado en la ventana de redacción de mensajes. Los valores son:
-<br /><ul>
-<li><em>Nunca</em>: Desactiva la firma, incluso si se activó en la ventana de redacción de mensajes (tiene preferencia sobre los otros valores).</li>
-<li><em>Sí, si está seleccionada en la redacción del mensaje</em>: Deja la firma como se haya especificado en la ventana de redacción de mensajes.</li>
-<li><em>Siempre</em>: Activa la firma, incluso si <strong>no</strong> estaba activada en la ventana de redacción de mensajes.</li>
-</ul>
-</li>
-</ul>
-<div style="margin-left: 40px;">Estas opciones de firma se aplican a todas las reglas que coincidan con el criterio. Si una de las reglas desactiva la firma, el mensaje no se firmará, independientemente de que otras especifiquen <em>Siempre</em>.<br /></div>
-<ul><li><strong>Cifrar</strong>: Activa o desactiva el cifrado del mensaje. Las opciones permitidas y su significado son las mismas que para la firma de mensajes.</li>
-<li><strong>PGP/MIME</strong>: Activa o desactiva el uso de la codificación PGP/MIME (RFC 3156) en el mensaje. Si PGP/MIME está desactivado, los mensajes se codifican usando "PGP integrado". Los valores permitidos y su significado son los mismos que para la firma de mensajes.</li>
-</ul>
-<p>Las reglas se procesan en el orden mostrado en la lista de <em>OpenPGP - Editar reglas por destinatario</em>. Cuando una regla coincida con un destinatario y contenga un ID de clave OpenPGP, además de usar el ID de clave especificado, el destinatario ya no se considera cuando se procesen más reglas.</p>
-<hr /><p>Más ayuda disponible en la <a href="https://www.enigmail.net/documentation/pgprules_file.php" onclick="window.open('https://www.enigmail.net/pgprules_file.html');return false">página de configuración por destinatario de Enigmail</a></p>
-</body></html>
-
lang/cs/enigmail.dtd
- ...