pax_global_header 0000666 0000000 0000000 00000000064 12667016244 0014522 g ustar 00root root 0000000 0000000 52 comment=99776ee97399ac723b7d687db43bd9a0bd8871eb
enigmail/ 0000775 0000000 0000000 00000000000 12667016244 0012653 5 ustar 00root root 0000000 0000000 enigmail/.eslintrc.js 0000664 0000000 0000000 00000002651 12667016244 0015116 0 ustar 00root root 0000000 0000000 module.exports = {
"rules": {
"linebreak-style": [
2,
"unix"
],
"semi": [
2,
"always"
],
"strict": [2, "global"],
"no-unused-vars": 0,
"no-empty": 0,
"comma-dangle": 0,
"consistent-return": 2,
"block-scoped-var": 2,
"dot-notation": 2,
"no-alert": 2,
"no-caller": 2,
"no-case-declarations": 2,
"no-div-regex": 2,
"no-empty-label": 2,
"no-empty-pattern": 2,
"no-eq-null": 2,
"no-eval": 2,
"no-extend-native": 2,
"no-extra-bind": 2,
"no-fallthrough": 2,
"no-floating-decimal": 2,
"no-implicit-coercion": 2,
"no-implied-eval": 2,
"no-invalid-this": 2,
"no-iterator": 2,
"no-labels": 2,
"no-lone-blocks": 2,
"no-loop-func": 2,
"no-multi-str": 2,
"no-native-reassign": 2,
"no-new-func": 2,
"no-new-wrappers": 2,
"no-new": 2,
"no-octal-escape": 2,
"no-process-env": 2,
"no-proto": 2,
"no-redeclare": [2, {
"builtinGlobals": true
}],
"no-return-assign": 2,
"no-script-url": 2,
"no-self-compare": 2,
"no-sequences": 2,
"no-unused-expressions": 2,
"no-useless-call": 2,
"no-useless-concat": 2,
"no-void": 2,
"no-with": 2,
"radix": 2,
"wrap-iife": [2, "inside"],
"yoda": 2,
// TODO:
//"eqeqeq": 2,
},
"env": {
"es6": true,
"browser": true,
"node": true,
},
"extends": "eslint:recommended"
};
enigmail/.gitattributes 0000664 0000000 0000000 00000000053 12667016244 0015544 0 ustar 00root root 0000000 0000000 *.xul text
*.rdf text
*.js text
*.jsm text
enigmail/.gitignore 0000664 0000000 0000000 00000000702 12667016244 0014642 0 ustar 00root root 0000000 0000000 # generated files:
*.pyc
*.dtd.gen
*.properties.gen
/config.log
/config.status
/config/autoconf.mk
/build
/ui/content/enigmailBuildDate.js
/ipc/src/subprocess.o
/public/_xpidlgen
ipc/src/libsubprocess-*.dylib
ipc/src/libsubprocess-*.so
/test_output.log
/ipc/tests/ipc-data.txt
# vi tmp files:
*.swp
*.swo
# emacs tmp files:
\#*\#
.dir-locals.el
# backup files:
*~
# vagrant files:
provisioning/.vagrant
# other local configuration files:
.ackrc
enigmail/.jsbeautifyrc 0000664 0000000 0000000 00000001150 12667016244 0015343 0 ustar 00root root 0000000 0000000 {
"indent_size": 2,
"indent_char": " ",
"eol": "\n",
"indent_level": 0,
"indent_with_tabs": false,
"preserve_newlines": true,
"max_preserve_newlines": 10,
"jslint_happy": false,
"space_after_anon_function": false,
"brace_style": "end-expand",
"keep_array_indentation": false,
"keep_function_indentation": false,
"space_before_conditional": true,
"break_chained_methods": false,
"eval_code": false,
"unescape_strings": false,
"wrap_line_length": 0,
"wrap_attributes": "auto",
"wrap_attributes_indent_size": 4,
"end_with_newline": true
}
enigmail/.travis.yml 0000664 0000000 0000000 00000000521 12667016244 0014762 0 ustar 00root root 0000000 0000000 language: c
sudo: required
compiler:
- gcc
install:
provisioning/provision-travis.sh
script:
- ./configure
- make > /dev/null 2>&1
- Xvfb :99 >/dev/null 2>&1 &
- export DISPLAY=:99
- ./configure --enable-tests --with-tb-path=$(which thunderbird)
- make
- ./build.sh
- ./test.sh
after_failure:
- cat test_output.log
enigmail/COMPILING 0000664 0000000 0000000 00000001014 12667016244 0014113 0 ustar 00root root 0000000 0000000 Instructions for compiling and packaging Enigmail
=================================================
Prerequisites
-------------
In order to build Enigmail you will need the following helper tools:
- GNU make 3.81 or newer
- zip
- python 2.7 or newer
- perl 5 or newer
If you want to execute unit tests, you will also need:
- eslint (installable via node.js / npm, see http://eslint.org)
Building
--------
Execute the following commands:
./configure
make
The resulting XPI file can be found in the "build" directory.
enigmail/Makefile 0000664 0000000 0000000 00000002025 12667016244 0014312 0 ustar 00root root 0000000 0000000 # This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
XPI_MODULE = enigmail
XPI_MODULE_VERS = 1.9.1
DEPTH = .
include $(DEPTH)/config/autoconf.mk
DIRS = ipc public
DIRS += ui package lang
ALL = dirs xpi
ifeq ($(TESTS),yes)
ALL += test
endif
XPIFILE = $(XPI_MODULE)-$(XPI_MODULE_VERS).xpi
.PHONY: dirs $(DIRS) test
all: $(ALL)
dirs: $(DIRS)
$(DIRS):
$(MAKE) -C $@
xpi:
$(srcdir)/util/genxpi $(XPIFILE) $(XPI_MODULE_VERS) $(DIST) $(srcdir) $(XPI_MODULE) $(ENABLE_LANG)
check:
util/checkFiles.py
eslint:
static_analysis/eslint ipc
static_analysis/eslint package
static_analysis/eslint ui
unit:
make -C package/tests
make -C ui/tests
test: eslint check unit
clean:
rm -f build/$(XPIFILE)
for dir in $(DIRS); do \
if [ "$${dir}x" != "checkx" ]; then \
$(MAKE) -C $$dir clean; fi; \
done
distclean: clean
rm -rf build/*
rm -f config/autoconf.mk config.log config.status
enigmail/build.sh 0000775 0000000 0000000 00000000503 12667016244 0014307 0 ustar 00root root 0000000 0000000 #!/usr/bin/env bash
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
#
export TB_PATH=${TB_PATH:-`which thunderbird`}
make clean
./configure --with-tb-path=$TB_PATH
make
enigmail/config.guess 0000775 0000000 0000000 00000127166 12667016244 0015210 0 ustar 00root root 0000000 0000000 #! /bin/sh
# Attempt to guess a canonical system name.
# Copyright 1992-2013 Free Software Foundation, Inc.
timestamp='2013-02-12'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, see Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails. If Display selection when necessary is set in Preferences -> Key Selection tab, 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. If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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. If you know the recipient(s) can read mail using the PGP/MIME format, you should use it. This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME. 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. 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. Further help is available on the Enigmail Help web page 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. The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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. Further help is available on the Enigmail Per-Recipient Settings page There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below;
for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed.
If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site. If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block. You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver. Clicking on the Pen and Question mark 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. To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default. Further help is available on the Enigmail Help web page 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: 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 Always. 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. Note: 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). Further information for directly editing the file is available on the Enigmail Homepage Further help is available on the Enigmail Help web page In the Sending Preferences you can choose the general model and preferences for encryption. This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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. Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails. If Display selection when necessary is set in Preferences -> Key Selection tab, 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. If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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. If you know the recipient(s) can read mail using the PGP/MIME format, you should use it. This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME. 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. 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. Further help is available on the Enigmail Help web page 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. The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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. Further help is available on the Enigmail Per-Recipient Settings page There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below;
for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed.
If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site. If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block. You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver. Clicking on the Pen and Question mark 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. To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default. Further help is available on the Enigmail Help web page 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: 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 Always. 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. Note: 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). Further information for directly editing the file is available on the Enigmail Homepage Further help is available on the Enigmail Help web page In the Sending Preferences you can choose the general model and preferences for encryption. This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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. Si s'ha activat Mostra la selecció només quan es necessiti a Preferències
-> Pestanya de selecció de claus, 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. Si s'ha activat No mostris mai el diàleg de selecció de claus OpenPGP a Preferències
-> Pestanya de selecció de claus, 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. Si teniu coneixement que el(s) destinatari(s) pot llegir el correu codificat amb el format PGP/MIME,
hauríeu d'activar-lo. Aquesta funcionalitat depèn de si estan actius els paràmetres Permet l'ús de PGP/MIME o
Empra sempre PGP/MIME a Preferències -> Pestanya PGP/MIME.
Teniu més ajuda a la vostra disposició a la
pàgina web de l'Enigmail
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.
Les regles es processen segons l'ordre mostrat a la llista de
l'editor de regles OpenPGP. 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.
Teniu més ajuda a la vostra disposició a la
pàgina de paràmetres per destinatari de l'Enigmail
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 pàgina d'ajuda de l'Enigmail.
Per a que funcioni l'OpenPGP, cal instal·lar l'eina GnuPG.
Si no es pot trobar el GnuPG, primer assegureu-vos que l'executable gpg.exe (a Windows, gpg 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ú OpenPGP > Preferències)
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 mozilla.org.
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 secció de codi font 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.
Hi ha més ajuda disponible en el lloc web d'ajuda de l'Enigmail. Si no heu establert l'opció keyserver-options auto-key-retrieve al vostre fitxer
gpg.conf i llegiu un missatge que està signat o xifrat,
veureu la icona d'un llapis a l'àrea de visualització de les capçaleres amb un interrogant,
i la línia d'estat de l'Enigmail a l'àrea de capçaleres indicarà Part
del missatge signat; feu un clic a la icona del llapis pels detalls i el missatge de la subfinestra
de la Missatgeria mostrarà tots els indicadors del bloc PGP del missatge i el bloc de signatura. També podreu veure això si teniu establerta l'opció keyserver-options auto-key-retrieve
al vostre fitxer gpg.conf i la clau PGP no es troba en el servidor de claus predeterminat. En fer un clic a la icona del llapis amb interrogant 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. Per a configurar la llista dels servidors de claus que voleu usar, aneu a la pestanya Enigmail ->
Preferències -> Bàsic i introduïu les adreces dels servidors de claus a la caixa
Servidor(s) de claus:, separats per comes. El primer servidor de claus serà el
predeterminat.
Teniu més ajuda a la vostra disposició a la
pàgina web de l'Enigmail
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:
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. Nota: 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).
Més informació
per editar directament el fitxer a la pàgina web de l'Enigmail
Teniu més ajuda a la vostra disposició a la
pàgina web d'ajuda de l'Enigmail
In the Sending Preferences you can choose the general model and preferences for encryption. This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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. 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Å™i nastavené volbÄ› Zobraz výbÄ›r, když je tÅ™eba v menu PÅ™edvolby-> záložka VýbÄ›r klÃÄe 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Å™i nastavené volbÄ› Nikdy nezobrazovat výbÄ›r OpenPGP klÃÄe v menu PÅ™edvolby -> záložka VýbÄ›r klÃÄe se odeÅ¡le zpráva nezaÅ¡ifrovaná, pokud jsou v seznamu pÅ™Ãjemců poÅ¡ty adresáti, jejichž veÅ™ejný klÃÄ nemáte. 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. Tato volba je povolena, pokud na záložce PÅ™edvolby -> PGP/MIME tab je nastaveno Povolit použità PGP/MIME nebo Vždy použÃt PGP/MIME. 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. 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. Dalšà nápovÄ›da je dostupná na stránkách dokumentace Enigmailu (anglicky). 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. 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á. Dalšà nápovÄ›da je dostupná na stránkách dokumentace Enigmailu (anglicky). Jestliže v souboru gpg.conf 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 pera s otaznÃkem a v hornà Äásti se zobrazÃ: Část zprávy byla podepsána; klepnÄ›te na ikonku pera nebo klÃÄe pro vÃce informacÃ. Ve zprávÄ› se zobrazà znaÄky úseku textu OpenPGP a blok podpisu. 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. KlepnutÃm na ikonku pera a otaznÃku 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. Seznam keyserverů, které chcete použÃvat, nastavÃte v menu OpenPGP -> PÅ™edvolby... -> UrÄete Váš/VaÅ¡e keyservery, adresy napiÅ¡te do řádku Keyserver(y):. VÃce adres oddÄ›lte Äárkou. Jako výchozà bude použit prvnà keyserver. Dalšà nápovÄ›da je dostupná na stránkách dokumentace Enigmailu (anglicky). 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:
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 Vždy. 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á. Poznámka: 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. Dalšà informace o pÅ™Ãmé úpravÄ› souboru s pravidly si můžete pÅ™eÄÃst na stránkách Enigmailu (anglicky). Dalšà nápovÄ›da je dostupná na stránkách dokumentace Enigmailu (anglicky). In the Sending Preferences you can choose the general model and preferences for encryption. This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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. Verschlüsselung an alle Adressaten aktivieren / deaktivieren. Der Benutzer wird benachrichtigt, falls die Verschlüsselung fehlschlägt. Falls Auswahl anzeigen, wenn notwendig im Menü Enigmail -> Einstellungen -> Schlüsselauswahl... 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. Falls Auswahlfenster nie anzeigen im Menü Enigmail -> Einstellungen -> Schlüsselauswahl... eingestellt ist, dann wird die Nachricht an die Empfänger unverschlüsselt gesendet, von denen Sie keinen öffentlichen Schlüssel besitzen. Wenn Sie wissen, dass die Empfänger das PGP/MIME-Format verwenden können, dann sollten Sie dies benutzen. Diese Möglichkeit hängt von den Einstellungen unter Enigmail -> Einstellungen -> PGP/MIME... ab. Hier muss PGP/MIME verwenden, wenn möglich oder Immer PGP/MIME verwenden aktiviert sein. 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. 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. Weitere Hilfe ist verfügbar auf der Enigmail-Hilfeseite 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. 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. Weitere Hilfe ist verfügbar auf der Enigmail Per-Recipient Settings Seite Es gibt verschiedene Ursachen für ein Fehlschlagen der Enigmail-Initialisierung. Die bekanntesten werden unten beschrieben&
für weitere Informationen besuchen Sie bitte die Enigmail-Hilfe-Webseite.
Damit Enigmail funktionieren kann, muss die Anwendung GnuPG installiert sein.
Wenn GnuPG nicht gefunden werden kann, stellen Sie als erstes sicher, dass die Anwendung gpg.exe (für Windows& gpg für andere Plattformen) auf Ihrem PC tatsächlich vorhanden ist.
Wenn GnuPG (gpg.exe bzw. gpg) 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ü Enigmail > Einstellungen...).
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 mozilla.org verwenden.
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 Bereich Source-Code. Bitte erstellen Sie keine Fehlerhinweise (Bugs) zu diesem Problem, da es dazu keine andere Lösung gibt.
Weitere Hilfe ist verfügbar unter Enigmail-Hilfeseite Falls Sie keyserver-options auto-key-retrieve nicht in der Datei gpg.conf eingestellt haben, und Sie lesen eine Nachricht, die signiert oder verschlüsselt ist, dann erscheint ein Stift-Symbol mit einem Fragezeichen. Die Enigmail-Statuszeile im Kopfzeilenbereich der Nachricht wird melden: Ein Teil der Nachricht ist signiert; klicken Sie auf das Stift-Symbol für Details, und im Nachrichtentext werden alle PGP-Nachrichtenblockanzeiger und Signaturblöcke angezeigt. Dies kann außerdem angezeigt werden, wenn Sie keyserver-options auto-key-retrieve in der Datei gpg.conf eingestellt haben aber der OpenPGP-Schlüssel nicht auf dem voreingestellten Schlüssel-Server verfügbar ist. Wenn Sie auf das Schlüssel mit Fragezeichen-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. Um die Liste der Schlüssel-Server, die Sie verwenden möchten, zu konfigurieren, gehen Sie zu Enigmail -> Einstellungen... -> Allgemein und geben die Adressen der Schlüssel-Server im Feld Schlüssel-Server ein (jeweils getrennt durch ein Komma). Der erste Schlüssel-Server wird als voreingestellter Server verwendet. Weitere Hilfe ist verfügbar unter Enigmail Hilfeseite 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: 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 Immer angegeben ist. 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. Hinweis: 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). Weitere Informationen, wie die Datei bearbeitet werden muss, gibt es auf der Enigmail-Homepage Weitere Hilfe ist verfügbar auf der Enigmail-Hilfeseite In den Senden Einstellungen kann man prinzipiell das Modell und die prinzipiellen Einstellungen zum Verschlüsseln einstellen. 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. 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. 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). 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).Enigmail Help
Using Enigmail when composing messages
Enigmail Help
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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 Always.
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
Enigmail Help
Using Enigmail when reading messages
Enigmail Help
Using the Enigmail Rules Editor
Enigmail Help
Defining Preferences to Send Encrypted
Enigmail Help
Using Enigmail when composing messages
Enigmail Help
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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 Always.
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
Enigmail Help
Using Enigmail when reading messages
Enigmail Help
Using the Enigmail Rules Editor
Enigmail Help
Defining Preferences to Send Encrypted
Ajuda Enigmail
Emprant l'Enigmail per redactar missatges
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.
Ajuda Enigmail
Emprant l'editor de regles de l'Enigmail: Edició d'una regla OpenPGP
L'activació d'aquesta funció us permet definir una regla sense
haver d'indicar una identificació de clau en el camp Empra les
claus OpenPGP següents:, 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).
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.
Empreu el botó Selecciona clau(s).. 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.
Ajuda de l'Enigmail
Com resoldre els problemes en inicialitzar l'OpenPGP
Ajuda Enigmail
Emprant l'Enigmail per llegir missatges
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.
Les icones del llapis i la clau 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
llapis canviarà a un llapis trencat 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:
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:
Desxifra i obre i Desxifra i desa. 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.
Ajuda Enigmail
Emprant l'editor de regles de l'Enigmail
Enigmail Help
Defining Preferences to Send Encrypted
Nápověda pro Enigmail
Použità Enigmailu při psanà zprávy
Nápověda pro Enigmail
PoužÃvánà editoru pravidel v Enigmailu: úprava pravidel OpenPGP
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 Vždy.
Nápověda pro Enigmail
PoužÃvánà Enigmailu pÅ™i Ätenà zpráv
Nápověda pro Enigmail
Použità editoru pravidel v Enigmailu
Enigmail Help
Defining Preferences to Send Encrypted
Enigmail-Hilfe
Verwenden von Enigmail beim Verfassen von Nachrichten
Enigmail-Hilfe
Enigmail-Empfängerregeln bearbeiten
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 Immer vorschreiben, nicht unterschrieben.
Enigmail-Hilfe
Beheben von Problemen bei der Enigmail-Initialisierung
Enigmail-Hilfe
Verwenden von Enigmail beim Lesen von Nachrichten
Enigmail-Hilfe
Enigmail-Empfängerregeln
Enigmail-Hilfe
Optionen zum Verschlüsselten Senden
Weitere Hilfe ist verfügbar auf der Enigmail-Hilfeseite
enigmail/lang/el/ 0000775 0000000 0000000 00000000000 12667016244 0014174 5 ustar 00root root 0000000 0000000 enigmail/lang/el/am-enigprefs.properties 0000664 0000000 0000000 00000000131 12667016244 0020662 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager prefPanel-enigprefs=Ασφάλεια OpenPGP enigmail/lang/el/enigmail.dtd 0000664 0000000 0000000 00000123026 12667016244 0016462 0 ustar 00root root 0000000 0000000 ΣΗΜΕΙΩΣΗ: Η δημιουÏγία του ÎºÎ»ÎµÎ¹Î´Î¹Î¿Ï Î¼Ï€Î¿Ïεί να διαÏκÎσει αÏκετά λεπτά. Μην τεÏματίσετε την εφαÏμογή κατά τη διάÏκεια της δημιουÏγίας του κλειδιοÏ. Κατά τη διάÏκεια της δημιουÏγίας του ÎºÎ»ÎµÎ¹Î´Î¹Î¿Ï Î¸Î± ήταν καλό να κάνετε κάποιες εÏγασίες που χÏησιμοποιοÏν τους πόÏους του συστήματος (επεξεÏγαστή, μνήμη, δίσκο) για να αυξηθεί η εντÏοπία και να επισπευσθεί η δημιουÏγία του κλειδιοÏ. Θα ειδοποιηθείτε όταν ολοκληÏωθεί η δημιουÏγία του κλειδιοÏ."> ' δεν είναι ÎγκυÏο"> ΣΗΜΕΙΩΣΗ: Η δημιουÏγία του ÎºÎ»ÎµÎ¹Î´Î¹Î¿Ï Î¼Ï€Î¿Ïεί να διαÏκÎσει αÏκετά λεπτά. Μην τεÏματίσετε την εφαÏμογή κατά τη διάÏκεια της δημιουÏγίας του κλειδιοÏ. Θα ειδοποιηθείτε όταν ολοκληÏωθεί η δημιουÏγία του κλειδιοÏ."> Σημείωση: Το Enigmail θα επαληθεÏει πάντα τις υπογÏαφÎÏ‚ των μηνυμάτων όλων των λογαÏιασμών και ταυτοτήτων, ανεξάÏτητα αν είναι ενεÏγοποιημÎνο για αυτÎÏ‚ ή όχι">Αν Îχει ενεÏγοποιηθεί η επιλογή Εμφάνιση επιλογών όταν είναι απαÏαίτητο στην καÏÏ„Îλα Î Ïοτιμήσεις -> Επιλογή κλειδιοÏ, και υπάÏχουν διευθÏνσεις στη λίστα παÏαληπτών για τις οποίες δεν υπάÏχει δημόσιο κλειδί, θα εμφανιστεί η λίστα κλειδιών για να επιλÎξετε αυτό που θα χÏησιμοποιηθεί.
Αν Îχει ενεÏγοποιηθεί η επιλογή Îα μην εμφανίζεται ποτΠο διάλογος επιλογής κλειδί OpenPGP στην καÏÏ„Îλα Î Ïοτιμήσεις -> Επιλογή κλειδιοÏ, και υπάÏχουν διευθÏνσεις στη λίστα παÏαληπτών για τις οποίες δεν υπάÏχει δημόσιο κλειδί, το μήνυμα θα αποσταλεί χωÏίς κÏυπτογÏάφηση.
Αν γνωÏίζετε ότι οι παÏαλήπτες του μηνÏματός σας μποÏοÏν να διαβάσουν μηνÏματα που χÏησιμοποιοÏν PGP/MIME, καλό είναι να το ενεÏγοποιήσετε.
Αυτό το χαÏακτηÏιστικό εξαÏτάται από το αν Îχετε ενεÏγοποιήσει μία από τις επιλογÎÏ‚ ΕπιτÏÎπεται η χÏήση PGP/MIME ή Îα χÏησιμοποιείται πάντα PGP/MIME, στην καÏÏ„Îλα Î Ïοτιμήσεις -> PGP/MIME.
ΠεÏισσότεÏη βοήθεια είναι διαθÎσιμη στο δικτυακό τόπο του Enigmail
enigmail/lang/el/help/editRcptRule.html 0000664 0000000 0000000 00000021074 12667016244 0020424 0 ustar 00root root 0000000 0000000Στον ΕπεξεÏγαστή κανόνων, μποÏείτε να καθοÏίσετε τις Ï€ÏοκαθοÏισμÎνες επιλογÎÏ‚ για κάθε παÏαλήπτη για την ενεÏγοποίηση της κÏυπτογÏάφησης, υπογÏαφής και χÏήση PGP/MIME, και να επιλÎξετε τα κλειδιά OpenPGP που θα χÏησιμοποιηθοÏν. Σε αυτόν το διάλογο μποÏείτε να καθοÏίσετε τους κανόνες για Îνα συγκεκÏιμÎνο παÏαλήπτη, ή για μια ομάδα παÏαληπτών με παÏόμοιες ιδιότητες.
Οι κανόνες εφαÏμόζονται με τη σειÏά που βÏίσκονται στη λίστα του ΕπεξεÏγαστή κανόνων OpenPGP. Κάθε φοÏά που Îνας κανόνας ταιÏιάζει με Îναν παÏαλήπτη και πεÏιÎχει Îνα ID ÎºÎ»ÎµÎ¹Î´Î¹Î¿Ï OpenPGP, εκτός του ότι θα χÏησιμοποιηθεί το καθοÏισμÎνο ID κλειδιοÏ, ο παÏαλήπτης δε θα θεωÏείται διαθÎσιμος για τους υπόλοιπους κανόνες.
ΠεÏισσότεÏη βοήθεια είναι διαθÎσιμη στο δικτυακό τόπο του Enigmail
enigmail/lang/el/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0017777 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/el/help/messenger.html 0000664 0000000 0000000 00000017324 12667016244 0020011 0 ustar 00root root 0000000 0000000Αν δεν Îχετε ενεÏγοποιημÎνη την επιλογή keyserver-options auto-key-retrieve στο αÏχείο gpg.conf σας, και διαβάζετε Îνα μήνυμα που είναι υπογεγÏαμμÎνο ή κÏυπτογÏαφημÎνο, στην κεφαλίδα του μηνÏματος θα εμφανιστεί το εικονίδιο Î Îνας με Îνα ΕÏωτηματικό πάνω του, ενώ το μήνυμα στη γÏαμμή κατάστασης του Enigmail θα λÎει Τμήμα του μηνÏματος υπογεγÏαμμÎνο· κάντε κλικ στο εικονίδιο Î Îνας για πληÏοφοÏίες και στην πεÏιοχή κειμÎνου του μηνÏματος θα εμφανίζονται όλα τα OpenPGP μπλοκ και το μπλοκ της υπογÏαφής.
Αυτό μποÏεί επίσης να συμβεί όταν το κλειδί δεν υπάÏχει στον Ï€ÏοκαθοÏισμÎνο εξυπηÏετητή κλειδιών, ακόμα κι αν Îχετε ενεÏγοποιημÎνη την επιλογήkeyserver-options auto-key-retrieve στο gpg.conf σας.
Κάνοντας κλικ στο εικονίδιο Î Îνας και ΕÏÏ‰Ï„Î·Î¼Î±Ï„Î¹ÎºÎ¿Ï Î¸Î± εμφανιστεί Îνα παÏάθυÏο που θα σας πληÏοφοÏεί ότι το κλειδί δεν είναι διαθÎσιμο στη λίστα κλειδιών σας. Πατώντας OK θα εμφανιστεί Îνα άλλο παÏάθυÏο με μία λίστα εξυπηÏετητών κλειδιών για να επιλÎξετε από ποιον θα γίνει λήψη του δημόσιου ÎºÎ»ÎµÎ¹Î´Î¹Î¿Ï Ï„Î¿Ï… αποστολÎα.
Για να οÏίσετε τη λίστα των εξυπηÏετητών κλειδιών που θÎλετε να χÏησιμοποιείτε, πηγαίνετε στην καÏÏ„Îλα Enigmail -> Î Ïοτιμήσεις -> ΒασικÎÏ‚ και εισάγετε τις διευθÏνσεις στο πεδίο ΕξυπηÏετητής(ÎÏ‚) κλειδιών:, χωÏισμÎνες με κόμματα. Ο Ï€Ïώτος εξυπηÏετητής στη λίστα θα χÏησιμοποιηθεί ως ο Ï€ÏοκαθοÏισμÎνος.
ΠεÏισσότεÏη βοήθεια είναι διαθÎσιμη στο δικτυακό τόπο του Enigmail
Αν Îχετε εÏωτήσεις ή σχόλια σχετικά με το enigmail, παÏακαλώ στείλτε Îνα μήνυμα στη λίστα του Enigmail OpenPGP
Το Enigmail OpenPGP είναι λογισμικό Î±Î½Î¿Î¹ÎºÏ„Î¿Ï ÎºÏŽÎ´Î¹ÎºÎ± και κυκλοφοÏεί υπό την Mozilla Public License και την GNU General Public License
enigmail/lang/el/help/rulesEditor.html 0000664 0000000 0000000 00000012215 12667016244 0020314 0 ustar 00root root 0000000 0000000Στον ΕπεξεÏγαστή κανόνων, μποÏείτε να καθοÏίσετε τις Ï€ÏοκαθοÏισμÎνες επιλογÎÏ‚ για κάθε παÏαλήπτη για την ενεÏγοποίηση της κÏυπτογÏάφησης, υπογÏαφής και χÏήση PGP/MIME, και να επιλÎξετε τα κλειδιά OpenPGP που θα χÏησιμοποιηθοÏν. Κάθε κανόνας αποτελείται από Ï€Îντε πεδία:
Οι κανόνες εφαÏμόζονται με τη σειÏά που βÏίσκονται στη λίστα. Κάθε φοÏά που Îνας κανόνας ταιÏιάζει με Îναν παÏαλήπτη και πεÏιÎχει Îνα ID ÎºÎ»ÎµÎ¹Î´Î¹Î¿Ï OpenPGP, εκτός του ότι θα χÏησιμοποιηθεί το καθοÏισμÎνο ID κλειδιοÏ, ο παÏαλήπτης δε θα θεωÏείται διαθÎσιμος για τους υπόλοιπους κανόνες.
Σημείωση: Ο ΕπεξεÏγαστής κανόνων δεν είναι ακόμα ολοκληÏωμÎνος. Είναι δυνατή η συγγÏαφή πιο Ï€ÏοχωÏημÎνων κανόνων με απευθείας επεξεÏγασία του αÏχείου κανόνων (δε θα Ï€ÏÎπει να γίνει πλÎον επεξεÏγασία αυτών των κανόνων με τον ΕπεξεÏγαστή). ΠεÏισσότεÏες πληÏοφοÏίες για την απευθείας επεξεÏγασία του αÏχείου κανόνων υπάÏχουν στο δικτυακό τόπο του Enigmail
ΠεÏισσότεÏη βοήθεια είναι διαθÎσιμη στο δικτυακό τόπο του Enigmail
enigmail/lang/el/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020460 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Si está activada la opción Mostrar la selección si es necesario en Preferencias -> pestaña Selección de clave, 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.
Si está activada la opción Nunca mostrar el diálogo de selección de clave OpenPGP en Preferencias -> pestaña Selección de clave, 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.
Si sabe con certeza que los destinatarios pueden leer el correo usando el formato PGP/MIME, entonces se debe usar.
Esta característica depende de la configuración en Preferencias -> pestaña PGP/MIME si está establecida en Usar PGP/MIME si es posible o Siempre usar PGP/MIME.
Más ayuda disponible en la página Web de ayuda de Enigmail
enigmail/lang/es-AR/help/editRcptRule.html 0000664 0000000 0000000 00000013344 12667016244 0020734 0 ustar 00root root 0000000 0000000En 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.
Las reglas se procesan en el orden mostrado en la lista de OpenPGP - Editar reglas por destinatario. 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.
Más ayuda disponible en la página de configuración por destinatario de Enigmail
enigmail/lang/es-AR/help/initError.html 0000664 0000000 0000000 00000005252 12667016244 0020302 0 ustar 00root root 0000000 0000000Hay 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 página de Soporte de Enigmail.
Para que funcione OpenPGP, la herramienta GnuPG debe ser instalada. Si GnuPG no puede ser encontrado, entonces primero asegúrese de que el ejecutable gpg.exe (en Windows& gpg 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ú OpenPGP > Preferencias)
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 mozilla.org.
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 sección de Código Fuente en la página de Enigmail. Por favor no envie reportes de bugs acerca de este problema, no puede ser solucionado.
Más ayuda está disponible en el Sitio Web de Soporte de Enigmail.
enigmail/lang/es-AR/help/messenger.html 0000664 0000000 0000000 00000011526 12667016244 0020316 0 ustar 00root root 0000000 0000000Si no tiene puesta la opción keyserver-options auto-key-retrieve en su archivo gpg.conf y lee un mensaje que está firmado o cifrado, verá un icono de un Lápiz en el área de visión de las cabeceras con un Signo de interrogación y, la línea de estado de Enigmail en el área de las cabeceras dirá: Parte del mensaje firmado; pulse el icono del lápiz para más detalles y el mensaje en el panel de mensajes mostrará todos los indicadores del bloque del mensaje OpenPGP y el bloque de la firma.
También se puede ver esto si tiene activada la opción keyserver-options auto-key-retrieve en su archivo gpg.conf y la clave OpenPGP no está disponible en el servidor de claves predeterminado.
Al pulsar en el icono del Lápiz y Signo de interrogación 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.
Para configurar la lista de servidores de claves que desee usar, vaya a la pestaña Enigmail -> Preferencias -> Básicas e introduzca la dirección de los servidores de claves en el recuadro Servidor(es) de claves: separados por una coma. El primer servidor de claves de la lista se usará como predeterminado.
Más ayuda disponible en la página Web de ayuda de Enigmail
enigmail/lang/es-AR/help/rulesEditor.html 0000664 0000000 0000000 00000006675 12667016244 0020640 0 ustar 00root root 0000000 0000000En 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:
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.
NOTA: 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). Más información para editar el archivo directamente se encuentra disponible en la página Web de Enigmail.
Más ayuda disponible en la página Web de ayuda de Enigmail
enigmail/lang/es-AR/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020767 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Si Mostrar selección cuando sea necesario está seleccionado en Preferencias -> pestaña Selección de Claves, una lista de claves aparecerá si hay direcciones en la lista de destinatarios para los que usted no tenga clave pública.
Si Nunca mostrar diálogo de selección de clave OpenPGP está seleccionado en Preferencias -> pestaña Selección de Claves, y hay direcciones en la lista de destinatarios para los cuales usted no tiene clave pública, el mensaje será enviado sin cifrar.
Si usted sabe que el(los) destinatario(s) pueden leer correos usando el formato PGP/MIME, usted debiera usarlo.
Esta característica depende de la configuración en Preferencias -> pestaña PGP/MIME estando configurada para Permitir el uso de PGP/MIME o Siempre usar PGP/MIME.
Más ayuda disponible en la Página web de Ayuda de Enigmail
enigmail/lang/es-ES/help/editRcptRule.html 0000664 0000000 0000000 00000013233 12667016244 0020736 0 ustar 00root root 0000000 0000000En el Editor de Reglas, usted puede especificar valores por defecto por destinatarios para activar cifrado, firmado y PGP/MIME, y para definir qué clave(s) OpenPGP utilizar. En este diálogo, usted puede especificar reglas para un único destinatario, y para un grupo de destinatarios con atributos muy similares.
Las reglas son procesadas en el orden en que se muestran en la lista en el Editor de Reglas OpenPGP. Siempre que una regla coincide con un destinatario y contiene una KeyID OpenPGP, adicionalmente a usar la KeyID especificada, el destinatario deja de ser considerado al procesar otras reglas adicionales.
Ayuda adicional disponible en la página de Configuración Por-Destinatario de Enigmail
enigmail/lang/es-ES/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020313 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/es-ES/help/messenger.html 0000664 0000000 0000000 00000011526 12667016244 0020323 0 ustar 00root root 0000000 0000000Si no tiene puesta la opción keyserver-options auto-key-retrieve en su archivo gpg.conf y lee un mensaje que está firmado o cifrado, verá un icono de un Lápiz en el área de visión de las cabeceras con un Signo de interrogación y, la línea de estado de Enigmail en el área de las cabeceras dirá: Parte del mensaje firmado; pulse el icono del lápiz para más detalles y el mensaje en el panel de mensajes mostrará todos los indicadores del bloque del mensaje OpenPGP y el bloque de la firma.
También se puede ver esto si tiene activada la opción keyserver-options auto-key-retrieve en su archivo gpg.conf y la clave OpenPGP no está disponible en el servidor de claves predeterminado.
Al pulsar en el icono del Lápiz y Signo de interrogación 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.
Para configurar la lista de servidores de claves que desee usar, vaya a la pestaña Enigmail -> Preferencias -> Básicas e introduzca la dirección de los servidores de claves en el recuadro Servidor(es) de claves: separados por una coma. El primer servidor de claves de la lista se usará como predeterminado.
Más ayuda disponible en la página Web de ayuda de Enigmail
enigmail/lang/es-ES/help/rulesEditor.html 0000664 0000000 0000000 00000006665 12667016244 0020644 0 ustar 00root root 0000000 0000000En 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:
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.
NOTA: 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). Más información para editar el archivo directamente se encuentra disponible en la página Web de Enigmail.
Más ayuda disponible en la página Web de ayuda de Enigmail
enigmail/lang/es-ES/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020774 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Bidali aurretik hartzaile guztientzat mezua zifratzeko aukera gaitu/ezgaitu. Erabiltzaileari ohar bat aterako zaio zifraketak huts egiten badu.
Aukeraketa behar denean erakutsi Lehentasunak -> Gako Aukeraketa fitxan aktibatuta badago, gako zerrenda bat agertuko da hartzaile zerrendan dauden eta euren gako publikorik ez duzun hartzaileentzako.
Ez erakutsi inoiz OpenPGP gako aukeraketa lehioa Lehentasunak -> Gako Aukeraketa fitxan gaituta badago, eta hartzaile zerrendan dagoen hartzaile baten gako publikoa baldin ez baduzu, mezua zifratu gabe bidaliko da.
Hartzaileek e-postak PGP/MIME formatuan irakurri ditzaketela baldin badakizu, erabili beharko zenuke.
Ezaugarri honek Lehentasuanak -> PGP/MIME fitxan dauden PGP/MIME erabiltzen utzi edo Beti PGP/MIME erabili aukerekin dependentzia dauka.
Mezua bidaltzerakoan arazoren bat baldin badago, adibidez, POP serbitzariak eskaera onartzen ez badu, Enigmail-ek ez du horren berri izango eta zifratutako mezua Idatzi lehioan agertzen jarraituko du. Menuaren aukera hau hautatuz sinadura/zifraketa desegingo du, Idatzi lehioa hasieran zegoen testura bueltatuz
Behin-behineko konponketa bezala, aukera hau erabili daiteke zifratutako mezuak erantzuterakoan aipatutako testua argitzeko. Enigmailek automatikoki aipatutako mezua argitu beharko luke, baina horrek huts egiten badu, menu aukera hau erabili dezakezu hori behartzeko
Laguntza gehiago nahi baduzu, Enigmail Laguntza weborrian aurkitu dezakezu.
enigmail/lang/eu/help/editRcptRule.html 0000664 0000000 0000000 00000012227 12667016244 0020435 0 ustar 00root root 0000000 0000000Arau editorean, hartzaile bakoitzaren lehenetsitako aukerak jarri ditzakezu zifraketa, sinadura, PGP/MIME eta ze OpenPGP gakoak erabiliko diren arloetan. Lehio honetan, hartzaile bakar batentzat arauak sartu ditzakezu eta, baita ere, antzeko ezaugarriak dituzten hartzaileentzat..
Arauak OpenPGP Arau Editorean dagoen zerrendaren ordenean prozesatuko dira. Hartzaile batek arau batekin bat datorrenean eta arau horrek OpenPGP gako ID-a badauka, gako ID hori erabiltzeaz gain, hartzailea ez da gehiago kontutan izango ondorengo arauak prozesatzerakoan.
Laguntza gehiago nahi baduzu Enigmail Hartzaile Bakoitzeko Ezaugarriak weborrian aurkitu dezakezu
enigmail/lang/eu/help/initError.html 0000664 0000000 0000000 00000004645 12667016244 0020011 0 ustar 00root root 0000000 0000000Arrazoi asko egon daitezke OpenPGP hasieratzerakoan errorea emateko. Ohikoenak azpian agertzen dira; informazio gehiago nahi baduzu, Enigmail Laguntza weborrian aurkitu dezakezu.
OpenPG funtzionatu dezan GnuPG tresna instalatuta egon behar du. GnuPG ezin izan bada aurkitu, lehendabizi gpg.exe (Windows-en; gpg beste plataformetan) exekutagarria zure ordenagailuan instalatuta dagoela ziurtatu zaitez. GnuPG instalatuta badago eta OpenPGP-k ezn badu aurkitu, OpenPGP lehentasunetan (menua OpenPGP > Lehentasunak) GnuPG-ren helbidea eskuz jarri beharko diozu.
OpenPGP bakarrik funtzionatuko du Thunderbird edo SeaMonkey eraiki ziren ingurune berdinean eraki bada. Horrek esan nahi du, Enigmail-en bertsio ofiziala bakarrik mozilla.org argitaratutako Thunderbird edo SeaMonkey bertsio ofizialekin bakarrik erabili daitekeela.
Beste jatorri bat daukan Thunderbird edo SeaMonkey erabiltzen baduzu (adibidez, zure Linux banaketarekin datorrena), edo zuk zeuk aplikazioa eraiki baduzu, jatorri berdinarekin eraiki den Enigmail bertsio bat erabili beharko zenuke, edo zuk zeuk Enigmail eraiki. Enigmail erakitzeko Iturburu Kodea atalera jo ezazu Enigmail weborrian. Mesedez, ez bidali akats txosten bat arazo honekin, konponketarik ez baitauka.
Informazio gehiago nahi baduzu Enigmail Laguntza weborrian aurkitu dezakezu.
enigmail/lang/eu/help/messenger.html 0000664 0000000 0000000 00000010531 12667016244 0020013 0 ustar 00root root 0000000 0000000Zure gpg.conf fitxategian gako-serbitzari-aukerak gakoak-auto-inportatu gaituta ez baldin baduzu eta sinatutako edo zifratutako mezu bat irakurtzen baduzu, goiburuan dagoen Idazluma ikonoak Galdera ikur bat izango du, eta goiburuan dagoen Enigmail egoera-lerroak hurrengoa esango du: Mezuaren zati bat sinatuta dago; xehetasunentzako idazluma ikonoak klik egin ezazu; horretaz gain mezu panelean OpenPGP mezu bolkearen adierazleak eta sinadura blokeak erakutsiko ditu.
Hau ere ikusi dezakezu zure gpg.conf fitxategian gako-serbitzari-aukerak gakoak-auto-inportatu gaituta gaituta badaukazu eta mezuaren OpenPGP gakoa lehenetsitako gako-serbitzarian eskuragarri ez baldin badago.
Idazluma eta Galdera ikurra ikonoan klik egiten baduzu, gakoa zure gako giltzatakoan ez dagoela abisatzeko lehioa agertuko da. Ados sakatuz, beste lehio bat erakutsiko da, honetan gako-zerbitzari zerrenda bat agertuko da eta bertan igorlearen gako publikoa deskargatzeko serbitzaria aukeratu ahal izango duzu.
Erabiliko diren gako-serbitzaren zerrenda konfiguratzeko, Enigmail -> Lehentasunak -> Oinarrizkoak fitxara joan zaitez eta gako-serbitzarien helbideak Gako-serbitzaria(k): eremuan sartu itzazu koma bitartez bananduz. Zerrendan dagoen lehendabiziko gako-serbitzaria lehenetsitakoa bezela erabiliko da
Laguntza gehiago nahi baldin baduzu Enigmail Laguntza weborrian aurkitu dezakezu.
enigmail/lang/eu/help/rulesEditor.html 0000664 0000000 0000000 00000006161 12667016244 0020330 0 ustar 00root root 0000000 0000000Arau editorean, hartzaile bakoitzaren lehentasunak jarri ditzakezu zifraketa, sinadura eta PGP/MIME gaitzeko, baita ze OpenPGP gako erabiliko diren. Arau bakotzak lerro batean agertzen diren 5 eremu dira:
Sinadura ezarpen hauek bateratzen diren arau guztiekin aplikatzen da. Arau batek sinadura ezgaitzen badu, mezua ez da sinatuko, nahiz eta beste arauek Beti esaten duten.
Arauak zerrendan agertzen diren ordenean prozesatuko dira. Hartzaile batek arau batekin bat datorrenean eta arau horrek OpenPGP gako ID-a badauka, gako ID hori erabiltzeaz gain, hartzailea ez da gehiago kontutan izango ondorengo arauak prozesatzerakoan.
Oharra: Arau editorea oraindik bukatu gabe dago. Arau aurreratuagoak egin daitezke arau fitxategia zuzenean editatuz (arau hauek ez lirateke inoiz gehiago arau editorearekin editatu behar).Informazio gehiago nahi baduzu arau fitxategia zuzenean editatzeari buruz Enigmail weborrian aurkitu dezakezu
Laguntza gehiago nahi baduzu Enigmail Laguntza weborrian aurkitu dezakezu
enigmail/lang/eu/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020471 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Jos sinulla ei ole salatun viestin kaikkien vastaanottajien julkisia avaimia ja asetuksissa on valittuna Näytä avainten valintaikkuna kun se on välttämätöntä, avainlista avautuu.
Jos sinulla ei ole salatun viestin kaikkien vastaanottajien julkisia avaimia ja asetuksissa on valittuna Älä koskaan näytä avainten valintaikkunaa, viesti lähetetään selkokielisenä.
Jos tiedät, että viestin vastaanottajien sähköpostiohjelmat ymmärtävät PGP/MIME-muotoa, sitä tulisi käyttää.
Tämä toiminto otetaan käyttöön valitsemalla PGP/MIME-asetuksista Salli PGP/MIME:n käyttö tai Käytä aina PGP/MIME:ä.
Lisää ohjeita Enigmailin ohjesivulta
enigmail/lang/fi/help/editRcptRule.html 0000664 0000000 0000000 00000011201 12667016244 0020411 0 ustar 00root root 0000000 0000000Sääntömuokkaimessa voit asettaa oletukset viestin allekirjoittamiselle, salaamiselle, PGP/MIME-koodauksen käytölle, ja määrittää käytettävät OpenPGP-avaimet vastaanottajakohtaisesti. Oletukset voidaan asettaa yhdelle vastaanottajalle tai usealle vastaanottajalle, jolla on toisensa kaltaiset sähköpostiosoitteet.
Säännöt käsitellään niiden listausjärjestyksessä OpenPGP-sääntömuokkaimessa. Jos säännössä on annettu vastaanottajan OpenPGP-avaintunnus ja osoite täsmää vastaanottajan osoitteeseen, muita viestin kanssa täsmääviä sääntöjä ei enää käsitellä.
Lisää ohjeita Enigmailin vastaanottajakohtaisten asetusten ohjesivuilta
enigmail/lang/fi/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0017775 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/fi/help/messenger.html 0000664 0000000 0000000 00000006760 12667016244 0020011 0 ustar 00root root 0000000 0000000Kun saat viestin, joka on allekirjoitettu sinulta puuttuvalla avaimella, ja jos sinulla ei ole keyserver-options auto-key-retrieve asetusta gpg.conf-tiedostossa (eli että kaikki tuntemattomat avaimet yritetään hakea avainpalvelimelta), Enigmail näyttää viestiotsakkeissa allekirjoituskuvakkeen, jossa on kysymysmerkki ja tekstirivin, jossa lukee Osa viestistä allekirjoitettu. Napsauta allekirjoituskuvaketta saadaksesi lisätietoja.
Sama allekirjoituskuvake voi näkyä vaikka keyserver-options auto-key-retrieve olisikin asetettu, koska haettua avainta ei ehkä löydy oletusavainpalvelimelta.
Napsauttamalla allekirjoituskuvaketta, jossa on kysymysmerkki, avautuu ikkuna, joka ilmoittaa, että avainta ei löydy avainrenkaastasi. Sulkemalla tämän ikkunan OK:ta napsauttamalla avautuu ikkuna, josta voit valita avainpalvelimen, jolta julkista avainta tulisi hakea.
Voit muokata valittavissa olevia avainpalvelimia Enigmailin asetuksista: Enigmail -> Asetukset -> Yleiset-välilehti, ja muokkaamalla pilkulla erotettuja avainpalvelinten osoitteita Avainpalvelimet:-kentässä. Oletusavainpalvelin on listassa ensimmäisenä.
Lisää ohjeita Enigmailin ohjesivuilta
enigmail/lang/fi/help/rulesEditor.html 0000664 0000000 0000000 00000005613 12667016244 0020316 0 ustar 00root root 0000000 0000000Sääntömuokkaimessa voit muokata vastaanottajakohtaisia lähetysasetuksia. Voit määrätä, missä PGP/MIME-muodossa viesti lähetetään, mitä avainta käytetään ja allekirjoitetaanko tai salataanko se. Jokainen sääntö muodostuu viidestä kentästä ja on kirjoitettu yhdelle riville:
Säännöt käsitellään niiden listausjärjestyksessä. Jos säännössä on annettu vastaanottajan OpenPGP-avaintunnus ja osoite täsmää vastaanottajan osoitteeseen, muita viestin kanssa täsmääviä sääntöjä ei enää käsitellä.
Huom.: Sääntömuokkain ei ole vielä valmis. Monimutkaisempia sääntöjä on mahdollista kirjoittaa muokkaamalla sääntötiedostoa käsin (näin muokattuihin sääntöihin ei pitäisi enää koskea sääntömuokkaimella). Tarkempia ohjeita sääntötiedoston muokkaamisesta Enigmailin kotisivulta.
Lisää ohjeita Enigmailin ohjesivuilta
enigmail/lang/fi/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020456 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Si l'option Afficher une sélection si nécessaire est définie dans Préférences -> onglet Sélection clef, une liste de clefs apparaitra s'il y a dans le message des adresses de destination pour lesquelles vous n'avez pas de clef publique.
Si l'option Ne jamais afficher le dialogue de sélection de clef est définie dans Préférences -> onglet Sélection clef et qu'il y a dans le message des adresses de destination pour lesquelles vous n'avez pas de clef publique, le message sera envoyé non chiffré.
Si vous savez que le destinataire peut lire les messages utilisant le format PGP/MIME, il est conseillé de l'utiliser.
Cette fonctionnalité est dépendante du réglage dans Préférences -> onglet PGP/MIME qui doit être Utiliser PGP/MIME si possible ou Toujours utiliser PGP/MIME.
De l'aide supplémentaire est disponible sur la page Web d'Enigmail
enigmail/lang/fr/help/editRcptRule.html 0000664 0000000 0000000 00000013474 12667016244 0020440 0 ustar 00root root 0000000 0000000Avec l'éditeur de règles, il est possible de définir les paramètres par défaut par destinataire concernant l'activation du chiffrement, de la signature, de PGP/MIME et de choisir quelle(s) clef(s) utiliser. Dans cette boite de dialogue, vous pouvez spécifier les règles pour un destinataire unique ou pour un groupe de destinataires ayant des attributs très proches.
Les règles sont appliquées dans l'ordre d'affichage de la liste de l'éditeur de règles OpenPGP. Dès lors qu'une règle correspond à un destinataire et contient un identifiant de clef OpenPGP, non seulement l'identifiant de clef spécifié est utilisé, mais le destinataire n'est plus pris en compte dans le traitement des règles suivantes.
De l'aide supplémentaire est disponible sur la page des réglages par destinataire d'Enigmail
enigmail/lang/fr/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020006 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/fr/help/messenger.html 0000664 0000000 0000000 00000010525 12667016244 0020014 0 ustar 00root root 0000000 0000000Si vous n'avez pas l'option keyserver-options auto-key-retrieve définie dans votre fichier gpg.conf et que vous lisez un message signé ou chiffré, vous verrez une icône de Stylo comportant un point d'interrogation dans la zone d'affichage des en-têtes, la ligne d'état Enigmail affichera Partie du message signée ; cliquez sur l'icône « stylo » pour plus de détails. De plus le message dans le panneau de message affichera tous les blocs de message OpenPGP et le bloc de signature.
Il est également possible d'observer ce comportement même si vous l'option keyserver-options auto-key-retrieve est bien définie dans votre fichier gpg.conf mais que la clef OpenPGP n'est pas disponible sur le serveur de clefs par défaut.
En cliquant sur l'icône Stylo et point d'interrogation apparaitra une fenêtre vous avertissant que la clef n'est pas disponible dans votre trousseau de clefs. Fermer la fenêtre par OK ouvrira une autre fenêtre contenant une liste de serveurs de clefs que vous pouvez sélectionner afin de télécharger la clef publique de l'expéditeur.
Pour configurer la liste des serveurs de clefs que vous désirez utiliser, allez dans Enigmail -> Préférences -> onglet Général et saisissez les adresses des serveurs de clefs dans la zone Serveur(s) de clefs : séparées par des virgules. Le premier serveur de la liste sera utilisé comme serveur par défaut.
De l'aide supplémentaire est disponible sur la page web d'Enigmail
enigmail/lang/fr/help/rulesEditor.html 0000664 0000000 0000000 00000006713 12667016244 0020331 0 ustar 00root root 0000000 0000000Dans l'éditeur de règles, vous pouvez spécifier les paramètres par défaut par destinataire, concernant l'activation du chiffrement, de la signature, de PGP/MIME et de choisir quelle(s) clef(s) utiliser. Chaque règle consiste en 5 champs et est représentée sur une seule ligne :
Les règles sont appliquées dans l'ordre d'affichage de la liste. Dès lors qu'une règle correspond à un destinataire et contient un identifiant de clef OpenPGP, non seulement l'identifiant de clef spécifié est utilisé, mais le destinataire n'est plus pris en compte dans le traitement des règles suivantes.
Note : l'éditeur de règles n'est pas encore terminé. Il est possible d'écrire des règles plus avancées en modifiant directement le fichier de règles (ces règles ne devront alors plus être modifiées dans l'éditeur de règles). Des informations complémentaires pour modifier directement le fichier sont disponibles sur le site Web d'Enigmail
De l'aide supplémentaire est disponible sur la page Web d'Enigmail
enigmail/lang/fr/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020467 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/gd/help/editRcptRule.html 0000664 0000000 0000000 00000011603 12667016244 0020413 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the Per-Recipient Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/gd/help/help.html 0000664 0000000 0000000 00000010467 12667016244 0016744 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
If you have questions or comments about enigmail, please send a message to the Enigmail mailing list
Enigmail is open source and licensed under the Mozilla Public License and the GNU General Public License
enigmail/lang/gd/help/initError.html 0000664 0000000 0000000 00000004546 12667016244 0017772 0 ustar 00root root 0000000 0000000There are several reasons why initializing Enigmail does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for Enigmail to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 Enigmail > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/gd/help/messenger.html 0000664 0000000 0000000 00000010141 12667016244 0017771 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/gd/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020305 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/gd/help/sendingPrefs.html 0000664 0000000 0000000 00000004757 12667016244 0020450 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Se Mostrar selección cando sexa necesario está definido na pestana de Preferencias -> Selección de chaves, mostrarase unha listaxe de chaves se hai algún enderezo na lista de destinatarios/as da mensaxe para os/as que non ten chave pública.
Se a opción de non mostrar nunca o diálogo de selección de chaves OpenPGP está activado na pestana Preferencias -> Selección de chaves, e hai enderezos na lista de destinatarios/as para os que non ten a chave pública, a mensaxe enviaras sen cifrar.
Se sabe que o(s) destinatario(s) ou destinataria(s) poden ler correo utilizando o formato PGP/MIME, debería utilizalo.
Esta característica depende da configuración na pestana Preferencias -> PGP/MIME sendo a opción Permitir o uso de PGP/MIME ou Usar sempre PGP/MIME.
Máis axuda dispoñíbel na páxina web de Axuda de Enigmail
enigmail/lang/gl/help/editRcptRule.html 0000664 0000000 0000000 00000013140 12667016244 0020421 0 ustar 00root root 0000000 0000000No Editor de regras, pode especificar configuracións predeterminadas por destinatario/a para a activación de cifrado, sinatura e PGP/MIME, e definir que chave(s) OpenPGP utilizar. Neste diálogo, pode especificar as regras para un único ou unha única destinataria, e para un grupo de destinatarios/as con atributos mois similares.
As regras son procesadas no orde mostrado na lista no Editor de regras OpenPGP. Cando unha regras coincide con un destinatario e contén un ID de chave OpenPGP, ademais de utilizar o ID de chave especificado, o destinatario non se utiliza para procesar máis regras.
Pode atopar máis información de axuda dispoñíbel na páxina de configuracións por-destinatario/a de Enigmail
enigmail/lang/gl/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020001 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/gl/help/messenger.html 0000664 0000000 0000000 00000011006 12667016244 0020002 0 ustar 00root root 0000000 0000000Se non ten definido keyserver-options auto-key-retrieve no seu ficheiro gpg.conf e quere ler unha mensaxe asinada ou cifrada verá unha icona con un lápis na área da cabeceira con un símbolo de interrogación enriba, a liña de estado de Enigmail na cabeceira mostrará a mensaxe Parte da mensaxe asinada; prema na icona do lápis para máis detalles e a mensaxe no panel da mensaxe mostrará todos os bloques de sinaturas e indicadores de bloques de mensaxe OpenPGP.
Tamén pode ver isto se ten definido keyserver-options auto-key-retrieve no seu ficheiro gpg.conf e a chave OpenPGP non está dispoñíbel no seu sevidor de chaves.
Premendo na icona do lapis e símbolo de interrogación aparecerá unha ventá advertindo que a chave non está dispoñíbel no seu anel de chaves. Premendo en OK aparecerá outra ventá con unha lista de servidores de chaves dos cales pode seleccionar desde onde descargar a chave pública da persoa que lle enviou o correo.
Para configurar a lista de servidores de chaves que quere usar, vaia á pestana Enigmail -> Preferencias -> Básico e introduza os enderezos dos servidores de chaves na caixa Servidor(es) de chaves: separados por comas. O primeiro servidor da lista será o que se utilice como servidor de chaves predeterminado.
Pode consultar máis información na páxina web de axuda de Enigmail
enigmail/lang/gl/help/rulesEditor.html 0000664 0000000 0000000 00000006526 12667016244 0020326 0 ustar 00root root 0000000 0000000No Editor de regras, pode especificar as opcións predeterminadas por destinatario/a para activar cifrado, sinatura e PGP/MIME, e definir que chave(s) OpenPGP utilizar. Cada regra consiste en 5 campos e está representada por unha soa liña:
As regras procésanse no orde que se mostra na lista. Cando unha regra coincide co/a destinatario/a e contén un ID de chave OpenPGP, ademais de usar o ID de chave especificado, o/a destinatario/a non se terá en conta ao procesar máis regras.
Nota: O editor de regras aínda non está completo. É posíbel escribir regras máis avanzadas editando directamente o ficheiro de regras (estas regras non poderás ser editadas despois no editor de regras) Máis información sobre como editar directamente o ficheiro está dispoñíbel na páxina web de Enigmail
Pode atopar máis información de axuda na páxina web de Axuda de Enigmail
enigmail/lang/gl/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020462 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/hr/help/editRcptRule.html 0000664 0000000 0000000 00000011603 12667016244 0020432 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the Per-Recipient Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/hr/help/help.html 0000664 0000000 0000000 00000010467 12667016244 0016763 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
If you have questions or comments about enigmail, please send a message to the Enigmail mailing list
Enigmail is open source and licensed under the Mozilla Public License and the GNU General Public License
enigmail/lang/hr/help/initError.html 0000664 0000000 0000000 00000004546 12667016244 0020011 0 ustar 00root root 0000000 0000000There are several reasons why initializing Enigmail does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for Enigmail to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 Enigmail > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/hr/help/messenger.html 0000664 0000000 0000000 00000010141 12667016244 0020010 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/hr/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020324 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/hr/help/sendingPrefs.html 0000664 0000000 0000000 00000004757 12667016244 0020467 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/hu/help/editRcptRule.html 0000664 0000000 0000000 00000011603 12667016244 0020435 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the Per-Recipient Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/hu/help/help.html 0000664 0000000 0000000 00000010467 12667016244 0016766 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
If you have questions or comments about enigmail, please send a message to the Enigmail mailing list
Enigmail is open source and licensed under the Mozilla Public License and the GNU General Public License
enigmail/lang/hu/help/initError.html 0000664 0000000 0000000 00000004546 12667016244 0020014 0 ustar 00root root 0000000 0000000There are several reasons why initializing Enigmail does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for Enigmail to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 Enigmail > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/hu/help/messenger.html 0000664 0000000 0000000 00000010141 12667016244 0020013 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/hu/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020327 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/hu/help/sendingPrefs.html 0000664 0000000 0000000 00000004757 12667016244 0020472 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Se in Impostazioni -> Scelta della chiave è stato impostato Mostra la finestra di selezione solo quando è necessario, e tra i destinatari del messaggio figurano indirizzi a cui non corrisponde nessuna delle chiavi pubbliche in tuo possesso, al momento dell'invio verrà mostrata una lista di chiavi tra cui scegliere.
Se in Impostazioni -> Scelta della chiave è stato impostato Non mostrare mai la finestra di selezione delle chiavi OpenPGP, e tra i destinatari del messaggio figurano indirizzi a cui non corrisponde nessuna delle chiavi pubbliche in tuo possesso, il messaggio sarà inviato come testo in chiaro, senza venire cifrato.
Se sai che i destinatari sono in grado di ricevere messaggi in formato PGP/MIME, allora faresti meglio ad usarlo.
La possibilità di attivare questa funzione dipende dall'avere impostato o meno Consenti l'uso di PGP/MIME, o Usa sempre PGP/MIME, in Impostazioni -> PGP/MIME.
Ulteriore aiuto è disponibile sul sito web di Enigmail
enigmail/lang/it/help/editRcptRule.html 0000664 0000000 0000000 00000013402 12667016244 0020434 0 ustar 00root root 0000000 0000000Nell'editor delle regole puoi specificare le impostazioni predefinite per ogni destinatario per abilitare la cifratura, la firma, il formato PGP/MIME e per definire quali chiavi OpenPGP usare. In questa finestra di dialogo, puoi specificare le regole per un singolo destinatario o per un gruppo di destinatari con caratteristiche simili.
Le regole sono elaborate nell'ordine in cui appaiono nella lista dell'Editor delle regole OpenPGP. Se una regola è applicabile a un destinatario e contiene un ID chiave OpenPGP, il destinatario, oltre a usare l'ID specificato, sarà ignorato nell'elaborazione delle altre regole.
Ulteriore aiuto è disponibile sulla pagina web di Enigmail sulle regole per singolo destinatario
enigmail/lang/it/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020013 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/it/help/messenger.html 0000664 0000000 0000000 00000010100 12667016244 0020006 0 ustar 00root root 0000000 0000000Se non hai impostato keyserver-options auto-key-retrieve nel file gpg.conf file e visualizzi un messaggio firmato e/o cifrato, vedrai una icona Penna tra le intestazioni del messaggio con un Punto interrogativo su di essa, la riga di stato di Enigmail mostrerà la scritta Parte del messaggio firmata; premi sull'icona della penna per i dettagli e il messaggio nella finestra mostrerà tutte le intestazioni OpenPGP e la firma in calce.
Puoi vedere questo messaggio anche se hai impostato keyserver-options auto-key-retrieve nel file gpg.conf e la chiave OpenPGP richiesta non è disponibile sul server della chiavi predefinito.
Premendo sull'icona Penna e punto interrogativo apparirà una finestra che avverte che la chiave pubblica richiesta non è disponibile nel tuo portachiavi. Premendo su OK apparirà un'altra finestra con una lista di server di chiavi da cui potrai scegliere di scaricare la chiave pubblica del mittente.
Per configurare la lista dei server di chiavi che vuoi usare, vai su Enigmail -> Impostazioni -> Generali e inserisci gli indirizzi dei server nella riga Keyserver:, separati da una virgola. Il primo server sarà considerato il predefinito.
Ulteriore aiuto è disponibile sul sito web di Enigmail
enigmail/lang/it/help/rulesEditor.html 0000664 0000000 0000000 00000006434 12667016244 0020336 0 ustar 00root root 0000000 0000000Nell'Editor delle regole, puoi specificare le impostazioni predefinite per ogni destinatario sull'abilitazione della cifratura, della firma del formato PGP/MIME, e sulla scelta della chiave OpenPGP da usare. Ogni regole è composta da 5 campi ed è rappresentata su una singola linea:
Le regole sono elaborate nell'ordine in cui appaiono nella lista. Se una regola è applicabile a un destinatario e contiene un ID chiave OpenPGP, il destinatario, oltre a usare l'ID specificato, sarà ignorato nell'elaborazione delle altre regole.
Nota: L'editor delle regole non è ancora completo. Regole più avanzate possono essere create modificando direttamente il file delle regole (tali regole non dovranno essere più modificate con l'editor delle regole). Ulteriori informazioni sulla modifica diretta del file delle regole sono disponibili sulla home page di Enigmail.
Ulteriore aiuto è disponibile sul sito web di Enigmail
enigmail/lang/it/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020474 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
æ›´ãªã‚‹ãƒ˜ãƒ«ãƒ—ã¯ä»¥ä¸‹ã®ã‚µã‚¤ãƒˆã§åˆ©ç”¨ã§ãã¾ã™ (英語): Enigmail Help web page
enigmail/lang/ja/help/editRcptRule.html 0000664 0000000 0000000 00000012735 12667016244 0020422 0 ustar 00root root 0000000 0000000å—å–人ã”ã¨ã®è¨å®šã®ç·¨é›†ã§ã€å—å–人ã”ã¨ã«ç½²åã€æš—å·åŒ–ã€PGP/MIME ã®å¯å¦ãŠã‚ˆã³ä½¿ç”¨ã™ã‚‹ OpenPGP éµã‚’指定ã§ãã¾ã™ã€‚ã“ã®ãƒ€ã‚¤ã‚¢ãƒã‚°ã§ 1 人ã®å—å–人ã€ãŠã‚ˆã³åŒæ§˜ãªæ–¹æ³•ã§ã‚°ãƒ«ãƒ¼ãƒ—ã«å¯¾ã—ã¦è¨å®šã§ãã¾ã™ã€‚
ã“れらã®ãƒ«ãƒ¼ãƒ«ã¯ å—å–人ã”ã¨ã®è¨å®š ã«è¡¨ç¤ºã•れã¦ã„ã‚‹é †ã«å‡¦ç†ã•れã¾ã™ã€‚ルールã«å—å–人ãŒãƒžãƒƒãƒã—ã€OpenPGP éµã® ID ã‚’å«ã¿ã€åŠ ãˆã¦è¨å®šã•れãŸéµ ID を使用ã—ã¦ã„ã‚‹å ´åˆã«ã¯ã€ãã®å—å–人ã«é–¢ã—ã¦ã¯ãれ以上ã®ãƒ«ãƒ¼ãƒ«ã¯è€ƒæ…®ã•れã¾ã›ã‚“。
æ›´ãªã‚‹ãƒ˜ãƒ«ãƒ—ã¯ä»¥ä¸‹ã®ã‚µã‚¤ãƒˆã§åˆ©ç”¨ã§ãã¾ã™ (英語): Enigmail Per-Recipient Settings page
enigmail/lang/ja/help/initError.html 0000664 0000000 0000000 00000005632 12667016244 0017767 0 ustar 00root root 0000000 0000000Enigmail ã®åˆæœŸåŒ–ãŒæˆåŠŸã—ãªã„ã“ã¨ã«ã¯ã„ãã¤ã‹ã®åŽŸå› ãŒã‚りã¾ã™ã€‚よãã‚ã‚‹åŽŸå› ã¯ä»¥ä¸‹ã®ã‚ˆã†ãªã‚‚ã®ã§ã™ã€‚ æ›´ãªã‚‹ãƒ˜ãƒ«ãƒ—ã¯ä»¥ä¸‹ã®ã‚µã‚¤ãƒˆã§åˆ©ç”¨ã§ãã¾ã™ (英語): Enigmail Help web page
Enigmail を利用ã™ã‚‹ãŸã‚ã«ã¯ã€GnuPG ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•れã¦ã„ã‚‹å¿…è¦ãŒã‚りã¾ã™ã€‚ GnuPG ãŒè¦‹ã¤ã‹ã‚‰ãªã„å ´åˆã«ã¯ã€ã¾ãšã¯ã˜ã‚ã« GnuPG ã®å®Ÿè¡Œãƒ•ァイルã§ã‚ã‚‹ gpg.exe (Windows ã®å ´åˆã€‚ä»–ã®ãƒ—ラットフォームã®å ´åˆã«ã¯ gpg) ãŒãŠä½¿ã„ã®ã‚³ãƒ³ãƒ”ュータã«ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•れã¦ã„ã‚‹ã“ã¨ã‚’確èªã—ã¦ãã ã•ã„。 GnuPG ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«ã‚‚ã‹ã‹ã‚ら㚠Enigmail ãŒãれを検出ã§ããªã„å ´åˆã«ã¯ã€GnuPG ã®å®Ÿè¡Œãƒ•ァイルã¸ã®ãƒ‘スを手動ã§è¨å®šã—ã¦ãã ã•ã„ (Enigmail > è¨å®š)
Enigmail ã¯ã€ãŠä½¿ã„ã® Thunderbird ã‚„ SeaMonkey ãŒãƒ“ルドã•れãŸç’°å¢ƒã¨åŒã˜ç’°å¢ƒã§ãƒ“ルドã•れãŸã‚‚ã®ã—ã‹å‹•作ã—ã¾ã›ã‚“。ã™ãªã‚ã¡ã€Enigmail ã®å…¬å¼ãƒªãƒªãƒ¼ã‚¹ã¯ mozilla.org ã‹ã‚‰ãƒªãƒªãƒ¼ã‚¹ã•れる Thunderbird ã‚„ SeaMonkey ã§ã—ã‹å‹•作ã—ã¾ã›ã‚“。
Linux ディストリビューションãªã©ã€mozilla.org 以外ã‹ã‚‰ãƒªãƒªãƒ¼ã‚¹ã•れる Thunderbird ã‚„ SeaMonkey ã‚’ãŠä½¿ã„ã®å ´åˆã‚„ã”自分ã§ãƒ“ルドã—㟠Thunderbird ã‚„ SeaMonkey ã‚’ãŠä½¿ã„ã®å ´åˆã«ã¯ã€åŒã˜æä¾›å…ƒã‹ã‚‰ãƒªãƒªãƒ¼ã‚¹ã•れる Enigmail を利用ã™ã‚‹ã‹ã€ã”自分ã§ãƒ“ルドã™ã‚‹å¿…è¦ãŒã‚りã¾ã™ã€‚Enigmail ã®ãƒ“ルドã«ã¤ã„ã¦ã¯ã€Source Code section ã‚’å‚ç…§ã—ã¦ãã ã•ã„。ã“ã®ã‚ˆã†ãªãƒ“ルド環境ã®é•ã„ã«èµ·å› ã™ã‚‹å•題を Enigmail ã®ãƒã‚°ã¨ã—ã¦å ±å‘Šã—ãªã„ã§ãã ã•ã„。
æ›´ãªã‚‹ãƒ˜ãƒ«ãƒ—ã¯ä»¥ä¸‹ã®ã‚µã‚¤ãƒˆã§åˆ©ç”¨ã§ãã¾ã™ (英語): Enigmail Support Web Site.
enigmail/lang/ja/help/messenger.html 0000664 0000000 0000000 00000011625 12667016244 0020001 0 ustar 00root root 0000000 0000000ã‚‚ã—ã‚ãªãŸãŒ keyserver-options auto-key-retrieve ã‚’ gpg.conf ã«è¨å®šã—ã¦ã„ãªã„状態ã§ç½²åã‹æš—å·åŒ–ã•れã¦ã„るメッセージをèªã‚€ã¨ã€å°ç’ã®ã‚¢ã‚¤ã‚³ãƒ³ãŒï¼Ÿã¨å…±ã«è¡¨ç¤ºã•れã€ãƒ˜ãƒƒãƒ€ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ãƒ©ã‚¤ãƒ³ã« メッセージã®ä¸€éƒ¨ãŒç½²åã•れã¦ã„ã¾ã™; å°ç’ã¾ãŸã¯éµã®ã‚¢ã‚¤ã‚³ãƒ³ã‚’クリックã—ã¦ãã ã•ã„ ã¨è¡¨ç¤ºã•れã€ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒšã‚¤ãƒ³ã«ã¯ OpenPGP メッセージブãƒãƒƒã‚¯ã¨ç½²åブãƒãƒƒã‚¯ãŒè¡¨ç¤ºã•れã¾ã™ã€‚
keyserver-options auto-key-retrieve ㌠gpg.conf ã«è¨å®šã•れã¦ã„ã‚‹å ´åˆã§ã‚‚ã€OpenPGP éµãŒãƒ‡ãƒ•ォルトéµã‚µãƒ¼ãƒã«ç„¡ã„å ´åˆã¯åŒæ§˜ã®ã‚¢ã‚¤ã‚³ãƒ³ãŒè¡¨ç¤ºã•れã¾ã™ã€‚
å°ç’ã¨ï¼Ÿ ã®ã‚¢ã‚¤ã‚³ãƒ³ã‚’クリックã™ã‚‹ã¨ã€è©²å½“ã™ã‚‹å…¬é–‹éµã‚’æŒã£ã¦ã„ãªã„æ—¨ãŒè¡¨ç¤ºã•れã¾ã™ã€‚OK をクリックã™ã‚‹ã¨ã€éµã‚µãƒ¼ãƒã®ãƒªã‚¹ãƒˆãŒè¡¨ç¤ºã•れãŸåˆ¥ã‚¦ã‚£ãƒ³ãƒ‰ã‚¦ãŒé–‹ãメールã®é€ä¿¡è€…ã®å…¬é–‹éµã‚’ダウンãƒãƒ¼ãƒ‰ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚
ã‚ãªãŸãŒä½¿ã„ãŸã„公開éµã‚µãƒ¼ãƒã®ãƒªã‚¹ãƒˆã‚’編集ã™ã‚‹ã«ã¯ã€Enigmail -> è¨å®š -> éµã‚µãƒ¼ãƒ ã‚¿ãƒ–ã‚’é¸æŠžã—ã€å…¬é–‹éµã‚µãƒ¼ãƒ: ã®æ¬„ã«ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’カンマ区切りã§å…¥åŠ›ã—ã¦ãã ã•ã„。リストã®ä¸€ç•ªä¸Šã®ã‚µãƒ¼ãƒãŒæ—¢å®šã§ä½¿ç”¨ã•れã¾ã™ã€‚
æ›´ãªã‚‹ãƒ˜ãƒ«ãƒ—ã¯ä»¥ä¸‹ã®ã‚µã‚¤ãƒˆã§åˆ©ç”¨ã§ãã¾ã™ (英語): Enigmail Help web page
enigmail/lang/ja/help/rulesEditor.html 0000664 0000000 0000000 00000006450 12667016244 0020312 0 ustar 00root root 0000000 0000000å—å–人ã”ã¨ã®è¨å®šã§ã¯ã€å—å–人ã”ã¨ã«æš—å·åŒ–ã€ç½²åã€PGP/MIME ã«é–¢ã™ã‚‹æ—¢å®šã®è¨å®šã¨ã€ã©ã® OpenPGP éµã‚’用ã„ã‚‹ã‹ã‚’è¨å®šã§ãã¾ã™ã€‚å„ルール㯠5 ã¤ã®ãƒ•ィールドã‹ã‚‰ãªã‚Šã€1 ã¤ã®æ–¹é‡ã‚’ã‚らã‚ã—ã¾ã™ã€‚:
ã“ã®ç½²åã«é–¢ã™ã‚‹è¨å®šã¯ãƒžãƒƒãƒã™ã‚‹ã™ã¹ã¦ã®ãƒ«ãƒ¼ãƒ«ã«å¯¾ã—ã¦é©ç”¨ã•れã¾ã™ã€‚ã‚‚ã—ç½²åã‚’ã—ãªã„ルール㌠1 ã¤ã§ã‚‚ã‚れã°ã€ä»–ã®ç½²åã‚’ã™ã‚‹ãƒ«ãƒ¼ãƒ«ãŒãƒžãƒƒãƒã—ã¦ã‚‚ã€ç½²åã¯ã•れã¾ã›ã‚“。
ルールã¯è¡¨ç¤ºã•れã¦ã„ã‚‹é †ã«å‡¦ç†ã•れã¾ã™ã€‚ã‚るルールãŒå—å–人ã«ã‚ã¦ã¯ã¾ã‚Šã€OpenPGP éµ IDã€ã•らã«ç‰¹å®šã•れãŸéµ ID ã‚’å«ã‚“ã§ã„ã‚‹å ´åˆã€ãã®å—å–人ã«ã¤ã„ã¦ã¯ã€ä»–ã®ãƒ«ãƒ¼ãƒ«ã¯è€ƒæ…®ã•れã¾ã›ã‚“。
注æ„: ルールエディタã¯ã¾ã 完æˆã—ã¦ã„ã¾ã›ã‚“。ルールファイルを直接編集ã™ã‚‹ã“ã¨ã§ã€ã‚ˆã‚Šè©³ç´°ãªãƒ«ãƒ¼ãƒ«ã‚’è¨å®šã™ã‚‹ã“ã¨ãŒå¯èƒ½ã§ã™ (ã“れらã®ãƒ«ãƒ¼ãƒ«ã¯ãƒ«ãƒ¼ãƒ«ã‚¨ãƒ‡ã‚£ã‚¿ã§ç·¨é›†ã§ããªã‹ã£ãŸã‚‚ã®ã§ã™)。直接ファイルを編集ã™ã‚‹ã“ã¨ã«ã¤ã„ã¦ã® è©³ç´°ãªæƒ…å ± (英語) 㯠Enigmail Homepage ã«ã‚りã¾ã™ã€‚
æ›´ãªã‚‹ãƒ˜ãƒ«ãƒ—ã¯ä»¥ä¸‹ã®ã‚µã‚¤ãƒˆã§åˆ©ç”¨ã§ãã¾ã™ (英語): Enigmail Help web page
enigmail/lang/ja/help/sendingPrefs.html 0000664 0000000 0000000 00000005754 12667016244 0020446 0 ustar 00root root 0000000 0000000é€ä¿¡è¨å®šã«ãŠã„ã¦ã€æš—å·åŒ–ã«é–¢ã™ã‚‹ä¸€èˆ¬çš„ãªãƒ¢ãƒ‡ãƒ«ã¨ãƒ«ãƒ¼ãƒ«ã‚’é¸æŠžã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚
å˜ã«æš—å·åŒ–ã™ã‚‹ã“ã¨ã§ãƒ—ライãƒã‚·ãƒ¼ã‚’強化ã—ãŸã„ã®ã§ã‚れã°ã€ã“ã®è¨å®šãŒé©ã—ã¦ã„ã¾ã™ã€‚
ã“れã¯ã€è‘‰æ›¸ã§ã¯ãªãå°æ›¸ã‚’用ã„ã‚‹ã“ã¨ã¨é¡žä¼¼ã—ã¦ã„ã¾ã™ã€‚葉書ã¨ã¯ç•°ãªã‚Šã€å°æ›¸ã§ã‚れã°é…é€ã®éŽç¨‹ã§ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å†…容ãŒç¬¬ä¸‰è€…ã®ç›®ã«è§¦ã‚Œã‚‹ã“ã¨ã¯ã‚りã¾ã›ã‚“。
ã—ã‹ã—ãªãŒã‚‰å°æ›¸ã‚’用ã„ãŸå ´åˆã¨åŒæ§˜ã«ã€ã“ã®è¨å®šã§ã¯é…é€éŽç¨‹ã§ç¬¬ä¸‰è€…ã«ã‚ˆã£ã¦ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã®å†…容ãŒè§£èªã•れるå¯èƒ½æ€§ã‚’完全ã«å¦å®šã™ã‚‹ã“ã¨ã¯ã§ãã¾ã›ã‚“ (ãã®ãŸã‚ã«ç‰¹åˆ¥ãªæŠ€è¡“ã‚’å¿…è¦ã¨ã™ã‚‹ã¨ã—ã¦ã‚‚)。
具体的ãªãƒªã‚¹ã‚¯ã¨ã—ã¦ã¯ã€æ£è¦ã®å—å–人を装ã£ãŸç¬¬ä¸‰è€…ã«ã‚ˆã‚‹ã€Œå½ç‰©ã®éµã€ã«å¯¾ã—ã¦æš—å·åŒ–ã—ã¦ã—ã¾ã†ã“ã¨ãŒæŒ™ã’られã¾ã™ã€‚ã“れをé¿ã‘ã‚‹ãŸã‚ã«ã¯ã€PGP ã®ä¿¡é ¼ãƒ¢ãƒ‡ãƒ«ã‚’利用ã™ã‚‹ã‹ (下記å‚ç…§)ã€å…¬é–‹éµã®ãƒ•ã‚£ãƒ³ã‚¬ãƒ¼ãƒ—ãƒªãƒ³ãƒˆãŒæ£ã—ã„ã‹å¸¸ã«ç¢ºèªã™ã‚‹å¿…è¦ãŒã‚りã¾ã™ã€‚
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/ko/help/editRcptRule.html 0000664 0000000 0000000 00000014007 12667016244 0020433 0 ustar 00root root 0000000 0000000규칙 편집기ì—서는 받는 사람별로 암호화, 서명 ê·¸ë¦¬ê³ PGP/MIME í™œì„±í™”ì— ëŒ€í•œ 기본 ë°©ì¹¨ì„ ì •í• ìˆ˜ 있으며, ì–´ë–¤ OpenPGP 키를 ì‚¬ìš©í• ì§€ë¥¼ ì§€ì •í• ìˆ˜ 있습니다. ì´ ëŒ€í™”ìƒìžì—서는 한 ì‚¬ëžŒì˜ ë°›ëŠ” 사람 ê·¸ë¦¬ê³ ë§¤ìš° ìœ ì‚¬í•œ 방법으로 받는 사람 ê·¸ë£¹ì— ëŒ€í•˜ì—¬ ê·œì¹™ì„ ì§€ì •í• ìˆ˜ 있습니다.
받는 ì‚¬ëžŒì˜ ì „ìž ë©”ì¼ ì£¼ì†Œê°€ (ì´ë¦„ì„ ì œì™¸í•˜ê³ , 예를 들어, somebody@email.domainê³¼ ê°™ì´ ì£¼ì†Œë§Œ) 들어갑니다. 여러 ê°œì˜ ì „ìž ë©”ì¼ ì£¼ì†Œë¥¼ 공백 문ìžë¡œ 구분하여 ì§€ì •í• ìˆ˜ 있습니다. 주소는 ë„ë©”ì¸ ë§Œìœ¼ë¡œë„ êµ¬ì„±í• ìˆ˜ 있습니다. ì´ë ‡ê²Œ 하면 ë„ë©”ì¸ì— ì†í•˜ëŠ” ì–´ë–¤ ì£¼ì†Œì™€ë„ ì¼ì¹˜í•©ë‹ˆë‹¤. 예를 들어, @email.domain ì€ body@email.domain, somebody@email.domain, anybody@emaildomain, 등과 ì¼ì¹˜í•˜ê²Œ ë©ë‹ˆë‹¤.
ì´ ì˜µì…˜ì€ ì „ìž ë©”ì¼ ì£¼ì†Œì˜ ëŒ€ì¡°ë²•ì„ ë³€ê²½í•©ë‹ˆë‹¤. 만약 ë‹¤ìˆ˜ì˜ ì£¼ì†Œê°€ ìž…ë ¥ë˜ë©´ ì„¤ì •ì€ ìž…ë ¥ëœ ëª¨ë‘ì— ëŒ€í•´ ì ìš©ë©ë‹ˆë‹¤. ì•„ëž˜ì˜ ì˜ˆëŠ” ìœ„ì˜ í•„ë“œì— OpenPGP 규칙으로 ìž…ë ¥ëœ body@email.domain 를 기준으로 한 예시입니다.
ì´ ê¸°ëŠ¥ì„ í™œì„±í™”í•˜ë©´ ê·œì¹™ì„ ì •ì˜í•˜ê¸´ 하지만 ë‹¤ìŒ OpenPGP í‚¤ë“¤ì„ ì‚¬ìš©: í•„ë“œì— í‚¤ ID를 ì§€ì •í•˜ì§€ ì•Šì•„ë„ ë˜ë¯€ë¡œ, ì „ìž ë©”ì¼ ì£¼ì†ŒëŠ” 메시지를 보낼 때 키를 검사하는 ìš©ë„로 사용ë©ë‹ˆë‹¤. ê·¸ë¦¬ê³ ê°™ì€ ì£¼ì†Œì— ëŒ€í•´ ì¼ì¹˜í•˜ëŠ” ê·œì¹™ì´ ê³„ì† ì ìš©ë©ë‹ˆë‹¤.
ì´ ê¸°ëŠ¥ì„ í™œì„±í™”í•˜ë©´ ì´ ê·œì¹™ì´ ì¼ì¹˜í•˜ëŠ” ì£¼ì†Œì— ëŒ€í•´ 다른 ê·œì¹™ì´ ë”는 ì ìš©ë˜ì§€ 않습니다. 다시 ë§í•´, 규칙 처리 ìž‘ì—…ì€ ë‹¤ìŒ ë°›ëŠ” 사람으로 넘어갑니다.
ì•”í˜¸í™”í•˜ëŠ”ë° ì‚¬ìš©í• ë°›ëŠ” 사람 키를 ì„ íƒí•˜ë ¤ë©´ 키 ì„ íƒ (S)... ë²„íŠ¼ì„ ì‚¬ìš©í•©ë‹ˆë‹¤. 바로 ìœ„ì˜ ë™ìž‘ê³¼ 마찬가지로 것처럼, ì¼ì¹˜ë˜ëŠ” ì£¼ì†Œì— ëŒ€í•´ ì´í›„ 다른 ê·œì¹™ì´ ì¶”ê°€ì 으로 ì ìš©ë˜ì§€ 않게ë©ë‹ˆë‹¤.
메시지 서명를 활성화 ë˜ëŠ” 비활성화 합니다. 메시지 작성 윈ë„ìš°ì—서 ì§€ì •í•œ 대로 í• ì§€, ë¬´ì‹œí•˜ê³ ì´ ê·œì¹™ì— ì„¤ì •ëœ ì •ì±…ì„ ì ìš©í• ì§€ë¥¼ ê²°ì •í•©ë‹ˆë‹¤. ì„ íƒ ê°€ëŠ¥í•œ ì •ì±…ì€ ë‹¤ìŒê³¼ 같습니다:
ì´ ì„œëª… ì„¤ì •ì€ ì¼ì¹˜í•˜ëŠ” ëª¨ë“ ê·œì¹™ì— ì ìš©ë©ë‹ˆë‹¤. 규칙들 중 하나가 서명하기를 비활성화하면, í•ìƒìœ¼ë¡œ ì„¤ì •í•´ë†“ì€ ë‹¤ë¥¸ ê·œì¹™ì´ ìžˆë”ë¼ë„, 메시지는 서명ë˜ì§€ 않습니다.
메시지 암호화를 활성화 ë˜ëŠ” 비활성화 합니다. ì œê³µí•˜ëŠ” ì •ì±…ê³¼ ê·¸ ì˜ë¯¸ëŠ” 메시지 ì„œëª…ì— ëŒ€í•œ 기본 ì •ì±…ì— ì„¤ëª…ëœ ê²ƒê³¼ 같습니다.
PGP/MIME (RFC 2156) 메시지 ì¸ì½”ë”©ì˜ ì‚¬ìš©ì—¬ë¶€ë¥¼ 활성화 ë˜ëŠ” 비활성화 합니다. PGP/MIMEê°€ 비활성화ë˜ë©´ 메시지는 "ì¸ë¼ì¸ 형ì‹"으로 ì¸ì½”딩ë©ë‹ˆë‹¤. ì œê³µí•˜ëŠ” ì •ì±…ê³¼ ê·¸ ì˜ë¯¸ëŠ” 메시지 ì„œëª…ì— ëŒ€í•œ 기본 ì •ì±…ì— ì„¤ëª…ëœ ê²ƒê³¼ 같습니다.
ê·œì¹™ë“¤ì€ OpenPGP 규칙 편집기 ë‚´ 목ë¡ì—서 í‘œì‹œëœ ìˆœì„œë¡œ 처리ë©ë‹ˆë‹¤. ì–´ë–¤ 한 ê·œì¹™ì´ ë°›ëŠ” 사람과 ì¼ì¹˜í•˜ê³ OpenPGP 키 ID를 í¬í•¨í•˜ëŠ” 경우, 추가ì 으로 키 ID를 ì‚¬ìš©í•˜ë ¤ê³ ì§€ì •í•´ë„, ì´í›„ ê·œì¹™ì„ ì²˜ë¦¬í• ë•Œ ê·¸ 받는 ì‚¬ëžŒì€ ë” ê³ ë ¤ë˜ì§€ 않습니다.
추가 ë„움ë§ì€ Enigmail 받는 사람별 ì„¤ì • 페ì´ì§€ì—서 ì–»ì„ ìˆ˜ 있습니다.
enigmail/lang/ko/help/initError.html 0000664 0000000 0000000 00000004424 12667016244 0020004 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/ko/help/messenger.html 0000664 0000000 0000000 00000011201 12667016244 0020006 0 ustar 00root root 0000000 0000000ì´ ë²„íŠ¼ì€ ì—¬ëŸ¬ê°€ì§€ ìš©ë„로 사용ë 수 있습니다: 복호화, ê²€ì¦, ë˜ëŠ” 공개키 ê°€ì ¸ì˜¤ê¸°. ì¼ë°˜ì 으로 복화화/ê²€ì¦ì€ ìžë™ìœ¼ë¡œ ì´ë¤„지지만, ì„¤ì •ì„ í†µí•´ 비활성화 í• ìˆ˜ 있습니다. 그러나 ì‹¤íŒ¨í• ê²½ìš°, Enigmail ìƒíƒœ í‘œì‹œì¤„ì— ì§§ì€ ì˜¤ë¥˜ 메시지로 나타나게 ë©ë‹ˆë‹¤. 복호화 ë²„íŠ¼ì„ ëˆ„ë¥´ë©´, GnuPG ëª…ë ¹ í–‰ì—서 ë°œìƒë˜ëŠ” ì¶œë ¥ 메시지를 í¬í•¨í•œ ë” ìžì„¸í•œ 오류 메시지를 ë³¼ 수 있습니다.
메시지 ë¨¸ë¦¬ë§ í‘œì‹œë¶€ì˜ íŒ¬ê³¼ 키 ì•„ì´ì½˜ì€ ì½ê³ 있는 메시지가 서명 ê·¸ë¦¬ê³ /ë˜ëŠ” 암호화ë˜ì—ˆëŠ”ì§€ ê·¸ë¦¬ê³ ì„œëª…ì´ ì˜¬ë°”ë¥¸ ìƒíƒœì¸ì§€ë¥¼ (예를 들어, ì„œëª…ëœ í›„ 메시지가 변형ë˜ì§€ 않았는지 등) 나타냅니다. 만약 메시지가 변형ë˜ì—ˆìœ¼ë©´ 팬 ì•„ì´ì½˜ì€ ì„œëª…ì´ ì˜¬ë°”ë¥´ì§€ ì•Šì€ ìƒíƒœìž„ì„ í‘œì‹œí•˜ê¸° 위해 깨진 팬으로 ë°”ë€ë‹ˆë‹¤. 팬ì´ë‚˜ 키 ì•„ì´ì½˜ì—서 오른쪽 ë²„íŠ¼ì„ í´ë¦í•˜ë©´ 다ìŒê³¼ ê°™ì€ ì˜µì…˜ì˜ ë©”ë‰´ê°€ 나타납니다:
만약 gpg.conf 파ì¼ì— keyserver-options auto-key-retrieve ì„¤ì •ì„ í•´ë†“ì§€ ì•Šì€ ìƒíƒœì—서 서명ë˜ê±°ë‚˜ ì•”í˜¸í™”ëœ ë©”ì‹œì§€ë¥¼ ì½ì–´ ë¨¸ë¦¬ë§ í‘œì‹œ ì˜ì—ì˜ íŒ¬ ì•„ì´ì½˜ì— 물ìŒí‘œê°€ 표시ë˜ëŠ” ê²ƒì„ ë³¼ 수 있는 경우, ë¨¸ë¦¬ë§ ì˜ì—ì˜ Enigmail ìƒíƒœ í‘œì‹œì¤„ì€ ì„œëª…ëœ ë©”ì‹œì§€ì˜ ì¼ë¶€ë¶„; 세부사í•ì„ ë³´ë ¤ë©´ 펜 ì•„ì´ì½˜ì„ í´ë¦ìœ¼ë¡œ 표시하여 사용ìžì—게 ì•Œë¦¬ê³ ë©”ì‹œì§€ 구ì—ì˜ ë©”ì‹œì§€ëŠ” ëª¨ë“ OpenPGP 메시지 ë¸”ë¡ í‘œì‹œìžì™€ 서명 블ë¡ì„ 보여줄 것 입니다.
gpg.conf 파ì¼ì— keyserver-options auto-key-retrieve ì„¤ì •ì„ í•´ë†“ì€ ìƒíƒœì—서 기본 키 ì„œë²„ì— OpenPGP 키가 없는 경우ì—ë„ ì´ë ‡ê²Œ ë˜ëŠ” ê²ƒì„ ë³¼ 수 있습니다.
팬과 물ìŒí‘œ ì•„ì´ì½˜ì„ í´ë¦í•˜ë©´ 키 ë§ì— 해당 키가 없다는 ê²ƒì„ ì•Œë ¤ì£¼ëŠ” ì°½ì´ ë‚˜íƒ€ë‚ ê²ƒìž…ë‹ˆë‹¤. 확ì¸ì„ 누르면 보낸 ì‚¬ëžŒì˜ ê³µê°œí‚¤ë¥¼ 다운로드 í• í‚¤ 서버를 ì„ íƒí• 수 있는 키 서버 ëª©ë¡ ìœˆë„ìš°ê°€ ë‚˜íƒ€ë‚ ê²ƒ 입니다.
ì‚¬ìš©í•˜ê³ ìží•˜ëŠ” 키 서버를 목ë¡ì„ ì„¤ì •í•˜ë ¤ë©´, Enigmail → ì„¤ì • → 기본 íƒìœ¼ë¡œ 가셔서 키 서버 ì§€ì •: ë°•ìŠ¤ì— ì½¤ë§ˆ(,)로 êµ¬ë¶„ëœ í‚¤ 서버 주소를 ìž…ë ¥í•´ì£¼ì‹œê¸° ë°”ëžë‹ˆë‹¤. 목ë¡ì˜ 처ìŒì— 있는 키 서버가 기본으로 사용ë©ë‹ˆë‹¤.
*.pgp, *.asc ê·¸ë¦¬ê³ *.gpg 확장ìžë¡œ ë˜ì–´ 있는 첨부 파ì¼ì€ Enigmailê°€ 특별히 ì·¨ê¸‰í• ìˆ˜ 있는 첨부파ì¼ë¡œì„œ ì¸ì‹ë©ë‹ˆë‹¤. 해당 첨부파ì¼ì— 오른쪽 í´ë¦ì„ 하면 컨í…스트 ë©”ë‰´ì— ë‘ ê°€ì§€ 특수 메뉴가 활성화 ë©ë‹ˆë‹¤: 복호화 후 열기와 복호화 후 다른 ì´ë¦„으로 ì €ìž¥. 메시지를 열거나 ì €ìž¥í•˜ê¸° ì „ì— ì²¨ë¶€íŒŒì¼ì„ Enigmailì´ ë³µí˜¸í™”í•˜ê¸°ë¥¼ ì›í•˜ëŠ” 경우, ì´ ë‘ ë©”ë‰´ë¥¼ 사용하ì‹ì‹œì˜¤. 첨부파ì¼ì´ OpenPGP 키 파ì¼ë¡œ ì¸ì‹ë˜ë©´, 사용ìžê°€ 키를 키 ë§ìœ¼ë¡œ ê°€ì ¸ì˜¤ê¸° í• ìˆ˜ 있ë„ë¡ í• ê²ƒìž…ë‹ˆë‹¤.
ì´í›„ ë„움ë§ì€ Enigmail OpenPGP ë„ì›€ë§ ì›¹ 페ì´ì§€ì—서 ì–»ì„ ìˆ˜ 있습니다.
enigmail/lang/ko/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020324 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/ko/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020471 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/lt/help/editRcptRule.html 0000664 0000000 0000000 00000011557 12667016244 0020450 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/lt/help/help.html 0000664 0000000 0000000 00000010515 12667016244 0016763 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail OpenPGP Help web page
If you have questions or comments about enigmail, please send a message to the Enigmail OpenPGP mailing list
Enigmail OpenPGP is open source and licensed under the Mozilla Public License and the GNU General Public License
enigmail/lang/lt/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020016 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/lt/help/messenger.html 0000664 0000000 0000000 00000010121 12667016244 0020014 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/lt/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020332 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/lt/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020477 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/nb-NO/help/editRcptRule.html 0000664 0000000 0000000 00000011557 12667016244 0020742 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/nb-NO/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020310 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/nb-NO/help/messenger.html 0000664 0000000 0000000 00000010121 12667016244 0020306 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/nb-NO/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020624 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/nb-NO/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020771 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Versleuteling voor alle ontvanger(s) in- of uitschakelen. De gebruiker wordt gewaarschuwd als de versleuteling mislukt.
Als Selectie tonen wanneer nodig ingesteld is in de Voorkeuren -> Sleutelselectie tab, dan zal er een lijst van sleutel getoond worden als er ontvangers in de lijst staan van wie u geen publieke sleutel hebt.
Als Toon nooit het PGP dialoogvenster voor sleutelselectie ingesteld is in de Voorkeuren -> Sleutelselectie tab, en er zijn adressen in de lijst met ontvangers van wie u geen publieke sleutel hebt, dan wordt de mail onversleuteld verstuurd.
Als u weet dat uw ontvanger mail kan lezen in het PGP/MIME formaat, dan gebruikt u dit best ook.
Deze mogelijkheid is afhankelijk van de instellingen in de Voorkeuren -> PGP/MIME tab. Deze moet ingesteld zijn op Sta het gebruik van PGP/MIME toe of Gebruik altijd PGP/MIME.
Als er een fout is bij het verzenden van de e-mail zoals wanneer de POP server de aanvraag niet accepteerd, zal Enigmail dit niet weten en het versleuteld bericht zal nog altijd getoond worden in het Opstelvenster. Bij het kiezen van dit menu-item wordt de versleuteling of ondertekening uit de mail verwijderd.
Deze optie kan ook gebruikt worden als een tijdelijke oplossing om de aangehaalde tekst in versleutelde berichten te ontcijferen bij het antwoorden. Enigmail zou het aangehaalde bericht automatisch moeten ontcijferen, maar als dat om één of andere reden mislukt, kan u dit menu-item gebruiken om het te forceren.
Verdere help kan u vinden op de Enigmail support website
enigmail/lang/nl/help/editRcptRule.html 0000664 0000000 0000000 00000012642 12667016244 0020436 0 ustar 00root root 0000000 0000000In de Regeleditor kan u standaarden opgeven om versleuteling, ondertekening en PGP/MIME te gebruiken en om te definiëren welke OpenPGP sleutel(s) er gebruikt moeten worden. In dit dialoogvenster kan u de regels voor een enkele ontvanger opgeven en voor een groep van ontvangers met sterk vergelijkbare eigenschappen.
De regels worden uitgevoerd in de volgorde waarin ze weergegeven worden in de PGP regeleditor. Wanneer een regel overeenstemt met een ontvanger en een PGP sleutel ID bevat, met daarbij nog een opgegeven sleutel ID, dan wordt de ontvanger niet meer gecontroleerd bij het uitvoeren van verdere regels.
Verdere help is beschikbaar op de Enigmail per-ontvanger instellingen pagina
enigmail/lang/nl/help/initError.html 0000664 0000000 0000000 00000005034 12667016244 0020002 0 ustar 00root root 0000000 0000000Er zijn verschillende oorzaken voor het mislukken van de OpenPGP initialisatie. De bekendsten worden hieronder beschreven; voor meer informatie kunt u de Enigmail help website bezoeken.
Voor een goede werking van OpenPGP moet de applicatie GnuPG geïnstalleerd zijn. Als GnuPG niet kan worden gevonden, moet u er eerst voor zorgen dat de applicatie gpg.exe (voor Windows; gpg voor andere platformen) op uw PC daadwerkelijk aanwezig is. Als GnuPG (gpg.exe of gpg) daadwerkelijk geïnstalleerd is, maar OpenPGP kan het toch niet vinden, moet u het pad naar GnuPG in de OpenPGP instellingen ingeven (Menu OpenPGP) > Voorkeuren).
OpenPGP werkt alleen als deze in dezelfde ontwikkelomgeving als Thunderbird of SeaMonkey gecreëerd (gecompileerd) is. U kunt de officiële Enigmail samen met officiële versies van Thunderbird of SeaMonkey downloaden van mozilla.org.
Als u Thunderbird of SeaMonkey in een andere versie/variant van een andere bron download (bv. van een Linux distributie provider), of als u de applicatie zelf gecompileerd heeft, moet u ook een versie van Enigmail gebruiken die in dezelfde ontwikelomgeving gecompileerd is. Om Enigmail zelf te compileren moet u de instructies opvolgen op de Enigmail website in Gebied Source-Code. Gelieve geen eventuele foutmeldingen (bugs) over dit probleem te maken, omdat er daarvoor geen andere oplossing is.
Verdere hulp is beschikbaar op de Enigmail support website.
enigmail/lang/nl/help/messenger.html 0000664 0000000 0000000 00000010476 12667016244 0020023 0 ustar 00root root 0000000 0000000Als u keyserver-options auto-key-retrieve niet ingesteld hebt in uw gpg.conf bestand en u leest een bericht dat ondertekend of versleuteld is, dan zal u een Pen icoon in de hoofding zien met een Vraagteken er op. De Enigmail statusregel zal zeggen Gedeelte van het bericht getekend; klik op het pen icoon voor details en het bericht in het berichtvenster zal alle OpenPGP informatie, samen met de ondertekening tonen.
U kan dit ook zien als u keyserver-options auto-key-retrieve ingesteld hebt in uw gpg.conf bestand en als de OpenPGP key niet beschikbaar is op de standaard keyserver.
Een klik op het Pen en Vraagteken icoon zal een venster tonen met het bericht dat de sleutel niet in uw sleutelbos zit. Als u dan op OK klikt, krijgt u een ander venster met een lijst met publieke keyservers waaruit u kan kiezen om de publieke sleutel van de verzender te downloaden.
Ga naar Enigmail -> Voorkeuren -> Basis tab en geef het adres van de keyserver in in het Keyserver(s): vakje, gescheiden door een komma om een lijst van keyservers die u wilt gebruiken te configureren. De eerste keyserver uit de lijst zal als standaardserver gebruikt worden.
Verdere help is verkrijgbaar op de Enigmail Helppagina
enigmail/lang/nl/help/rulesEditor.html 0000664 0000000 0000000 00000006463 12667016244 0020335 0 ustar 00root root 0000000 0000000In de regeleditor kan u standaarden opgeven per ontvanger om versleuteling, ondertekening en PGP/MIME in- of uit te schakelen. U kan er ook OpenPGP sleutels definiëren. Elke regel bestaat uit 5 velden en wordt getoond op een enkele lijn:
Deze ondertekeningsinstellingen worden toegepast op alle regels die ermee overeenstemmen. Als één van de regels ondertekening uitschakeld, zal het bericht niet ondertekend worden, ook al is er een regel die Altijd opgeeft.
De regels worden uitgevoerd in de volgorde waarin ze weergegeven worden in de PGP regeleditor. Wanneer een regel overeenstemt met een ontvanger en een PGP sleutel ID bevat, met daarbij nog een opgegeven sleutel ID, dan wordt de ontvanger niet meer gecontroleerd bij het uitvoeren van verdere regels.
Let op: De regeleditor is nog niet volledig. Het is mogelijk om meer geavanceerde regels te schrijven door het regelbestand direct te bewerken (deze regels zouden dan niet meer bewerkt mogen worden in de regeleditor). Verdere informatie voor het direct bewerken van het bestand is beschikbaar op de Enigmail homepage
Verdere help is beschikbaar op de Enigmail support website
enigmail/lang/nl/help/sendingPrefs.html 0000664 0000000 0000000 00000005545 12667016244 0020463 0 ustar 00root root 0000000 0000000Bij de Verzenden voorkeuren kunt u het algemene model en de voorkeuren voor versleuteling kiezen.
Deze instelling is geschikt als u uw privacy wilt vergroten door versleutelde e-mails te versturen in plaats van onversleutelde e-mails als dat mogelijk is.
Het effect is alsof u vrieven stuurt in plaats van ansichtkaarten. In tegenstelling tot bij ansichtkaarten, kunnen brieven normaal gesproken niet gelezen worden tijdens het transport.
Het is echter net als bij brieven niet zeker, dat niemand de brief tijdens het transport opent (hoewel daar wel technische inspanning voor nodig is).
Een concreet risico is dat u per ongeluk ‘vervalste sleutels’ gebruikt, die u van iemand heeft gekregen die beweert dat de sleutel eigendom is van de persoon die u wilt e-mailen. Om dit risico te voorkomen kunt u ofwel het vertrouwensmodel van OpenPGP gebruiken (zie onder) of u moet altijd controleren of de vingerafdruk van de publieke sleutel juist is.
Włącza/wyłącza szyfrowanie dla wszystkich odbiorców przed wysłaniem. Użytkownik jest powiadamiany, jeśli szyfrowanie się nie powiodło.
Jeśli funkcja Wyświetlaj wybór w razie potrzeby, jest ustawiona na karcie Ustawienia » Zaawansowane » Wybór klucza, będzie wyświetlana lista kluczy, jeśli na liście odbiorców wiadomości znajdują się adresy dla, których nie masz kluczy publicznych.
Jeśli funkcja Nigdy nie wyświetlaj wyboru klucza OpenPGP, jest ustawiona na karcie Ustawienia » Wybór klucza, wiadomość będzie wysyłana niezaszyfrowana, jeśli na liście odbiorców wiadomości znajdują się adresy dla, których nie masz kluczy publicznych.
Jeśli wiesz, że odbiorca może przeczytać wiadomość za pomocą formatu PGP/MIME, należy go użyć.
Ta funkcja jest zależna od ustawień na karcie Ustawienia » PGP/MIME Zezwalaj na używanie PGP/MIME lub Zawsze używaj PGP/MIME.
Jeśli wysyłanie wiadomości się nie powiodło, na przykład z powodu odrzucenia żądania przez serwer POP, Enigmail nie będzie o tym wiedział i zaszyfrowana wiadomość będzie wyświetlana w oknie tworzenia wiadomości. Wybranie tej funkcji spowoduje cofnięcie szyfrowania/podpisywania i w oknie tworzenia wiadomości będzie wyświetlany oryginalny tekst.
Jako tymczasowe rozwiązanie, funkcja ta może być również używana do odszyfrowania cytowanego tekstu podczas odpowiedzi na zaszyfrowane wiadomości. Enigmail powinien automatycznie rozszyfrować cytowaną wiadomość, ale jeśli z jakiegoś powodu zawiedzie, można za pomocą tej funkcji wymusić deszyfrowanie.
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail/lang/pl/help/editRcptRule.html 0000664 0000000 0000000 00000012326 12667016244 0020437 0 ustar 00root root 0000000 0000000W edytorze reguł można określić dla każdego odbiorcy domyślne ustawienia szyfrowania, podpisywania, PGP/MIME i zdefiniować używane klucze OpenPGP. W tym oknie dialogowym można określić reguły dla konkretnego odbiorcy i dla grupy odbiorców, używając podobnych atrybutów.
Reguły są przetwarzane w kolejności, w jakiej są wyświetlane w edytorze reguł OpenPGP. Gdy reguła pasuje do odbiorcy i zawiera klucz OpenPGP, oprócz używania określonego klucza, przy kolejnym przetwarzaniu reguł odbiorca nie jest brany pod uwagę.
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail/lang/pl/help/initError.html 0000664 0000000 0000000 00000005005 12667016244 0020002 0 ustar 00root root 0000000 0000000Zainicjowanie OpenPGP może się nie powieść z różnych powodów. Najczęściej występujące są opisane poniżej. Więcej informacji na ten temat można znaleźć na stronie pomocy Enigmail.
Aby OpenPGP działało, musi być zainstalowane narzędzie GnuPG. Jeśli nie można znaleźć GnuPG, najpierw należy sprawdzić czy na komputerz jest zainstalowanye plik wykonywalny: gpg.exe w systemie Windows lub gpg w innych systemach. Jeśli GnuPG jest zainstalowane i OpenPGP nie może go znaleźć, trzeba w ustawieniach OpenPGP (menu OpenPGP » Preferencje) ręcznie określić ścieżkę do GnuPG.
OpenPGP działa tylko, jeśli zostało zbudowane za pomocą tego samego środowiska tworzenia, co np. Thunderbird lub SeaMonkey. Oznacza to, że możesz używać oficjalnych wydań Enigmail tylko jeśli używasz oficjalnych wydań Thunderbird lub SeaMonkey dostarczanych przez mozilla.org.
Jeśli używasz wersji Thunderbirda lub SeaMonkey pochodzących z innych źródeł, np. od dostarczyciela twojej dystrybucji Linuksa lub aplikacja została zbudowana we własnym zakresie, należy użyć Enigmail zbudowanego przez to samo źródło lub zbudować go we własnym zakresie. Aby zbudować Enigmail, przejdź do sekcji z kodem źródłowym znajdującej się na stronie Enigmail. Nie zgłaszaj błędów dotyczących tego błędu - nie są one rozwiązywalne.
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail/lang/pl/help/messenger.html 0000664 0000000 0000000 00000011343 12667016244 0020017 0 ustar 00root root 0000000 0000000Jeśli w pliku gpg.conf nie są ustawione funkcje keyserver-options auto-key-retrieve i czytasz podpisaną lub zaszyfrowaną wiadomość, w nagłówku czytanej wiadomości będzie widoczna ikona pióra ze znakiem zapytania, a w pasku statusu Enigmail będzie wyświetlana informacja Część wiadomości podpisana; kliknij ikonę pióra, by zobaczyć szczegóły i w wiadomości zostanie wyświetlony blok zawierający wszystkie wskaźniki OpenPGP i blok podpisu.
Możesz także zobaczyć tę informację, jeśli w pliku gpg.conf są ustawione funkcje keyserver-options auto-key-retrieve, a klucz OpenPGP jest niedostępny na domyślnym serwerze kluczy.
Po kliknięciu ikony pióra ze znakiem zapytania, zostanie wyświetlone okno informujące, że klucz nie jest dostępny w twojej bazie kluczy. Po naciśnięciu przycisku OK, zostanie wyświetlone kolejne okno zawierające listę serwerów kluczy, z której można wybrać do pobrania klucz publiczny nadawcy.
Aby skonfigurować listę serwerów kluczy, których chcesz używać, przejdź na kartę OpenPGP » Ustawienia » Zaawansowane » Serwery kluczy i w polu Określ swoje serwery kluczy, wprowadź adresy serwerów kluczy, oddzielając je przecinkami. Pierwszy serwer na liście będzie używany jako domyślny serwer.
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail/lang/pl/help/rulesEditor.html 0000664 0000000 0000000 00000006737 12667016244 0020343 0 ustar 00root root 0000000 0000000W edytorze reguł można określić domyślne ustawienia dla każdego adresata: włączyć szyfrowanie, podpisywanie, kodowanie PGP/MIME oraz zdefiniować działanie kluczy OpenPGP. Każda reguła składa się z pięciu, umieszczonych każde w osobnym wierszu, pól:
Ustawienia podpisywania są stosowane dla tych wszystkich reguł, które mają włączoną funkcję podpisywania. Jeśli jakaś reguła wyłącza podpisywanie, wiadomość nie będzie podpisywana bez względu na inne reguły, które określają Zawsze.
Reguły są przetwarzane w kolejności, w jakiej są wyświetlane na liście. W przypadku, gdy reguła pasuje do odbiorcy i zawiera ID klucza OpenPGP, oprócz korzystania z określonego ID klucza odbiorcy, nic innego nie jest brane pod uwagę podczas przetwarzania kolejnych reguł.
Informacja. Proces twórczy edytora reguł nie jest jeszcze zakończony. Bardziej zaawansowane reguły można tworzyć, edytując bezpośrednio plik reguł. Reguły edytowane w ten sposób nie powinny już być nigdy edytowane w edytorze reguł. Więcej informacji na temat bezpośredniego edytowania pliku reguł jest dostępnych na stronie domowej Enigmail.
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail/lang/pl/help/sendingPrefs.html 0000664 0000000 0000000 00000005076 12667016244 0020464 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Caso a opção Mostrar seleção quanto necessário estiver habilitada na aba Preferências -> Seleção de Chaves , uma lista de chaves será mostrada caso existam endereços na lista de destinatários da mensagem para os quais você não possua uma chave pública correspondente.
Caso a opção Nunca mostrar diálogo de seleção de chaves OpenPGP estiver habilitada na aba Preferêencias -> Seleção de Chaves, e existam endereços na lista de destinatários para os quais você não possua a chave pública correspondente, a mensagem será enviada sem criptografia.
Se você sabe que o(s) destinatário(s) consegue(m) ler mensagens utilizando o formato PGP/MIME format, você deve utilizar esta opção.
Esta facilidade depende de ter a opção da aba Preferências -> PGP/MIME configurada para Permitir o uso de PGP/MIME ou Sempre usar PGP/MIME.
Mais ajuda pode ser encontrada na página web de Ajuda do Enigmail
enigmail/lang/pt-BR/help/editRcptRule.html 0000664 0000000 0000000 00000014555 12667016244 0020756 0 ustar 00root root 0000000 0000000No Editor de Regras, você pode especificar padrões por destinatário para permitir criptografia, assinatura e PGP/MIME, e definir quais chaves OpenPGP serão utilizadas. Neste diálogo, você poderá especificar as regras para um único destinatário, ou para um grupo de destinatários com características similares.
As regras são processadas na ordem mostrada na lista do Editor de Regras OpenPGP. Sempre que uma regras coincidir com um destinatário e conter um ID de Chave OpenPGP, além de utilizar o ID de Chave especificado, o destinatário não é mais considerado ao se processar as regras seguintes.
Mais ajuda pode ser encontrada na página web de Ajuda do Enigmail para Configuraçáo por Destinatário
enigmail/lang/pt-BR/help/initError.html 0000664 0000000 0000000 00000005446 12667016244 0020324 0 ustar 00root root 0000000 0000000Existem diversas razões pelas quais a inicialização do OpenPGP pode falhar. As mais comuns estão descritas abaixo; Para mais informações visite a página de suporte do Enigmail.
Para que o OpenPGP funcione, a ferramenta GnuPG precisa estar instalada. Caso o GnuPG não seja encontrado, verifique primeiramente se o arquivo executável gpg.exe (no Windows; gpg nas outras plataformas) está instalado em seu computador. Caso o GnuPG esteja instalado, e o OpenPGP não consiga encontrá-lo, você precisará informar manualmente o caminho para ele nas Preferências do OpenPGP Preferences (menu OpenPGP > Preferências)
O OpenPGP funciona apenas se tiver sido compilado utilizando-se o mesmo ambiente utilizado para construir o Thunderbird ou SeaMonkey. Isto significa que você apenas pode utilizar uma versão oficial do Enigmail se utilizar também uma versão oficial do Thunderbird ou SeaMonkey fornecida pela mozilla.org.
Caso você utilize uma versão do Thunderbird ou SeaMonkey de outro fornecedor (por exemplo, do distribuidor de sua distribuição Linux), ou se você mesmo compilou a aplicação, você deve utilizar uma versão construída pelo mesmo fornecedor, ou compilar uma versão do Enigmail. Para compilar o Enigmail, siga as instruções na seção Código Fonte na página do Enigmail. Por favor não abra relatórios de erro sobre este problema, ele não pode ser resolvido de outra maneira.
Mais ajuda está disponível na Página de Suporte do Enigmail.
enigmail/lang/pt-BR/help/messenger.html 0000664 0000000 0000000 00000011655 12667016244 0020336 0 ustar 00root root 0000000 0000000Se você não tiver a opção de buscar chaves automaticamente no servidor de chaves definida em seu gpg.conf e ler uma mensagem que está assinada ou criptografada, você verá um ícone de uma Caneta no cabeçalho da mensagem juntamente com um Ponto de Interrogação nele, e a barra de status na área do cabeçalho do Enigmail dirá Parte da mensagem foi assinada; clique no ícone da caneta para detalhes e a mensagem mostrará todos os indicadores de blocos de mensagem do OpenPGP e o bloco de assinatura.
Você também pode ver este ícone caso tenha a opção de buscar chaves automaticamente no servidor de chaves definida em seu gpg.conf e a chave OpenPGP não esteja disponível no servidor de chaves padrão.
Clicando no ícone de Caneta com Ponto de Interrogação irá trazer uma janela informando que a chave não está disponível em seu chaveiro. Clicando em OK irá trazer uma outra janela com uma relação de servidores de chaves a partir dos quais você poderá selecionar de onde deseja baixar a chave pública do remetente.
Para configurar a lista de servidores de chaves que você deseja utilizar, vá até a aba Enigmail -> Preferências -> Báasicas e entre com os endereços dos servidores de chaves na caixa Servidor(es) de Chaves: separados por uma vírgulas. O primeiro servidor de chaves na lista será utilizado como padrão.
Mais ajuda pode ser encontrada na página web de Ajuda do Enigmail
enigmail/lang/pt-BR/help/rulesEditor.html 0000664 0000000 0000000 00000007066 12667016244 0020650 0 ustar 00root root 0000000 0000000No Editor de Regras, você pode especificar os padrões para cada destinatário para permitir criptografia, assinatura e PGP/MIME, e para definir quais chaves OpenPGP serão utilizadas. Cada regra consiste em 5 campos e é representada em uma única linha:
As regras são processadas na ordem em que são mostradas na lista. Sempre que uma coincide com um destinatário e contém um ID de Chave OpenPGP, além de utilizar o ID de Chave especificado, o destinatário não é mais considerado ao se processar as regras seguintes.
Nota: O editor de regras ainda não está completo. É possível escrever regras muito mais avançadas editando o arquivo de regras diretamente (neste caso, as regras não deverão ser mais editadas no editor de regras). Maiores informações sobre como editar o arquivo diretamente estão disponíveis na página do Enigmail
Mais ajuda pode ser encontrada na página de Ajuda do Enigmail na web
enigmail/lang/pt-BR/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0021004 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Se a opção Mostrar selecção quando necessário estiver seleccionada no separador Preferências Enigmail -> Selecção de chaves, será apresentada uma lista de chaves no caso de haver endereços de email na lista de destinatários para os quais tenha a chave pública.
Se a opção Nunca mostrar selecção de chave OpenPGP estiver seleccionada no separador Preferências Enigmail -> Selecção de chaves, e houver endereços de email na lista de destinatários para os quais não tem a chave pública, a mensagem será enviada em claro.
Se sabe que o(s) destinatário(s) podem ler correio electrónico no formato PGP/MIME, deve usá-lo.
Esta funcionalidade depende da configuração no separador Preferências -> PGP/MIME estar para Permitir o uso de PGP/MIME ou Usar sempre PGP/MIME.
Ajuda adicional disponível na página web de Ajuda do Enigmail
enigmail/lang/pt-PT/help/editRcptRule.html 0000664 0000000 0000000 00000013763 12667016244 0020776 0 ustar 00root root 0000000 0000000No Editor de Regras, pode especificar, para cada destinatário, se deseja cifrar, assinar ou usar PGP/MIME por omissão e ainda quais as chaves OpenPGP a usar. Neste diálogo, pode especificar as regras para cada destinatário individualmente ou para cada grupo de destinatários com atributos semelhantes.
As regras são processadas na ordem em que são mostradas na lista Editor de Regras por Destinatário. Sempre que uma regra coincidir com um destinatário e contiver um Identificador de chave OpenPGP, para além de usar o Identificador de chave específico, implica que o destinatário não seja mais considerado ao processar regras posteriores.
Pode encontrar mais ajuda na página de Configurações de Regras por Destinatário do Enigmail
enigmail/lang/pt-PT/help/initError.html 0000664 0000000 0000000 00000004653 12667016244 0020343 0 ustar 00root root 0000000 0000000Há vários motivos para que o OpenPGP não consiga inicializar. Os mais comuns estão descritos abaixo; para mais informação, visite por favor a Página de Suporte do Enigmail.
Para que o OpenPGP possa funcionar, é necessário que a ferramenta GnuPG esteja instalada. Se não for possÃvel encontrar o GnuPG, certifique-se que o executável gpg.exe (em Windows; gpg nas outras platformas) está instalado no seu computador. Em caso afirmativo, e se o OpenPGP não o conseguir encontrar, é necessário configurar manualmente o caminho para o GnuPG nas Preferências (menu OpenPGP > Preferências)
O OpenPGP funciona apenas se for compilado na mesma plataforma que o Thunderbird ou Seamonkey. Isto significa que a versão oficial do Enigmail apenas pode ser usada em conjunto com as versões oficiais do Thunderbird ou Seamonkey fornecidas pela mozilla.org.
Se usa o Thunderbird ou Seamonkey provenientes de outra fonte (por exemplo, o fornecedor da sua distribuição de Linux), ou se compilou a aplicação localmente, deve usar uma versão de Enigmail do mesmo fornecedor ou compilar o Enigmail localmente. Instruções para compilar o Enigmail podem ser encontradas na Secção de Código Fonte da página web do Enigmail. Por favor, não submeta nenhum relatório de erro sobre este problema, uma vez que não tem solução.
Pode encontrar mais ajuda no SÃtio Web de Suporte ao Enigmail.
enigmail/lang/pt-PT/help/messenger.html 0000664 0000000 0000000 00000011473 12667016244 0020354 0 ustar 00root root 0000000 0000000Se não tiver keyserver-options auto-key-retrieve no seu ficheiro gpg.conf e receber uma mensagem assinada ou cifrada, verá, na área de visualização do cabeçalho da mensagem, um ícone com uma Caneta com um ponto de interrogação sobreposto, a barra de estado do Enigmail na área do cabeçalho dirá Parte da mensagem assinada; para mais informação, clique sobre o ícone da caneta e a mensagem no Painel de Mensagem mostrará os indicadores de um bloco OpenPGP e o bloco da assinatura.
Também poderá ver isto se tiver keyserver-options auto-key-retrieve no seu ficheiro gpg.conf e a chave não estiver disponível no seu servidor de chaves por omissão.
Clicar sobre o ícone da Caneta e Ponto de Interrogação fará aparecer uma janela informando que a chave não está disponível no seu porta-chaves. Clicar em OK mostrará outra janela com uma lista de servidores de chaves para escolher a partir de qual quer fazer a transferência da chave pública do remetente.
Para configurar a lista dos servidores de chaves que deseja usar, vá ao separador Enigmail -> Preferências -> Básicas e introduza os endereços dos servidores no campo Servidor(es) de chave(s):, separados por vírgulas. O servidor de chaves listado em primeiro lugar será usado como o servidor por omissão.
Ajuda adicional disponível na página web de Ajuda do Enigmail
enigmail/lang/pt-PT/help/rulesEditor.html 0000664 0000000 0000000 00000007271 12667016244 0020666 0 ustar 00root root 0000000 0000000No Editor de Regras, pode indicar as configurações a usar por omissão para cifrar, assinar e usar PGP/MIME, por destinatário e quais as chaves a usar. Cada regra consiste em 5 campos e é representada numa única linha:
As regras são processadas na ordem em que são mostradas na lista. Sempre que uma regra coincidir com um destinatário e contiver um Identificador de chave OpenPGP, esse destinatário não será mais considerado ao processar as regras seguintes, para além de ser usado o Identificador de chave especificado.
Nota: O editor de regras ainda não está completo. É possível escrever regras mais avançadas editando o ficheiro de regras directamente (estas regras não devem ser posteriormente editadas no editor de regras). Mais informação sobre a edição directa deste ficheiro está disponível na Homepage do Enigmail.
Ajuda adicional disponível na página web de Ajuda do Enigmail
enigmail/lang/pt-PT/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0021024 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/ru/help/editRcptRule.html 0000664 0000000 0000000 00000011557 12667016244 0020457 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/ru/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020025 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/ru/help/messenger.html 0000664 0000000 0000000 00000010121 12667016244 0020023 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/ru/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020341 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/ru/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020506 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/sk/help/editRcptRule.html 0000664 0000000 0000000 00000011557 12667016244 0020446 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/sk/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020014 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/sk/help/messenger.html 0000664 0000000 0000000 00000010121 12667016244 0020012 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/sk/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020330 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/sk/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020475 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
ÄŒe je nastavljeno Prikaži izbiro, ko je to potrebno v Nastavitve -> zavihek Izbira kljuÄa, se pojavi seznam s kljuÄi, Äe so naslovi na voljo v seznamu prejemnikovi za sporoÄilo, za katerega nimate javnega kljuÄa.
ÄŒe je nastavljeno Nikoli ne prikaži pogovornega okna Izbira kljuÄa OpenPGP v Nastavitve -> zavihek Izbira kljuÄa in se v seznamu prejemnikov sporoÄila nahajajo naslovi, za katere nimate javnega kljuÄa, bo sporoÄilo odposlano neÅ¡ifrirano.
Če poznani prejemnik/i lahko berejo pošto z uporabo zapisa PGP/MIME, bi ga morali uporabiti.
Ta možnost je odvisna od nastavitev v Nastavitve -> zavihek PGP/MIME - Äe je nastavljeno Dovoli uporabo PGP/MIME ali Vedno uporabi PGP/MIME.
Nadaljno pomoÄ najdete na spletni strani pomoÄi za Enigmail.
enigmail/lang/sl/help/editRcptRule.html 0000664 0000000 0000000 00000012210 12667016244 0020432 0 ustar 00root root 0000000 0000000V urejevalniku pravil lahko navedete privzete dejavnosti po uporabniku za omogoÄanje Å¡ifriranja, podpisovanje in PGP/MIME, ter doloÄite, kateri kljuÄ(i) OpenPGP naj bo(do) uporabljen(i). V tem pogovornem oknu lahko doloÄite pravila za posameznega prejemnika ali za skupino prejemnikov z zelo podobnimi atributi.
Pravila se obdelujejo v zaporedju seznama v Urejevalniku pravil OpenPGP. VsakiÄ, ko se pravilo ujema s prejemnikom in ko vsebuje ID kljuÄa OpenPGP, poleg uporabe navedenega ID kljuÄa, se prejemnik ne obravnava veÄ pri obdelavi naslednjih pravil.
Nadaljno pomoÄ najdete na strani nastavitev Enigmail po prejemniku.
enigmail/lang/sl/help/messenger.html 0000664 0000000 0000000 00000007560 12667016244 0020030 0 ustar 00root root 0000000 0000000ÄŒe nimate nastavljenega keyserver-options autoretrieve-key v datoteki gpg.conf in preberete sporoÄilo, ki je podpisano ali Å¡ifrirano, boste videli ikono Peresa v podroÄju izpisa glave z VpraÅ¡ajem, vrstica stanja Enigmaila v podroÄju glave bo izpisala Del sporoÄila je podpisan; kliknite ikono peresa za podrobnosti in sporoÄilo v podoknu sporoÄila bo prikazalo vse pokazatelje blokov sporoÄila OpenPGP in blok podpisa.
Ta znak boste videli tudi, Äe imate nastavljeno keyserver-options auto-key-retrieve v svoji datoteki gpg.conf, vendar kljuÄ OpenPGP ni na voljo na privzetem strežniku kljuÄev.
S klikom na ikono Pero in vpraÅ¡aj prikliÄete okno z obvestilom, da kljuÄ ni na voljo v vaÅ¡em skladiÅ¡Äu kljuÄev. ÄŒe kliknete V redu, se pojavi novo okno s seznamom strežnikov kljuÄev, s katerega izberete tistega, s katerega naj bo prenesen javni kljuÄ poÅ¡iljatelja.
Za nastavitev seznama strežnikov kljuÄev, ki bi jih radi uporabljali, pojdite na zavihek Enigmail -> Nastavitve -> SploÅ¡no in vnesite naslove strežnikov kljuÄev v polje Strežnik(i) kljuÄev:, loÄene z vejico. Prvi strežnik kljuÄev na seznamu bo uporabljen kot privzeti.
Nadaljna pomoÄ je na voljo na spletni strani pomoÄi za Enigmail.
enigmail/lang/sl/help/rulesEditor.html 0000664 0000000 0000000 00000006071 12667016244 0020335 0 ustar 00root root 0000000 0000000V Urejevalniku pravil lahko doloÄite privzete vrednosti za prejemnike z omogoÄanjem Å¡ifriranja, podpisovanja in PGP/MIME, ter doloÄite, katerei kljuÄ(i) OpenPGP naj bo(do) uporabljen(i). Vsako pravilo sestavlja pet polj in je predstavljeno v eni vrstici:
Pravila se procesirajo v vrstnem redu seznama. Ko se pravilo ujema s prejemnikom in vsebuje ID kljuÄa OpenPGP poleg zporabe navedenega ID kljuÄa, se prejemnik veÄ ne preuÄuje pri procesiranju nadaljnih pravil.
Opomba: Urejevalnik pravil Å¡e ni dokonÄan. Možno je napisati nekaj naprednejÅ¡ih pravil z neposrednim urejanjem datoteke pravil (ta pravila kasneje veÄ ne smete urejati v urejevalniku pravil). Nadaljne informacije za neposredno urejanje datoteke je na voljo na domaÄi strani Enigmail.
Nadaljna pomoÄ je na voljo na naslovu spletni strani pomoÄi za Enigmail
enigmail/lang/sl/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020476 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/sq/help/editRcptRule.html 0000664 0000000 0000000 00000011603 12667016244 0020444 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the Per-Recipient Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/sq/help/help.html 0000664 0000000 0000000 00000010467 12667016244 0016775 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
If you have questions or comments about enigmail, please send a message to the Enigmail mailing list
Enigmail is open source and licensed under the Mozilla Public License and the GNU General Public License
enigmail/lang/sq/help/initError.html 0000664 0000000 0000000 00000004546 12667016244 0020023 0 ustar 00root root 0000000 0000000There are several reasons why initializing Enigmail does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for Enigmail to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 Enigmail > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/sq/help/messenger.html 0000664 0000000 0000000 00000010141 12667016244 0020022 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/sq/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020336 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/sq/help/sendingPrefs.html 0000664 0000000 0000000 00000004757 12667016244 0020501 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Om du vet att mottagaren kan läsa e-post med hjälp av PGP/MIME-formatet, ska du använda det.
Den här funktionen är beroende av inställningarna i Inställningar -> PGP/MIME -fliken är satta till Tillåt att använda PGP/MIME eller Alltid använda PGP/MIME.
Om det uppstår ett fel när du skickar mail, till exempel POP-servern inte accepterar begäran, kommer Enigmail inte vet om det, och det krypterade meddelandet fortsätter att visas i meddelandefönstret. Att välja detta menyalternativ kommer att ångra kryptering/signering, då återgår skrivfönstret tillbaka till sin ursprungliga text.
Som en temporär fix, kan detta alternativ också användas för att dekryptera den citerade texten när du svarar på krypterade meddelanden. Enigmail bör automatiskt dekryptera det citerade meddelandet, men om det misslyckas av någon anledning, kan du använda det här menyalternativet för att tvinga det.
Ytterligare hjälp finns på Enigmail's Supportwebbplats
enigmail/lang/sv-SE/help/editRcptRule.html 0000664 0000000 0000000 00000011660 12667016244 0020761 0 ustar 00root root 0000000 0000000I regelredigeraren kan du ange standardinställningar per mottagare för att aktivera kryptering, signering och PGP/MIME, och för att definiera vilken OpenPGP-nyckel som ska användas. I det här fönstret kan du ange regler för en enda mottagare, och för en grupp av mottagare med mycket liknande egenskaper.
Reglerna behandlas i den ordning de visas i listan i OpenPGP regelredigerare. När en regel matchar en mottagare och innehåller en OpenPGP nyckel-ID, utöver att använda den angivna Nyckel-ID, mottagaren räknas inte längre vid behandling av ytterligare regler.
Ytterligare hjälp finns på Enigmail Per-Recipient Settings page
enigmail/lang/sv-SE/help/initError.html 0000664 0000000 0000000 00000004574 12667016244 0020336 0 ustar 00root root 0000000 0000000Det finns flera skäl till varför initiering av OpenPGP inte lyckas. De vanligaste beskrivs nedan; Mer information finns på Enigmail supportsida.
För att OpenPGP ska fungera, behövs verktyget GnuPG installeras. Om GnuPG inte kan hittas, se då först till att den körbara gpg.exe (för Windows; gpg för andra plattformar) är installeras på din dator. Om GnuPG är installerat, och OpenPGP kan inte hitta den, måste du manuellt ange sökväg till GnuPG i OpenPGP's inställningar (meny OpenPGP > Inställningar)
OpenPGP fungerar endast om den är byggd med samma byggmiljö som Thunderbird eller SeaMonkey byggdes med. Det innebär att du kan använda den officiella Enigmail releaser endast om du använder de officiella releaserna av Thunderbird eller SeaMonkey som tillhandahålls av mozilla.org.
Om du använder en Thunderbird eller SeaMonkey version som kommer från någon annan källa (t.ex. leverantören av din Linux-distribution), eller om du byggde programmet själv, bör du antingen använda en Enigmail version byggda med samma källa, eller bygga Enigmail själv. För att bygga Enigmail, se Avsnittet källkod på Enigmail's hemsida. Skicka eller lämna inte någon felrapporter om detta problem, det kan inte lösas.
Ytterligare hjälp finns på Enigmail's Supportwebbplats.
enigmail/lang/sv-SE/help/messenger.html 0000664 0000000 0000000 00000010250 12667016244 0020335 0 ustar 00root root 0000000 0000000Om du inte har angett keyserver-options auto-key-retrieve i din gpg.conf fil och du läser ett meddelande som är signerat eller krypterat, kommer du att se en Penn-ikon i huvudområdet med ett Frågetecken på den, Enigmail's statusrad i huvudområdet visar del av meddelandet signerat; klicka på pennikonen för detaljer och meddelandet i meddelandefönstret visar alla OpenPGP meddelandeblocksindikatorer och signaturblock.
Du kan också se detta om du har angett keyserver-options auto-key-retrieve i din gpg.conf fil och OpenPGP nyckeln inte finns på standardnyckelservern.
Genom att klicka på Penn och frågetecknet-ikonen kommer ett fönster upp som meddelar att nyckeln inte är tillgänglig i din nyckelring. Om du klickar på OK kommer att ett nytt fönster upp med en lista över nyckelservrar där du kan välja att hämta avsändarens publika nyckel från.
För att konfigurera listan med nyckelservrar som du vill använda, gå till Enigmail-> Inställningar->grundläggande fliken och ange nyckelserverns adress i nyckelserver: rutan, separerade med ett kommatecken. Den första nyckelservern i listan kommer att användas som standard.
Ytterligare hjälp finns på Enigmail's Supportwebbplats
enigmail/lang/sv-SE/help/rulesEditor.html 0000664 0000000 0000000 00000006237 12667016244 0020660 0 ustar 00root root 0000000 0000000I regelredigeraren kan du ange standardinställningar per mottagare för att möjliggöra kryptering, signering och PGP/MIME, och ange vilken OpenPGP nyckel som ska användas. Varje regel består av fem områden och är representerade på en rad:
Dessa signeringsinställningar tillämpas för alla regler som matchar. Om en av reglerna inaktiverar signering kommer meddelandet inte signeras, oberoende av andra regler som anger Alltid.
Reglerna behandlas i den ordning som visas i listan. När en regel matchar en mottagare och innehåller en OpenPGP nyckel-ID, utöver att använda den angivna nyckel-ID, mottagaren räknas inte längre vid behandling av ytterligare regler.
OBS: Regelredigeraren är ännu inte klar. Det är möjligt att skriva några mer avancerade regler genom att direkt redigera filen rules (dessa regler bör då inte redigeras längre i regelredigeraren). Mer information för att direkt redigera filen finns tillgänglig på Enigmail's hemsida
Ytterligare hjälp finns på Enigmail's Supportwebbplats
enigmail/lang/sv-SE/help/sendingPrefs.html 0000664 0000000 0000000 00000005402 12667016244 0020777 0 ustar 00root root 0000000 0000000I inställningar för att skicka kan du välja en allmän modell och inställningar för kryptering.
Denna inställning är lämplig, om du vill förbättra din integritet genom att skicka e-post krypterat istället för okrypterat om det är möjligt.
Effekten är som att skicka e-post som brev istället för vykort. Till skillnad från vykort, döljer brev oftast sitt innehåll under transport.
Observera dock att som med brev kan du inte vara säker på att ingen öppnar brevet under transporten (även om vissa tekniska ansträngningar krävs för det).
En konkret risk är att du av misstag använder "förfalskade nycklar" du fick från någonstans eller någon som hävdar att nyckeln tillhör den person som du vill skicka e-post till. För att undvika denna risk, kan du antingen använda förtroende modellen av PGP (se nedan) eller bör du alltid kontrollera, om fingeravtryck av en publik nyckel är korrekt.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/tr/help/editRcptRule.html 0000664 0000000 0000000 00000011557 12667016244 0020456 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/tr/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020024 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/tr/help/messenger.html 0000664 0000000 0000000 00000010121 12667016244 0020022 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/tr/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020340 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/tr/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020505 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Báºt/Tắt mã hóa cho tất cả ngưá»i nháºn trước khi gá»i. Ngưá»i dùng được thông báo, nếu không mã hóa được.
Nếu Hiển thị lá»±a chá»n khi cần thiết được đặt trong Tùy thÃch -> thẻ Chá»n Khóa, má»™t danh sách các khóa sẽ báºt lên nếu có địa chỉ trong danh sách những ngưá»i nháºn cho tin nhắn cho ngưá»i mà bạn không có khóa công.
Nếu Không bao giá» hiển thị thoại lá»±a chá»n khóa OpenPGP được đặt trong Tùy thÃch -> thẻ Chá»n Khóa, và có địa chỉ trong danh sách những ngưá»i nháºn cho tin nhắn cho ngưá»i mà bạn không có khóa công, tin nhắn sẽ được gá»i mà không được mã hóa.
Nếu bạn biết (những) ngưá»i nháºn có thể Ä‘á»c thư bằng cách dùng định dạng PGP/MIME thì bạn nên sá» dụng nó.
TÃnh năng nà y phụ thuá»™c và o các thiết láºp trong Tùy thÃch -> thẻ PGP/MIME Ä‘ang được đặt để Cho phép sá» dụng PGP/MIME hoặc Luôn luôn sá» dụng PGP/MIME.
Nếu bị trục trặc khi tháºt sá»± gá»i thư, chẳng hạn như máy chá»§ POP không chấp nháºn yêu cầu, Enigmail sẽ không biết gì vá» nó, và tin nhắn được mã hóa sẽ tiếp tục được hiển thị trong cá»a sổ Soạn tin. Chá»n mục trình đơn nà y sẽ há»§y bước mã hóa/ký tên, rồi trở ngược lại văn bản ban đầu cá»§a cá»a sổ Soạn tin.
Tùy chá»n nà y là má»™t sá»a chữa tạm thá»i nhưng cÅ©ng có thể được sá» dụng để giải mã các văn bản trÃch dẫn khi trả lá»i các tin nhắn được mã hóa. Enigmail sẽ tá»± động giải mã tin trÃch dẫn, nhưng nếu không là m được vì lý do nà o đó thì bạn có thể sá» dụng mục trình đơn nà y để ép buá»™c nó.
Trợ giúp thêm nữa có sẵn trên Trang web Trợ giúp Enigmail
enigmail/lang/vi/help/editRcptRule.html 0000664 0000000 0000000 00000014137 12667016244 0020444 0 ustar 00root root 0000000 0000000Trong Chỉnh sá»a Quy tắc, bạn có thể Ä‘iá»n rõ các mặc định cho má»—i ngưá»i nháºn để báºt mã hóa lên, ký tên và PGP/MIME, và để xác định (các) khóa OpenPGP nà o để sá» dụng. Trong há»™p thoại nà y, bạn có thể Ä‘iá»n rõ các quy tắc cho má»™t ngưá»i nháºn duy nhất, và cho má»™t nhóm ngưá»i nháºn vá»›i các thuá»™c tÃnh rất giống nhau.
Các quy tắc được xá» lý theo thứ tá»± hiển thị trong danh sách trong Chỉnh sá»a Quy tắc cá»§a OpenPGP. Bất cứ khi nà o má»™t quy tắc trùng hợp vá»›i má»™t ngưá»i nháºn và chứa má»™t ID khóa OpenPGP, ngoà i việc sá» dụng ID khóa được Ä‘iá»n rõ, ngưá»i nháºn không được lưu ý đến nữa khi tiếp tục xá» lý các quy tắc khác.
Trợ Giúp thêm nữa có sẵn trên trang Thiết láºp Từng-Ngưá»i nháºn cá»§a Enigmail
enigmail/lang/vi/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020015 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/vi/help/messenger.html 0000664 0000000 0000000 00000012164 12667016244 0020024 0 ustar 00root root 0000000 0000000Nếu bạn không có tùy chá»n-máy phục vụ khóa tá»± động-lấy-khóa đặt trong táºp tin gpg.conf cá»§a bạn và bạn Ä‘á»c tin nhắn mà đã được ký tên hoặc mã hóa, bạn sẽ thấy má»™t biểu tượng Bút trong khu vá»±c hiển thị đầu đỠvá»›i má»™t Dấu Há»itrên đó, dòng trạng thái Enigmail trong khu vá»±c đầu đỠsẽ nói là Má»™t phần tin nhắn đã được ký; nhấn biểu tượng bút để có chi tiết và tin nhắn trong Cá»a sổ tin nhắn sẽ hiển thị tất cả các OpenPGP chỉ số khối tin và ngăn chặn các chữ ký.
Bạn cÅ©ng có thể thấy Ä‘iá»u nà y nếu bạn có tùy chá»n-máy phục vụ khóa tá»± động-lấy-khóa đặt trong táºp tin gpg.conf cá»§a bạn và khoá OpenPGP không có sẵn trên máy phục vụ khóa mặc định.
Nhấp và o biểu tượng Bút và dấu Há»i sẽ Ä‘em đến má»™t cá»a sổ cho biết rằng khóa không có sẵn trong vòng khoá cá»§a bạn. Nhấn OK sẽ Ä‘em đến má»™t cá»a sổ khác vá»›i má»™t danh sách các máy phục vụ khóa để từ đó bạn có thể chá»n để tải xuống khoá công cá»§a ngưá»i gá»i.
Äể cấu hình danh sách các máy phục vụ khóa mà bạn muốn sá» dụng, hãy và o thẻ Enigmail -> Tùy thÃch -> Căn bản và nháºp địa chỉ máy phục vụ khóa và o há»™p (Các) máy phục vụ khóa:, phân biệt bằng dấu phẩy. Máy phục vụ khóa đầu tiên trong danh sách sẽ được dùng là m mặc định.
Trợ Giúp thêm nữa có sẵn trên Trang web Trợ giúp của Enigmail
enigmail/lang/vi/help/rulesEditor.html 0000664 0000000 0000000 00000007434 12667016244 0020341 0 ustar 00root root 0000000 0000000Trong Chỉnh sá»a Quy tắc, bạn có thể Ä‘iá»n rõ các mặc định cho má»—i ngưá»i nháºn để báºt mã hóa lên, ký tên và PGP/MIME, và để xác định (các) khóa OpenPGP nà o để sá» dụng. Má»—i quy tắc bao gồm 5 lÄ©nh vá»±c và được biểu hiện trên má»™t dòng đơn:
Các thiết láºp ký tên nà y được áp dụng cho tất cả các quy tắc trùng hợp. Nếu má»™t trong những quy tắc tắt việc ký tên thì tin nhắn sẽ không được ký, ngay cả những quy tắc khác có Ä‘iá»n rõ là Luôn luôn.
Các quy tắc được xá» lý theo thứ tá»± hiển thị trong danh sách. Bất cứ khi nà o má»™t quy tắc trùng hợp vá»›i má»™t ngưá»i nháºn và chứa má»™t ID khóa OpenPGP, ngoà i việc sá» dụng ID khóa được Ä‘iá»n rõ, ngưá»i nháºn không được lưu ý đến nữa khi tiếp tục xá» lý các quy tắc khác.
Lưu ý: Chỉnh sá»a quy tắc chưa được hoà n tất. Có thể viết thêm má»™t số quy tắc tiên tiến hÆ¡n bằng cách trá»±c tiếp chỉnh sá»a táºp tin quy tắc (các quy tắc nà y sau đó không nên được chỉnh sá»a nữa trong chỉnh sá»a quy tắc). Tin tức thêm nữa để trá»±c tiếp chỉnh sá»a táºp tin có sẵn trên Trang chá»§ Enigmail
Giúp hơn nữa có sẵn trên Enigmail Help web page
enigmail/lang/vi/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020476 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
如果您在 选项 -> 密钥选择 æ ‡ç¾ä¸è®¾ç½®äº† 在需è¦çš„æ—¶å€™æç¤ºé€‰å–密钥 , å½“æ— æ³•æ‰¾åˆ°æ‚¨çš„é‚®ä»¶æ”¶ä»¶äººä¸æŸä¸ªæ”¶ä»¶äººåœ°å€å¯¹åº”的公用密钥时将会弹出一个密钥列表。
如果您在 选项 -> 密钥选择 æ ‡ç¾ä¸è®¾ç½®äº† ä¸è¦æç¤ºé€‰å–密钥 , å½“æ— æ³•æ‰¾åˆ°æ‚¨çš„é‚®ä»¶æ”¶ä»¶äººä¸æŸä¸ªæ”¶ä»¶äººåœ°å€å¯¹åº”的公用密钥时, å°†ä¸åР坆å‘é€é‚®ä»¶ã€‚
å¦‚æžœæ‚¨ç¡®è®¤æ‚¨çš„æ”¶ä»¶äººèƒ½å¤Ÿå¤„ç† PGP/MIME æ ¼å¼çš„邮件, 您应该使用它。
è¦ä½¿ç”¨æœ¬åŠŸèƒ½, 您必须设置 选项 -> PGP/MIME æ ‡ç¾ä¸çš„ å…许使用 PGP/MIME 或 总是使用 PGP/MIME。
您å¯ä»¥ä»Ž Enigmail 帮助网页获得更多的帮助
enigmail/lang/zh-CN/help/editRcptRule.html 0000664 0000000 0000000 00000012125 12667016244 0020740 0 ustar 00root root 0000000 0000000在规则编辑器ä¸ï¼Œæ‚¨å¯ä»¥ä¸ºæ¯ä¸ªæ”¶ä»¶äººå•独指定 åŠ å¯†ï¼Œæ•°å—ç¾åå’Œ PGP/MIME,并定义è¦ä½¿ç”¨çš„ OpenPGP 密钥。通过这个 å¯¹è¯æ¡†ï¼Œæ‚¨å¯ä»¥ä¸ºå•个收件人定义规则,也å¯ä»¥ä¸ºå…·æœ‰ç›¸ä¼¼å±žæ€§çš„一组 收件人定义规则。
所有的规则将会按照 OpenPGP 规则编辑器 列表ä¸çš„顺åºé€ä¸ªå¤„ç†ã€‚å½“ä»»ä¸€åŒ…å« OpenPGP å¯†é’¥æ ‡è¯†çš„è§„åˆ™æˆåŠŸåŒ¹é…一个收件人,我们除了为这个收件人使用规则ä¸åŒ…å«çš„密钥之外,还将在åŽç»çš„规则 测试ä¸å¿½ç•¥è¯¥æ”¶ä»¶äººã€‚
您å¯ä»¥ä»Ž Enigmail æ¯æ”¶ä»¶äººè®¾ç½®å¸®åЩ页 获得更多帮助
enigmail/lang/zh-CN/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020316 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/zh-CN/help/messenger.html 0000664 0000000 0000000 00000007460 12667016244 0020330 0 ustar 00root root 0000000 0000000如果您的 gpg.conf æ–‡ä»¶ä¸æ²¡æœ‰è®¾ç½® keyserver-options auto-key-retrieve,当您阅读一å°ç»è¿‡æ•°å—ç¾å或者 åŠ å¯†çš„é‚®ä»¶çš„æ—¶å€™ï¼Œæ‚¨ä¼šçœ‹åˆ°é‚®ä»¶å¤´æ˜¾ç¤ºåŒºåŸŸçš„ 钢笔 å›¾æ ‡ä¸Šé¢æœ‰ä¸ª é—®å·ï¼Œ 邮件头区域ä¸çš„ Enigmail 状æ€è¡Œå°†ä¼šæ˜¾ç¤º 邮件包å«å·² æ•°å—ç¾å 部分 ;请点击“钢笔â€å›¾æ ‡æŸ¥çœ‹è¯¦ç»†ä¿¡æ¯ å¹¶ä¸”é‚®ä»¶æ£æ–‡æ˜¾ç¤ºéƒ¨åˆ† 将显示全部 OpenPGP 段指示符å·å’Œå…¨éƒ¨æ•°å—ç¾å段。
䏿žœå³ä½¿æ‚¨åœ¨ gpg.conf 文件ä¸è®¾ç½®äº† keyserver-options auto-key-retrieveï¼Œå½“æ— æ³•ä»Žé»˜è®¤å¯†é’¥æœåŠ¡å™¨æ‰¾åˆ°å‘ä»¶äººçš„å¯†é’¥æ—¶æ‚¨ä¹Ÿä¼šçœ‹åˆ°æ¤æç¤ºã€‚
点击该 带有问å·çš„钢笔 å°†ä¼šå¼¹å‡ºä¸€ä¸ªçª—å£æç¤ºæ‚¨çš„å¯†é’¥é“¾ä¸åŒ…å«è¯¥å‘件人的密钥。 æ¤æ—¶ç‚¹å‡»â€œç¡®å®šâ€å°±ä¼šå¼¹å‡ºå¦ä¸€ä¸ªå¸¦æœ‰å¯†é’¥æœåŠ¡å™¨åˆ—è¡¨çš„çª—å£ä»¥ä¾¿æ‚¨ä»Žä¸é€‰æ‹©ä¸€ä¸ªæœåС噍æ¥ä¸‹è½½ å‘件人的公用密钥。
您å¯ä»¥é€šè¿‡åœ¨ Enigmail -> 选项 -> 基本 æ ‡ç¾çš„ 密钥æœåС噍: 框ä¸è¾“入以逗å·åˆ†éš”的密钥æœåŠ¡å™¨åœ°å€æ¥é…ç½®ä¸Šé¢æåˆ°çš„å¯†é’¥æœåŠ¡å™¨åˆ—è¡¨çª—å£ä¸æ˜¾ç¤ºçš„æœåŠ¡å™¨ã€‚ 这里所填写的第一个密钥æœåŠ¡å™¨å°†è¢«ä½œä¸ºé»˜è®¤å¯†é’¥æœåŠ¡å™¨ã€‚
您å¯ä»¥ä»Ž Enigmail 帮助网页获得更多帮助
enigmail/lang/zh-CN/help/rulesEditor.html 0000664 0000000 0000000 00000005615 12667016244 0020641 0 ustar 00root root 0000000 0000000åœ¨è§„åˆ™ç¼–è¾‘å™¨ä¸æ‚¨å¯ä»¥ä¸ºæ¯ä¸ªæ”¶ä»¶äººé»˜è®¤è®¾ç½®åР坆ã€ç¾åå’ŒPGP/MIME,以åŠå®šä¹‰ä½¿ç”¨æŸä¸ª OpenPGP 密钥。æ¯ä¸€æ¡è§„则由5ä¸ªå—æ®µç»„æˆï¼Œå¹¶ä¸”æ¯æ¡è§„则å 一行:
所有的规则将会按照 OpenPGP 规则编辑器 列表ä¸çš„顺åºé€ä¸ªå¤„ç†ã€‚å½“ä»»ä¸€åŒ…å« OpenPGP å¯†é’¥æ ‡è¯†çš„è§„åˆ™æˆåŠŸåŒ¹é…一个收件人,我们除了为这个收件人使用规则ä¸åŒ…å«çš„密钥之外,还将在åŽç»çš„规则 测试ä¸å¿½ç•¥è¯¥æ”¶ä»¶äººã€‚
注æ„: 规则编辑器的功能还ä¸å®Œå…¨ã€‚ ä½ å¯ä»¥é€šè¿‡ç›´æŽ¥ç¼–辑规则文件æ¥å†™æ›´å¤šé«˜çº§çš„规则(ä¸è¦å†åœ¨è§„则编辑器ä¸ç¼–辑这些规则)。直接编辑规则文件的更详细帮助 å¯ä»¥ Enigmail 的主页上找到
您å¯ä»¥ä»Ž Enigmail 帮助web页上获得更多的帮助信æ¯
enigmail/lang/zh-CN/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0020777 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.
If Display selection when necessary is set in Preferences -> Key Selection tab, 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.
If Never display OpenPGP key selection dialog is set in Preferences -> Key Selection tab, 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.
If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.
This feature is dependent on the settings in Preferences -> PGP/MIME tab being set to Allow to use PGP/MIME or Always use PGP/MIME.
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.
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.
Further help is available on the Enigmail Help web page
enigmail/lang/zh-TW/help/editRcptRule.html 0000664 0000000 0000000 00000011557 12667016244 0021002 0 ustar 00root root 0000000 0000000In 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.
The rules are processed in the order displayed in the list in the OpenPGP Rules Editor. 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.
Further help is available on the Enigmail Per-Recipient Settings page
enigmail/lang/zh-TW/help/initError.html 0000664 0000000 0000000 00000004536 12667016244 0020350 0 ustar 00root root 0000000 0000000There are several reasons why initializing OpenPGP does not succeed. The most common ones are described below; for more information please visit the Enigmail Support page.
In order for OpenPGP to work, the tool GnuPG needs to be installed. If GnuPG cannot be found, then first make sure that the executable gpg.exe (on Windows; gpg 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 OpenPGP > Preferences)
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 mozilla.org.
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 Source Code section on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
Further help is available on the Enigmail Support Web Site.
enigmail/lang/zh-TW/help/messenger.html 0000664 0000000 0000000 00000010121 12667016244 0020346 0 ustar 00root root 0000000 0000000If you do not have keyserver-options auto-key-retrieve set in your gpg.conf file and you read a message which is signed or encrypted, you will see a Pen icon in the headers display area with a Question mark on it, the Enigmail status line in the headers area will say Part of the message signed; click pen icon for details and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.
You may also see this if you have keyserver-options auto-key-retrieve set in your gpg.conf file and the OpenPGP key is not available on the default keyserver.
Clicking on the Pen and Question mark 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.
To configure the list of keyservers you wish to use, go to Enigmail -> Preferences -> Basic tab and enter the keyserver addresses in the Keyserver(s): box, separated by a comma. The first keyserver in the list will be used as the default.
Further help is available on the Enigmail Help web page
enigmail/lang/zh-TW/help/rulesEditor.html 0000664 0000000 0000000 00000006031 12667016244 0020664 0 ustar 00root root 0000000 0000000In 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:
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 Always.
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.
Note: 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). Further information for directly editing the file is available on the Enigmail Homepage
Further help is available on the Enigmail Help web page
enigmail/lang/zh-TW/help/sendingPrefs.html 0000664 0000000 0000000 00000004777 12667016244 0021031 0 ustar 00root root 0000000 0000000In the Sending Preferences you can choose the general model and preferences for encryption.
This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
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).
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.
'; } preface += '"; preface += '\n'; } else if (citeLevel < oldCiteLevel) { preface = ''; for (let j = 0; j < oldCiteLevel - citeLevel; j++) preface += "
\n'; } if (logLineStart.value > 0) { preface += ''; //EnigmailLog.DEBUG("funcs.jsm: r='"+r+"'\n"); return r; }, /** * extract the data fields following a header. * e.g. ContentType: xyz; Aa=b; cc=d * @data: |string| containing a single header * * @return |array| of |arrays| containing pairs of aa/b and cc/d */ getHeaderData: function(data) { EnigmailLog.DEBUG("funcs.jsm: getHeaderData: " + data.substr(0, 100) + "\n"); var a = data.split(/\n/); var res = []; for (let i = 0; i < a.length; i++) { if (a[i].length === 0) break; let b = a[i].split(/;/); // extract "abc = xyz" tuples for (let j = 0; j < b.length; j++) { let m = b[j].match(/^(\s*)([^=\s;]+)(\s*)(=)(\s*)(.*)(\s*)$/); if (m) { // m[2]: identifier / m[6]: data res[m[2].toLowerCase()] = m[6].replace(/\s*$/, ""); EnigmailLog.DEBUG("funcs.jsm: getHeaderData: " + m[2].toLowerCase() + " = " + res[m[2].toLowerCase()] + "\n"); } } if (i === 0 && a[i].indexOf(";") < 0) break; if (i > 0 && a[i].search(/^\s/) < 0) break; } return res; }, /*** * Get the text for the encrypted subject (either configured by user or default) */ getProtectedSubjectText: function() { if (EnigmailPrefs.getPref("protectedSubjectText").length > 0) { return EnigmailPrefs.getPref("protectedSubjectText"); } else { return EnigmailLocale.getString("msgCompose.encryptedSubjectStub"); } }, cloneObj: function(orig) { let newObj; if (typeof orig !== "object" || orig === null || orig === undefined) { return orig; } if ("clone" in orig && typeof orig.clone === "function") { return orig.clone(); } if (Array.isArray(orig) && orig.length > 0) { newObj = []; for (let i in orig) { if (typeof orig[i] === "object") { newObj.push(this.cloneObj(orig[i])); } else { newObj.push(orig[i]); } } } else { newObj = {}; for (let i in orig) { if (typeof orig[i] === "object") { newObj[i] = this.cloneObj(orig[i]); } else newObj[i] = orig[i]; } } return newObj; }, /** * Compare two MIME part numbers to determine which of the two is earlier in the tree * MIME part numbers have the structure "x.y.z...", e.g 1, 1.2, 2.3.1.4.5.1.2 * * @param mime1, mime2 - String the two mime part numbers to compare. * * @return Number (one of -2, -1, 0, 1 , 2) * - Negative number if mime1 is before mime2 * - Positive number if mime1 is after mime2 * - 0 if mime1 and mime2 are equal * - if mime1 is a parent of mime2 the return value is -2 * - if mime2 is a parent of mime1 the return value is 2 * * Throws an error if mime1 or mime2 do not comply to the required format */ compareMimePartLevel: function(mime1, mime2) { let s = new RegExp("^[0-9]+(\.[0-9]+)*$"); if (mime1.search(s) < 0) throw "Invalid mime1"; if (mime2.search(s) < 0) throw "Invalid mime2"; let a1 = mime1.split(/./); let a2 = mime2.split(/./); for (let i = 0; i < Math.min(a1.length, a2.length); i++) { if (Number(mime1[i]) < Number(mime2[i])) return -1; if (Number(mime1[i]) > Number(mime2[i])) return 1; } if (a2.length > a1.length) return -2; if (a2.length < a1.length) return 2; return 0; } }; enigmail/package/glodaMime.jsm 0000664 0000000 0000000 00000002057 12667016244 0016663 0 ustar 00root root 0000000 0000000 /*global Components: false */ /*jshint -W097 */ /* * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ /* This module is a shim module to make it easier to load the Gloda EnigmailMime utilities from the various potential sources */ "use strict"; var EXPORTED_SYMBOLS = ["msgHdrToMimeMessage", "MimeMessage", "MimeContainer", "MimeBody", "MimeUnknown", "MimeMessageAttachment" ]; const Cu = Components.utils; /*global MsgHdrToMimeMessage: false */ try { // TB with omnijar Cu.import("resource:///modules/gloda/mimemsg.js"); } catch (ex) { // "old style" TB Cu.import("resource://app/modules/gloda/mimemsg.js"); } // The original naming is inconsistent with JS standards for classes vs functions // Thus we rename it here. const msgHdrToMimeMessage = MsgHdrToMimeMessage; // We don't need to explicitly create the other variables, since they will be // imported into the current namespace anyway enigmail/package/glodaUtils.jsm 0000664 0000000 0000000 00000001372 12667016244 0017073 0 ustar 00root root 0000000 0000000 /*global Components: false */ /*jshint -W097 */ /* * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ /* This module is a shim module to make it easier to load GlodaUtils from the various potential sources */ "use strict"; var EXPORTED_SYMBOLS = ["GlodaUtils"]; const Cu = Components.utils; try { // TB with omnijar Cu.import("resource:///modules/gloda/utils.js"); } catch (ex) { // "old style" TB Cu.import("resource://app/modules/gloda/utils.js"); } // We don't define the exported symbol here - that is on purpose // The goal of this module is simply to simplify loading of the component enigmail/package/gpg.jsm 0000664 0000000 0000000 00000020627 12667016244 0015545 0 ustar 00root root 0000000 0000000 /*global Components: false */ /*jshint -W097 */ /* * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ "use strict"; var EXPORTED_SYMBOLS = ["EnigmailGpg"]; const Cc = Components.classes; const Ci = Components.interfaces; const Cu = Components.utils; Cu.import("resource://enigmail/files.jsm"); /*global EnigmailFiles: false */ Cu.import("resource://enigmail/log.jsm"); /*global EnigmailLog: false */ Cu.import("resource://enigmail/locale.jsm"); /*global EnigmailLocale: false */ Cu.import("resource://enigmail/dialog.jsm"); /*global EnigmailDialog: false */ Cu.import("resource://enigmail/prefs.jsm"); /*global EnigmailPrefs: false */ Cu.import("resource://enigmail/execution.jsm"); /*global EnigmailExecution: false */ Cu.import("resource://enigmail/subprocess.jsm"); /*global subprocess: false */ Cu.import("resource://enigmail/core.jsm"); /*global EnigmailCore: false */ const GPG_BATCH_OPT_LIST = ["--batch", "--no-tty", "--status-fd", "2"]; function pushTrimmedStr(arr, str, splitStr) { // Helper function for pushing a string without leading/trailing spaces // to an array str = str.replace(/^ */, "").replace(/ *$/, ""); if (str.length > 0) { if (splitStr) { const tmpArr = str.split(/[\t ]+/); for (let i = 0; i < tmpArr.length; i++) { arr.push(tmpArr[i]); } } else { arr.push(str); } } return (str.length > 0); } const EnigmailGpg = { agentVersion: "", _agentPath: null, get agentPath() { return this._agentPath; }, setAgentPath: function(path) { this._agentPath = path; }, /*** determine if a specific feature is available in the GnuPG version used @featureName: String; one of the following values: version-supported - is the gpg version supported at all (true for gpg >= 2.0.7) supports-gpg-agent - is gpg-agent is usually provided (true for gpg >= 2.0) autostart-gpg-agent - is gpg-agent started automatically by gpg (true for gpg >= 2.0.16) keygen-passphrase - can the passphrase be specified when generating keys (false for gpg 2.1 and 2.1.1) windows-photoid-bug - is there a bug in gpg with the output of photoid on Windows (true for gpg < 2.0.16) @return: depending on featureName - Boolean unless specified differently: (true if feature is available / false otherwise) If the feature cannot be found, undefined is returned */ getGpgFeature: function(featureName) { let gpgVersion = EnigmailGpg.agentVersion; if (!gpgVersion || typeof(gpgVersion) != "string" || gpgVersion.length === 0) { return undefined; } gpgVersion = gpgVersion.replace(/\-.*$/, ""); if (gpgVersion.search(/^\d+\.\d+/) < 0) { // not a valid version number return undefined; } const vc = Cc["@mozilla.org/xpcom/version-comparator;1"].getService(Ci.nsIVersionComparator); switch (featureName) { case 'version-supported': return vc.compare(gpgVersion, "2.0.7") >= 0; case 'supports-gpg-agent': return vc.compare(gpgVersion, "2.0") >= 0; case 'autostart-gpg-agent': return vc.compare(gpgVersion, "2.0.16") >= 0; case 'keygen-passphrase': return vc.compare(gpgVersion, "2.1") < 0 || vc.compare(gpgVersion, "2.1.2") >= 0; case 'windows-photoid-bug': return vc.compare(gpgVersion, "2.0.16") < 0; } return undefined; }, /** * get the standard arguments to pass to every GnuPG subprocess * * @withBatchOpts: Boolean - true: use --batch and some more options * false: don't use --batch and co. * * @return: Array of String - the list of arguments */ getStandardArgs: function(withBatchOpts) { // return the arguments to pass to every GnuPG subprocess let r = ["--charset", "utf-8", "--display-charset", "utf-8", "--use-agent"]; // mandatory parameter to add in all cases try { let p = EnigmailPrefs.getPref("agentAdditionalParam").replace(/\\\\/g, "\\"); let i = 0; let last = 0; let foundSign = ""; let startQuote = -1; while ((i = p.substr(last).search(/['"]/)) >= 0) { if (startQuote == -1) { startQuote = i; foundSign = p.substr(last).charAt(i); last = i + 1; } else if (p.substr(last).charAt(i) == foundSign) { // found enquoted part if (startQuote > 1) pushTrimmedStr(r, p.substr(0, startQuote), true); pushTrimmedStr(r, p.substr(startQuote + 1, last + i - startQuote - 1), false); p = p.substr(last + i + 1); last = 0; startQuote = -1; foundSign = ""; } else { last = last + i + 1; } } pushTrimmedStr(r, p, true); } catch (ex) {} if (withBatchOpts) { r = r.concat(GPG_BATCH_OPT_LIST); } return r; }, // returns the output of --with-colons --list-config getGnupgConfig: function(exitCodeObj, errorMsgObj) { const args = EnigmailGpg.getStandardArgs(true). concat(["--fixed-list-mode", "--with-colons", "--list-config"]); const statusMsgObj = {}; const cmdErrorMsgObj = {}; const statusFlagsObj = {}; const listText = EnigmailExecution.execCmd(EnigmailGpg.agentPath, args, "", exitCodeObj, statusFlagsObj, statusMsgObj, cmdErrorMsgObj); if (exitCodeObj.value !== 0) { errorMsgObj.value = EnigmailLocale.getString("badCommand"); if (cmdErrorMsgObj.value) { errorMsgObj.value += "\n" + EnigmailFiles.formatCmdLine(EnigmailGpg.agentPath, args); errorMsgObj.value += "\n" + cmdErrorMsgObj.value; } return ""; } return listText.replace(/(\r\n|\r)/g, "\n"); }, /** * return an array containing the aliases and the email addresses * of groups defined in gpg.conf * * @return: array of objects with the following properties: * - alias: group name as used by GnuPG * - keylist: list of keys (any form that GnuPG accepts), separated by ";" * * (see docu for gnupg parameter --group) */ getGpgGroups: function() { let exitCodeObj = {}; let errorMsgObj = {}; let cfgStr = EnigmailGpg.getGnupgConfig(exitCodeObj, errorMsgObj); if (exitCodeObj.value !== 0) { EnigmailDialog.alert(errorMsgObj.value); return null; } let groups = []; let cfg = cfgStr.split(/\n/); for (let i = 0; i < cfg.length; i++) { if (cfg[i].indexOf("cfg:group") === 0) { let groupArr = cfg[i].split(/:/); groups.push({ alias: groupArr[2], keylist: groupArr[3] }); } } return groups; }, /** * Force GnuPG to recalculate the trust db. This is sometimes required after importing keys. * * no return value */ recalcTrustDb: function() { EnigmailLog.DEBUG("enigmailCommon.jsm: recalcTrustDb:\n"); const command = EnigmailGpg.agentPath; const args = EnigmailGpg.getStandardArgs(false). concat(["--check-trustdb"]); try { const proc = subprocess.call({ command: EnigmailGpg.agentPath, arguments: args, environment: EnigmailCore.getEnvList(), charset: null, mergeStderr: false }); proc.wait(); } catch (ex) { EnigmailLog.ERROR("enigmailCommon.jsm: recalcTrustDb: subprocess.call failed with '" + ex.toString() + "'\n"); throw ex; } }, signingAlgIdToString: function(id) { // RFC 4880 Sec. 9.1, RFC 6637 Sec. 5 and draft-koch-eddsa-for-openpgp-03 Sec. 8 switch (parseInt(id, 10)) { case 1: case 2: case 3: return "RSA"; case 16: return "Elgamal"; case 17: return "DSA"; case 18: return "ECDH"; case 19: return "ECDSA"; case 20: return "ELG"; case 22: return "EDDSA"; default: return EnigmailLocale.getString("unknownSigningAlg", [parseInt(id, 10)]); } }, hashAlgIdToString: function(id) { // RFC 4880 Sec. 9.4 switch (parseInt(id, 10)) { case 1: return "MD5"; case 2: return "SHA-1"; case 3: return "RIPE-MD/160"; case 8: return "SHA256"; case 9: return "SHA384"; case 10: return "SHA512"; case 11: return "SHA224"; default: return EnigmailLocale.getString("unknownHashAlg", [parseInt(id, 10)]); } } }; enigmail/package/gpgAgent.jsm 0000664 0000000 0000000 00000062541 12667016244 0016525 0 ustar 00root root 0000000 0000000 /*global Components: false, unescape: false */ /*jshint -W097 */ /* * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ "use strict"; var EXPORTED_SYMBOLS = ["EnigmailGpgAgent"]; const Cu = Components.utils; Cu.import("resource://gre/modules/ctypes.jsm"); /*global ctypes: false */ Cu.import("resource://enigmail/subprocess.jsm"); /*global subprocess: false */ Cu.import("resource://enigmail/core.jsm"); /*global EnigmailCore: false */ Cu.import("resource://enigmail/files.jsm"); /*global EnigmailFiles: false */ Cu.import("resource://enigmail/log.jsm"); /*global EnigmailLog: false */ Cu.import("resource://enigmail/prefs.jsm"); /*global EnigmailPrefs: false */ Cu.import("resource://enigmail/os.jsm"); /*global EnigmailOS: false */ Cu.import("resource://enigmail/locale.jsm"); /*global EnigmailLocale: false */ Cu.import("resource://enigmail/dialog.jsm"); /*global EnigmailDialog: false */ Cu.import("resource://enigmail/windows.jsm"); /*global EnigmailWindows: false */ Cu.import("resource://enigmail/app.jsm"); /*global EnigmailApp: false */ Cu.import("resource://enigmail/gpg.jsm"); /*global EnigmailGpg: false */ Cu.import("resource://enigmail/execution.jsm"); /*global EnigmailExecution: false */ Cu.import("resource://enigmail/passwords.jsm"); /*global EnigmailPassword: false */ Cu.import("resource://enigmail/system.jsm"); /*global EnigmailSystem: false */ Cu.import("resource://enigmail/data.jsm"); /*global EnigmailData: false */ const Cc = Components.classes; const Ci = Components.interfaces; const nsIEnigmail = Ci.nsIEnigmail; const NS_LOCAL_FILE_CONTRACTID = "@mozilla.org/file/local;1"; const DIR_SERV_CONTRACTID = "@mozilla.org/file/directory_service;1"; const NS_LOCALFILEOUTPUTSTREAM_CONTRACTID = "@mozilla.org/network/file-output-stream;1"; const DEFAULT_FILE_PERMS = 0x180; // equals 0600 // Making this a var makes it possible to test windows things on linux var nsIWindowsRegKey = Ci.nsIWindowsRegKey; var gIsGpgAgent = -1; const DUMMY_AGENT_INFO = "none"; function cloneOrNull(v) { if (v && typeof v.clone === "function") { return v.clone(); } else { return v; } } function extractAgentInfo(fullStr) { if (fullStr) { return fullStr. replace(/[\r\n]/g, ""). replace(/^.*\=/, ""). replace(/\;.*$/, ""); } else { return ""; } } function getHomedirFromParam(param) { let i = param.search(/--homedir/); if (i >= 0) { param = param.substr(i + 9); let m = param.match(/^(\s*)([^\\]".+[^\\]")/); if (m && m.length > 2) { param = m[2].substr(1); let j = param.search(/[^\\]"/); return param.substr(1, j); } m = param.match(/^(\s*)([^\\]'.+[^\\]')/); if (m && m.length > 2) { param = m[2].substr(1); let j = param.search(/[^\\]'/); return param.substr(1, j); } m = param.match(/^(\s*)(\S+)/); if (m && m.length > 2) { return m[2]; } } return null; } var EnigmailGpgAgent = { agentType: "", agentPath: null, connGpgAgentPath: null, gpgconfPath: null, gpgAgentInfo: { preStarted: false, envStr: "" }, gpgAgentProcess: null, gpgAgentIsOptional: true, isDummy: function() { return EnigmailGpgAgent.gpgAgentInfo.envStr === DUMMY_AGENT_INFO; }, useGpgAgent: function() { let useAgent = false; try { if (EnigmailOS.isDosLike() && !EnigmailGpg.getGpgFeature("supports-gpg-agent")) { useAgent = false; } else { // gpg version >= 2.0.16 launches gpg-agent automatically if (EnigmailGpg.getGpgFeature("autostart-gpg-agent")) { useAgent = true; EnigmailLog.DEBUG("enigmail.js: Setting useAgent to " + useAgent + " for gpg2 >= 2.0.16\n"); } else { useAgent = (EnigmailGpgAgent.gpgAgentInfo.envStr.length > 0 || EnigmailPrefs.getPrefBranch().getBoolPref("useGpgAgent")); } } } catch (ex) {} return useAgent; }, resetGpgAgent: function() { EnigmailLog.DEBUG("gpgAgent.jsm: resetGpgAgent\n"); gIsGpgAgent = -1; }, isCmdGpgAgent: function(pid) { EnigmailLog.DEBUG("gpgAgent.jsm: isCmdGpgAgent:\n"); const environment = Cc["@mozilla.org/process/environment;1"].getService(Ci.nsIEnvironment); let ret = false; let path = environment.get("PATH"); if (!path || path.length === 0) { path = "/bin:/usr/bin:/usr/local/bin"; } const psCmd = EnigmailFiles.resolvePath("ps", path, false); const proc = { command: psCmd, arguments: ["-o", "comm", "-p", pid], environment: EnigmailCore.getEnvList(), charset: null, done: function(result) { EnigmailLog.DEBUG("gpgAgent.jsm: isCmdGpgAgent: got data: '" + result.stdout + "'\n"); var data = result.stdout.replace(/[\r\n]/g, " "); if (data.search(/gpg-agent/) >= 0) { ret = true; } } }; try { subprocess.call(proc).wait(); } catch (ex) {} return ret; }, isAgentTypeGpgAgent: function() { // determine if the used agent is a gpg-agent EnigmailLog.DEBUG("gpgAgent.jsm: isAgentTypeGpgAgent:\n"); // to my knowledge there is no other agent than gpg-agent on Windows if (EnigmailOS.getOS() == "WINNT") return true; if (gIsGpgAgent >= 0) { return gIsGpgAgent == 1; } let pid = -1; let exitCode = -1; if (!EnigmailCore.getService()) return false; const proc = { command: EnigmailGpgAgent.connGpgAgentPath, arguments: [], charset: null, environment: EnigmailCore.getEnvList(), stdin: function(pipe) { pipe.write("/subst\n"); pipe.write("/serverpid\n"); pipe.write("/echo pid: ${get serverpid}\n"); pipe.write("/bye\n"); pipe.close(); }, done: function(result) { exitCode = result.exitCode; const data = result.stdout.replace(/[\r\n]/g, ""); if (data.search(/^pid: [0-9]+$/) === 0) { pid = data.replace(/^pid: /, ""); } } }; try { subprocess.call(proc).wait(); if (exitCode) pid = -2; } catch (ex) {} EnigmailLog.DEBUG("gpgAgent.jsm: isAgentTypeGpgAgent: pid=" + pid + "\n"); EnigmailGpgAgent.isCmdGpgAgent(pid); let isAgent = false; try { isAgent = EnigmailGpgAgent.isCmdGpgAgent(pid); gIsGpgAgent = isAgent ? 1 : 0; } catch (ex) {} return isAgent; }, getAgentMaxIdle: function() { EnigmailLog.DEBUG("gpgAgent.jsm: getAgentMaxIdle:\n"); let maxIdle = -1; if (!EnigmailCore.getService()) return maxIdle; const DEFAULT = 7; const CFGVALUE = 9; const proc = { command: EnigmailGpgAgent.gpgconfPath, arguments: ["--list-options", "gpg-agent"], charset: null, environment: EnigmailCore.getEnvList(), done: function(result) { const lines = result.stdout.split(/[\r\n]/); for (let i = 0; i < lines.length; i++) { EnigmailLog.DEBUG("gpgAgent.jsm: getAgentMaxIdle: line: " + lines[i] + "\n"); if (lines[i].search(/^default-cache-ttl:/) === 0) { const m = lines[i].split(/:/); if (m[CFGVALUE].length === 0) { maxIdle = Math.round(m[DEFAULT] / 60); } else { maxIdle = Math.round(m[CFGVALUE] / 60); } break; } } } }; subprocess.call(proc).wait(); return maxIdle; }, setAgentMaxIdle: function(idleMinutes) { EnigmailLog.DEBUG("gpgAgent.jsm: setAgentMaxIdle:\n"); if (!EnigmailCore.getService()) return; const RUNTIME = 8; const proc = { command: EnigmailGpgAgent.gpgconfPath, arguments: ["--runtime", "--change-options", "gpg-agent"], environment: EnigmailCore.getEnvList(), charset: null, mergeStderr: true, stdin: function(pipe) { pipe.write("default-cache-ttl:" + RUNTIME + ":" + (idleMinutes * 60) + "\n"); pipe.write("max-cache-ttl:" + RUNTIME + ":" + (idleMinutes * 600) + "\n"); pipe.close(); }, stdout: function(data) { EnigmailLog.DEBUG("gpgAgent.jsm: setAgentMaxIdle.stdout: " + data + "\n"); }, done: function(result) { EnigmailLog.DEBUG("gpgAgent.jsm: setAgentMaxIdle.stdout: gpgconf exitCode=" + result.exitCode + "\n"); } }; try { subprocess.call(proc); } catch (ex) { EnigmailLog.DEBUG("gpgAgent.jsm: setAgentMaxIdle: exception: " + ex.toString() + "\n"); } }, getMaxIdlePref: function(win) { let maxIdle = EnigmailPrefs.getPref("maxIdleMinutes"); try { if (EnigmailCore.getService(win)) { if (EnigmailGpgAgent.gpgconfPath && EnigmailGpgAgent.connGpgAgentPath) { if (EnigmailGpgAgent.isAgentTypeGpgAgent()) { const m = EnigmailGpgAgent.getAgentMaxIdle(); if (m > -1) maxIdle = m; } } } } catch (ex) {} return maxIdle; }, setMaxIdlePref: function(minutes) { EnigmailPrefs.setPref("maxIdleMinutes", minutes); if (EnigmailGpgAgent.isAgentTypeGpgAgent()) { try { EnigmailGpgAgent.setAgentMaxIdle(minutes); } catch (ex) {} } }, /** * Determine the "gpg home dir", i.e. the directory where gpg.conf and the keyring are * stored * * @return String - directory name, or NULL (in case the command did not succeed) */ getGpgHomeDir: function() { let param = EnigmailPrefs.getPref("agentAdditionalParam"); if (param) { let hd = getHomedirFromParam(param); if (hd) return hd; } if (EnigmailGpgAgent.gpgconfPath === null) return null; const command = EnigmailGpgAgent.gpgconfPath; let args = ["--list-dirs"]; let exitCode = -1; let outStr = ""; EnigmailLog.DEBUG("enigmail.js: Enigmail.setAgentPath: calling subprocess with '" + command.path + "'\n"); EnigmailLog.CONSOLE("enigmail> " + EnigmailFiles.formatCmdLine(command, args) + "\n"); const proc = { command: command, arguments: args, environment: EnigmailCore.getEnvList(), charset: null, done: function(result) { exitCode = result.exitCode; outStr = result.stdout; }, mergeStderr: false }; try { subprocess.call(proc).wait(); } catch (ex) { EnigmailLog.ERROR("enigmail.js: Enigmail.getGpgHomeDir: subprocess.call failed with '" + ex.toString() + "'\n"); EnigmailLog.DEBUG(" enigmail> DONE with FAILURE\n"); throw ex; } let m = outStr.match(/^(homedir:)(.*)$/mi); if (m && m.length > 2) { return EnigmailData.convertGpgToUnicode(unescape(m[2])); } return null; }, setAgentPath: function(domWindow, esvc) { let agentPath = ""; try { agentPath = EnigmailPrefs.getPrefBranch().getCharPref("agentPath"); } catch (ex) {} var agentType = "gpg"; var agentName = ""; EnigmailGpgAgent.resetGpgAgent(); if (EnigmailOS.isDosLike()) { agentName = "gpg2.exe;gpg.exe;gpg1.exe"; } else { agentName = "gpg2;gpg;gpg1"; } if (agentPath) { // Locate GnuPG executable // Append default .exe extension for DOS-Like systems, if needed if (EnigmailOS.isDosLike() && (agentPath.search(/\.\w+$/) < 0)) { agentPath += ".exe"; } try { let pathDir = Cc[NS_LOCAL_FILE_CONTRACTID].createInstance(Ci.nsIFile); if (!EnigmailFiles.isAbsolutePath(agentPath, EnigmailOS.isDosLike())) { // path relative to Mozilla installation dir const ds = Cc[DIR_SERV_CONTRACTID].getService(); const dsprops = ds.QueryInterface(Ci.nsIProperties); pathDir = dsprops.get("CurProcD", Ci.nsIFile); const dirs = agentPath.split(new RegExp(EnigmailOS.isDosLike() ? "\\\\" : "/")); for (let i = 0; i < dirs.length; i++) { if (dirs[i] != ".") { pathDir.append(dirs[i]); } } pathDir.normalize(); } else { // absolute path EnigmailFiles.initPath(pathDir, agentPath); } if (!(pathDir.isFile() /* && pathDir.isExecutable()*/ )) { throw Components.results.NS_ERROR_FAILURE; } agentPath = pathDir.QueryInterface(Ci.nsIFile); } catch (ex) { esvc.initializationError = EnigmailLocale.getString("gpgNotFound", [agentPath]); EnigmailLog.ERROR("enigmail.js: Enigmail.initialize: Error - " + esvc.initializationError + "\n"); throw Components.results.NS_ERROR_FAILURE; } } else { // Resolve relative path using PATH environment variable const envPath = esvc.environment.get("PATH"); agentPath = EnigmailFiles.resolvePath(agentName, envPath, EnigmailOS.isDosLike()); if (!agentPath && EnigmailOS.isDosLike()) { // DOS-like systems: search for GPG in c:\gnupg, c:\gnupg\bin, d:\gnupg, d:\gnupg\bin let gpgPath = "c:\\gnupg;c:\\gnupg\\bin;d:\\gnupg;d:\\gnupg\\bin"; agentPath = EnigmailFiles.resolvePath(agentName, gpgPath, EnigmailOS.isDosLike()); } if ((!agentPath) && EnigmailOS.isWin32) { // Look up in Windows Registry try { let gpgPath = EnigmailOS.getWinRegistryString("Software\\GNU\\GNUPG", "Install Directory", nsIWindowsRegKey.ROOT_KEY_LOCAL_MACHINE); agentPath = EnigmailFiles.resolvePath(agentName, gpgPath, EnigmailOS.isDosLike()); } catch (ex) {} if (!agentPath) { let gpgPath = gpgPath + "\\pub"; agentPath = EnigmailFiles.resolvePath(agentName, gpgPath, EnigmailOS.isDosLike()); } } if (!agentPath && !EnigmailOS.isDosLike()) { // Unix-like systems: check /usr/bin and /usr/local/bin let gpgPath = "/usr/bin:/usr/local/bin"; agentPath = EnigmailFiles.resolvePath(agentName, gpgPath, EnigmailOS.isDosLike()); } if (!agentPath) { esvc.initializationError = EnigmailLocale.getString("gpgNotInPath"); EnigmailLog.ERROR("enigmail.js: Enigmail: Error - " + esvc.initializationError + "\n"); throw Components.results.NS_ERROR_FAILURE; } agentPath = agentPath.QueryInterface(Ci.nsIFile); } EnigmailLog.CONSOLE("EnigmailAgentPath=" + EnigmailFiles.getFilePathDesc(agentPath) + "\n\n"); EnigmailGpgAgent.agentType = agentType; EnigmailGpgAgent.agentPath = agentPath; EnigmailGpg.setAgentPath(agentPath); EnigmailExecution.agentType = agentType; const command = agentPath; let args = []; if (agentType == "gpg") { args = ["--version", "--version", "--batch", "--no-tty", "--charset", "utf-8", "--display-charset", "utf-8"]; } let exitCode = -1; let outStr = ""; let errStr = ""; EnigmailLog.DEBUG("enigmail.js: Enigmail.setAgentPath: calling subprocess with '" + command.path + "'\n"); EnigmailLog.CONSOLE("enigmail> " + EnigmailFiles.formatCmdLine(command, args) + "\n"); const proc = { command: command, arguments: args, environment: EnigmailCore.getEnvList(), charset: null, done: function(result) { exitCode = result.exitCode; outStr = result.stdout; errStr = result.stderr; }, mergeStderr: false }; try { subprocess.call(proc).wait(); } catch (ex) { EnigmailLog.ERROR("enigmail.js: Enigmail.setAgentPath: subprocess.call failed with '" + ex.toString() + "'\n"); EnigmailLog.DEBUG(" enigmail> DONE with FAILURE\n"); throw ex; } EnigmailLog.DEBUG(" enigmail> DONE\n"); outStr = EnigmailSystem.convertNativeToUnicode(outStr); if (exitCode !== 0) { EnigmailLog.ERROR("enigmail.js: Enigmail.setAgentPath: gpg failed with exitCode " + exitCode + " msg='" + outStr + " " + errStr + "'\n"); throw Components.results.NS_ERROR_FAILURE; } EnigmailLog.CONSOLE(outStr + "\n"); // detection for Gpg4Win wrapper if (outStr.search(/^gpgwrap.*;/) === 0) { const outLines = outStr.split(/[\n\r]+/); const firstLine = outLines[0]; outLines.splice(0, 1); outStr = outLines.join("\n"); agentPath = firstLine.replace(/^.*;[ \t]*/, ""); EnigmailLog.CONSOLE("gpg4win-gpgwrapper detected; EnigmailAgentPath=" + agentPath + "\n\n"); } const versionParts = outStr.replace(/[\r\n].*/g, "").replace(/ *\(gpg4win.*\)/i, "").split(/ /); const gpgVersion = versionParts[versionParts.length - 1]; EnigmailLog.DEBUG("enigmail.js: detected GnuPG version '" + gpgVersion + "'\n"); EnigmailGpg.agentVersion = gpgVersion; if (!EnigmailGpg.getGpgFeature("version-supported")) { if (!domWindow) { domWindow = EnigmailWindows.getBestParentWin(); } EnigmailDialog.alert(domWindow, EnigmailLocale.getString("oldGpgVersion14", [gpgVersion])); throw Components.results.NS_ERROR_FAILURE; } EnigmailGpgAgent.gpgconfPath = EnigmailGpgAgent.resolveToolPath("gpgconf"); EnigmailGpgAgent.connGpgAgentPath = EnigmailGpgAgent.resolveToolPath("gpg-connect-agent"); EnigmailLog.DEBUG("enigmail.js: Enigmail.setAgentPath: gpgconf found: " + (EnigmailGpgAgent.gpgconfPath ? "yes" : "no") + "\n"); }, // resolve the path for GnuPG helper tools resolveToolPath: function(fileName) { if (EnigmailOS.isDosLike()) { fileName += ".exe"; } let filePath = cloneOrNull(EnigmailGpgAgent.agentPath); if (filePath) filePath = filePath.parent; if (filePath) { filePath.append(fileName); if (filePath.exists()) { filePath.normalize(); return filePath; } } const foundPath = EnigmailFiles.resolvePath(fileName, EnigmailCore.getEnigmailService().environment.get("PATH"), EnigmailOS.isDosLike()); if (foundPath) { foundPath.normalize(); } return foundPath; }, detectGpgAgent: function(domWindow, esvc) { EnigmailLog.DEBUG("enigmail.js: detectGpgAgent\n"); var gpgAgentInfo = esvc.environment.get("GPG_AGENT_INFO"); if (gpgAgentInfo && gpgAgentInfo.length > 0) { EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: GPG_AGENT_INFO variable available\n"); // env. variable suggests running gpg-agent EnigmailGpgAgent.gpgAgentInfo.preStarted = true; EnigmailGpgAgent.gpgAgentInfo.envStr = gpgAgentInfo; EnigmailGpgAgent.gpgAgentIsOptional = false; } else { EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: no GPG_AGENT_INFO variable set\n"); EnigmailGpgAgent.gpgAgentInfo.preStarted = false; var command = null; var outStr = ""; var errorStr = ""; var exitCode = -1; EnigmailGpgAgent.gpgAgentIsOptional = false; if (EnigmailGpg.getGpgFeature("autostart-gpg-agent")) { EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: gpg 2.0.16 or newer - not starting agent\n"); } else { if (EnigmailGpgAgent.connGpgAgentPath && EnigmailGpgAgent.connGpgAgentPath.isExecutable()) { // try to connect to a running gpg-agent EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: gpg-connect-agent is executable\n"); EnigmailGpgAgent.gpgAgentInfo.envStr = DUMMY_AGENT_INFO; command = EnigmailGpgAgent.connGpgAgentPath.QueryInterface(Ci.nsIFile); EnigmailLog.CONSOLE("enigmail> " + command.path + "\n"); try { subprocess.call({ command: command, environment: EnigmailCore.getEnvList(), stdin: "/echo OK\n", charset: null, done: function(result) { EnigmailLog.DEBUG("detectGpgAgent detection terminated with " + result.exitCode + "\n"); exitCode = result.exitCode; outStr = result.stdout; errorStr = result.stderr; if (result.stdout.substr(0, 2) == "OK") exitCode = 0; }, mergeStderr: false }).wait(); } catch (ex) { EnigmailLog.ERROR("enigmail.js: detectGpgAgent: " + command.path + " failed\n"); EnigmailLog.DEBUG(" enigmail> DONE with FAILURE\n"); exitCode = -1; } EnigmailLog.DEBUG(" enigmail> DONE\n"); if (exitCode === 0) { EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: found running gpg-agent\n"); return; } else { EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: no running gpg-agent. Output='" + outStr + "' error text='" + errorStr + "'\n"); } } // and finally try to start gpg-agent var commandFile = EnigmailGpgAgent.resolveToolPath("gpg-agent"); var agentProcess = null; if ((!commandFile) || (!commandFile.exists())) { commandFile = EnigmailGpgAgent.resolveToolPath("gpg-agent2"); } if (commandFile && commandFile.exists()) { command = commandFile.QueryInterface(Ci.nsIFile); } if (command === null) { EnigmailLog.ERROR("enigmail.js: detectGpgAgent: gpg-agent not found\n"); EnigmailDialog.alert(domWindow, EnigmailLocale.getString("gpgAgentNotStarted", [EnigmailGpg.agentVersion])); throw Components.results.NS_ERROR_FAILURE; } } if ((!EnigmailOS.isDosLike()) && (!EnigmailGpg.getGpgFeature("autostart-gpg-agent"))) { // create unique tmp file var ds = Cc[DIR_SERV_CONTRACTID].getService(); var dsprops = ds.QueryInterface(Ci.nsIProperties); var tmpFile = dsprops.get("TmpD", Ci.nsIFile); tmpFile.append("gpg-wrapper.tmp"); tmpFile.createUnique(tmpFile.NORMAL_FILE_TYPE, DEFAULT_FILE_PERMS); let args = [command.path, tmpFile.path, "--sh", "--no-use-standard-socket", "--daemon", "--default-cache-ttl", (EnigmailPassword.getMaxIdleMinutes() * 60).toString(), "--max-cache-ttl", "999999" ]; // ca. 11 days try { var process = Cc["@mozilla.org/process/util;1"].createInstance(Ci.nsIProcess); var exec = EnigmailApp.getInstallLocation().clone(); exec.append("wrappers"); exec.append("gpg-agent-wrapper.sh"); process.init(exec); process.run(true, args, args.length); if (!tmpFile.exists()) { EnigmailLog.ERROR("enigmail.js: detectGpgAgent no temp file created\n"); } else { outStr = EnigmailFiles.readFile(tmpFile); tmpFile.remove(false); exitCode = 0; } } catch (ex) { EnigmailLog.ERROR("enigmail.js: detectGpgAgent: failed with '" + ex + "'\n"); exitCode = -1; } if (exitCode === 0) { EnigmailGpgAgent.gpgAgentInfo.envStr = extractAgentInfo(outStr); EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: started -> " + EnigmailGpgAgent.gpgAgentInfo.envStr + "\n"); EnigmailGpgAgent.gpgAgentProcess = EnigmailGpgAgent.gpgAgentInfo.envStr.split(":")[1]; } else { EnigmailLog.ERROR("enigmail.js: detectGpgAgent: gpg-agent output: " + outStr + "\n"); EnigmailDialog.alert(domWindow, EnigmailLocale.getString("gpgAgentNotStarted", [EnigmailGpg.agentVersion])); throw Components.results.NS_ERROR_FAILURE; } } else { EnigmailGpgAgent.gpgAgentInfo.envStr = DUMMY_AGENT_INFO; var envFile = Components.classes[NS_LOCAL_FILE_CONTRACTID].createInstance(Ci.nsIFile); EnigmailFiles.initPath(envFile, EnigmailGpgAgent.determineGpgHomeDir(esvc)); envFile.append("gpg-agent.conf"); var data = "default-cache-ttl " + (EnigmailPassword.getMaxIdleMinutes() * 60) + "\n"; data += "max-cache-ttl 999999"; if (!envFile.exists()) { try { var flags = 0x02 | 0x08 | 0x20; var fileOutStream = Cc[NS_LOCALFILEOUTPUTSTREAM_CONTRACTID].createInstance(Ci.nsIFileOutputStream); fileOutStream.init(envFile, flags, 384, 0); // 0600 fileOutStream.write(data, data.length); fileOutStream.flush(); fileOutStream.close(); } catch (ex) {} // ignore file write errors } } } EnigmailLog.DEBUG("enigmail.js: detectGpgAgent: GPG_AGENT_INFO='" + EnigmailGpgAgent.gpgAgentInfo.envStr + "'\n"); }, determineGpgHomeDir: function(esvc) { let homeDir = esvc.environment.get("GNUPGHOME"); if (!homeDir && EnigmailOS.isWin32) { homeDir = EnigmailOS.getWinRegistryString("Software\\GNU\\GNUPG", "HomeDir", nsIWindowsRegKey.ROOT_KEY_CURRENT_USER); if (!homeDir) { homeDir = esvc.environment.get("USERPROFILE") || esvc.environment.get("SystemRoot"); if (homeDir) homeDir += "\\Application Data\\GnuPG"; } if (!homeDir) homeDir = "C:\\gnupg"; } if (!homeDir) homeDir = esvc.environment.get("HOME") + "/.gnupg"; return homeDir; }, finalize: function() { if (EnigmailGpgAgent.gpgAgentProcess) { EnigmailLog.DEBUG("gpgAgent.jsm: EnigmailGpgAgent.finalize: stopping gpg-agent PID=" + EnigmailGpgAgent.gpgAgentProcess + "\n"); try { const libc = ctypes.open(subprocess.getPlatformValue(0)); //int kill(pid_t pid, int sig); const kill = libc.declare("kill", ctypes.default_abi, ctypes.int, ctypes.int32_t, ctypes.int); kill(parseInt(EnigmailGpgAgent.gpgAgentProcess, 10), 15); } catch (ex) { EnigmailLog.ERROR("gpgAgent.jsm: EnigmailGpgAgent.finalize ERROR: " + ex + "\n"); } } } }; enigmail/package/hash.jsm 0000664 0000000 0000000 00000007704 12667016244 0015714 0 ustar 00root root 0000000 0000000 /*global Components: false */ /*jshint -W097 */ /* * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ "use strict"; var EXPORTED_SYMBOLS = ["EnigmailHash"]; const Cu = Components.utils; Cu.import("resource://enigmail/log.jsm"); /*global EnigmailLog: false */ Cu.import("resource://enigmail/windows.jsm"); /*global EnigmailWindows: false */ Cu.import("resource://enigmail/locale.jsm"); /*global EnigmailLocale: false */ Cu.import("resource://enigmail/prefs.jsm"); /*global EnigmailPrefs: false */ Cu.import("resource://enigmail/encryption.jsm"); /*global EnigmailEncryption: false */ Cu.import("resource://enigmail/dialog.jsm"); /*global EnigmailDialog: false */ const Ci = Components.interfaces; const nsIEnigmail = Ci.nsIEnigmail; const keyAlgorithms = []; const mimeHashAlgorithms = [null, "sha1", "ripemd160", "sha256", "sha384", "sha512", "sha224", "md5"]; const EnigmailHash = { determineAlgorithm: function(win, uiFlags, fromMailAddr, hashAlgoObj) { EnigmailLog.DEBUG("hash.jsm: determineAlgorithm\n"); if (!win) { win = EnigmailWindows.getMostRecentWindow(); } const sendFlags = nsIEnigmail.SEND_TEST | nsIEnigmail.SEND_SIGNED; const hashAlgo = mimeHashAlgorithms[EnigmailPrefs.getPref("mimeHashAlgorithm")]; if (typeof(keyAlgorithms[fromMailAddr]) != "string") { // hash algorithm not yet known const testUiFlags = nsIEnigmail.UI_TEST; const listener = { stdoutData: "", stderrData: "", exitCode: -1, stdin: function(pipe) { pipe.write("Dummy Test"); pipe.close(); }, stdout: function(data) { this.stdoutData += data; }, stderr: function(data) { this.stderrData += data; }, done: function(exitCode) { this.exitCode = exitCode; } }; const proc = EnigmailEncryption.encryptMessageStart(win, testUiFlags, fromMailAddr, "", "", hashAlgo, sendFlags, listener, {}, {}); if (!proc) { return 1; } proc.wait(); const msgText = listener.stdoutData; const exitCode = listener.exitCode; const retStatusObj = {}; let exitCode2 = EnigmailEncryption.encryptMessageEnd(fromMailAddr, listener.stderrData, exitCode, testUiFlags, sendFlags, 10, retStatusObj); if ((exitCode2 === 0) && !msgText) exitCode2 = 1; // if (exitCode2 > 0) exitCode2 = -exitCode2; if (exitCode2 !== 0) { // Abormal return if (retStatusObj.statusFlags & nsIEnigmail.BAD_PASSPHRASE) { // "Unremember" passphrase on error return retStatusObj.errorMsg = EnigmailLocale.getString("badPhrase"); } EnigmailDialog.alert(win, retStatusObj.errorMsg); return exitCode2; } let hashAlgorithm = "sha1"; // default as defined in RFC 4880, section 7 is MD5 -- but that's outdated const m = msgText.match(/^(Hash: )(.*)$/m); if (m && (m.length > 2) && (m[1] == "Hash: ")) { hashAlgorithm = m[2].toLowerCase(); } else { EnigmailLog.DEBUG("hash.jsm: determineAlgorithm: no hashAlgorithm specified - using MD5\n"); } for (let i = 1; i < mimeHashAlgorithms.length; i++) { if (mimeHashAlgorithms[i] === hashAlgorithm) { EnigmailLog.DEBUG("hash.jsm: determineAlgorithm: found hashAlgorithm " + hashAlgorithm + "\n"); keyAlgorithms[fromMailAddr] = hashAlgorithm; hashAlgoObj.value = hashAlgorithm; return 0; } } EnigmailLog.ERROR("hash.jsm: determineAlgorithm: no hashAlgorithm found\n"); return 2; } else { EnigmailLog.DEBUG("hash.jsm: determineAlgorithm: hashAlgorithm " + keyAlgorithms[fromMailAddr] + " is cached\n"); hashAlgoObj.value = keyAlgorithms[fromMailAddr]; } return 0; } }; enigmail/package/httpProxy.jsm 0000664 0000000 0000000 00000005524 12667016244 0017010 0 ustar 00root root 0000000 0000000 /*global Components: false */ /*jshint -W097 */ /* * This Source Code Form is subject to the terms of the Mozilla Public * License, v. 2.0. If a copy of the MPL was not distributed with this * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ "use strict"; var EXPORTED_SYMBOLS = ["EnigmailHttpProxy"]; const Cc = Components.classes; const Ci = Components.interfaces; const Cu = Components.utils; Cu.import("resource://enigmail/prefs.jsm"); /*global EnigmailPrefs: false */ const NS_PREFS_SERVICE_CID = "@mozilla.org/preferences-service;1"; function getPasswdForHost(hostname, userObj, passwdObj) { var loginmgr = Cc["@mozilla.org/login-manager;1"].getService(Ci.nsILoginManager); // search HTTP password 1st var logins = loginmgr.findLogins({}, "http://" + hostname, "", ""); if (logins.length > 0) { userObj.value = logins[0].username; passwdObj.value = logins[0].password; return true; } // look for any other password for same host logins = loginmgr.getAllLogins({}); for (var i = 0; i < logins.lenth; i++) { if (hostname == logins[i].hostname.replace(/^.*:\/\//, "")) { userObj.value = logins[i].username; passwdObj.value = logins[i].password; return true; } } return false; } const EnigmailHttpProxy = { /** * get Proxy for a given hostname as configured in Mozilla * * @hostname: String - the host to check if there is a proxy. * * @return: String - proxy host URL to provide to GnuPG * null if no proxy required */ getHttpProxy: function(hostName) { var proxyHost = null; if (EnigmailPrefs.getPref("respectHttpProxy")) { // determine proxy host var prefsSvc = Cc[NS_PREFS_SERVICE_CID].getService(Ci.nsIPrefService); var prefRoot = prefsSvc.getBranch(null); var useProxy = prefRoot.getIntPref("network.proxy.type"); if (useProxy == 1) { var proxyHostName = prefRoot.getCharPref("network.proxy.http"); var proxyHostPort = prefRoot.getIntPref("network.proxy.http_port"); var noProxy = prefRoot.getCharPref("network.proxy.no_proxies_on").split(/[ ,]/); for (var i = 0; i < noProxy.length; i++) { var proxySearch = new RegExp(noProxy[i].replace(/\./g, "\\.").replace(/\*/g, ".*") + "$", "i"); if (noProxy[i] && hostName.search(proxySearch) >= 0) { i = noProxy.length + 1; proxyHostName = null; } } if (proxyHostName) { var userObj = {}; var passwdObj = {}; if (getPasswdForHost(proxyHostName, userObj, passwdObj)) { proxyHostName = userObj.value + ":" + passwdObj.value + "@" + proxyHostName; } } if (proxyHostName && proxyHostPort) { proxyHost = "http://" + proxyHostName + ":" + proxyHostPort; } } } return proxyHost; } }; enigmail/package/install.rdf 0000664 0000000 0000000 00000003612 12667016244 0016413 0 ustar 00root root 0000000 0000000 '; } else if (lines[i] == "-- ") { preface += ''; isSignature = true; } lines[i] = preface + gTxtConverter.scanTXT(lines[i].substr(logLineStart.value), convFlags); } var r = '' : '') + '' + lines.join("\n") + (isSignature ? '