pax_global_header 0000666 0000000 0000000 00000000064 13343027545 0014520 g ustar 00root root 0000000 0000000 52 comment=92e13d818fb64603724e184bf2cd6acfab1c09a1
enigmail-2.0.8/ 0000775 0000000 0000000 00000000000 13343027545 0013314 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/.eslintrc.js 0000664 0000000 0000000 00000003156 13343027545 0015560 0 ustar 00root root 0000000 0000000 module.exports = {
"parserOptions": {
"ecmaVersion": 2017
},
"rules": {
"linebreak-style": [
2,
"unix"
],
"semi": [
2,
"always"
],
"strict": [2, "global"],
"no-unused-vars": 0,
"no-empty": 0,
"comma-dangle": 2,
"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-labels": 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-useless-escape": 1,
"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",
"globals": {
"ChromeUtils": true,
"Components": true,
"Cc": true,
"Cu": true,
"Ci": true
}
};
enigmail-2.0.8/.gitattributes 0000664 0000000 0000000 00000000053 13343027545 0016205 0 ustar 00root root 0000000 0000000 *.xul text
*.rdf text
*.js text
*.jsm text
enigmail-2.0.8/.gitignore 0000664 0000000 0000000 00000001015 13343027545 0015301 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
/package/tests/jsunit.result
unused.txt
/package/tests/enigdbug.txt
# vi tmp files:
*.swp
*.swo
# emacs tmp files:
\#*\#
.dir-locals.el
# backup files:
*~
# vagrant files:
provisioning/.vagrant
# other local configuration files:
.ackrc
.envrc
enigmail-2.0.8/.gitlab-ci.yml 0000664 0000000 0000000 00000004260 13343027545 0015752 0 ustar 00root root 0000000 0000000 image: node:10-stretch
build:
script:
- apt update -y -qq
- apt install zip -y -qq
- ./configure
- make
lint:
before_script:
- npm install -g eslint
script:
- ./configure
- make eslint
check:
script:
- ./configure
- make check
test:
before_script:
- export TBPROFILE="$(pwd)/tb-test-profile"
- apt update -y -qq
- apt install thunderbird gnupg zip unzip curl xvfb libgtk-3-0 -y -qq
- mkdir -p $TBPROFILE/extensions tmp jsunit
- printf '%s/build/dist/' "$(pwd)" > "$TBPROFILE/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}"
- printf 'user_pref("extensions.autoDisableScopes", 14);\n' > "$TBPROFILE/prefs.js"
- printf 'user_pref("browser.dom.window.dump.enabled", true);\n' >> "$TBPROFILE/prefs.js"
- printf 'user_pref("extensions.update.enabled", false);\n' >> "$TBPROFILE/prefs.js"
- printf 'user_pref("extensions.update.autoUpdateDefault", false);\n' >> "$TBPROFILE/prefs.js"
- printf 'user_pref("extensions.blocklist.enabled", false);\n' >> "$TBPROFILE/prefs.js"
- printf 'user_pref("app.update.enabled", false);\n' >> "$TBPROFILE/prefs.js"
- printf 'user_pref("extensions.enigmail.logDirectory", "%s");\n' $(pwd)/tmp >> "$TBPROFILE/prefs.js"
- curl -s -o "$TBPROFILE/extensions/jsunit@enigmail.net.xpi" https://www.enigmail.net/jsunit/jsunit-0.1.6.xpi
- export TBDOWNLOAD=$(curl -s 'https://download.mozilla.org/?product=thunderbird-beta-latest&os=linux64&lang=en-US' | sed -E 's/(.*href=")([^"]+)(".*)/\2/')
- curl -s -o thunderbird.tar.bz2 $TBDOWNLOAD
- tar -xjvf thunderbird.tar.bz2
- thunderbird/thunderbird --version
script:
- export TBPROFILE="$(pwd)/tb-test-profile"
- export TMPDIR="$(pwd)/tmp"
- export XAUTHORITY="$(pwd)/tmp/.Xauthority"
- export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
- ./configure --enable-tests --with-tb-path=`printf '%s/thunderbird/thunderbird' "$(pwd)"` --with-tb-args="--headless --profile $TBPROFILE"
- make dirs xpi
- cat config/autoconf.mk
- ls $TBPROFILE
- cat $TBPROFILE/prefs.js
- USER=root xvfb-run -a -f "$XAUTHORITY" $(which make) unit
artifacts:
paths:
- config
- tmp
- tb-test-profile
enigmail-2.0.8/.jsbeautifyrc 0000664 0000000 0000000 00000001150 13343027545 0016004 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-2.0.8/.travis.yml 0000664 0000000 0000000 00000000500 13343027545 0015420 0 ustar 00root root 0000000 0000000 language: c
sudo: required
compiler:
- gcc
install:
provisioning/provision-travis.sh
script:
- ./configure --with-tb-path=$(which thunderbird)
- make > /dev/null 2>&1
- Xvfb :99 -screen 0 1024x768x24 >/dev/null 2>&1 &
- export DISPLAY=:99
- make eslint
- ./test.sh
after_failure:
- cat test_output.log
enigmail-2.0.8/COMPILING 0000664 0000000 0000000 00000001015 13343027545 0014555 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 https://eslint.org)
Building
--------
Execute the following commands:
./configure
make
The resulting XPI file can be found in the "build" directory.
enigmail-2.0.8/LICENSE 0000664 0000000 0000000 00000041033 13343027545 0014322 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 https://mozilla.org/MPL/2.0/.
Mozilla Public License Version 2.0
==================================
1. Definitions
--------------
1.1. "Contributor"
means each individual or legal entity that creates, contributes to
the creation of, or owns Covered Software.
1.2. "Contributor Version"
means the combination of the Contributions of others (if any) used
by a Contributor and that particular Contributor's Contribution.
1.3. "Contribution"
means Covered Software of a particular Contributor.
1.4. "Covered Software"
means Source Code Form to which the initial Contributor has attached
the notice in Exhibit A, the Executable Form of such Source Code
Form, and Modifications of such Source Code Form, in each case
including portions thereof.
1.5. "Incompatible With Secondary Licenses"
means
(a) that the initial Contributor has attached the notice described
in Exhibit B to the Covered Software; or
(b) that the Covered Software was made available under the terms of
version 1.1 or earlier of the License, but not also under the
terms of a Secondary License.
1.6. "Executable Form"
means any form of the work other than Source Code Form.
1.7. "Larger Work"
means a work that combines Covered Software with other material, in
a separate file or files, that is not Covered Software.
1.8. "License"
means this document.
1.9. "Licensable"
means having the right to grant, to the maximum extent possible,
whether at the time of the initial grant or subsequently, any and
all of the rights conveyed by this License.
1.10. "Modifications"
means any of the following:
(a) any file in Source Code Form that results from an addition to,
deletion from, or modification of the contents of Covered
Software; or
(b) any new file in Source Code Form that contains any Covered
Software.
1.11. "Patent Claims" of a Contributor
means any patent claim(s), including without limitation, method,
process, and apparatus claims, in any patent Licensable by such
Contributor that would be infringed, but for the grant of the
License, by the making, using, selling, offering for sale, having
made, import, or transfer of either its Contributions or its
Contributor Version.
1.12. "Secondary License"
means either the GNU General Public License, Version 2.0, the GNU
Lesser General Public License, Version 2.1, the GNU Affero General
Public License, Version 3.0, or any later versions of those
licenses.
1.13. "Source Code Form"
means the form of the work preferred for making modifications.
1.14. "You" (or "Your")
means an individual or a legal entity exercising rights under this
License. For legal entities, "You" includes any entity that
controls, is controlled by, or is under common control with You. For
purposes of this definition, "control" means (a) the power, direct
or indirect, to cause the direction or management of such entity,
whether by contract or otherwise, or (b) ownership of more than
fifty percent (50%) of the outstanding shares or beneficial
ownership of such entity.
2. License Grants and Conditions
--------------------------------
2.1. Grants
Each Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license:
(a) under intellectual property rights (other than patent or trademark)
Licensable by such Contributor to use, reproduce, make available,
modify, display, perform, distribute, and otherwise exploit its
Contributions, either on an unmodified basis, with Modifications, or
as part of a Larger Work; and
(b) under Patent Claims of such Contributor to make, use, sell, offer
for sale, have made, import, and otherwise transfer either its
Contributions or its Contributor Version.
2.2. Effective Date
The licenses granted in Section 2.1 with respect to any Contribution
become effective for each Contribution on the date the Contributor first
distributes such Contribution.
2.3. Limitations on Grant Scope
The licenses granted in this Section 2 are the only rights granted under
this License. No additional rights or licenses will be implied from the
distribution or licensing of Covered Software under this License.
Notwithstanding Section 2.1(b) above, no patent license is granted by a
Contributor:
(a) for any code that a Contributor has removed from Covered Software;
or
(b) for infringements caused by: (i) Your and any other third party's
modifications of Covered Software, or (ii) the combination of its
Contributions with other software (except as part of its Contributor
Version); or
(c) under Patent Claims infringed by Covered Software in the absence of
its Contributions.
This License does not grant any rights in the trademarks, service marks,
or logos of any Contributor (except as may be necessary to comply with
the notice requirements in Section 3.4).
2.4. Subsequent Licenses
No Contributor makes additional grants as a result of Your choice to
distribute the Covered Software under a subsequent version of this
License (see Section 10.2) or under the terms of a Secondary License (if
permitted under the terms of Section 3.3).
2.5. Representation
Each Contributor represents that the Contributor believes its
Contributions are its original creation(s) or it has sufficient rights
to grant the rights to its Contributions conveyed by this License.
2.6. Fair Use
This License is not intended to limit any rights You have under
applicable copyright doctrines of fair use, fair dealing, or other
equivalents.
2.7. Conditions
Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
in Section 2.1.
3. Responsibilities
-------------------
3.1. Distribution of Source Form
All distribution of Covered Software in Source Code Form, including any
Modifications that You create or to which You contribute, must be under
the terms of this License. You must inform recipients that the Source
Code Form of the Covered Software is governed by the terms of this
License, and how they can obtain a copy of this License. You may not
attempt to alter or restrict the recipients' rights in the Source Code
Form.
3.2. Distribution of Executable Form
If You distribute Covered Software in Executable Form then:
(a) such Covered Software must also be made available in Source Code
Form, as described in Section 3.1, and You must inform recipients of
the Executable Form how they can obtain a copy of such Source Code
Form by reasonable means in a timely manner, at a charge no more
than the cost of distribution to the recipient; and
(b) You may distribute such Executable Form under the terms of this
License, or sublicense it under different terms, provided that the
license for the Executable Form does not attempt to limit or alter
the recipients' rights in the Source Code Form under this License.
3.3. Distribution of a Larger Work
You may create and distribute a Larger Work under terms of Your choice,
provided that You also comply with the requirements of this License for
the Covered Software. If the Larger Work is a combination of Covered
Software with a work governed by one or more Secondary Licenses, and the
Covered Software is not Incompatible With Secondary Licenses, this
License permits You to additionally distribute such Covered Software
under the terms of such Secondary License(s), so that the recipient of
the Larger Work may, at their option, further distribute the Covered
Software under the terms of either this License or such Secondary
License(s).
3.4. Notices
You may not remove or alter the substance of any license notices
(including copyright notices, patent notices, disclaimers of warranty,
or limitations of liability) contained within the Source Code Form of
the Covered Software, except that You may alter any license notices to
the extent required to remedy known factual inaccuracies.
3.5. Application of Additional Terms
You may choose to offer, and to charge a fee for, warranty, support,
indemnity or liability obligations to one or more recipients of Covered
Software. However, You may do so only on Your own behalf, and not on
behalf of any Contributor. You must make it absolutely clear that any
such warranty, support, indemnity, or liability obligation is offered by
You alone, and You hereby agree to indemnify every Contributor for any
liability incurred by such Contributor as a result of warranty, support,
indemnity or liability terms You offer. You may include additional
disclaimers of warranty and limitations of liability specific to any
jurisdiction.
4. Inability to Comply Due to Statute or Regulation
---------------------------------------------------
If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Software due to
statute, judicial order, or regulation then You must: (a) comply with
the terms of this License to the maximum extent possible; and (b)
describe the limitations and the code they affect. Such description must
be placed in a text file included with all distributions of the Covered
Software under this License. Except to the extent prohibited by statute
or regulation, such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.
5. Termination
--------------
5.1. The rights granted under this License will terminate automatically
if You fail to comply with any of its terms. However, if You become
compliant, then the rights granted under this License from a particular
Contributor are reinstated (a) provisionally, unless and until such
Contributor explicitly and finally terminates Your grants, and (b) on an
ongoing basis, if such Contributor fails to notify You of the
non-compliance by some reasonable means prior to 60 days after You have
come back into compliance. Moreover, Your grants from a particular
Contributor are reinstated on an ongoing basis if such Contributor
notifies You of the non-compliance by some reasonable means, this is the
first time You have received notice of non-compliance with this License
from such Contributor, and You become compliant prior to 30 days after
Your receipt of the notice.
5.2. If You initiate litigation against any entity by asserting a patent
infringement claim (excluding declaratory judgment actions,
counter-claims, and cross-claims) alleging that a Contributor Version
directly or indirectly infringes any patent, then the rights granted to
You by any and all Contributors for the Covered Software under Section
2.1 of this License shall terminate.
5.3. In the event of termination under Sections 5.1 or 5.2 above, all
end user license agreements (excluding distributors and resellers) which
have been validly granted by You or Your distributors under this License
prior to termination shall survive termination.
************************************************************************
* *
* 6. Disclaimer of Warranty *
* ------------------------- *
* *
* Covered Software is provided under this License on an "as is" *
* basis, without warranty of any kind, either expressed, implied, or *
* statutory, including, without limitation, warranties that the *
* Covered Software is free of defects, merchantable, fit for a *
* particular purpose or non-infringing. The entire risk as to the *
* quality and performance of the Covered Software is with You. *
* Should any Covered Software prove defective in any respect, You *
* (not any Contributor) assume the cost of any necessary servicing, *
* repair, or correction. This disclaimer of warranty constitutes an *
* essential part of this License. No use of any Covered Software is *
* authorized under this License except under this disclaimer. *
* *
************************************************************************
************************************************************************
* *
* 7. Limitation of Liability *
* -------------------------- *
* *
* Under no circumstances and under no legal theory, whether tort *
* (including negligence), contract, or otherwise, shall any *
* Contributor, or anyone who distributes Covered Software as *
* permitted above, be liable to You for any direct, indirect, *
* special, incidental, or consequential damages of any character *
* including, without limitation, damages for lost profits, loss of *
* goodwill, work stoppage, computer failure or malfunction, or any *
* and all other commercial damages or losses, even if such party *
* shall have been informed of the possibility of such damages. This *
* limitation of liability shall not apply to liability for death or *
* personal injury resulting from such party's negligence to the *
* extent applicable law prohibits such limitation. Some *
* jurisdictions do not allow the exclusion or limitation of *
* incidental or consequential damages, so this exclusion and *
* limitation may not apply to You. *
* *
************************************************************************
8. Litigation
-------------
Any litigation relating to this License may be brought only in the
courts of a jurisdiction where the defendant maintains its principal
place of business and such litigation shall be governed by laws of that
jurisdiction, without reference to its conflict-of-law provisions.
Nothing in this Section shall prevent a party's ability to bring
cross-claims or counter-claims.
9. Miscellaneous
----------------
This License represents the complete agreement concerning the subject
matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent
necessary to make it enforceable. Any law or regulation which provides
that the language of a contract shall be construed against the drafter
shall not be used to construe this License against a Contributor.
10. Versions of the License
---------------------------
10.1. New Versions
Mozilla Foundation is the license steward. Except as provided in Section
10.3, no one other than the license steward has the right to modify or
publish new versions of this License. Each version will be given a
distinguishing version number.
10.2. Effect of New Versions
You may distribute the Covered Software under the terms of the version
of the License under which You originally received the Covered Software,
or under the terms of any subsequent version published by the license
steward.
10.3. Modified Versions
If you create software not governed by this License, and you want to
create a new license for such software, you may create and use a
modified version of this License if you rename the license and remove
any references to the name of the license steward (except to note that
such modified license differs from this License).
10.4. Distributing Source Code Form that is Incompatible With Secondary
Licenses
If You choose to distribute Source Code Form that is Incompatible With
Secondary Licenses under the terms of this version of the License, the
notice described in Exhibit B of this License must be attached.
Exhibit A - Source Code Form License Notice
-------------------------------------------
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 https://mozilla.org/MPL/2.0/.
If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely to look
for such a notice.
You may add additional accurate notices of copyright ownership.
Exhibit B - "Incompatible With Secondary Licenses" Notice
---------------------------------------------------------
This Source Code Form is "Incompatible With Secondary Licenses", as
defined by the Mozilla Public License, v. 2.0.
enigmail-2.0.8/Makefile 0000664 0000000 0000000 00000002051 13343027545 0014752 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 https://mozilla.org/MPL/2.0/.
XPI_MODULE = enigmail
XPI_MODULE_VERS = 2.0.8
DEPTH = .
include $(DEPTH)/config/autoconf.mk
DIRS = ipc ui package lang stdlib
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: $(DIRS)
$(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 ipc/tests
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-2.0.8/README.md 0000664 0000000 0000000 00000000316 13343027545 0014573 0 ustar 00root root 0000000 0000000 [](https://travis-ci.org/twtiger/enigmail)
Instructions for setting up the developer environment are in the provisioning directory.
enigmail-2.0.8/build.sh 0000775 0000000 0000000 00000000523 13343027545 0014752 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 https://mozilla.org/MPL/2.0/.
#
export TB_PATH=${TB_PATH:-`which thunderbird`}
make clean
make distclean
./configure --with-tb-path=$TB_PATH
make
enigmail-2.0.8/config.guess 0000775 0000000 0000000 00000127172 13343027545 0015646 0 ustar 00root root 0000000 0000000 #! /bin/sh
# Attempt to guess a canonical system name.
# Copyright 1992-2013 Free Software Foundation, Inc.
timestamp='2018-07-10'
# 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 .
#
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that
# program. This Exception is an additional permission under section 7
# of the GNU General Public License, version 3 ("GPLv3").
#
# Originally written by Per Bothner.
#
# You can get the latest version of this script from:
# https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
#
# Please send patches with a ChangeLog entry to config-patches@gnu.org.
me=`echo "$0" | sed -e 's,.*/,,'`
usage="\
Usage: $0 [OPTION]
Output the configuration name of the system \`$me' is run on.
Operation modes:
-h, --help print this help, then exit
-t, --time-stamp print date of last modification, then exit
-v, --version print version number, then exit
Report bugs and patches to ."
version="\
GNU config.guess ($timestamp)
Originally written by Per Bothner.
Copyright 1992-2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
help="
Try \`$me --help' for more information."
# Parse command line
while test $# -gt 0 ; do
case $1 in
--time-stamp | --time* | -t )
echo "$timestamp" ; exit ;;
--version | -v )
echo "$version" ; exit ;;
--help | --h* | -h )
echo "$usage"; exit ;;
-- ) # Stop option processing
shift; break ;;
- ) # Use stdin as input.
break ;;
-* )
echo "$me: invalid option $1$help" >&2
exit 1 ;;
* )
break ;;
esac
done
if test $# != 0; then
echo "$me: too many arguments$help" >&2
exit 1
fi
trap 'exit 1' 1 2 15
# CC_FOR_BUILD -- compiler used by this script. Note that the use of a
# compiler to aid in system detection is discouraged as it requires
# temporary files to be created and, as you can see below, it is a
# headache to deal with in a portable fashion.
# Historically, `CC_FOR_BUILD' used to be named `HOST_CC'. We still
# use `HOST_CC' if defined, but it is deprecated.
# Portable tmp directory creation inspired by the Autoconf team.
set_cc_for_build='
trap "exitcode=\$?; (rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null) && exit \$exitcode" 0 ;
trap "rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null; exit 1" 1 2 13 15 ;
: ${TMPDIR=/tmp} ;
{ tmp=`(umask 077 && mktemp -d "$TMPDIR/cgXXXXXX") 2>/dev/null` && test -n "$tmp" && test -d "$tmp" ; } ||
{ test -n "$RANDOM" && tmp=$TMPDIR/cg$$-$RANDOM && (umask 077 && mkdir $tmp) ; } ||
{ tmp=$TMPDIR/cg-$$ && (umask 077 && mkdir $tmp) && echo "Warning: creating insecure temp directory" >&2 ; } ||
{ echo "$me: cannot create a temporary directory in $TMPDIR" >&2 ; exit 1 ; } ;
dummy=$tmp/dummy ;
tmpfiles="$dummy.c $dummy.o $dummy.rel $dummy" ;
case $CC_FOR_BUILD,$HOST_CC,$CC in
,,) echo "int x;" > $dummy.c ;
for c in cc gcc c89 c99 ; do
if ($c -c -o $dummy.o $dummy.c) >/dev/null 2>&1 ; then
CC_FOR_BUILD="$c"; break ;
fi ;
done ;
if test x"$CC_FOR_BUILD" = x ; then
CC_FOR_BUILD=no_compiler_found ;
fi
;;
,,*) CC_FOR_BUILD=$CC ;;
,*,*) CC_FOR_BUILD=$HOST_CC ;;
esac ; set_cc_for_build= ;'
# This is needed to find uname on a Pyramid OSx when run in the BSD universe.
# (ghazi@noc.rutgers.edu 1994-08-24)
if (test -f /.attbin/uname) >/dev/null 2>&1 ; then
PATH=$PATH:/.attbin ; export PATH
fi
UNAME_MACHINE=`(uname -m) 2>/dev/null` || UNAME_MACHINE=unknown
UNAME_RELEASE=`(uname -r) 2>/dev/null` || UNAME_RELEASE=unknown
UNAME_SYSTEM=`(uname -s) 2>/dev/null` || UNAME_SYSTEM=unknown
UNAME_VERSION=`(uname -v) 2>/dev/null` || UNAME_VERSION=unknown
# Note: order is significant - the case branches are not exclusive.
case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in
*:NetBSD:*:*)
# NetBSD (nbsd) targets should (where applicable) match one or
# more of the tuples: *-*-netbsdelf*, *-*-netbsdaout*,
# *-*-netbsdecoff* and *-*-netbsd*. For targets that recently
# switched to ELF, *-*-netbsd* would select the old
# object file format. This provides both forward
# compatibility and a consistent mechanism for selecting the
# object file format.
#
# Note: NetBSD doesn't particularly care about the vendor
# portion of the name. We always set it to "unknown".
sysctl="sysctl -n hw.machine_arch"
UNAME_MACHINE_ARCH=`(/sbin/$sysctl 2>/dev/null || \
/usr/sbin/$sysctl 2>/dev/null || echo unknown)`
case "${UNAME_MACHINE_ARCH}" in
armeb) machine=armeb-unknown ;;
arm*) machine=arm-unknown ;;
sh3el) machine=shl-unknown ;;
sh3eb) machine=sh-unknown ;;
sh5el) machine=sh5le-unknown ;;
*) machine=${UNAME_MACHINE_ARCH}-unknown ;;
esac
# The Operating System including object format, if it has switched
# to ELF recently, or will in the future.
case "${UNAME_MACHINE_ARCH}" in
arm*|i386|m68k|ns32k|sh3*|sparc|vax)
eval $set_cc_for_build
if echo __ELF__ | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ELF__
then
# Once all utilities can be ECOFF (netbsdecoff) or a.out (netbsdaout).
# Return netbsd for either. FIX?
os=netbsd
else
os=netbsdelf
fi
;;
*)
os=netbsd
;;
esac
# The OS release
# Debian GNU/NetBSD machines have a different userland, and
# thus, need a distinct triplet. However, they do not need
# kernel version information, so it can be replaced with a
# suitable tag, in the style of linux-gnu.
case "${UNAME_VERSION}" in
Debian*)
release='-gnu'
;;
*)
release=`echo ${UNAME_RELEASE}|sed -e 's/[-_].*/\./'`
;;
esac
# Since CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM:
# contains redundant information, the shorter form:
# CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM is used.
echo "${machine}-${os}${release}"
exit ;;
*:Bitrig:*:*)
UNAME_MACHINE_ARCH=`arch | sed 's/Bitrig.//'`
echo ${UNAME_MACHINE_ARCH}-unknown-bitrig${UNAME_RELEASE}
exit ;;
*:OpenBSD:*:*)
UNAME_MACHINE_ARCH=`arch | sed 's/OpenBSD.//'`
echo ${UNAME_MACHINE_ARCH}-unknown-openbsd${UNAME_RELEASE}
exit ;;
*:ekkoBSD:*:*)
echo ${UNAME_MACHINE}-unknown-ekkobsd${UNAME_RELEASE}
exit ;;
*:SolidBSD:*:*)
echo ${UNAME_MACHINE}-unknown-solidbsd${UNAME_RELEASE}
exit ;;
macppc:MirBSD:*:*)
echo powerpc-unknown-mirbsd${UNAME_RELEASE}
exit ;;
*:MirBSD:*:*)
echo ${UNAME_MACHINE}-unknown-mirbsd${UNAME_RELEASE}
exit ;;
alpha:OSF1:*:*)
case $UNAME_RELEASE in
*4.0)
UNAME_RELEASE=`/usr/sbin/sizer -v | awk '{print $3}'`
;;
*5.*)
UNAME_RELEASE=`/usr/sbin/sizer -v | awk '{print $4}'`
;;
esac
# According to Compaq, /usr/sbin/psrinfo has been available on
# OSF/1 and Tru64 systems produced since 1995. I hope that
# covers most systems running today. This code pipes the CPU
# types through head -n 1, so we only detect the type of CPU 0.
ALPHA_CPU_TYPE=`/usr/sbin/psrinfo -v | sed -n -e 's/^ The alpha \(.*\) processor.*$/\1/p' | head -n 1`
case "$ALPHA_CPU_TYPE" in
"EV4 (21064)")
UNAME_MACHINE="alpha" ;;
"EV4.5 (21064)")
UNAME_MACHINE="alpha" ;;
"LCA4 (21066/21068)")
UNAME_MACHINE="alpha" ;;
"EV5 (21164)")
UNAME_MACHINE="alphaev5" ;;
"EV5.6 (21164A)")
UNAME_MACHINE="alphaev56" ;;
"EV5.6 (21164PC)")
UNAME_MACHINE="alphapca56" ;;
"EV5.7 (21164PC)")
UNAME_MACHINE="alphapca57" ;;
"EV6 (21264)")
UNAME_MACHINE="alphaev6" ;;
"EV6.7 (21264A)")
UNAME_MACHINE="alphaev67" ;;
"EV6.8CB (21264C)")
UNAME_MACHINE="alphaev68" ;;
"EV6.8AL (21264B)")
UNAME_MACHINE="alphaev68" ;;
"EV6.8CX (21264D)")
UNAME_MACHINE="alphaev68" ;;
"EV6.9A (21264/EV69A)")
UNAME_MACHINE="alphaev69" ;;
"EV7 (21364)")
UNAME_MACHINE="alphaev7" ;;
"EV7.9 (21364A)")
UNAME_MACHINE="alphaev79" ;;
esac
# A Pn.n version is a patched version.
# A Vn.n version is a released version.
# A Tn.n version is a released field test version.
# A Xn.n version is an unreleased experimental baselevel.
# 1.2 uses "1.2" for uname -r.
echo ${UNAME_MACHINE}-dec-osf`echo ${UNAME_RELEASE} | sed -e 's/^[PVTX]//' | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz'`
# Reset EXIT trap before exiting to avoid spurious non-zero exit code.
exitcode=$?
trap '' 0
exit $exitcode ;;
Alpha\ *:Windows_NT*:*)
# How do we know it's Interix rather than the generic POSIX subsystem?
# Should we change UNAME_MACHINE based on the output of uname instead
# of the specific Alpha model?
echo alpha-pc-interix
exit ;;
21064:Windows_NT:50:3)
echo alpha-dec-winnt3.5
exit ;;
Amiga*:UNIX_System_V:4.0:*)
echo m68k-unknown-sysv4
exit ;;
*:[Aa]miga[Oo][Ss]:*:*)
echo ${UNAME_MACHINE}-unknown-amigaos
exit ;;
*:[Mm]orph[Oo][Ss]:*:*)
echo ${UNAME_MACHINE}-unknown-morphos
exit ;;
*:OS/390:*:*)
echo i370-ibm-openedition
exit ;;
*:z/VM:*:*)
echo s390-ibm-zvmoe
exit ;;
*:OS400:*:*)
echo powerpc-ibm-os400
exit ;;
arm:RISC*:1.[012]*:*|arm:riscix:1.[012]*:*)
echo arm-acorn-riscix${UNAME_RELEASE}
exit ;;
arm*:riscos:*:*|arm*:RISCOS:*:*)
echo arm-unknown-riscos
exit ;;
SR2?01:HI-UX/MPP:*:* | SR8000:HI-UX/MPP:*:*)
echo hppa1.1-hitachi-hiuxmpp
exit ;;
Pyramid*:OSx*:*:* | MIS*:OSx*:*:* | MIS*:SMP_DC-OSx*:*:*)
# akee@wpdis03.wpafb.af.mil (Earle F. Ake) contributed MIS and NILE.
if test "`(/bin/universe) 2>/dev/null`" = att ; then
echo pyramid-pyramid-sysv3
else
echo pyramid-pyramid-bsd
fi
exit ;;
NILE*:*:*:dcosx)
echo pyramid-pyramid-svr4
exit ;;
DRS?6000:unix:4.0:6*)
echo sparc-icl-nx6
exit ;;
DRS?6000:UNIX_SV:4.2*:7* | DRS?6000:isis:4.2*:7*)
case `/usr/bin/uname -p` in
sparc) echo sparc-icl-nx7; exit ;;
esac ;;
s390x:SunOS:*:*)
echo ${UNAME_MACHINE}-ibm-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
exit ;;
sun4H:SunOS:5.*:*)
echo sparc-hal-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
exit ;;
sun4*:SunOS:5.*:* | tadpole*:SunOS:5.*:*)
echo sparc-sun-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
exit ;;
i86pc:AuroraUX:5.*:* | i86xen:AuroraUX:5.*:*)
echo i386-pc-auroraux${UNAME_RELEASE}
exit ;;
i86pc:SunOS:5.*:* | i86xen:SunOS:5.*:*)
eval $set_cc_for_build
SUN_ARCH="i386"
# If there is a compiler, see if it is configured for 64-bit objects.
# Note that the Sun cc does not turn __LP64__ into 1 like gcc does.
# This test works for both compilers.
if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
if (echo '#ifdef __amd64'; echo IS_64BIT_ARCH; echo '#endif') | \
(CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_64BIT_ARCH >/dev/null
then
SUN_ARCH="x86_64"
fi
fi
echo ${SUN_ARCH}-pc-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
exit ;;
sun4*:SunOS:6*:*)
# According to config.sub, this is the proper way to canonicalize
# SunOS6. Hard to guess exactly what SunOS6 will be like, but
# it's likely to be more like Solaris than SunOS4.
echo sparc-sun-solaris3`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
exit ;;
sun4*:SunOS:*:*)
case "`/usr/bin/arch -k`" in
Series*|S4*)
UNAME_RELEASE=`uname -v`
;;
esac
# Japanese Language versions have a version number like `4.1.3-JL'.
echo sparc-sun-sunos`echo ${UNAME_RELEASE}|sed -e 's/-/_/'`
exit ;;
sun3*:SunOS:*:*)
echo m68k-sun-sunos${UNAME_RELEASE}
exit ;;
sun*:*:4.2BSD:*)
UNAME_RELEASE=`(sed 1q /etc/motd | awk '{print substr($5,1,3)}') 2>/dev/null`
test "x${UNAME_RELEASE}" = "x" && UNAME_RELEASE=3
case "`/bin/arch`" in
sun3)
echo m68k-sun-sunos${UNAME_RELEASE}
;;
sun4)
echo sparc-sun-sunos${UNAME_RELEASE}
;;
esac
exit ;;
aushp:SunOS:*:*)
echo sparc-auspex-sunos${UNAME_RELEASE}
exit ;;
# The situation for MiNT is a little confusing. The machine name
# can be virtually everything (everything which is not
# "atarist" or "atariste" at least should have a processor
# > m68000). The system name ranges from "MiNT" over "FreeMiNT"
# to the lowercase version "mint" (or "freemint"). Finally
# the system name "TOS" denotes a system which is actually not
# MiNT. But MiNT is downward compatible to TOS, so this should
# be no problem.
atarist[e]:*MiNT:*:* | atarist[e]:*mint:*:* | atarist[e]:*TOS:*:*)
echo m68k-atari-mint${UNAME_RELEASE}
exit ;;
atari*:*MiNT:*:* | atari*:*mint:*:* | atarist[e]:*TOS:*:*)
echo m68k-atari-mint${UNAME_RELEASE}
exit ;;
*falcon*:*MiNT:*:* | *falcon*:*mint:*:* | *falcon*:*TOS:*:*)
echo m68k-atari-mint${UNAME_RELEASE}
exit ;;
milan*:*MiNT:*:* | milan*:*mint:*:* | *milan*:*TOS:*:*)
echo m68k-milan-mint${UNAME_RELEASE}
exit ;;
hades*:*MiNT:*:* | hades*:*mint:*:* | *hades*:*TOS:*:*)
echo m68k-hades-mint${UNAME_RELEASE}
exit ;;
*:*MiNT:*:* | *:*mint:*:* | *:*TOS:*:*)
echo m68k-unknown-mint${UNAME_RELEASE}
exit ;;
m68k:machten:*:*)
echo m68k-apple-machten${UNAME_RELEASE}
exit ;;
powerpc:machten:*:*)
echo powerpc-apple-machten${UNAME_RELEASE}
exit ;;
RISC*:Mach:*:*)
echo mips-dec-mach_bsd4.3
exit ;;
RISC*:ULTRIX:*:*)
echo mips-dec-ultrix${UNAME_RELEASE}
exit ;;
VAX*:ULTRIX*:*:*)
echo vax-dec-ultrix${UNAME_RELEASE}
exit ;;
2020:CLIX:*:* | 2430:CLIX:*:*)
echo clipper-intergraph-clix${UNAME_RELEASE}
exit ;;
mips:*:*:UMIPS | mips:*:*:RISCos)
eval $set_cc_for_build
sed 's/^ //' << EOF >$dummy.c
#ifdef __cplusplus
#include /* for printf() prototype */
int main (int argc, char *argv[]) {
#else
int main (argc, argv) int argc; char *argv[]; {
#endif
#if defined (host_mips) && defined (MIPSEB)
#if defined (SYSTYPE_SYSV)
printf ("mips-mips-riscos%ssysv\n", argv[1]); exit (0);
#endif
#if defined (SYSTYPE_SVR4)
printf ("mips-mips-riscos%ssvr4\n", argv[1]); exit (0);
#endif
#if defined (SYSTYPE_BSD43) || defined(SYSTYPE_BSD)
printf ("mips-mips-riscos%sbsd\n", argv[1]); exit (0);
#endif
#endif
exit (-1);
}
EOF
$CC_FOR_BUILD -o $dummy $dummy.c &&
dummyarg=`echo "${UNAME_RELEASE}" | sed -n 's/\([0-9]*\).*/\1/p'` &&
SYSTEM_NAME=`$dummy $dummyarg` &&
{ echo "$SYSTEM_NAME"; exit; }
echo mips-mips-riscos${UNAME_RELEASE}
exit ;;
Motorola:PowerMAX_OS:*:*)
echo powerpc-motorola-powermax
exit ;;
Motorola:*:4.3:PL8-*)
echo powerpc-harris-powermax
exit ;;
Night_Hawk:*:*:PowerMAX_OS | Synergy:PowerMAX_OS:*:*)
echo powerpc-harris-powermax
exit ;;
Night_Hawk:Power_UNIX:*:*)
echo powerpc-harris-powerunix
exit ;;
m88k:CX/UX:7*:*)
echo m88k-harris-cxux7
exit ;;
m88k:*:4*:R4*)
echo m88k-motorola-sysv4
exit ;;
m88k:*:3*:R3*)
echo m88k-motorola-sysv3
exit ;;
AViiON:dgux:*:*)
# DG/UX returns AViiON for all architectures
UNAME_PROCESSOR=`/usr/bin/uname -p`
if [ $UNAME_PROCESSOR = mc88100 ] || [ $UNAME_PROCESSOR = mc88110 ]
then
if [ ${TARGET_BINARY_INTERFACE}x = m88kdguxelfx ] || \
[ ${TARGET_BINARY_INTERFACE}x = x ]
then
echo m88k-dg-dgux${UNAME_RELEASE}
else
echo m88k-dg-dguxbcs${UNAME_RELEASE}
fi
else
echo i586-dg-dgux${UNAME_RELEASE}
fi
exit ;;
M88*:DolphinOS:*:*) # DolphinOS (SVR3)
echo m88k-dolphin-sysv3
exit ;;
M88*:*:R3*:*)
# Delta 88k system running SVR3
echo m88k-motorola-sysv3
exit ;;
XD88*:*:*:*) # Tektronix XD88 system running UTekV (SVR3)
echo m88k-tektronix-sysv3
exit ;;
Tek43[0-9][0-9]:UTek:*:*) # Tektronix 4300 system running UTek (BSD)
echo m68k-tektronix-bsd
exit ;;
*:IRIX*:*:*)
echo mips-sgi-irix`echo ${UNAME_RELEASE}|sed -e 's/-/_/g'`
exit ;;
????????:AIX?:[12].1:2) # AIX 2.2.1 or AIX 2.1.1 is RT/PC AIX.
echo romp-ibm-aix # uname -m gives an 8 hex-code CPU id
exit ;; # Note that: echo "'`uname -s`'" gives 'AIX '
i*86:AIX:*:*)
echo i386-ibm-aix
exit ;;
ia64:AIX:*:*)
if [ -x /usr/bin/oslevel ] ; then
IBM_REV=`/usr/bin/oslevel`
else
IBM_REV=${UNAME_VERSION}.${UNAME_RELEASE}
fi
echo ${UNAME_MACHINE}-ibm-aix${IBM_REV}
exit ;;
*:AIX:2:3)
if grep bos325 /usr/include/stdio.h >/dev/null 2>&1; then
eval $set_cc_for_build
sed 's/^ //' << EOF >$dummy.c
#include
main()
{
if (!__power_pc())
exit(1);
puts("powerpc-ibm-aix3.2.5");
exit(0);
}
EOF
if $CC_FOR_BUILD -o $dummy $dummy.c && SYSTEM_NAME=`$dummy`
then
echo "$SYSTEM_NAME"
else
echo rs6000-ibm-aix3.2.5
fi
elif grep bos324 /usr/include/stdio.h >/dev/null 2>&1; then
echo rs6000-ibm-aix3.2.4
else
echo rs6000-ibm-aix3.2
fi
exit ;;
*:AIX:*:[4567])
IBM_CPU_ID=`/usr/sbin/lsdev -C -c processor -S available | sed 1q | awk '{ print $1 }'`
if /usr/sbin/lsattr -El ${IBM_CPU_ID} | grep ' POWER' >/dev/null 2>&1; then
IBM_ARCH=rs6000
else
IBM_ARCH=powerpc
fi
if [ -x /usr/bin/oslevel ] ; then
IBM_REV=`/usr/bin/oslevel`
else
IBM_REV=${UNAME_VERSION}.${UNAME_RELEASE}
fi
echo ${IBM_ARCH}-ibm-aix${IBM_REV}
exit ;;
*:AIX:*:*)
echo rs6000-ibm-aix
exit ;;
ibmrt:4.4BSD:*|romp-ibm:BSD:*)
echo romp-ibm-bsd4.4
exit ;;
ibmrt:*BSD:*|romp-ibm:BSD:*) # covers RT/PC BSD and
echo romp-ibm-bsd${UNAME_RELEASE} # 4.3 with uname added to
exit ;; # report: romp-ibm BSD 4.3
*:BOSX:*:*)
echo rs6000-bull-bosx
exit ;;
DPX/2?00:B.O.S.:*:*)
echo m68k-bull-sysv3
exit ;;
9000/[34]??:4.3bsd:1.*:*)
echo m68k-hp-bsd
exit ;;
hp300:4.4BSD:*:* | 9000/[34]??:4.3bsd:2.*:*)
echo m68k-hp-bsd4.4
exit ;;
9000/[34678]??:HP-UX:*:*)
HPUX_REV=`echo ${UNAME_RELEASE}|sed -e 's/[^.]*.[0B]*//'`
case "${UNAME_MACHINE}" in
9000/31? ) HP_ARCH=m68000 ;;
9000/[34]?? ) HP_ARCH=m68k ;;
9000/[678][0-9][0-9])
if [ -x /usr/bin/getconf ]; then
sc_cpu_version=`/usr/bin/getconf SC_CPU_VERSION 2>/dev/null`
sc_kernel_bits=`/usr/bin/getconf SC_KERNEL_BITS 2>/dev/null`
case "${sc_cpu_version}" in
523) HP_ARCH="hppa1.0" ;; # CPU_PA_RISC1_0
528) HP_ARCH="hppa1.1" ;; # CPU_PA_RISC1_1
532) # CPU_PA_RISC2_0
case "${sc_kernel_bits}" in
32) HP_ARCH="hppa2.0n" ;;
64) HP_ARCH="hppa2.0w" ;;
'') HP_ARCH="hppa2.0" ;; # HP-UX 10.20
esac ;;
esac
fi
if [ "${HP_ARCH}" = "" ]; then
eval $set_cc_for_build
sed 's/^ //' << EOF >$dummy.c
#define _HPUX_SOURCE
#include
#include
int main ()
{
#if defined(_SC_KERNEL_BITS)
long bits = sysconf(_SC_KERNEL_BITS);
#endif
long cpu = sysconf (_SC_CPU_VERSION);
switch (cpu)
{
case CPU_PA_RISC1_0: puts ("hppa1.0"); break;
case CPU_PA_RISC1_1: puts ("hppa1.1"); break;
case CPU_PA_RISC2_0:
#if defined(_SC_KERNEL_BITS)
switch (bits)
{
case 64: puts ("hppa2.0w"); break;
case 32: puts ("hppa2.0n"); break;
default: puts ("hppa2.0"); break;
} break;
#else /* !defined(_SC_KERNEL_BITS) */
puts ("hppa2.0"); break;
#endif
default: puts ("hppa1.0"); break;
}
exit (0);
}
EOF
(CCOPTS= $CC_FOR_BUILD -o $dummy $dummy.c 2>/dev/null) && HP_ARCH=`$dummy`
test -z "$HP_ARCH" && HP_ARCH=hppa
fi ;;
esac
if [ ${HP_ARCH} = "hppa2.0w" ]
then
eval $set_cc_for_build
# hppa2.0w-hp-hpux* has a 64-bit kernel and a compiler generating
# 32-bit code. hppa64-hp-hpux* has the same kernel and a compiler
# generating 64-bit code. GNU and HP use different nomenclature:
#
# $ CC_FOR_BUILD=cc ./config.guess
# => hppa2.0w-hp-hpux11.23
# $ CC_FOR_BUILD="cc +DA2.0w" ./config.guess
# => hppa64-hp-hpux11.23
if echo __LP64__ | (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) |
grep -q __LP64__
then
HP_ARCH="hppa2.0w"
else
HP_ARCH="hppa64"
fi
fi
echo ${HP_ARCH}-hp-hpux${HPUX_REV}
exit ;;
ia64:HP-UX:*:*)
HPUX_REV=`echo ${UNAME_RELEASE}|sed -e 's/[^.]*.[0B]*//'`
echo ia64-hp-hpux${HPUX_REV}
exit ;;
3050*:HI-UX:*:*)
eval $set_cc_for_build
sed 's/^ //' << EOF >$dummy.c
#include
int
main ()
{
long cpu = sysconf (_SC_CPU_VERSION);
/* The order matters, because CPU_IS_HP_MC68K erroneously returns
true for CPU_PA_RISC1_0. CPU_IS_PA_RISC returns correct
results, however. */
if (CPU_IS_PA_RISC (cpu))
{
switch (cpu)
{
case CPU_PA_RISC1_0: puts ("hppa1.0-hitachi-hiuxwe2"); break;
case CPU_PA_RISC1_1: puts ("hppa1.1-hitachi-hiuxwe2"); break;
case CPU_PA_RISC2_0: puts ("hppa2.0-hitachi-hiuxwe2"); break;
default: puts ("hppa-hitachi-hiuxwe2"); break;
}
}
else if (CPU_IS_HP_MC68K (cpu))
puts ("m68k-hitachi-hiuxwe2");
else puts ("unknown-hitachi-hiuxwe2");
exit (0);
}
EOF
$CC_FOR_BUILD -o $dummy $dummy.c && SYSTEM_NAME=`$dummy` &&
{ echo "$SYSTEM_NAME"; exit; }
echo unknown-hitachi-hiuxwe2
exit ;;
9000/7??:4.3bsd:*:* | 9000/8?[79]:4.3bsd:*:* )
echo hppa1.1-hp-bsd
exit ;;
9000/8??:4.3bsd:*:*)
echo hppa1.0-hp-bsd
exit ;;
*9??*:MPE/iX:*:* | *3000*:MPE/iX:*:*)
echo hppa1.0-hp-mpeix
exit ;;
hp7??:OSF1:*:* | hp8?[79]:OSF1:*:* )
echo hppa1.1-hp-osf
exit ;;
hp8??:OSF1:*:*)
echo hppa1.0-hp-osf
exit ;;
i*86:OSF1:*:*)
if [ -x /usr/sbin/sysversion ] ; then
echo ${UNAME_MACHINE}-unknown-osf1mk
else
echo ${UNAME_MACHINE}-unknown-osf1
fi
exit ;;
parisc*:Lites*:*:*)
echo hppa1.1-hp-lites
exit ;;
C1*:ConvexOS:*:* | convex:ConvexOS:C1*:*)
echo c1-convex-bsd
exit ;;
C2*:ConvexOS:*:* | convex:ConvexOS:C2*:*)
if getsysinfo -f scalar_acc
then echo c32-convex-bsd
else echo c2-convex-bsd
fi
exit ;;
C34*:ConvexOS:*:* | convex:ConvexOS:C34*:*)
echo c34-convex-bsd
exit ;;
C38*:ConvexOS:*:* | convex:ConvexOS:C38*:*)
echo c38-convex-bsd
exit ;;
C4*:ConvexOS:*:* | convex:ConvexOS:C4*:*)
echo c4-convex-bsd
exit ;;
CRAY*Y-MP:*:*:*)
echo ymp-cray-unicos${UNAME_RELEASE} | sed -e 's/\.[^.]*$/.X/'
exit ;;
CRAY*[A-Z]90:*:*:*)
echo ${UNAME_MACHINE}-cray-unicos${UNAME_RELEASE} \
| sed -e 's/CRAY.*\([A-Z]90\)/\1/' \
-e y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/ \
-e 's/\.[^.]*$/.X/'
exit ;;
CRAY*TS:*:*:*)
echo t90-cray-unicos${UNAME_RELEASE} | sed -e 's/\.[^.]*$/.X/'
exit ;;
CRAY*T3E:*:*:*)
echo alphaev5-cray-unicosmk${UNAME_RELEASE} | sed -e 's/\.[^.]*$/.X/'
exit ;;
CRAY*SV1:*:*:*)
echo sv1-cray-unicos${UNAME_RELEASE} | sed -e 's/\.[^.]*$/.X/'
exit ;;
*:UNICOS/mp:*:*)
echo craynv-cray-unicosmp${UNAME_RELEASE} | sed -e 's/\.[^.]*$/.X/'
exit ;;
F30[01]:UNIX_System_V:*:* | F700:UNIX_System_V:*:*)
FUJITSU_PROC=`uname -m | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz'`
FUJITSU_SYS=`uname -p | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz' | sed -e 's/\///'`
FUJITSU_REL=`echo ${UNAME_RELEASE} | sed -e 's/ /_/'`
echo "${FUJITSU_PROC}-fujitsu-${FUJITSU_SYS}${FUJITSU_REL}"
exit ;;
5000:UNIX_System_V:4.*:*)
FUJITSU_SYS=`uname -p | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz' | sed -e 's/\///'`
FUJITSU_REL=`echo ${UNAME_RELEASE} | tr 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' 'abcdefghijklmnopqrstuvwxyz' | sed -e 's/ /_/'`
echo "sparc-fujitsu-${FUJITSU_SYS}${FUJITSU_REL}"
exit ;;
i*86:BSD/386:*:* | i*86:BSD/OS:*:* | *:Ascend\ Embedded/OS:*:*)
echo ${UNAME_MACHINE}-pc-bsdi${UNAME_RELEASE}
exit ;;
sparc*:BSD/OS:*:*)
echo sparc-unknown-bsdi${UNAME_RELEASE}
exit ;;
*:BSD/OS:*:*)
echo ${UNAME_MACHINE}-unknown-bsdi${UNAME_RELEASE}
exit ;;
*:FreeBSD:*:*)
UNAME_PROCESSOR=`/usr/bin/uname -p`
case ${UNAME_PROCESSOR} in
amd64)
echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
*)
echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
esac
exit ;;
i*:CYGWIN*:*)
echo ${UNAME_MACHINE}-pc-cygwin
exit ;;
*:MINGW64*:*)
echo ${UNAME_MACHINE}-pc-mingw64
exit ;;
*:MINGW*:*)
echo ${UNAME_MACHINE}-pc-mingw32
exit ;;
i*:MSYS*:*)
echo ${UNAME_MACHINE}-pc-msys
exit ;;
i*:windows32*:*)
# uname -m includes "-pc" on this system.
echo ${UNAME_MACHINE}-mingw32
exit ;;
i*:PW*:*)
echo ${UNAME_MACHINE}-pc-pw32
exit ;;
*:Interix*:*)
case ${UNAME_MACHINE} in
x86)
echo i586-pc-interix${UNAME_RELEASE}
exit ;;
authenticamd | genuineintel | EM64T)
echo x86_64-unknown-interix${UNAME_RELEASE}
exit ;;
IA64)
echo ia64-unknown-interix${UNAME_RELEASE}
exit ;;
esac ;;
[345]86:Windows_95:* | [345]86:Windows_98:* | [345]86:Windows_NT:*)
echo i${UNAME_MACHINE}-pc-mks
exit ;;
8664:Windows_NT:*)
echo x86_64-pc-mks
exit ;;
i*:Windows_NT*:* | Pentium*:Windows_NT*:*)
# How do we know it's Interix rather than the generic POSIX subsystem?
# It also conflicts with pre-2.0 versions of AT&T UWIN. Should we
# UNAME_MACHINE based on the output of uname instead of i386?
echo i586-pc-interix
exit ;;
i*:UWIN*:*)
echo ${UNAME_MACHINE}-pc-uwin
exit ;;
amd64:CYGWIN*:*:* | x86_64:CYGWIN*:*:*)
echo x86_64-unknown-cygwin
exit ;;
p*:CYGWIN*:*)
echo powerpcle-unknown-cygwin
exit ;;
prep*:SunOS:5.*:*)
echo powerpcle-unknown-solaris2`echo ${UNAME_RELEASE}|sed -e 's/[^.]*//'`
exit ;;
*:GNU:*:*)
# the GNU system
echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-gnu`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'`
exit ;;
*:GNU/*:*:*)
# other systems with GNU libc and userland
echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-gnu
exit ;;
i*86:Minix:*:*)
echo ${UNAME_MACHINE}-pc-minix
exit ;;
aarch64:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
aarch64_be:Linux:*:*)
UNAME_MACHINE=aarch64_be
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
alpha:Linux:*:*)
case `sed -n '/^cpu model/s/^.*: \(.*\)/\1/p' < /proc/cpuinfo` in
EV5) UNAME_MACHINE=alphaev5 ;;
EV56) UNAME_MACHINE=alphaev56 ;;
PCA56) UNAME_MACHINE=alphapca56 ;;
PCA57) UNAME_MACHINE=alphapca56 ;;
EV6) UNAME_MACHINE=alphaev6 ;;
EV67) UNAME_MACHINE=alphaev67 ;;
EV68*) UNAME_MACHINE=alphaev68 ;;
esac
objdump --private-headers /bin/sh | grep -q ld.so.1
if test "$?" = 0 ; then LIBC="libc1" ; else LIBC="" ; fi
echo ${UNAME_MACHINE}-unknown-linux-gnu${LIBC}
exit ;;
arm*:Linux:*:*)
eval $set_cc_for_build
if echo __ARM_EABI__ | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ARM_EABI__
then
echo ${UNAME_MACHINE}-unknown-linux-gnu
else
if echo __ARM_PCS_VFP | $CC_FOR_BUILD -E - 2>/dev/null \
| grep -q __ARM_PCS_VFP
then
echo ${UNAME_MACHINE}-unknown-linux-gnueabi
else
echo ${UNAME_MACHINE}-unknown-linux-gnueabihf
fi
fi
exit ;;
avr32*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
cris:Linux:*:*)
echo ${UNAME_MACHINE}-axis-linux-gnu
exit ;;
crisv32:Linux:*:*)
echo ${UNAME_MACHINE}-axis-linux-gnu
exit ;;
frv:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
hexagon:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
i*86:Linux:*:*)
LIBC=gnu
eval $set_cc_for_build
sed 's/^ //' << EOF >$dummy.c
#ifdef __dietlibc__
LIBC=dietlibc
#endif
EOF
eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'`
echo "${UNAME_MACHINE}-pc-linux-${LIBC}"
exit ;;
ia64:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
m32r*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
m68*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
mips:Linux:*:* | mips64:Linux:*:*)
eval $set_cc_for_build
sed 's/^ //' << EOF >$dummy.c
#undef CPU
#undef ${UNAME_MACHINE}
#undef ${UNAME_MACHINE}el
#if defined(__MIPSEL__) || defined(__MIPSEL) || defined(_MIPSEL) || defined(MIPSEL)
CPU=${UNAME_MACHINE}el
#else
#if defined(__MIPSEB__) || defined(__MIPSEB) || defined(_MIPSEB) || defined(MIPSEB)
CPU=${UNAME_MACHINE}
#else
CPU=
#endif
#endif
EOF
eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^CPU'`
test x"${CPU}" != x && { echo "${CPU}-unknown-linux-gnu"; exit; }
;;
or1k:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
or32:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
padre:Linux:*:*)
echo sparc-unknown-linux-gnu
exit ;;
parisc64:Linux:*:* | hppa64:Linux:*:*)
echo hppa64-unknown-linux-gnu
exit ;;
parisc:Linux:*:* | hppa:Linux:*:*)
# Look for CPU level
case `grep '^cpu[^a-z]*:' /proc/cpuinfo 2>/dev/null | cut -d' ' -f2` in
PA7*) echo hppa1.1-unknown-linux-gnu ;;
PA8*) echo hppa2.0-unknown-linux-gnu ;;
*) echo hppa-unknown-linux-gnu ;;
esac
exit ;;
ppc64:Linux:*:*)
echo powerpc64-unknown-linux-gnu
exit ;;
ppc:Linux:*:*)
echo powerpc-unknown-linux-gnu
exit ;;
s390:Linux:*:* | s390x:Linux:*:*)
echo ${UNAME_MACHINE}-ibm-linux
exit ;;
sh64*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
sh*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
sparc:Linux:*:* | sparc64:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
tile*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
vax:Linux:*:*)
echo ${UNAME_MACHINE}-dec-linux-gnu
exit ;;
x86_64:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
xtensa*:Linux:*:*)
echo ${UNAME_MACHINE}-unknown-linux-gnu
exit ;;
i*86:DYNIX/ptx:4*:*)
# ptx 4.0 does uname -s correctly, with DYNIX/ptx in there.
# earlier versions are messed up and put the nodename in both
# sysname and nodename.
echo i386-sequent-sysv4
exit ;;
i*86:UNIX_SV:4.2MP:2.*)
# Unixware is an offshoot of SVR4, but it has its own version
# number series starting with 2...
# I am not positive that other SVR4 systems won't match this,
# I just have to hope. -- rms.
# Use sysv4.2uw... so that sysv4* matches it.
echo ${UNAME_MACHINE}-pc-sysv4.2uw${UNAME_VERSION}
exit ;;
i*86:OS/2:*:*)
# If we were able to find `uname', then EMX Unix compatibility
# is probably installed.
echo ${UNAME_MACHINE}-pc-os2-emx
exit ;;
i*86:XTS-300:*:STOP)
echo ${UNAME_MACHINE}-unknown-stop
exit ;;
i*86:atheos:*:*)
echo ${UNAME_MACHINE}-unknown-atheos
exit ;;
i*86:syllable:*:*)
echo ${UNAME_MACHINE}-pc-syllable
exit ;;
i*86:LynxOS:2.*:* | i*86:LynxOS:3.[01]*:* | i*86:LynxOS:4.[02]*:*)
echo i386-unknown-lynxos${UNAME_RELEASE}
exit ;;
i*86:*DOS:*:*)
echo ${UNAME_MACHINE}-pc-msdosdjgpp
exit ;;
i*86:*:4.*:* | i*86:SYSTEM_V:4.*:*)
UNAME_REL=`echo ${UNAME_RELEASE} | sed 's/\/MP$//'`
if grep Novell /usr/include/link.h >/dev/null 2>/dev/null; then
echo ${UNAME_MACHINE}-univel-sysv${UNAME_REL}
else
echo ${UNAME_MACHINE}-pc-sysv${UNAME_REL}
fi
exit ;;
i*86:*:5:[678]*)
# UnixWare 7.x, OpenUNIX and OpenServer 6.
case `/bin/uname -X | grep "^Machine"` in
*486*) UNAME_MACHINE=i486 ;;
*Pentium) UNAME_MACHINE=i586 ;;
*Pent*|*Celeron) UNAME_MACHINE=i686 ;;
esac
echo ${UNAME_MACHINE}-unknown-sysv${UNAME_RELEASE}${UNAME_SYSTEM}${UNAME_VERSION}
exit ;;
i*86:*:3.2:*)
if test -f /usr/options/cb.name; then
UNAME_REL=`sed -n 's/.*Version //p' /dev/null >/dev/null ; then
UNAME_REL=`(/bin/uname -X|grep Release|sed -e 's/.*= //')`
(/bin/uname -X|grep i80486 >/dev/null) && UNAME_MACHINE=i486
(/bin/uname -X|grep '^Machine.*Pentium' >/dev/null) \
&& UNAME_MACHINE=i586
(/bin/uname -X|grep '^Machine.*Pent *II' >/dev/null) \
&& UNAME_MACHINE=i686
(/bin/uname -X|grep '^Machine.*Pentium Pro' >/dev/null) \
&& UNAME_MACHINE=i686
echo ${UNAME_MACHINE}-pc-sco$UNAME_REL
else
echo ${UNAME_MACHINE}-pc-sysv32
fi
exit ;;
pc:*:*:*)
# Left here for compatibility:
# uname -m prints for DJGPP always 'pc', but it prints nothing about
# the processor, so we play safe by assuming i586.
# Note: whatever this is, it MUST be the same as what config.sub
# prints for the "djgpp" host, or else GDB configury will decide that
# this is a cross-build.
echo i586-pc-msdosdjgpp
exit ;;
Intel:Mach:3*:*)
echo i386-pc-mach3
exit ;;
paragon:*:*:*)
echo i860-intel-osf1
exit ;;
i860:*:4.*:*) # i860-SVR4
if grep Stardent /usr/include/sys/uadmin.h >/dev/null 2>&1 ; then
echo i860-stardent-sysv${UNAME_RELEASE} # Stardent Vistra i860-SVR4
else # Add other i860-SVR4 vendors below as they are discovered.
echo i860-unknown-sysv${UNAME_RELEASE} # Unknown i860-SVR4
fi
exit ;;
mini*:CTIX:SYS*5:*)
# "miniframe"
echo m68010-convergent-sysv
exit ;;
mc68k:UNIX:SYSTEM5:3.51m)
echo m68k-convergent-sysv
exit ;;
M680?0:D-NIX:5.3:*)
echo m68k-diab-dnix
exit ;;
M68*:*:R3V[5678]*:*)
test -r /sysV68 && { echo 'm68k-motorola-sysv'; exit; } ;;
3[345]??:*:4.0:3.0 | 3[34]??A:*:4.0:3.0 | 3[34]??,*:*:4.0:3.0 | 3[34]??/*:*:4.0:3.0 | 4400:*:4.0:3.0 | 4850:*:4.0:3.0 | SKA40:*:4.0:3.0 | SDS2:*:4.0:3.0 | SHG2:*:4.0:3.0 | S7501*:*:4.0:3.0)
OS_REL=''
test -r /etc/.relid \
&& OS_REL=.`sed -n 's/[^ ]* [^ ]* \([0-9][0-9]\).*/\1/p' < /etc/.relid`
/bin/uname -p 2>/dev/null | grep 86 >/dev/null \
&& { echo i486-ncr-sysv4.3${OS_REL}; exit; }
/bin/uname -p 2>/dev/null | /bin/grep entium >/dev/null \
&& { echo i586-ncr-sysv4.3${OS_REL}; exit; } ;;
3[34]??:*:4.0:* | 3[34]??,*:*:4.0:*)
/bin/uname -p 2>/dev/null | grep 86 >/dev/null \
&& { echo i486-ncr-sysv4; exit; } ;;
NCR*:*:4.2:* | MPRAS*:*:4.2:*)
OS_REL='.3'
test -r /etc/.relid \
&& OS_REL=.`sed -n 's/[^ ]* [^ ]* \([0-9][0-9]\).*/\1/p' < /etc/.relid`
/bin/uname -p 2>/dev/null | grep 86 >/dev/null \
&& { echo i486-ncr-sysv4.3${OS_REL}; exit; }
/bin/uname -p 2>/dev/null | /bin/grep entium >/dev/null \
&& { echo i586-ncr-sysv4.3${OS_REL}; exit; }
/bin/uname -p 2>/dev/null | /bin/grep pteron >/dev/null \
&& { echo i586-ncr-sysv4.3${OS_REL}; exit; } ;;
m68*:LynxOS:2.*:* | m68*:LynxOS:3.0*:*)
echo m68k-unknown-lynxos${UNAME_RELEASE}
exit ;;
mc68030:UNIX_System_V:4.*:*)
echo m68k-atari-sysv4
exit ;;
TSUNAMI:LynxOS:2.*:*)
echo sparc-unknown-lynxos${UNAME_RELEASE}
exit ;;
rs6000:LynxOS:2.*:*)
echo rs6000-unknown-lynxos${UNAME_RELEASE}
exit ;;
PowerPC:LynxOS:2.*:* | PowerPC:LynxOS:3.[01]*:* | PowerPC:LynxOS:4.[02]*:*)
echo powerpc-unknown-lynxos${UNAME_RELEASE}
exit ;;
SM[BE]S:UNIX_SV:*:*)
echo mips-dde-sysv${UNAME_RELEASE}
exit ;;
RM*:ReliantUNIX-*:*:*)
echo mips-sni-sysv4
exit ;;
RM*:SINIX-*:*:*)
echo mips-sni-sysv4
exit ;;
*:SINIX-*:*:*)
if uname -p 2>/dev/null >/dev/null ; then
UNAME_MACHINE=`(uname -p) 2>/dev/null`
echo ${UNAME_MACHINE}-sni-sysv4
else
echo ns32k-sni-sysv
fi
exit ;;
PENTIUM:*:4.0*:*) # Unisys `ClearPath HMP IX 4000' SVR4/MP effort
# says
echo i586-unisys-sysv4
exit ;;
*:UNIX_System_V:4*:FTX*)
# From Gerald Hewes .
# How about differentiating between stratus architectures? -djm
echo hppa1.1-stratus-sysv4
exit ;;
*:*:*:FTX*)
# From seanf@swdc.stratus.com.
echo i860-stratus-sysv4
exit ;;
i*86:VOS:*:*)
# From Paul.Green@stratus.com.
echo ${UNAME_MACHINE}-stratus-vos
exit ;;
*:VOS:*:*)
# From Paul.Green@stratus.com.
echo hppa1.1-stratus-vos
exit ;;
mc68*:A/UX:*:*)
echo m68k-apple-aux${UNAME_RELEASE}
exit ;;
news*:NEWS-OS:6*:*)
echo mips-sony-newsos6
exit ;;
R[34]000:*System_V*:*:* | R4000:UNIX_SYSV:*:* | R*000:UNIX_SV:*:*)
if [ -d /usr/nec ]; then
echo mips-nec-sysv${UNAME_RELEASE}
else
echo mips-unknown-sysv${UNAME_RELEASE}
fi
exit ;;
BeBox:BeOS:*:*) # BeOS running on hardware made by Be, PPC only.
echo powerpc-be-beos
exit ;;
BeMac:BeOS:*:*) # BeOS running on Mac or Mac clone, PPC only.
echo powerpc-apple-beos
exit ;;
BePC:BeOS:*:*) # BeOS running on Intel PC compatible.
echo i586-pc-beos
exit ;;
BePC:Haiku:*:*) # Haiku running on Intel PC compatible.
echo i586-pc-haiku
exit ;;
x86_64:Haiku:*:*)
echo x86_64-unknown-haiku
exit ;;
SX-4:SUPER-UX:*:*)
echo sx4-nec-superux${UNAME_RELEASE}
exit ;;
SX-5:SUPER-UX:*:*)
echo sx5-nec-superux${UNAME_RELEASE}
exit ;;
SX-6:SUPER-UX:*:*)
echo sx6-nec-superux${UNAME_RELEASE}
exit ;;
SX-7:SUPER-UX:*:*)
echo sx7-nec-superux${UNAME_RELEASE}
exit ;;
SX-8:SUPER-UX:*:*)
echo sx8-nec-superux${UNAME_RELEASE}
exit ;;
SX-8R:SUPER-UX:*:*)
echo sx8r-nec-superux${UNAME_RELEASE}
exit ;;
Power*:Rhapsody:*:*)
echo powerpc-apple-rhapsody${UNAME_RELEASE}
exit ;;
*:Rhapsody:*:*)
echo ${UNAME_MACHINE}-apple-rhapsody${UNAME_RELEASE}
exit ;;
*:Darwin:*:*)
UNAME_PROCESSOR=`uname -p` || UNAME_PROCESSOR=unknown
case $UNAME_PROCESSOR in
i386)
eval $set_cc_for_build
if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then
if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \
(CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \
grep IS_64BIT_ARCH >/dev/null
then
UNAME_PROCESSOR="x86_64"
fi
fi ;;
unknown) UNAME_PROCESSOR=powerpc ;;
esac
echo ${UNAME_PROCESSOR}-apple-darwin${UNAME_RELEASE}
exit ;;
*:procnto*:*:* | *:QNX:[0123456789]*:*)
UNAME_PROCESSOR=`uname -p`
if test "$UNAME_PROCESSOR" = "x86"; then
UNAME_PROCESSOR=i386
UNAME_MACHINE=pc
fi
echo ${UNAME_PROCESSOR}-${UNAME_MACHINE}-nto-qnx${UNAME_RELEASE}
exit ;;
*:QNX:*:4*)
echo i386-pc-qnx
exit ;;
NEO-?:NONSTOP_KERNEL:*:*)
echo neo-tandem-nsk${UNAME_RELEASE}
exit ;;
NSE-*:NONSTOP_KERNEL:*:*)
echo nse-tandem-nsk${UNAME_RELEASE}
exit ;;
NSR-?:NONSTOP_KERNEL:*:*)
echo nsr-tandem-nsk${UNAME_RELEASE}
exit ;;
*:NonStop-UX:*:*)
echo mips-compaq-nonstopux
exit ;;
BS2000:POSIX*:*:*)
echo bs2000-siemens-sysv
exit ;;
DS/*:UNIX_System_V:*:*)
echo ${UNAME_MACHINE}-${UNAME_SYSTEM}-${UNAME_RELEASE}
exit ;;
*:Plan9:*:*)
# "uname -m" is not consistent, so use $cputype instead. 386
# is converted to i386 for consistency with other x86
# operating systems.
if test "$cputype" = "386"; then
UNAME_MACHINE=i386
else
UNAME_MACHINE="$cputype"
fi
echo ${UNAME_MACHINE}-unknown-plan9
exit ;;
*:TOPS-10:*:*)
echo pdp10-unknown-tops10
exit ;;
*:TENEX:*:*)
echo pdp10-unknown-tenex
exit ;;
KS10:TOPS-20:*:* | KL10:TOPS-20:*:* | TYPE4:TOPS-20:*:*)
echo pdp10-dec-tops20
exit ;;
XKL-1:TOPS-20:*:* | TYPE5:TOPS-20:*:*)
echo pdp10-xkl-tops20
exit ;;
*:TOPS-20:*:*)
echo pdp10-unknown-tops20
exit ;;
*:ITS:*:*)
echo pdp10-unknown-its
exit ;;
SEI:*:*:SEIUX)
echo mips-sei-seiux${UNAME_RELEASE}
exit ;;
*:DragonFly:*:*)
echo ${UNAME_MACHINE}-unknown-dragonfly`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`
exit ;;
*:*VMS:*:*)
UNAME_MACHINE=`(uname -p) 2>/dev/null`
case "${UNAME_MACHINE}" in
A*) echo alpha-dec-vms ; exit ;;
I*) echo ia64-dec-vms ; exit ;;
V*) echo vax-dec-vms ; exit ;;
esac ;;
*:XENIX:*:SysV)
echo i386-pc-xenix
exit ;;
i*86:skyos:*:*)
echo ${UNAME_MACHINE}-pc-skyos`echo ${UNAME_RELEASE}` | sed -e 's/ .*$//'
exit ;;
i*86:rdos:*:*)
echo ${UNAME_MACHINE}-pc-rdos
exit ;;
i*86:AROS:*:*)
echo ${UNAME_MACHINE}-pc-aros
exit ;;
x86_64:VMkernel:*:*)
echo ${UNAME_MACHINE}-unknown-esx
exit ;;
esac
eval $set_cc_for_build
cat >$dummy.c <
# include
#endif
main ()
{
#if defined (sony)
#if defined (MIPSEB)
/* BFD wants "bsd" instead of "newsos". Perhaps BFD should be changed,
I don't know.... */
printf ("mips-sony-bsd\n"); exit (0);
#else
#include
printf ("m68k-sony-newsos%s\n",
#ifdef NEWSOS4
"4"
#else
""
#endif
); exit (0);
#endif
#endif
#if defined (__arm) && defined (__acorn) && defined (__unix)
printf ("arm-acorn-riscix\n"); exit (0);
#endif
#if defined (hp300) && !defined (hpux)
printf ("m68k-hp-bsd\n"); exit (0);
#endif
#if defined (NeXT)
#if !defined (__ARCHITECTURE__)
#define __ARCHITECTURE__ "m68k"
#endif
int version;
version=`(hostinfo | sed -n 's/.*NeXT Mach \([0-9]*\).*/\1/p') 2>/dev/null`;
if (version < 4)
printf ("%s-next-nextstep%d\n", __ARCHITECTURE__, version);
else
printf ("%s-next-openstep%d\n", __ARCHITECTURE__, version);
exit (0);
#endif
#if defined (MULTIMAX) || defined (n16)
#if defined (UMAXV)
printf ("ns32k-encore-sysv\n"); exit (0);
#else
#if defined (CMU)
printf ("ns32k-encore-mach\n"); exit (0);
#else
printf ("ns32k-encore-bsd\n"); exit (0);
#endif
#endif
#endif
#if defined (__386BSD__)
printf ("i386-pc-bsd\n"); exit (0);
#endif
#if defined (sequent)
#if defined (i386)
printf ("i386-sequent-dynix\n"); exit (0);
#endif
#if defined (ns32000)
printf ("ns32k-sequent-dynix\n"); exit (0);
#endif
#endif
#if defined (_SEQUENT_)
struct utsname un;
uname(&un);
if (strncmp(un.version, "V2", 2) == 0) {
printf ("i386-sequent-ptx2\n"); exit (0);
}
if (strncmp(un.version, "V1", 2) == 0) { /* XXX is V1 correct? */
printf ("i386-sequent-ptx1\n"); exit (0);
}
printf ("i386-sequent-ptx\n"); exit (0);
#endif
#if defined (vax)
# if !defined (ultrix)
# include
# if defined (BSD)
# if BSD == 43
printf ("vax-dec-bsd4.3\n"); exit (0);
# else
# if BSD == 199006
printf ("vax-dec-bsd4.3reno\n"); exit (0);
# else
printf ("vax-dec-bsd\n"); exit (0);
# endif
# endif
# else
printf ("vax-dec-bsd\n"); exit (0);
# endif
# else
printf ("vax-dec-ultrix\n"); exit (0);
# endif
#endif
#if defined (alliant) && defined (i860)
printf ("i860-alliant-bsd\n"); exit (0);
#endif
exit (1);
}
EOF
$CC_FOR_BUILD -o $dummy $dummy.c 2>/dev/null && SYSTEM_NAME=`$dummy` &&
{ echo "$SYSTEM_NAME"; exit; }
# Apollos put the system type in the environment.
test -d /usr/apollo && { echo ${ISP}-apollo-${SYSTYPE}; exit; }
# Convex versions that predate uname can use getsysinfo(1)
if [ -x /usr/convex/getsysinfo ]
then
case `getsysinfo -f cpu_type` in
c1*)
echo c1-convex-bsd
exit ;;
c2*)
if getsysinfo -f scalar_acc
then echo c32-convex-bsd
else echo c2-convex-bsd
fi
exit ;;
c34*)
echo c34-convex-bsd
exit ;;
c38*)
echo c38-convex-bsd
exit ;;
c4*)
echo c4-convex-bsd
exit ;;
esac
fi
cat >&2 < in order to provide the needed
information to handle your system.
config.guess timestamp = $timestamp
uname -m = `(uname -m) 2>/dev/null || echo unknown`
uname -r = `(uname -r) 2>/dev/null || echo unknown`
uname -s = `(uname -s) 2>/dev/null || echo unknown`
uname -v = `(uname -v) 2>/dev/null || echo unknown`
/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null`
/bin/uname -X = `(/bin/uname -X) 2>/dev/null`
hostinfo = `(hostinfo) 2>/dev/null`
/bin/universe = `(/bin/universe) 2>/dev/null`
/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null`
/bin/arch = `(/bin/arch) 2>/dev/null`
/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null`
/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null`
UNAME_MACHINE = ${UNAME_MACHINE}
UNAME_RELEASE = ${UNAME_RELEASE}
UNAME_SYSTEM = ${UNAME_SYSTEM}
UNAME_VERSION = ${UNAME_VERSION}
EOF
exit 1
# Local variables:
# eval: (add-hook 'write-file-hooks 'time-stamp)
# time-stamp-start: "timestamp='"
# time-stamp-format: "%:y-%02m-%02d"
# time-stamp-end: "'"
# End:
enigmail-2.0.8/config.sub 0000775 0000000 0000000 00000105261 13343027545 0015304 0 ustar 00root root 0000000 0000000 #! /bin/sh
# Configuration validation subroutine script.
# Copyright 1992-2013 Free Software Foundation, Inc.
timestamp='2018-07-10'
# 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 .
#
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that
# program. This Exception is an additional permission under section 7
# of the GNU General Public License, version 3 ("GPLv3").
# Please send patches with a ChangeLog entry to config-patches@gnu.org.
#
# Configuration subroutine to validate and canonicalize a configuration type.
# Supply the specified configuration type as an argument.
# If it is invalid, we print an error message on stderr and exit with code 1.
# Otherwise, we print the canonical config type on stdout and succeed.
# You can get the latest version of this script from:
# https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD
# This file is supposed to be the same for all GNU packages
# and recognize all the CPU types, system types and aliases
# that are meaningful with *any* GNU software.
# Each package is responsible for reporting which valid configurations
# it does not support. The user should be able to distinguish
# a failure to support a valid configuration from a meaningless
# configuration.
# The goal of this file is to map all the various variations of a given
# machine specification into a single specification in the form:
# CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM
# or in some cases, the newer four-part form:
# CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM
# It is wrong to echo any other type of specification.
me=`echo "$0" | sed -e 's,.*/,,'`
usage="\
Usage: $0 [OPTION] CPU-MFR-OPSYS
$0 [OPTION] ALIAS
Canonicalize a configuration name.
Operation modes:
-h, --help print this help, then exit
-t, --time-stamp print date of last modification, then exit
-v, --version print version number, then exit
Report bugs and patches to ."
version="\
GNU config.sub ($timestamp)
Copyright 1992-2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
help="
Try \`$me --help' for more information."
# Parse command line
while test $# -gt 0 ; do
case $1 in
--time-stamp | --time* | -t )
echo "$timestamp" ; exit ;;
--version | -v )
echo "$version" ; exit ;;
--help | --h* | -h )
echo "$usage"; exit ;;
-- ) # Stop option processing
shift; break ;;
- ) # Use stdin as input.
break ;;
-* )
echo "$me: invalid option $1$help"
exit 1 ;;
*local*)
# First pass through any local machine types.
echo $1
exit ;;
* )
break ;;
esac
done
case $# in
0) echo "$me: missing argument$help" >&2
exit 1;;
1) ;;
*) echo "$me: too many arguments$help" >&2
exit 1;;
esac
# Separate what the user gave into CPU-COMPANY and OS or KERNEL-OS (if any).
# Here we must recognize all the valid KERNEL-OS combinations.
maybe_os=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\2/'`
case $maybe_os in
nto-qnx* | linux-gnu* | linux-android* | linux-dietlibc | linux-newlib* | \
linux-musl* | linux-uclibc* | uclinux-uclibc* | uclinux-gnu* | kfreebsd*-gnu* | \
knetbsd*-gnu* | netbsd*-gnu* | \
kopensolaris*-gnu* | \
storm-chaos* | os2-emx* | rtmk-nova*)
os=-$maybe_os
basic_machine=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\1/'`
;;
android-linux)
os=-linux-android
basic_machine=`echo $1 | sed 's/^\(.*\)-\([^-]*-[^-]*\)$/\1/'`-unknown
;;
*)
basic_machine=`echo $1 | sed 's/-[^-]*$//'`
if [ $basic_machine != $1 ]
then os=`echo $1 | sed 's/.*-/-/'`
else os=; fi
;;
esac
### Let's recognize common machines as not being operating systems so
### that things like config.sub decstation-3100 work. We also
### recognize some manufacturers as not being operating systems, so we
### can provide default operating systems below.
case $os in
-sun*os*)
# Prevent following clause from handling this invalid input.
;;
-dec* | -mips* | -sequent* | -encore* | -pc532* | -sgi* | -sony* | \
-att* | -7300* | -3300* | -delta* | -motorola* | -sun[234]* | \
-unicom* | -ibm* | -next | -hp | -isi* | -apollo | -altos* | \
-convergent* | -ncr* | -news | -32* | -3600* | -3100* | -hitachi* |\
-c[123]* | -convex* | -sun | -crds | -omron* | -dg | -ultra | -tti* | \
-harris | -dolphin | -highlevel | -gould | -cbm | -ns | -masscomp | \
-apple | -axis | -knuth | -cray | -microblaze*)
os=
basic_machine=$1
;;
-bluegene*)
os=-cnk
;;
-sim | -cisco | -oki | -wec | -winbond)
os=
basic_machine=$1
;;
-scout)
;;
-wrs)
os=-vxworks
basic_machine=$1
;;
-chorusos*)
os=-chorusos
basic_machine=$1
;;
-chorusrdb)
os=-chorusrdb
basic_machine=$1
;;
-hiux*)
os=-hiuxwe2
;;
-sco6)
os=-sco5v6
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-sco5)
os=-sco3.2v5
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-sco4)
os=-sco3.2v4
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-sco3.2.[4-9]*)
os=`echo $os | sed -e 's/sco3.2./sco3.2v/'`
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-sco3.2v[4-9]*)
# Don't forget version if it is 3.2v4 or newer.
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-sco5v6*)
# Don't forget version if it is 3.2v4 or newer.
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-sco*)
os=-sco3.2v2
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-udk*)
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-isc)
os=-isc2.2
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-clix*)
basic_machine=clipper-intergraph
;;
-isc*)
basic_machine=`echo $1 | sed -e 's/86-.*/86-pc/'`
;;
-lynx*178)
os=-lynxos178
;;
-lynx*5)
os=-lynxos5
;;
-lynx*)
os=-lynxos
;;
-ptx*)
basic_machine=`echo $1 | sed -e 's/86-.*/86-sequent/'`
;;
-windowsnt*)
os=`echo $os | sed -e 's/windowsnt/winnt/'`
;;
-psos*)
os=-psos
;;
-mint | -mint[0-9]*)
basic_machine=m68k-atari
os=-mint
;;
esac
# Decode aliases for certain CPU-COMPANY combinations.
case $basic_machine in
# Recognize the basic CPU types without company name.
# Some are omitted here because they have special meanings below.
1750a | 580 \
| a29k \
| aarch64 | aarch64_be \
| alpha | alphaev[4-8] | alphaev56 | alphaev6[78] | alphapca5[67] \
| alpha64 | alpha64ev[4-8] | alpha64ev56 | alpha64ev6[78] | alpha64pca5[67] \
| am33_2.0 \
| arc \
| arm | arm[bl]e | arme[lb] | armv[2-8] | armv[3-8][lb] | armv7[arm] \
| avr | avr32 \
| be32 | be64 \
| bfin \
| c4x | clipper \
| d10v | d30v | dlx | dsp16xx \
| epiphany \
| fido | fr30 | frv \
| h8300 | h8500 | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \
| hexagon \
| i370 | i860 | i960 | ia64 \
| ip2k | iq2000 \
| le32 | le64 \
| lm32 \
| m32c | m32r | m32rle | m68000 | m68k | m88k \
| maxq | mb | microblaze | microblazeel | mcore | mep | metag \
| mips | mipsbe | mipseb | mipsel | mipsle \
| mips16 \
| mips64 | mips64el \
| mips64octeon | mips64octeonel \
| mips64orion | mips64orionel \
| mips64r5900 | mips64r5900el \
| mips64vr | mips64vrel \
| mips64vr4100 | mips64vr4100el \
| mips64vr4300 | mips64vr4300el \
| mips64vr5000 | mips64vr5000el \
| mips64vr5900 | mips64vr5900el \
| mipsisa32 | mipsisa32el \
| mipsisa32r2 | mipsisa32r2el \
| mipsisa64 | mipsisa64el \
| mipsisa64r2 | mipsisa64r2el \
| mipsisa64sb1 | mipsisa64sb1el \
| mipsisa64sr71k | mipsisa64sr71kel \
| mipsr5900 | mipsr5900el \
| mipstx39 | mipstx39el \
| mn10200 | mn10300 \
| moxie \
| mt \
| msp430 \
| nds32 | nds32le | nds32be \
| nios | nios2 | nios2eb | nios2el \
| ns16k | ns32k \
| open8 \
| or1k | or32 \
| pdp10 | pdp11 | pj | pjl \
| powerpc | powerpc64 | powerpc64le | powerpcle \
| pyramid \
| rl78 | rx \
| score \
| sh | sh[1234] | sh[24]a | sh[24]aeb | sh[23]e | sh[34]eb | sheb | shbe | shle | sh[1234]le | sh3ele \
| sh64 | sh64le \
| sparc | sparc64 | sparc64b | sparc64v | sparc86x | sparclet | sparclite \
| sparcv8 | sparcv9 | sparcv9b | sparcv9v \
| spu \
| tahoe | tic4x | tic54x | tic55x | tic6x | tic80 | tron \
| ubicom32 \
| v850 | v850e | v850e1 | v850e2 | v850es | v850e2v3 \
| we32k \
| x86 | xc16x | xstormy16 | xtensa \
| z8k | z80)
basic_machine=$basic_machine-unknown
;;
c54x)
basic_machine=tic54x-unknown
;;
c55x)
basic_machine=tic55x-unknown
;;
c6x)
basic_machine=tic6x-unknown
;;
m6811 | m68hc11 | m6812 | m68hc12 | m68hcs12x | picochip)
basic_machine=$basic_machine-unknown
os=-none
;;
m88110 | m680[12346]0 | m683?2 | m68360 | m5200 | v70 | w65 | z8k)
;;
ms1)
basic_machine=mt-unknown
;;
strongarm | thumb | xscale)
basic_machine=arm-unknown
;;
xgate)
basic_machine=$basic_machine-unknown
os=-none
;;
xscaleeb)
basic_machine=armeb-unknown
;;
xscaleel)
basic_machine=armel-unknown
;;
# We use `pc' rather than `unknown'
# because (1) that's what they normally are, and
# (2) the word "unknown" tends to confuse beginning users.
i*86 | x86_64)
basic_machine=$basic_machine-pc
;;
# Object if more than one company name word.
*-*-*)
echo Invalid configuration \`$1\': machine \`$basic_machine\' not recognized 1>&2
exit 1
;;
# Recognize the basic CPU types with company name.
580-* \
| a29k-* \
| aarch64-* | aarch64_be-* \
| alpha-* | alphaev[4-8]-* | alphaev56-* | alphaev6[78]-* \
| alpha64-* | alpha64ev[4-8]-* | alpha64ev56-* | alpha64ev6[78]-* \
| alphapca5[67]-* | alpha64pca5[67]-* | arc-* \
| arm-* | armbe-* | armle-* | armeb-* | armv*-* \
| avr-* | avr32-* \
| be32-* | be64-* \
| bfin-* | bs2000-* \
| c[123]* | c30-* | [cjt]90-* | c4x-* \
| clipper-* | craynv-* | cydra-* \
| d10v-* | d30v-* | dlx-* \
| elxsi-* \
| f30[01]-* | f700-* | fido-* | fr30-* | frv-* | fx80-* \
| h8300-* | h8500-* \
| hppa-* | hppa1.[01]-* | hppa2.0-* | hppa2.0[nw]-* | hppa64-* \
| hexagon-* \
| i*86-* | i860-* | i960-* | ia64-* \
| ip2k-* | iq2000-* \
| le32-* | le64-* \
| lm32-* \
| m32c-* | m32r-* | m32rle-* \
| m68000-* | m680[012346]0-* | m68360-* | m683?2-* | m68k-* \
| m88110-* | m88k-* | maxq-* | mcore-* | metag-* \
| microblaze-* | microblazeel-* \
| mips-* | mipsbe-* | mipseb-* | mipsel-* | mipsle-* \
| mips16-* \
| mips64-* | mips64el-* \
| mips64octeon-* | mips64octeonel-* \
| mips64orion-* | mips64orionel-* \
| mips64r5900-* | mips64r5900el-* \
| mips64vr-* | mips64vrel-* \
| mips64vr4100-* | mips64vr4100el-* \
| mips64vr4300-* | mips64vr4300el-* \
| mips64vr5000-* | mips64vr5000el-* \
| mips64vr5900-* | mips64vr5900el-* \
| mipsisa32-* | mipsisa32el-* \
| mipsisa32r2-* | mipsisa32r2el-* \
| mipsisa64-* | mipsisa64el-* \
| mipsisa64r2-* | mipsisa64r2el-* \
| mipsisa64sb1-* | mipsisa64sb1el-* \
| mipsisa64sr71k-* | mipsisa64sr71kel-* \
| mipsr5900-* | mipsr5900el-* \
| mipstx39-* | mipstx39el-* \
| mmix-* \
| mt-* \
| msp430-* \
| nds32-* | nds32le-* | nds32be-* \
| nios-* | nios2-* | nios2eb-* | nios2el-* \
| none-* | np1-* | ns16k-* | ns32k-* \
| open8-* \
| orion-* \
| pdp10-* | pdp11-* | pj-* | pjl-* | pn-* | power-* \
| powerpc-* | powerpc64-* | powerpc64le-* | powerpcle-* \
| pyramid-* \
| rl78-* | romp-* | rs6000-* | rx-* \
| sh-* | sh[1234]-* | sh[24]a-* | sh[24]aeb-* | sh[23]e-* | sh[34]eb-* | sheb-* | shbe-* \
| shle-* | sh[1234]le-* | sh3ele-* | sh64-* | sh64le-* \
| sparc-* | sparc64-* | sparc64b-* | sparc64v-* | sparc86x-* | sparclet-* \
| sparclite-* \
| sparcv8-* | sparcv9-* | sparcv9b-* | sparcv9v-* | sv1-* | sx?-* \
| tahoe-* \
| tic30-* | tic4x-* | tic54x-* | tic55x-* | tic6x-* | tic80-* \
| tile*-* \
| tron-* \
| ubicom32-* \
| v850-* | v850e-* | v850e1-* | v850es-* | v850e2-* | v850e2v3-* \
| vax-* \
| we32k-* \
| x86-* | x86_64-* | xc16x-* | xps100-* \
| xstormy16-* | xtensa*-* \
| ymp-* \
| z8k-* | z80-*)
;;
# Recognize the basic CPU types without company name, with glob match.
xtensa*)
basic_machine=$basic_machine-unknown
;;
# Recognize the various machine names and aliases which stand
# for a CPU type and a company and sometimes even an OS.
386bsd)
basic_machine=i386-unknown
os=-bsd
;;
3b1 | 7300 | 7300-att | att-7300 | pc7300 | safari | unixpc)
basic_machine=m68000-att
;;
3b*)
basic_machine=we32k-att
;;
a29khif)
basic_machine=a29k-amd
os=-udi
;;
abacus)
basic_machine=abacus-unknown
;;
adobe68k)
basic_machine=m68010-adobe
os=-scout
;;
alliant | fx80)
basic_machine=fx80-alliant
;;
altos | altos3068)
basic_machine=m68k-altos
;;
am29k)
basic_machine=a29k-none
os=-bsd
;;
amd64)
basic_machine=x86_64-pc
;;
amd64-*)
basic_machine=x86_64-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
amdahl)
basic_machine=580-amdahl
os=-sysv
;;
amiga | amiga-*)
basic_machine=m68k-unknown
;;
amigaos | amigados)
basic_machine=m68k-unknown
os=-amigaos
;;
amigaunix | amix)
basic_machine=m68k-unknown
os=-sysv4
;;
apollo68)
basic_machine=m68k-apollo
os=-sysv
;;
apollo68bsd)
basic_machine=m68k-apollo
os=-bsd
;;
aros)
basic_machine=i386-pc
os=-aros
;;
aux)
basic_machine=m68k-apple
os=-aux
;;
balance)
basic_machine=ns32k-sequent
os=-dynix
;;
blackfin)
basic_machine=bfin-unknown
os=-linux
;;
blackfin-*)
basic_machine=bfin-`echo $basic_machine | sed 's/^[^-]*-//'`
os=-linux
;;
bluegene*)
basic_machine=powerpc-ibm
os=-cnk
;;
c54x-*)
basic_machine=tic54x-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
c55x-*)
basic_machine=tic55x-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
c6x-*)
basic_machine=tic6x-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
c90)
basic_machine=c90-cray
os=-unicos
;;
cegcc)
basic_machine=arm-unknown
os=-cegcc
;;
convex-c1)
basic_machine=c1-convex
os=-bsd
;;
convex-c2)
basic_machine=c2-convex
os=-bsd
;;
convex-c32)
basic_machine=c32-convex
os=-bsd
;;
convex-c34)
basic_machine=c34-convex
os=-bsd
;;
convex-c38)
basic_machine=c38-convex
os=-bsd
;;
cray | j90)
basic_machine=j90-cray
os=-unicos
;;
craynv)
basic_machine=craynv-cray
os=-unicosmp
;;
cr16 | cr16-*)
basic_machine=cr16-unknown
os=-elf
;;
crds | unos)
basic_machine=m68k-crds
;;
crisv32 | crisv32-* | etraxfs*)
basic_machine=crisv32-axis
;;
cris | cris-* | etrax*)
basic_machine=cris-axis
;;
crx)
basic_machine=crx-unknown
os=-elf
;;
da30 | da30-*)
basic_machine=m68k-da30
;;
decstation | decstation-3100 | pmax | pmax-* | pmin | dec3100 | decstatn)
basic_machine=mips-dec
;;
decsystem10* | dec10*)
basic_machine=pdp10-dec
os=-tops10
;;
decsystem20* | dec20*)
basic_machine=pdp10-dec
os=-tops20
;;
delta | 3300 | motorola-3300 | motorola-delta \
| 3300-motorola | delta-motorola)
basic_machine=m68k-motorola
;;
delta88)
basic_machine=m88k-motorola
os=-sysv3
;;
dicos)
basic_machine=i686-pc
os=-dicos
;;
djgpp)
basic_machine=i586-pc
os=-msdosdjgpp
;;
dpx20 | dpx20-*)
basic_machine=rs6000-bull
os=-bosx
;;
dpx2* | dpx2*-bull)
basic_machine=m68k-bull
os=-sysv3
;;
ebmon29k)
basic_machine=a29k-amd
os=-ebmon
;;
elxsi)
basic_machine=elxsi-elxsi
os=-bsd
;;
encore | umax | mmax)
basic_machine=ns32k-encore
;;
es1800 | OSE68k | ose68k | ose | OSE)
basic_machine=m68k-ericsson
os=-ose
;;
fx2800)
basic_machine=i860-alliant
;;
genix)
basic_machine=ns32k-ns
;;
gmicro)
basic_machine=tron-gmicro
os=-sysv
;;
go32)
basic_machine=i386-pc
os=-go32
;;
h3050r* | hiux*)
basic_machine=hppa1.1-hitachi
os=-hiuxwe2
;;
h8300hms)
basic_machine=h8300-hitachi
os=-hms
;;
h8300xray)
basic_machine=h8300-hitachi
os=-xray
;;
h8500hms)
basic_machine=h8500-hitachi
os=-hms
;;
harris)
basic_machine=m88k-harris
os=-sysv3
;;
hp300-*)
basic_machine=m68k-hp
;;
hp300bsd)
basic_machine=m68k-hp
os=-bsd
;;
hp300hpux)
basic_machine=m68k-hp
os=-hpux
;;
hp3k9[0-9][0-9] | hp9[0-9][0-9])
basic_machine=hppa1.0-hp
;;
hp9k2[0-9][0-9] | hp9k31[0-9])
basic_machine=m68000-hp
;;
hp9k3[2-9][0-9])
basic_machine=m68k-hp
;;
hp9k6[0-9][0-9] | hp6[0-9][0-9])
basic_machine=hppa1.0-hp
;;
hp9k7[0-79][0-9] | hp7[0-79][0-9])
basic_machine=hppa1.1-hp
;;
hp9k78[0-9] | hp78[0-9])
# FIXME: really hppa2.0-hp
basic_machine=hppa1.1-hp
;;
hp9k8[67]1 | hp8[67]1 | hp9k80[24] | hp80[24] | hp9k8[78]9 | hp8[78]9 | hp9k893 | hp893)
# FIXME: really hppa2.0-hp
basic_machine=hppa1.1-hp
;;
hp9k8[0-9][13679] | hp8[0-9][13679])
basic_machine=hppa1.1-hp
;;
hp9k8[0-9][0-9] | hp8[0-9][0-9])
basic_machine=hppa1.0-hp
;;
hppa-next)
os=-nextstep3
;;
hppaosf)
basic_machine=hppa1.1-hp
os=-osf
;;
hppro)
basic_machine=hppa1.1-hp
os=-proelf
;;
i370-ibm* | ibm*)
basic_machine=i370-ibm
;;
i*86v32)
basic_machine=`echo $1 | sed -e 's/86.*/86-pc/'`
os=-sysv32
;;
i*86v4*)
basic_machine=`echo $1 | sed -e 's/86.*/86-pc/'`
os=-sysv4
;;
i*86v)
basic_machine=`echo $1 | sed -e 's/86.*/86-pc/'`
os=-sysv
;;
i*86sol2)
basic_machine=`echo $1 | sed -e 's/86.*/86-pc/'`
os=-solaris2
;;
i386mach)
basic_machine=i386-mach
os=-mach
;;
i386-vsta | vsta)
basic_machine=i386-unknown
os=-vsta
;;
iris | iris4d)
basic_machine=mips-sgi
case $os in
-irix*)
;;
*)
os=-irix4
;;
esac
;;
isi68 | isi)
basic_machine=m68k-isi
os=-sysv
;;
m68knommu)
basic_machine=m68k-unknown
os=-linux
;;
m68knommu-*)
basic_machine=m68k-`echo $basic_machine | sed 's/^[^-]*-//'`
os=-linux
;;
m88k-omron*)
basic_machine=m88k-omron
;;
magnum | m3230)
basic_machine=mips-mips
os=-sysv
;;
merlin)
basic_machine=ns32k-utek
os=-sysv
;;
microblaze*)
basic_machine=microblaze-xilinx
;;
mingw64)
basic_machine=x86_64-pc
os=-mingw64
;;
mingw32)
basic_machine=i386-pc
os=-mingw32
;;
mingw32ce)
basic_machine=arm-unknown
os=-mingw32ce
;;
miniframe)
basic_machine=m68000-convergent
;;
*mint | -mint[0-9]* | *MiNT | *MiNT[0-9]*)
basic_machine=m68k-atari
os=-mint
;;
mips3*-*)
basic_machine=`echo $basic_machine | sed -e 's/mips3/mips64/'`
;;
mips3*)
basic_machine=`echo $basic_machine | sed -e 's/mips3/mips64/'`-unknown
;;
monitor)
basic_machine=m68k-rom68k
os=-coff
;;
morphos)
basic_machine=powerpc-unknown
os=-morphos
;;
msdos)
basic_machine=i386-pc
os=-msdos
;;
ms1-*)
basic_machine=`echo $basic_machine | sed -e 's/ms1-/mt-/'`
;;
msys)
basic_machine=i386-pc
os=-msys
;;
mvs)
basic_machine=i370-ibm
os=-mvs
;;
nacl)
basic_machine=le32-unknown
os=-nacl
;;
ncr3000)
basic_machine=i486-ncr
os=-sysv4
;;
netbsd386)
basic_machine=i386-unknown
os=-netbsd
;;
netwinder)
basic_machine=armv4l-rebel
os=-linux
;;
news | news700 | news800 | news900)
basic_machine=m68k-sony
os=-newsos
;;
news1000)
basic_machine=m68030-sony
os=-newsos
;;
news-3600 | risc-news)
basic_machine=mips-sony
os=-newsos
;;
necv70)
basic_machine=v70-nec
os=-sysv
;;
next | m*-next )
basic_machine=m68k-next
case $os in
-nextstep* )
;;
-ns2*)
os=-nextstep2
;;
*)
os=-nextstep3
;;
esac
;;
nh3000)
basic_machine=m68k-harris
os=-cxux
;;
nh[45]000)
basic_machine=m88k-harris
os=-cxux
;;
nindy960)
basic_machine=i960-intel
os=-nindy
;;
mon960)
basic_machine=i960-intel
os=-mon960
;;
nonstopux)
basic_machine=mips-compaq
os=-nonstopux
;;
np1)
basic_machine=np1-gould
;;
neo-tandem)
basic_machine=neo-tandem
;;
nse-tandem)
basic_machine=nse-tandem
;;
nsr-tandem)
basic_machine=nsr-tandem
;;
op50n-* | op60c-*)
basic_machine=hppa1.1-oki
os=-proelf
;;
openrisc | openrisc-*)
basic_machine=or32-unknown
;;
os400)
basic_machine=powerpc-ibm
os=-os400
;;
OSE68000 | ose68000)
basic_machine=m68000-ericsson
os=-ose
;;
os68k)
basic_machine=m68k-none
os=-os68k
;;
pa-hitachi)
basic_machine=hppa1.1-hitachi
os=-hiuxwe2
;;
paragon)
basic_machine=i860-intel
os=-osf
;;
parisc)
basic_machine=hppa-unknown
os=-linux
;;
parisc-*)
basic_machine=hppa-`echo $basic_machine | sed 's/^[^-]*-//'`
os=-linux
;;
pbd)
basic_machine=sparc-tti
;;
pbb)
basic_machine=m68k-tti
;;
pc532 | pc532-*)
basic_machine=ns32k-pc532
;;
pc98)
basic_machine=i386-pc
;;
pc98-*)
basic_machine=i386-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
pentium | p5 | k5 | k6 | nexgen | viac3)
basic_machine=i586-pc
;;
pentiumpro | p6 | 6x86 | athlon | athlon_*)
basic_machine=i686-pc
;;
pentiumii | pentium2 | pentiumiii | pentium3)
basic_machine=i686-pc
;;
pentium4)
basic_machine=i786-pc
;;
pentium-* | p5-* | k5-* | k6-* | nexgen-* | viac3-*)
basic_machine=i586-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
pentiumpro-* | p6-* | 6x86-* | athlon-*)
basic_machine=i686-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
pentiumii-* | pentium2-* | pentiumiii-* | pentium3-*)
basic_machine=i686-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
pentium4-*)
basic_machine=i786-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
pn)
basic_machine=pn-gould
;;
power) basic_machine=power-ibm
;;
ppc | ppcbe) basic_machine=powerpc-unknown
;;
ppc-* | ppcbe-*)
basic_machine=powerpc-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
ppcle | powerpclittle | ppc-le | powerpc-little)
basic_machine=powerpcle-unknown
;;
ppcle-* | powerpclittle-*)
basic_machine=powerpcle-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
ppc64) basic_machine=powerpc64-unknown
;;
ppc64-*) basic_machine=powerpc64-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
ppc64le | powerpc64little | ppc64-le | powerpc64-little)
basic_machine=powerpc64le-unknown
;;
ppc64le-* | powerpc64little-*)
basic_machine=powerpc64le-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
ps2)
basic_machine=i386-ibm
;;
pw32)
basic_machine=i586-unknown
os=-pw32
;;
rdos | rdos64)
basic_machine=x86_64-pc
os=-rdos
;;
rdos32)
basic_machine=i386-pc
os=-rdos
;;
rom68k)
basic_machine=m68k-rom68k
os=-coff
;;
rm[46]00)
basic_machine=mips-siemens
;;
rtpc | rtpc-*)
basic_machine=romp-ibm
;;
s390 | s390-*)
basic_machine=s390-ibm
;;
s390x | s390x-*)
basic_machine=s390x-ibm
;;
sa29200)
basic_machine=a29k-amd
os=-udi
;;
sb1)
basic_machine=mipsisa64sb1-unknown
;;
sb1el)
basic_machine=mipsisa64sb1el-unknown
;;
sde)
basic_machine=mipsisa32-sde
os=-elf
;;
sei)
basic_machine=mips-sei
os=-seiux
;;
sequent)
basic_machine=i386-sequent
;;
sh)
basic_machine=sh-hitachi
os=-hms
;;
sh5el)
basic_machine=sh5le-unknown
;;
sh64)
basic_machine=sh64-unknown
;;
sparclite-wrs | simso-wrs)
basic_machine=sparclite-wrs
os=-vxworks
;;
sps7)
basic_machine=m68k-bull
os=-sysv2
;;
spur)
basic_machine=spur-unknown
;;
st2000)
basic_machine=m68k-tandem
;;
stratus)
basic_machine=i860-stratus
os=-sysv4
;;
strongarm-* | thumb-*)
basic_machine=arm-`echo $basic_machine | sed 's/^[^-]*-//'`
;;
sun2)
basic_machine=m68000-sun
;;
sun2os3)
basic_machine=m68000-sun
os=-sunos3
;;
sun2os4)
basic_machine=m68000-sun
os=-sunos4
;;
sun3os3)
basic_machine=m68k-sun
os=-sunos3
;;
sun3os4)
basic_machine=m68k-sun
os=-sunos4
;;
sun4os3)
basic_machine=sparc-sun
os=-sunos3
;;
sun4os4)
basic_machine=sparc-sun
os=-sunos4
;;
sun4sol2)
basic_machine=sparc-sun
os=-solaris2
;;
sun3 | sun3-*)
basic_machine=m68k-sun
;;
sun4)
basic_machine=sparc-sun
;;
sun386 | sun386i | roadrunner)
basic_machine=i386-sun
;;
sv1)
basic_machine=sv1-cray
os=-unicos
;;
symmetry)
basic_machine=i386-sequent
os=-dynix
;;
t3e)
basic_machine=alphaev5-cray
os=-unicos
;;
t90)
basic_machine=t90-cray
os=-unicos
;;
tile*)
basic_machine=$basic_machine-unknown
os=-linux-gnu
;;
tx39)
basic_machine=mipstx39-unknown
;;
tx39el)
basic_machine=mipstx39el-unknown
;;
toad1)
basic_machine=pdp10-xkl
os=-tops20
;;
tower | tower-32)
basic_machine=m68k-ncr
;;
tpf)
basic_machine=s390x-ibm
os=-tpf
;;
udi29k)
basic_machine=a29k-amd
os=-udi
;;
ultra3)
basic_machine=a29k-nyu
os=-sym1
;;
v810 | necv810)
basic_machine=v810-nec
os=-none
;;
vaxv)
basic_machine=vax-dec
os=-sysv
;;
vms)
basic_machine=vax-dec
os=-vms
;;
vpp*|vx|vx-*)
basic_machine=f301-fujitsu
;;
vxworks960)
basic_machine=i960-wrs
os=-vxworks
;;
vxworks68)
basic_machine=m68k-wrs
os=-vxworks
;;
vxworks29k)
basic_machine=a29k-wrs
os=-vxworks
;;
w65*)
basic_machine=w65-wdc
os=-none
;;
w89k-*)
basic_machine=hppa1.1-winbond
os=-proelf
;;
xbox)
basic_machine=i686-pc
os=-mingw32
;;
xps | xps100)
basic_machine=xps100-honeywell
;;
xscale-* | xscalee[bl]-*)
basic_machine=`echo $basic_machine | sed 's/^xscale/arm/'`
;;
ymp)
basic_machine=ymp-cray
os=-unicos
;;
z8k-*-coff)
basic_machine=z8k-unknown
os=-sim
;;
z80-*-coff)
basic_machine=z80-unknown
os=-sim
;;
none)
basic_machine=none-none
os=-none
;;
# Here we handle the default manufacturer of certain CPU types. It is in
# some cases the only manufacturer, in others, it is the most popular.
w89k)
basic_machine=hppa1.1-winbond
;;
op50n)
basic_machine=hppa1.1-oki
;;
op60c)
basic_machine=hppa1.1-oki
;;
romp)
basic_machine=romp-ibm
;;
mmix)
basic_machine=mmix-knuth
;;
rs6000)
basic_machine=rs6000-ibm
;;
vax)
basic_machine=vax-dec
;;
pdp10)
# there are many clones, so DEC is not a safe bet
basic_machine=pdp10-unknown
;;
pdp11)
basic_machine=pdp11-dec
;;
we32k)
basic_machine=we32k-att
;;
sh[1234] | sh[24]a | sh[24]aeb | sh[34]eb | sh[1234]le | sh[23]ele)
basic_machine=sh-unknown
;;
sparc | sparcv8 | sparcv9 | sparcv9b | sparcv9v)
basic_machine=sparc-sun
;;
cydra)
basic_machine=cydra-cydrome
;;
orion)
basic_machine=orion-highlevel
;;
orion105)
basic_machine=clipper-highlevel
;;
mac | mpw | mac-mpw)
basic_machine=m68k-apple
;;
pmac | pmac-mpw)
basic_machine=powerpc-apple
;;
*-unknown)
# Make sure to match an already-canonicalized machine name.
;;
*)
echo Invalid configuration \`$1\': machine \`$basic_machine\' not recognized 1>&2
exit 1
;;
esac
# Here we canonicalize certain aliases for manufacturers.
case $basic_machine in
*-digital*)
basic_machine=`echo $basic_machine | sed 's/digital.*/dec/'`
;;
*-commodore*)
basic_machine=`echo $basic_machine | sed 's/commodore.*/cbm/'`
;;
*)
;;
esac
# Decode manufacturer-specific aliases for certain operating systems.
if [ x"$os" != x"" ]
then
case $os in
# First match some system type aliases
# that might get confused with valid system types.
# -solaris* is a basic system type, with this one exception.
-auroraux)
os=-auroraux
;;
-solaris1 | -solaris1.*)
os=`echo $os | sed -e 's|solaris1|sunos4|'`
;;
-solaris)
os=-solaris2
;;
-svr4*)
os=-sysv4
;;
-unixware*)
os=-sysv4.2uw
;;
-gnu/linux*)
os=`echo $os | sed -e 's|gnu/linux|linux-gnu|'`
;;
# First accept the basic system types.
# The portable systems comes first.
# Each alternative MUST END IN A *, to match a version number.
# -sysv* is not here because it comes later, after sysvr4.
-gnu* | -bsd* | -mach* | -minix* | -genix* | -ultrix* | -irix* \
| -*vms* | -sco* | -esix* | -isc* | -aix* | -cnk* | -sunos | -sunos[34]*\
| -hpux* | -unos* | -osf* | -luna* | -dgux* | -auroraux* | -solaris* \
| -sym* | -kopensolaris* | -plan9* \
| -amigaos* | -amigados* | -msdos* | -newsos* | -unicos* | -aof* \
| -aos* | -aros* \
| -nindy* | -vxsim* | -vxworks* | -ebmon* | -hms* | -mvs* \
| -clix* | -riscos* | -uniplus* | -iris* | -rtu* | -xenix* \
| -hiux* | -386bsd* | -knetbsd* | -mirbsd* | -netbsd* \
| -bitrig* | -openbsd* | -solidbsd* \
| -ekkobsd* | -kfreebsd* | -freebsd* | -riscix* | -lynxos* \
| -bosx* | -nextstep* | -cxux* | -aout* | -elf* | -oabi* \
| -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \
| -udi* | -eabi* | -lites* | -ieee* | -go32* | -aux* \
| -chorusos* | -chorusrdb* | -cegcc* \
| -cygwin* | -msys* | -pe* | -psos* | -moss* | -proelf* | -rtems* \
| -mingw32* | -mingw64* | -linux-gnu* | -linux-android* \
| -linux-newlib* | -linux-musl* | -linux-uclibc* \
| -uxpv* | -beos* | -mpeix* | -udk* \
| -interix* | -uwin* | -mks* | -rhapsody* | -darwin* | -opened* \
| -openstep* | -oskit* | -conix* | -pw32* | -nonstopux* \
| -storm-chaos* | -tops10* | -tenex* | -tops20* | -its* \
| -os2* | -vos* | -palmos* | -uclinux* | -nucleus* \
| -morphos* | -superux* | -rtmk* | -rtmk-nova* | -windiss* \
| -powermax* | -dnix* | -nx6 | -nx7 | -sei* | -dragonfly* \
| -skyos* | -haiku* | -rdos* | -toppers* | -drops* | -es*)
# Remember, each alternative MUST END IN *, to match a version number.
;;
-qnx*)
case $basic_machine in
x86-* | i*86-*)
;;
*)
os=-nto$os
;;
esac
;;
-nto-qnx*)
;;
-nto*)
os=`echo $os | sed -e 's|nto|nto-qnx|'`
;;
-sim | -es1800* | -hms* | -xray | -os68k* | -none* | -v88r* \
| -windows* | -osx | -abug | -netware* | -os9* | -beos* | -haiku* \
| -macos* | -mpw* | -magic* | -mmixware* | -mon960* | -lnews*)
;;
-mac*)
os=`echo $os | sed -e 's|mac|macos|'`
;;
-linux-dietlibc)
os=-linux-dietlibc
;;
-linux*)
os=`echo $os | sed -e 's|linux|linux-gnu|'`
;;
-sunos5*)
os=`echo $os | sed -e 's|sunos5|solaris2|'`
;;
-sunos6*)
os=`echo $os | sed -e 's|sunos6|solaris3|'`
;;
-opened*)
os=-openedition
;;
-os400*)
os=-os400
;;
-wince*)
os=-wince
;;
-osfrose*)
os=-osfrose
;;
-osf*)
os=-osf
;;
-utek*)
os=-bsd
;;
-dynix*)
os=-bsd
;;
-acis*)
os=-aos
;;
-atheos*)
os=-atheos
;;
-syllable*)
os=-syllable
;;
-386bsd)
os=-bsd
;;
-ctix* | -uts*)
os=-sysv
;;
-nova*)
os=-rtmk-nova
;;
-ns2 )
os=-nextstep2
;;
-nsk*)
os=-nsk
;;
# Preserve the version number of sinix5.
-sinix5.*)
os=`echo $os | sed -e 's|sinix|sysv|'`
;;
-sinix*)
os=-sysv4
;;
-tpf*)
os=-tpf
;;
-triton*)
os=-sysv3
;;
-oss*)
os=-sysv3
;;
-svr4)
os=-sysv4
;;
-svr3)
os=-sysv3
;;
-sysvr4)
os=-sysv4
;;
# This must come after -sysvr4.
-sysv*)
;;
-ose*)
os=-ose
;;
-es1800*)
os=-ose
;;
-xenix)
os=-xenix
;;
-*mint | -mint[0-9]* | -*MiNT | -MiNT[0-9]*)
os=-mint
;;
-aros*)
os=-aros
;;
-zvmoe)
os=-zvmoe
;;
-dicos*)
os=-dicos
;;
-nacl*)
;;
-none)
;;
*)
# Get rid of the `-' at the beginning of $os.
os=`echo $os | sed 's/[^-]*-//'`
echo Invalid configuration \`$1\': system \`$os\' not recognized 1>&2
exit 1
;;
esac
else
# Here we handle the default operating systems that come with various machines.
# The value should be what the vendor currently ships out the door with their
# machine or put another way, the most popular os provided with the machine.
# Note that if you're going to try to match "-MANUFACTURER" here (say,
# "-sun"), then you have to tell the case statement up towards the top
# that MANUFACTURER isn't an operating system. Otherwise, code above
# will signal an error saying that MANUFACTURER isn't an operating
# system, and we'll never get to this point.
case $basic_machine in
score-*)
os=-elf
;;
spu-*)
os=-elf
;;
*-acorn)
os=-riscix1.2
;;
arm*-rebel)
os=-linux
;;
arm*-semi)
os=-aout
;;
c4x-* | tic4x-*)
os=-coff
;;
hexagon-*)
os=-elf
;;
tic54x-*)
os=-coff
;;
tic55x-*)
os=-coff
;;
tic6x-*)
os=-coff
;;
# This must come before the *-dec entry.
pdp10-*)
os=-tops20
;;
pdp11-*)
os=-none
;;
*-dec | vax-*)
os=-ultrix4.2
;;
m68*-apollo)
os=-domain
;;
i386-sun)
os=-sunos4.0.2
;;
m68000-sun)
os=-sunos3
;;
m68*-cisco)
os=-aout
;;
mep-*)
os=-elf
;;
mips*-cisco)
os=-elf
;;
mips*-*)
os=-elf
;;
or1k-*)
os=-elf
;;
or32-*)
os=-coff
;;
*-tti) # must be before sparc entry or we get the wrong os.
os=-sysv3
;;
sparc-* | *-sun)
os=-sunos4.1.1
;;
*-be)
os=-beos
;;
*-haiku)
os=-haiku
;;
*-ibm)
os=-aix
;;
*-knuth)
os=-mmixware
;;
*-wec)
os=-proelf
;;
*-winbond)
os=-proelf
;;
*-oki)
os=-proelf
;;
*-hp)
os=-hpux
;;
*-hitachi)
os=-hiux
;;
i860-* | *-att | *-ncr | *-altos | *-motorola | *-convergent)
os=-sysv
;;
*-cbm)
os=-amigaos
;;
*-dg)
os=-dgux
;;
*-dolphin)
os=-sysv3
;;
m68k-ccur)
os=-rtu
;;
m88k-omron*)
os=-luna
;;
*-next )
os=-nextstep
;;
*-sequent)
os=-ptx
;;
*-crds)
os=-unos
;;
*-ns)
os=-genix
;;
i370-*)
os=-mvs
;;
*-next)
os=-nextstep3
;;
*-gould)
os=-sysv
;;
*-highlevel)
os=-bsd
;;
*-encore)
os=-bsd
;;
*-sgi)
os=-irix
;;
*-siemens)
os=-sysv4
;;
*-masscomp)
os=-rtu
;;
f30[01]-fujitsu | f700-fujitsu)
os=-uxpv
;;
*-rom68k)
os=-coff
;;
*-*bug)
os=-coff
;;
*-apple)
os=-macos
;;
*-atari*)
os=-mint
;;
*)
os=-none
;;
esac
fi
# Here we handle the case where we know the os, and the CPU type, but not the
# manufacturer. We pick the logical manufacturer.
vendor=unknown
case $basic_machine in
*-unknown)
case $os in
-riscix*)
vendor=acorn
;;
-sunos*)
vendor=sun
;;
-cnk*|-aix*)
vendor=ibm
;;
-beos*)
vendor=be
;;
-hpux*)
vendor=hp
;;
-mpeix*)
vendor=hp
;;
-hiux*)
vendor=hitachi
;;
-unos*)
vendor=crds
;;
-dgux*)
vendor=dg
;;
-luna*)
vendor=omron
;;
-genix*)
vendor=ns
;;
-mvs* | -opened*)
vendor=ibm
;;
-os400*)
vendor=ibm
;;
-ptx*)
vendor=sequent
;;
-tpf*)
vendor=ibm
;;
-vxsim* | -vxworks* | -windiss*)
vendor=wrs
;;
-aux*)
vendor=apple
;;
-hms*)
vendor=hitachi
;;
-mpw* | -macos*)
vendor=apple
;;
-*mint | -mint[0-9]* | -*MiNT | -MiNT[0-9]*)
vendor=atari
;;
-vos*)
vendor=stratus
;;
esac
basic_machine=`echo $basic_machine | sed "s/unknown/$vendor/"`
;;
esac
echo $basic_machine$os
exit
# Local variables:
# eval: (add-hook 'write-file-hooks 'time-stamp)
# time-stamp-start: "timestamp='"
# time-stamp-format: "%:y-%02m-%02d"
# time-stamp-end: "'"
# End:
enigmail-2.0.8/config/ 0000775 0000000 0000000 00000000000 13343027545 0014561 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/config/autoconf.mk.in 0000664 0000000 0000000 00000000505 13343027545 0017335 0 ustar 00root root 0000000 0000000 # @configure_input@
PERL = @PERL@
PYTHON = @PYTHON@
TB_PATH = "@TB_PATH@"
TB_ARGS = @TB_ARGS@
TESTS = @enable_tests@
FIX_LANGUAGES = @enable_fix_lang@
ENABLE_LANG = @enable_lang@
srcdir = @srcdir@
DIST = $(DEPTH)/build/dist
BUILD = $(DEPTH)/build
JSUNIT = $(DEPTH)/util/run-jsunit $(PERL) $(TB_PATH) $(TB_ARGS) -jsunit
enigmail-2.0.8/configure.ac 0000664 0000000 0000000 00000003451 13343027545 0015605 0 ustar 00root root 0000000 0000000 # Process this file with autoconf to produce a configure script.
AC_PREREQ(2.61)
min_automake_version="1.10"
AC_INIT([enigmail],[2.0.8], [https://www.enigmail.net])
AC_PATH_PROG(PYTHON, "python2")
# fallback to python if python2 does not exist
if test "x$PYTHON" = "x" ; then
AC_PATH_PROG(PYTHON, "python")
fi
if test "x$PYTHON" = "x" ; then
AC_MSG_ERROR([[python2 or python not found.]])
fi
AC_PATH_PROG(PERL,"perl")
if test "x$PERL" = "x" ; then
AC_MSG_ERROR([[Perl not found.]])
fi
AC_CANONICAL_TARGET
# Enable running of unit test during build
#
AC_ARG_ENABLE(tests,
AC_HELP_STRING([--enable-tests],[run unit tests during build process]),
enable_tests=$enableval)
# Disable creation of languages other than en-US (for submitting to babelzilla)
#
AC_ARG_ENABLE(lang,
AC_HELP_STRING([--disable-lang],[disable creation of locales other than en-US]),
enable_lang=$enableval,
enable_lang=yes
)
AC_SUBST(enable_tests)
AC_SUBST(enable_lang)
AC_ARG_WITH(tb-path,
[ --with-tb-path=/path/to/thunderbird set the path to an installed Thunderbird],
[if test "$withval" = yes ; then
withval=no
elif test "$withval" != no ; then
TB_PATH="$withval"
fi],withval=no)
AC_SUBST(TB_PATH)
AC_ARG_WITH(tb-args,
[ --with-tb-args="-P profilename" set additional arguments for Thunderbird],
[if test "$withval" = yes ; then
withval=no
elif test "$withval" != no ; then
TB_ARGS="$withval"
fi],withval=no)
AC_SUBST(TB_ARGS)
AC_ARG_ENABLE(fix-lang,
AC_HELP_STRING([--disable-fix-lang],[disable replacing of missing strings in localizations with en-US]),
enable_fix_lang=$enableval,
enable_fix_lang=yes
)
AC_SUBST(enable_fix_lang)
AC_CONFIG_FILES([config/autoconf.mk])
AC_OUTPUT
enigmail-2.0.8/install-sh 0000775 0000000 0000000 00000033255 13343027545 0015330 0 ustar 00root root 0000000 0000000 #!/bin/sh
# install - install a program, script, or datafile
scriptversion=2011-11-20.07; # UTC
# This originates from X11R5 (mit/util/scripts/install.sh), which was
# later released in X11R6 (xc/config/util/install.sh) with the
# following copyright and license.
#
# Copyright (C) 1994 X Consortium
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to
# deal in the Software without restriction, including without limitation the
# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
# sell copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
# AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
# TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
#
# Except as contained in this notice, the name of the X Consortium shall not
# be used in advertising or otherwise to promote the sale, use or other deal-
# ings in this Software without prior written authorization from the X Consor-
# tium.
#
#
# FSF changes to this file are in the public domain.
#
# Calling this script install-sh is preferred over install.sh, to prevent
# 'make' implicit rules from creating a file called install from it
# when there is no Makefile.
#
# This script is compatible with the BSD install script, but was written
# from scratch.
nl='
'
IFS=" "" $nl"
# set DOITPROG to echo to test this script
# Don't use :- since 4.3BSD and earlier shells don't like it.
doit=${DOITPROG-}
if test -z "$doit"; then
doit_exec=exec
else
doit_exec=$doit
fi
# Put in absolute file names if you don't have them in your path;
# or use environment vars.
chgrpprog=${CHGRPPROG-chgrp}
chmodprog=${CHMODPROG-chmod}
chownprog=${CHOWNPROG-chown}
cmpprog=${CMPPROG-cmp}
cpprog=${CPPROG-cp}
mkdirprog=${MKDIRPROG-mkdir}
mvprog=${MVPROG-mv}
rmprog=${RMPROG-rm}
stripprog=${STRIPPROG-strip}
posix_glob='?'
initialize_posix_glob='
test "$posix_glob" != "?" || {
if (set -f) 2>/dev/null; then
posix_glob=
else
posix_glob=:
fi
}
'
posix_mkdir=
# Desired mode of installed file.
mode=0755
chgrpcmd=
chmodcmd=$chmodprog
chowncmd=
mvcmd=$mvprog
rmcmd="$rmprog -f"
stripcmd=
src=
dst=
dir_arg=
dst_arg=
copy_on_change=false
no_target_directory=
usage="\
Usage: $0 [OPTION]... [-T] SRCFILE DSTFILE
or: $0 [OPTION]... SRCFILES... DIRECTORY
or: $0 [OPTION]... -t DIRECTORY SRCFILES...
or: $0 [OPTION]... -d DIRECTORIES...
In the 1st form, copy SRCFILE to DSTFILE.
In the 2nd and 3rd, copy all SRCFILES to DIRECTORY.
In the 4th, create DIRECTORIES.
Options:
--help display this help and exit.
--version display version info and exit.
-c (ignored)
-C install only if different (preserve the last data modification time)
-d create directories instead of installing files.
-g GROUP $chgrpprog installed files to GROUP.
-m MODE $chmodprog installed files to MODE.
-o USER $chownprog installed files to USER.
-s $stripprog installed files.
-t DIRECTORY install into DIRECTORY.
-T report an error if DSTFILE is a directory.
Environment variables override the default commands:
CHGRPPROG CHMODPROG CHOWNPROG CMPPROG CPPROG MKDIRPROG MVPROG
RMPROG STRIPPROG
"
while test $# -ne 0; do
case $1 in
-c) ;;
-C) copy_on_change=true;;
-d) dir_arg=true;;
-g) chgrpcmd="$chgrpprog $2"
shift;;
--help) echo "$usage"; exit $?;;
-m) mode=$2
case $mode in
*' '* | *' '* | *'
'* | *'*'* | *'?'* | *'['*)
echo "$0: invalid mode: $mode" >&2
exit 1;;
esac
shift;;
-o) chowncmd="$chownprog $2"
shift;;
-s) stripcmd=$stripprog;;
-t) dst_arg=$2
# Protect names problematic for 'test' and other utilities.
case $dst_arg in
-* | [=\(\)!]) dst_arg=./$dst_arg;;
esac
shift;;
-T) no_target_directory=true;;
--version) echo "$0 $scriptversion"; exit $?;;
--) shift
break;;
-*) echo "$0: invalid option: $1" >&2
exit 1;;
*) break;;
esac
shift
done
if test $# -ne 0 && test -z "$dir_arg$dst_arg"; then
# When -d is used, all remaining arguments are directories to create.
# When -t is used, the destination is already specified.
# Otherwise, the last argument is the destination. Remove it from $@.
for arg
do
if test -n "$dst_arg"; then
# $@ is not empty: it contains at least $arg.
set fnord "$@" "$dst_arg"
shift # fnord
fi
shift # arg
dst_arg=$arg
# Protect names problematic for 'test' and other utilities.
case $dst_arg in
-* | [=\(\)!]) dst_arg=./$dst_arg;;
esac
done
fi
if test $# -eq 0; then
if test -z "$dir_arg"; then
echo "$0: no input file specified." >&2
exit 1
fi
# It's OK to call 'install-sh -d' without argument.
# This can happen when creating conditional directories.
exit 0
fi
if test -z "$dir_arg"; then
do_exit='(exit $ret); exit $ret'
trap "ret=129; $do_exit" 1
trap "ret=130; $do_exit" 2
trap "ret=141; $do_exit" 13
trap "ret=143; $do_exit" 15
# Set umask so as not to create temps with too-generous modes.
# However, 'strip' requires both read and write access to temps.
case $mode in
# Optimize common cases.
*644) cp_umask=133;;
*755) cp_umask=22;;
*[0-7])
if test -z "$stripcmd"; then
u_plus_rw=
else
u_plus_rw='% 200'
fi
cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
*)
if test -z "$stripcmd"; then
u_plus_rw=
else
u_plus_rw=,u+rw
fi
cp_umask=$mode$u_plus_rw;;
esac
fi
for src
do
# Protect names problematic for 'test' and other utilities.
case $src in
-* | [=\(\)!]) src=./$src;;
esac
if test -n "$dir_arg"; then
dst=$src
dstdir=$dst
test -d "$dstdir"
dstdir_status=$?
else
# Waiting for this to be detected by the "$cpprog $src $dsttmp" command
# might cause directories to be created, which would be especially bad
# if $src (and thus $dsttmp) contains '*'.
if test ! -f "$src" && test ! -d "$src"; then
echo "$0: $src does not exist." >&2
exit 1
fi
if test -z "$dst_arg"; then
echo "$0: no destination specified." >&2
exit 1
fi
dst=$dst_arg
# If destination is a directory, append the input filename; won't work
# if double slashes aren't ignored.
if test -d "$dst"; then
if test -n "$no_target_directory"; then
echo "$0: $dst_arg: Is a directory" >&2
exit 1
fi
dstdir=$dst
dst=$dstdir/`basename "$src"`
dstdir_status=0
else
# Prefer dirname, but fall back on a substitute if dirname fails.
dstdir=`
(dirname "$dst") 2>/dev/null ||
expr X"$dst" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$dst" : 'X\(//\)[^/]' \| \
X"$dst" : 'X\(//\)$' \| \
X"$dst" : 'X\(/\)' \| . 2>/dev/null ||
echo X"$dst" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'
`
test -d "$dstdir"
dstdir_status=$?
fi
fi
obsolete_mkdir_used=false
if test $dstdir_status != 0; then
case $posix_mkdir in
'')
# Create intermediate dirs using mode 755 as modified by the umask.
# This is like FreeBSD 'install' as of 1997-10-28.
umask=`umask`
case $stripcmd.$umask in
# Optimize common cases.
*[2367][2367]) mkdir_umask=$umask;;
.*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
*[0-7])
mkdir_umask=`expr $umask + 22 \
- $umask % 100 % 40 + $umask % 20 \
- $umask % 10 % 4 + $umask % 2
`;;
*) mkdir_umask=$umask,go-w;;
esac
# With -d, create the new directory with the user-specified mode.
# Otherwise, rely on $mkdir_umask.
if test -n "$dir_arg"; then
mkdir_mode=-m$mode
else
mkdir_mode=
fi
posix_mkdir=false
case $umask in
*[123567][0-7][0-7])
# POSIX mkdir -p sets u+wx bits regardless of umask, which
# is incompatible with FreeBSD 'install' when (umask & 300) != 0.
;;
*)
tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
if (umask $mkdir_umask &&
exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
then
if test -z "$dir_arg" || {
# Check for POSIX incompatibilities with -m.
# HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
# other-writable bit of parent directory when it shouldn't.
# FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
ls_ld_tmpdir=`ls -ld "$tmpdir"`
case $ls_ld_tmpdir in
d????-?r-*) different_mode=700;;
d????-?--*) different_mode=755;;
*) false;;
esac &&
$mkdirprog -m$different_mode -p -- "$tmpdir" && {
ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
}
}
then posix_mkdir=:
fi
rmdir "$tmpdir/d" "$tmpdir"
else
# Remove any dirs left behind by ancient mkdir implementations.
rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
fi
trap '' 0;;
esac;;
esac
if
$posix_mkdir && (
umask $mkdir_umask &&
$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
)
then :
else
# The umask is ridiculous, or mkdir does not conform to POSIX,
# or it failed possibly due to a race condition. Create the
# directory the slow way, step by step, checking for races as we go.
case $dstdir in
/*) prefix='/';;
[-=\(\)!]*) prefix='./';;
*) prefix='';;
esac
eval "$initialize_posix_glob"
oIFS=$IFS
IFS=/
$posix_glob set -f
set fnord $dstdir
shift
$posix_glob set +f
IFS=$oIFS
prefixes=
for d
do
test X"$d" = X && continue
prefix=$prefix$d
if test -d "$prefix"; then
prefixes=
else
if $posix_mkdir; then
(umask=$mkdir_umask &&
$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
# Don't fail if two instances are running concurrently.
test -d "$prefix" || exit 1
else
case $prefix in
*\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
*) qprefix=$prefix;;
esac
prefixes="$prefixes '$qprefix'"
fi
fi
prefix=$prefix/
done
if test -n "$prefixes"; then
# Don't fail if two instances are running concurrently.
(umask $mkdir_umask &&
eval "\$doit_exec \$mkdirprog $prefixes") ||
test -d "$dstdir" || exit 1
obsolete_mkdir_used=true
fi
fi
fi
if test -n "$dir_arg"; then
{ test -z "$chowncmd" || $doit $chowncmd "$dst"; } &&
{ test -z "$chgrpcmd" || $doit $chgrpcmd "$dst"; } &&
{ test "$obsolete_mkdir_used$chowncmd$chgrpcmd" = false ||
test -z "$chmodcmd" || $doit $chmodcmd $mode "$dst"; } || exit 1
else
# Make a couple of temp file names in the proper directory.
dsttmp=$dstdir/_inst.$$_
rmtmp=$dstdir/_rm.$$_
# Trap to clean up those temp files at exit.
trap 'ret=$?; rm -f "$dsttmp" "$rmtmp" && exit $ret' 0
# Copy the file name to the temp name.
(umask $cp_umask && $doit_exec $cpprog "$src" "$dsttmp") &&
# and set any options; do chmod last to preserve setuid bits.
#
# If any of these fail, we abort the whole thing. If we want to
# ignore errors from any of these, just make sure not to ignore
# errors from the above "$doit $cpprog $src $dsttmp" command.
#
{ test -z "$chowncmd" || $doit $chowncmd "$dsttmp"; } &&
{ test -z "$chgrpcmd" || $doit $chgrpcmd "$dsttmp"; } &&
{ test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } &&
{ test -z "$chmodcmd" || $doit $chmodcmd $mode "$dsttmp"; } &&
# If -C, don't bother to copy if it wouldn't change the file.
if $copy_on_change &&
old=`LC_ALL=C ls -dlL "$dst" 2>/dev/null` &&
new=`LC_ALL=C ls -dlL "$dsttmp" 2>/dev/null` &&
eval "$initialize_posix_glob" &&
$posix_glob set -f &&
set X $old && old=:$2:$4:$5:$6 &&
set X $new && new=:$2:$4:$5:$6 &&
$posix_glob set +f &&
test "$old" = "$new" &&
$cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
then
rm -f "$dsttmp"
else
# Rename the file to the real destination.
$doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null ||
# The rename failed, perhaps because mv can't rename something else
# to itself, or perhaps because mv is so ancient that it does not
# support -f.
{
# Now remove or move aside any old file at destination location.
# We try this two ways since rm can't unlink itself on some
# systems and the destination file might be busy for other
# reasons. In this case, the final cleanup might fail but the new
# file should still install successfully.
{
test ! -f "$dst" ||
$doit $rmcmd -f "$dst" 2>/dev/null ||
{ $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
{ $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
} ||
{ echo "$0: cannot unlink or rename $dst" >&2
(exit 1); exit 1
}
} &&
# Now rename the file to the real destination.
$doit $mvcmd "$dsttmp" "$dst"
}
fi || exit 1
trap '' 0
fi
done
# Local variables:
# eval: (add-hook 'write-file-hooks 'time-stamp)
# time-stamp-start: "scriptversion="
# time-stamp-format: "%:y-%02m-%02d.%02H"
# time-stamp-time-zone: "UTC"
# time-stamp-end: "; # UTC"
# End:
enigmail-2.0.8/ipc/ 0000775 0000000 0000000 00000000000 13343027545 0014067 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/ipc/Makefile 0000664 0000000 0000000 00000000645 13343027545 0015534 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 https://mozilla.org/MPL/2.0/.
DEPTH = ..
include $(DEPTH)/config/autoconf.mk
DIRS = modules
.PHONY: dirs $(DIRS)
all: dirs
dirs: $(DIRS)
$(DIRS):
$(MAKE) -C $@
clean:
for dir in $(DIRS); do \
$(MAKE) -C $$dir clean; \
done
enigmail-2.0.8/ipc/modules/ 0000775 0000000 0000000 00000000000 13343027545 0015537 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/ipc/modules/.eslintrc.js 0000664 0000000 0000000 00000000204 13343027545 0017772 0 ustar 00root root 0000000 0000000 module.exports = {
"extends": "../../.eslintrc.js",
"rules": {
"no-constant-condition": 0,
"no-invalid-this": 0
}
};
enigmail-2.0.8/ipc/modules/Makefile 0000664 0000000 0000000 00000001362 13343027545 0017201 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 https://mozilla.org/MPL/2.0/.
DEPTH = ../..
include $(DEPTH)/config/autoconf.mk
EXTRA_JS_MODULES = \
subprocess.jsm \
enigmailprocess_shared_unix.js \
enigmailprocess_worker_common.js \
enigmailprocess_common.jsm \
enigmailprocess_shared_win.js \
enigmailprocess_worker_unix.js \
enigmailprocess_main.jsm \
enigmailprocess_unix.jsm \
enigmailprocess_worker_win.js \
enigmailprocess_shared.js \
enigmailprocess_win.jsm
all: $(EXTRA_JS_MODULES)
$(DEPTH)/util/install -m 644 $(DIST)/modules $^
clean: $(EXTRA_JS_MODULES)
$(DEPTH)/util/install -u $(DIST)/modules $^
enigmail-2.0.8/ipc/modules/enigmailprocess_common.jsm 0000664 0000000 0000000 00000051567 13343027545 0023024 0 ustar 00root root 0000000 0000000 /* -*- Mode: indent-tabs-mode: nil; js-indent-level: 2 -*- */
/* vim: set sts=2 sw=2 et tw=80: */
/* 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 https://mozilla.org/MPL/2.0/. */
"use strict";
/* eslint-disable mozilla/balanced-listeners */
/* exported BaseProcess, PromiseWorker */
/* global Components: false, ChromeWorker: false, */
var {
classes: Cc,
interfaces: Ci,
utils: Cu,
results: Cr
} = Components;
// const {
// Services
// } = Cu.import("resource://gre/modules/Services.jsm", {}); /* global Services: false */
Cu.import("resource://gre/modules/XPCOMUtils.jsm"); /* global XPCOMUtils: false */
Cu.importGlobalProperties(["TextDecoder", "TextEncoder"]);
XPCOMUtils.defineLazyModuleGetter(this, "AsyncShutdown",
"resource://gre/modules/AsyncShutdown.jsm"); /* global AsyncShutdown: false */
XPCOMUtils.defineLazyModuleGetter(this, "setTimeout",
"resource://gre/modules/Timer.jsm"); /* global Timer: false */
var SubScriptLoader = Cc["@mozilla.org/moz/jssubscript-loader;1"].getService(Ci.mozIJSSubScriptLoader);
SubScriptLoader.loadSubScript("resource://enigmail/enigmailprocess_shared.js", this);
var EXPORTED_SYMBOLS = ["BaseProcess", "PromiseWorker", "SubprocessConstants"];
const BUFFER_SIZE = 4096;
let nextResponseId = 0;
/* global SubprocessConstants: true */
/**
* Wraps a ChromeWorker so that messages sent to it return a promise which
* resolves when the message has been received and the operation it triggers is
* complete.
*/
class PromiseWorker extends ChromeWorker {
constructor(url) {
super(url);
this.listeners = new Map();
this.pendingResponses = new Map();
this.addListener("close", this.onClose.bind(this));
this.addListener("failure", this.onFailure.bind(this));
this.addListener("success", this.onSuccess.bind(this));
this.addListener("debug", this.onDebug.bind(this));
this.addEventListener("message", this.onmessage);
this.shutdown = this.shutdown.bind(this);
AsyncShutdown.webWorkersShutdown.addBlocker(
"Subprocess.jsm: Shut down IO worker",
this.shutdown);
}
onClose() {
AsyncShutdown.webWorkersShutdown.removeBlocker(this.shutdown);
}
shutdown() {
return this.call("shutdown", []);
}
/**
* Adds a listener for the given message from the worker. Any message received
* from the worker with a `data.msg` property matching the given `msg`
* parameter are passed to the given listener.
*
* @param {string} msg
* The message to listen for.
* @param {function(Event)} listener
* The listener to call when matching messages are received.
*/
addListener(msg, listener) {
if (!this.listeners.has(msg)) {
this.listeners.set(msg, new Set());
}
this.listeners.get(msg).add(listener);
}
/**
* Removes the given message listener.
*
* @param {string} msg
* The message to stop listening for.
* @param {function(Event)} listener
* The listener to remove.
*/
removeListener(msg, listener) {
let listeners = this.listeners.get(msg);
if (listeners) {
listeners.delete(listener);
if (!listeners.size) {
this.listeners.delete(msg);
}
}
}
onmessage(event) {
let {
msg
} = event.data;
let listeners = this.listeners.get(msg) || new Set();
for (let listener of listeners) {
try {
listener(event.data);
}
catch (e) {
Cu.reportError(e);
}
}
}
/**
* Called when a message sent to the worker has failed, and rejects its
* corresponding promise.
*
* @private
*/
onFailure({
msgId, error
}) {
this.pendingResponses.get(msgId).reject(error);
this.pendingResponses.delete(msgId);
}
/**
* Called when a message sent to the worker has succeeded, and resolves its
* corresponding promise.
*
* @private
*/
onSuccess({
msgId, data
}) {
this.pendingResponses.get(msgId).resolve(data);
this.pendingResponses.delete(msgId);
}
onDebug({
message
}) {
//dump(`Worker debug: ${message}\n`);
}
/**
* Calls the given method in the worker, and returns a promise which resolves
* or rejects when the method has completed.
*
* @param {string} method
* The name of the method to call.
* @param {Array} args
* The arguments to pass to the method.
* @param {Array} [transferList]
* A list of objects to transfer to the worker, rather than cloning.
* @returns {Promise}
*/
call(method, args, transferList = []) {
let msgId = nextResponseId++;
return new Promise((resolve, reject) => {
this.pendingResponses.set(msgId, {
resolve, reject
});
let message = {
msg: method,
msgId,
args
};
this.postMessage(message, transferList);
});
}
}
/**
* Represents an input or output pipe connected to a subprocess.
*
* @property {integer} fd
* The file descriptor number of the pipe on the child process's side.
* @readonly
*/
class Pipe {
/**
* @param {Process} process
* The child process that this pipe is connected to.
* @param {integer} fd
* The file descriptor number of the pipe on the child process's side.
* @param {integer} id
* The internal ID of the pipe, which ties it to the corresponding Pipe
* object on the Worker side.
*/
constructor(process, fd, id) {
this.id = id;
this.fd = fd;
this.processId = process.id;
this.worker = process.worker;
/**
* @property {boolean} closed
* True if the file descriptor has been closed, and can no longer
* be read from or written to. Pending IO operations may still
* complete, but new operations may not be initiated.
* @readonly
*/
this.closed = false;
}
/**
* Closes the end of the pipe which belongs to this process.
*
* @param {boolean} force
* If true, the pipe is closed immediately, regardless of any pending
* IO operations. If false, the pipe is closed after any existing
* pending IO operations have completed.
* @returns {Promise
ΠεÏισσότεÏη βοήθεια είναι διαθÎσιμη στο δικτυακό τόπο του
Enigmail
enigmail-2.0.8/lang/el/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020435 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Menú Enigmail en la ventana de redacción de mensajes
Firmar mensaje: Activa/desactiva el envío de correo firmado. El usuario recibe una notificación si hay un fallo en la firma.
Cifrar mensaje: Activa/desactiva el cifrado para todos los destinatarios antes de enviarlo. El usuario recibe una notificación si hay un fallo al cifrar.
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.
Usar PGP/MIME en este mensaje: Activa/desactiva el uso de PGP/MIME en este mensaje.
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.
Opciones predeterminadas de redacción: Submenú
Opciones de firmado/cifrado...: acceder a Configuración de cuentas... -> Seguridad OpenPGP.
Opciones de envío...: acceder a Preferencias -> pestaña Enviar.
Opciones de selección de clave...: acceder a Preferencias -> pestaña Selección de clave.
Opciones PGP/MIME...: acceder a Preferencias -> pestaña PGP/MIME.
Deshacer cifrado: Si hay algún problema al enviar el correo, como un fallo en el servidor POP que no acepta la solicitud, Enigmail no lo sabrá, y el mensaje cifrado seguirá mostrándose en la ventana de redacción. Con esta opción de menú, se deshacerá el cifrado/firma, volviendo a la ventana de redacción con su texto original. Como solución temporal, también se puede usar para descifrar el texto citado al contestar a mensajes cifrados. Enigmail debe descifrar automáticamente el mensaje citado, pero si se produce un fallo por cualquier motivo, se puede usar esta opción del menú para forzarlo.
Adjuntar clave pública...: Adjunta el bloque de la clave pública al mensaje, en un archivo con armadura ASCII. Se le preguntará el ID de usuario de las claves que se van a adjuntar.
Borrar frase contraseña guardada: Elimina de la caché las frases contraseñas introducidas manualmente. Esto es útil si se tienen varias frases contraseñas.
Ayuda: Muestra información de ayuda (esta página).
Usando el editor de reglas de Enigmail: Editar regla OpenPGP
En el editor de reglas, se pueden especificar opciones predeterminadas para cada destinatario, activando el cifrado, la firma y PGP/MIME; y para definir qué clave(s) OpenPGP va a usar. En este diálogo, se pueden especificar las reglas para un único destinatario, y para un grupo de destinatarios con atributos muy similares.
Definir reglas OpenPGP para: Contiene las direcciones de correo electrónico de los destinatarios (sin nombre, por ejemplo una dirección como alguien@correo.org). Se pueden especificar varias direcciones de correo, separadas por espacios. La dirección especificada aquí puede consistir de sólo la sección del dominio, para que se aplique al correo de cualquier dirección de ese dominio, como @correo.org se aplicará a alguien@correo.org, cualquiera@correo.org, otro@correo.org, etc.
Aplicar regla si el destinatario: Esto modifica si coinciden las direcciones de correo electrónico. Si se introducen varias direcciones, la opción se aplicará a todas. Los ejemplos de abajo están basados en que se ha introducido alguien@correo.org en el campo Reglas openPGP de arriba.
Es exactamente: Con esta opción, la regla sólo se activará en los correos a alguien@correo.org (exacto, no se tienen en cuenta las mayúsculas).
Contiene: Con esta opción, cualquier dirección de correo que contenga la cadena, cumplirá la regla, como unnombre@correo.dominio o nombre@correo.dominio.org
Comienza con: Con esta opción, cualquier dirección de correo que empiece por la cadena, cumplirá la regla, como alguien@correo.dominio.net, alguien@correo.nombre-dominio.com.
Acaba en: Con esta opción, cualquier dirección de correo que acabe en la cadena, cumplirá la regla, como otronombre@correo.org, alguien@correo.org
Continuar con la regla siguiente para la dirección coincidente
Activar esta función permitirá definir una regla pero no tener que especificar un ID de clave en el campo Usar las siguientes claves OpenPGP: para que se use la dirección de correo electrónico para comprobar una clave en el momento del envío. También se procesarán las reglas posteriores para la misma dirección.
No comprobar las reglas siguientes para la dirección coincidente
Activar esta función detiene el procesamiento de cualquier otra regla para las direcciones que cumplan la regla. Es decir, las reglas se reanudan procesando el próximo destinatario.
Usar las siguientes claves OpenPGP:
Use el botón Seleccionar clave(s)... para seleccionar las claves del destinatario que se usen para el cifrado. Al igual que la acción anterior, no se continúan procesando las reglas para las direcciones que cumplan la regla.
Predeterminada para firmar: Activa o desactiva la firma del mensaje. Esta opción usa o ignora lo especificado en la ventana de redacción de mensajes. Los valores son:
Nunca: Desactiva la firma, incluso si se activó en la ventana de redacción de mensajes (tiene preferencia sobre los otros valores).
Sí, si está seleccionada en la redacción del mensaje: Deja la firma como se haya especificado en la ventana de redacción de mensajes.
Siempre: Activa la firma, incluso si no estaba activada en la ventana de redacción de mensajes.
Estas opciones de firma se aplican a todas las reglas que coincidan con el criterio. Si una de las reglas desactiva la firma, el mensaje no se firmará, independientemente de que otras especifiquen Siempre.
Cifrar: Activa o desactiva el cifrado del mensaje. Las opciones permitidas y su significado son las mismas que para la firma de mensajes.
PGP/MIME: Activa o desactiva el uso de la codificación PGP/MIME (RFC 3156) en el mensaje. Si PGP/MIME está desactivado, los mensajes se codifican usando "PGP integrado". Los valores permitidos y su significado son los mismos que para la firma de mensajes.
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.
enigmail-2.0.8/lang/es-AR/help/initError.html 0000664 0000000 0000000 00000005256 13343027545 0020747 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Ayuda de Enigmail
Cómo Resolver Problemas al Iniciar OpenPGP
Hay varias razones por las que no se tiene éxito al inicializar OpenPGP. Las más comunes son descritas más abajo &
para más información por favor visite la página de Soporte de Enigmail.
No se pudo encontrar GnuPG
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)
Enigmime falló al inicilizarse
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.
enigmail-2.0.8/lang/es-AR/help/messenger.html 0000664 0000000 0000000 00000011530 13343027545 0020752 0 ustar 00root root 0000000 0000000
Ayuda de Enigmail: Lectura de mensajes
Ayuda de Enigmail
Usando Enigmail para leer mensajes
Botón Descifrar en la ventana principal de correo
Este botón se puede usar para varios propósitos: descifrar, verificar o importar claves públicas. Normalmente el descifrado/verificación se realiza automáticamente, aunque hay una opción para desactivar esto. Sin embargo, si esto falla, normalmente aparecerá un breve mensaje de error en la línea de estado de Enigmail. Si se pulsa el botón Descifrar, podrá ver un mensaje de error más detallado, incluyendo la salida del comando GnuPG.
Los iconos Lápiz y Llave mostrados en la cabecera del mensaje
Los iconos Lápiz y Llave en la cabecera del mensaje indican si el mensaje que se está leyendo está firmado y/o cifrado y si la firma es buena, es decir; que el mensaje no se ha modificado desde el momento de su firma. Si el mensaje ha sido modificado, el icono del Lápiz cambiará a un Lápiz roto para indicar que la firma no es correcta. Al pulsar con el botón derecho del ratón en los iconos del Lápiz o Llave, se obtendrá un menú con las siguientes opciones:
Información de seguridad OpenPGP: permite ver el estado de salida de GnuPG para el mensaje.
Copiar información de seguridad OpenPGP: copia el estado de salida de GnuPG al portapapeles; para pegarlo en un mensaje de respuesta, etc.
Ver ID fotográfico OpenPGP: permite ver la Foto ID de la persona que envió el mensaje, si tiene una foto incrustada en su clave pública (Esta opción sólo se activará si existe un ID fotográfico en su clave).
Información de seguridad S/MIME: permite ver la información de seguridad S/MIME del mensaje.
Si 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.
Abrir adjuntos cifrados / importar claves OpenPGP adjuntas
Los adjuntos con el nombre *.pgp, *.asc y *.gpg se reconocen como adjuntos que se pueden manejar especialmente con Enigmail. Al pulsar con el botón derecho en un adjunto de este tipo se activan dos elementos especiales en el menú contextual: Descifrar y Abrir y Descifrar y Guardar. Use estos elementos si desea que Enigmail descifre un adjunto antes de abrirlo o guardarlo. Si se reconoce un adjunto como un archivo de clave OpenPGP, se le ofrece la posibilidad de importar las claves a sus anillos.
enigmail-2.0.8/lang/es-AR/help/rulesEditor.html 0000664 0000000 0000000 00000006701 13343027545 0021267 0 ustar 00root root 0000000 0000000
Ayuda de Enigmail: Editor de reglas
Ayuda de Enigmail
Usando el editor de reglas de Enigmail
En el editor de reglas, se pueden especificar opciones predeterminadas por destinatario para activar el cifrado, firma y PGP/MIME, así como definir qué clave(s) OpenPGP usar. Cada regla consiste de 5 campos y se representa en una sola línea:
Correo electrónico: Las direcciones de correo en los campos Para:, Cc: y Cco: tienen que coincidir. La coincidencia funciona en subcadenas (Más detalles en el diálogo de Editar regla)
Clave(s) OpenPGP: Una lista de IDs de claves OpenPGP para usar con el destinatario.
Firmar: Activar o desactivar el firmado de mensajes. Esta opción usa o ignora lo que se haya especificado en la ventana de redacción de mensajes. Los valores son:
Nunca: Desactiva la firma, incluso si estaba activada en la ventana de redacción del mensaje (tiene preferencia sobre los otros valores).
Posible: Deja la firma como se haya especificado en la ventana de redacción de mensajes.
Siempre: Activar la firma, incluso si no está activada en la ventana de redacción de mensajes.
Estas opciones de firma se aplican a todas las reglas que las cumplan. Si una de las reglas desactiva la firma, el mensaje no se firmará, independientemente de otras reglas que especifiquen Siempre.
Cifrar: Activa o desactiva el cifrado del mensaje. Las opciones permitidas y su significado son las mismas que para la firma.
PGP/MIME: Activa o desactiva el uso de la codificación del mensaje PGP/MIME (RFC 3156). Si PGP/MIME está desactivado, los mensajes se codifican usando "PGP integrado". Los valores permitidos y su significado son los mismos que para la firma de mensajes.
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Menú Enigmail en la ventana de Redacción de Correo
Firmar mensaje: Activa/Desactiva el envío de mensajes firmados. El usuario es notificado si el firmado falla.
Cifrar mensaje: Activa/Desactiva el cifrado para el(los) destinatario(s) antes del envío. El usuario es notificado si el cifrado falla.
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.
Usar PGP/MIME para este mensaje : Activa/Desactiva el uso de
PGP/MIME
para este mensaje.
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.
Opciones por defecto para redacción: Submenú.
Opciones de Firma/Cifrado...: atajo a Configuración de Cuentas ->
Opciones de OpenPGP.
Opciones de Envío...: atajo a la pestaña Opciones ->
Enviando.
Opciones de Selección de Clave...: atajo a la pestaña Preferencias ->
Selección de Clave.
Opciones PGP/MIME...: atajo a la pestaña Preferencias ->
PGP/MIME.
Deshacer cifrado: Si hay un fallo al momento del envío,
tal como el servidor POP no aceptando la petición, Enigmail no sabrá al respecto, y el mensaje cifrado continuará siendo mostrado en la ventana de Redacción. Elegir este ítem de menú deshará el cifrado/firmado, devolviendo la ventana de Redacción a su texto original. Como una solución temporal, esta opción puede también ser usada para descifrar el texto citado cuando se responde a mensajes cifrados. Enigmail debiera descifrar automáticamente el texto citado, pero si eso falla por alguna razón, usted puede utilizar este ítem de menú para forzarlo.
Insertar clave pública: inserta la clave pública como un bloque de texto ASCII-blindado en la posición actual del cursor en la ventana de Redacción. Se le preguntará por la dirección email de la(s) clave(s) a ser insertada(s). Las Claves insertadas de esta manera serán reconocidas automáticamente en el lado receptor por Enigmail. Luego de la inserción de clave, usted aún puede elegir firmar/cifrar el mensaje como sea necesario. Además, no inserte más de un bloque de claves en un mensaje; sólo especifique múltiples direcciones email, separadas por comas o espacios, cuando se le pregunte.
Limpiar clave salvada: Limpia la contraseña retenida. útil si usted tiene múltiples contraseñas.
Ayuda: Despliega la información de Ayuda del sitio web (esta página).
Usando el Editor de Reglas de Enigmail: Editar Regla OpenPGP
En 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.
Poner Regla OpenPGP para : Contiene la(s) dirección(es) email de el/los destinatario(s) (sin nombres, p.ej. sólo una dirección como alguien@email.dom). Usted puede especificar varias direcciones email, separadas por espacios. La dirección especificada aquí puede consistir sólo de la sección de dominio de modo que cualquier dirección en ese dominio concuerde, p.ej. @email.domain permitirá concordancia a body@email.comain, somebody@email.domain, anybody@email.domain, etc.
Aplicar regla si el destinatario ...:
Esto modifica la concordancia de las direcciones email. Si se ingresa múltiples direcciones, la configuración se aplicará a todas. Los ejemplos abajo están basados en body@email.domain ingresado en el campo Poner Regla OpenPGP para más arriba.
Es exactamente: con esta configuración, la regla sólo se disparará en emails para body@email.domain (comparación exacta, sin considerar mayúsculas/minúsculas).
Contiene: con esta configuración, cualquier dirección email que contenga el patrón concuerda, p.ej. anybody@email.domain o body@email.domain.net
Empieza por : con esta configuración, cualquier dirección email comenzando con el patrón concuerda, p.ej. body@email.domain.net, body@email.domain-name.com.
Acaba en: con esta configuración, cualquier dirección email finalizando en el patrón concuerda, p.ej. anybody@email.domain, somebody@email.domain.
Continuar con la siguiente regla para la dirección que coincida
Activar esta función le permitirá definir una regla pero no tener que especificar un KeyID en el campo Usar las siguientes claves OpenPGP:
, de modo que la dirección email es usada para buscar una clave al momento de enviar. Además, reglas adicionales para la(s) misma(s) dirección(es) también será(n) procesada(s).
No comprobar más reglas para la dirección que coincida
Activar esta función detiene el procesamiento de cualquier otra regla para la(s) dirección(es) que coincide(n) si es que la regla coincide; p.ej. el procesamiento de reglas continúa con el siguiente destinatario.
Usar las siguientes claves OpenPGP:
Use el botón Seleccionar Clave(s).. para seleccionar las claves receptoras a ser usadas para el cifrado. Como en la acción de arriba, no se sigue procesando más reglas para la(s) dirección(es) coincidentes.
Por defecto para Firmado: activa o desactiva la firma de mensaje. Esto o bien usa o anula lo que usted ha especificado en la ventana de redacción de mensaje. Los valores son:
Nunca: desactiva el firmado, incluso si está activado en la ventana de redacción de mensaje (anula los otros valores)
Sí, si está seleccionado en la redacción del mensaje: deja el firmado tal como está especificado en la ventana de redacción del mensaje
Siempre: activa el firmado, incluso si no estaba activado en la ventana de redacción del mensaje
Esas configuraciones para firmado son aplicadas para todas las reglas que coinciden. Si una de las reglas desactiva el firmado, el mensaje no será firmado, sin importar otras reglas que especifiquen Siempre.
Cifrado: activa o desactiva el cifrado de mensaje. Las configuraciones permitidas y su significado son las mismas que para la firma de mensajes.
PGP/MIME: activa o desactiva el uso de la codificación de mensaje PGP/MIME (RFC 3156).
Si PGP/MIME está desactivado, los mensajes son codificados utilizando "inline PGP". Los valores permitidos y sus significados son los mismos que para la firma de mensajes.
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.
enigmail-2.0.8/lang/es-ES/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020751 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
enigmail-2.0.8/lang/es-ES/help/messenger.html 0000664 0000000 0000000 00000011530 13343027545 0020757 0 ustar 00root root 0000000 0000000
Ayuda de Enigmail: Lectura de mensajes
Ayuda de Enigmail
Usando Enigmail para leer mensajes
Botón Descifrar en la ventana principal de correo
Este botón se puede usar para varios propósitos: descifrar, verificar o importar claves públicas. Normalmente el descifrado/verificación se realiza automáticamente, aunque hay una opción para desactivar esto. Sin embargo, si esto falla, normalmente aparecerá un breve mensaje de error en la línea de estado de Enigmail. Si se pulsa el botón Descifrar, podrá ver un mensaje de error más detallado, incluyendo la salida del comando GnuPG.
Los iconos Lápiz y Llave mostrados en la cabecera del mensaje
Los iconos Lápiz y Llave en la cabecera del mensaje indican si el mensaje que se está leyendo está firmado y/o cifrado y si la firma es buena, es decir; que el mensaje no se ha modificado desde el momento de su firma. Si el mensaje ha sido modificado, el icono del Lápiz cambiará a un Lápiz roto para indicar que la firma no es correcta. Al pulsar con el botón derecho del ratón en los iconos del Lápiz o Llave, se obtendrá un menú con las siguientes opciones:
Información de seguridad OpenPGP: permite ver el estado de salida de GnuPG para el mensaje.
Copiar información de seguridad OpenPGP: copia el estado de salida de GnuPG al portapapeles; para pegarlo en un mensaje de respuesta, etc.
Ver ID fotográfico OpenPGP: permite ver la Foto ID de la persona que envió el mensaje, si tiene una foto incrustada en su clave pública (Esta opción sólo se activará si existe un ID fotográfico en su clave).
Información de seguridad S/MIME: permite ver la información de seguridad S/MIME del mensaje.
Si 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.
Abrir adjuntos cifrados / importar claves OpenPGP adjuntas
Los adjuntos con el nombre *.pgp, *.asc y *.gpg se reconocen como adjuntos que se pueden manejar especialmente con Enigmail. Al pulsar con el botón derecho en un adjunto de este tipo se activan dos elementos especiales en el menú contextual: Descifrar y Abrir y Descifrar y Guardar. Use estos elementos si desea que Enigmail descifre un adjunto antes de abrirlo o guardarlo. Si se reconoce un adjunto como un archivo de clave OpenPGP, se le ofrece la posibilidad de importar las claves a sus anillos.
enigmail-2.0.8/lang/es-ES/help/rulesEditor.html 0000664 0000000 0000000 00000006671 13343027545 0021302 0 ustar 00root root 0000000 0000000
Ayuda de Enigmail: Editor de reglas
Ayuda de Enigmail
Usando el editor de reglas de Enigmail
En el editor de reglas, se pueden especificar opciones predeterminadas por destinatario para activar el cifrado, firma y PGP/MIME, así como definir qué clave(s) OpenPGP usar. Cada regla consiste de 5 campos y se representa en una sola línea:
Correo electrónico: Las direcciones de correo en los campos Para:, Cc: y Cco: tienen que coincidir. La coincidencia funciona en subcadenas (Más detalles en el diálogo de Editar regla)
Clave(s) OpenPGP: Una lista de IDs de claves OpenPGP para usar con el destinatario.
Firmar: Activar o desactivar el firmado de mensajes. Esta opción usa o ignora lo que se haya especificado en la ventana de redacción de mensajes. Los valores son:
Nunca: Desactiva la firma, incluso si estaba activada en la ventana de redacción del mensaje (tiene preferencia sobre los otros valores).
Posible: Deja la firma como se haya especificado en la ventana de redacción de mensajes.
Siempre: Activar la firma, incluso si no está activada en la ventana de redacción de mensajes.
Estas opciones de firma se aplican a todas las reglas que las cumplan. Si una de las reglas desactiva la firma, el mensaje no se firmará, independientemente de otras reglas que especifiquen Siempre.
Cifrar: Activa o desactiva el cifrado del mensaje. Las opciones permitidas y su significado son las mismas que para la firma.
PGP/MIME: Activa o desactiva el uso de la codificación del mensaje PGP/MIME (RFC 3156). Si PGP/MIME está desactivado, los mensajes se codifican usando "PGP integrado". Los valores permitidos y su significado son los mismos que para la firma de mensajes.
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/eu/ 0000775 0000000 0000000 00000000000 13343027545 0014646 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/eu/am-enigprefs.properties 0000664 0000000 0000000 00000000124 13343027545 0021336 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=OpenPGP Sekurtasuna
enigmail-2.0.8/lang/eu/contents.rdf 0000775 0000000 0000000 00000001156 13343027545 0017206 0 ustar 00root root 0000000 0000000
enigmail-2.0.8/lang/eu/enigmail.dtd 0000664 0000000 0000000 00000104703 13343027545 0017135 0 ustar 00root root 0000000 0000000
OHARRA: Gakoa sortzeko prozesua zenbait minutu iraun ditzake. Ez zaitez aplikaziotik atera gakoa sortzen ari den bitartean. Bitartean ordenagailua erabiltzea edo disko gogorran eragiketak egiten dituzten ekintzak egiten badituzu, ausazko datuen sorreran lagunduko du eta prozesua azkartuko du. Jakinarazi egingo zaizu gako sorrera prozesua bukatzerakoan.">
' ez du balio">
OHARRA: Gakoa sortzeko prozesua minutu batzuk iraun ditzake. Ez zaitez aplikaziotik atera gakoa sortzen ari den bitartean. Gakoa sortu eta gero abisu bat agertuko zaizu.">
Oharra: Enigmail-k sinadurak kontu
eta nortasun guztientzat egiaztatuko ditu, gaituta egon ez arren.">
Mila esker Enigmail erabiltzeagatik.">
Mila esker Enigmail erabiltzeagatik.">
enigmail-2.0.8/lang/eu/enigmail.properties 0000664 0000000 0000000 00000062553 13343027545 0020564 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
# Strings used within enigmailCommon.js
# Strings in enigmailAbout.js
# Strings in enigmailKeygen.js
enigAlert=Enigmail Abisua
enigConfirm=Enigmail Baieztapena
enigError=Enigmail Errorea
enigPrompt=Enigmail Mezua
dlgYes=&Bai
dlgNo=&Ez
dlgKeepSetting=Nire erantzuna gogoratu eta ez galdetu berriro
dlgNoPrompt=Ez erakutsi gehiago mezu hau
dlg.button.delete=&Ezabatu
dlg.button.cancel=&Utzi
dlg.button.close=&Itxi
dlg.button.continue=&Jarraitu
dlg.button.skip=&Saltatu
dlg.button.view=I&kusi
repeatPrefix=\n\nAbisu hau %S errepikatuko da.
repeatSuffixSingular=behin gehiago
repeatSuffixPlural=gehiagotan
noRepeat=\n\nAbisua hau ez da errepikatuko Enigmail eguneratzen duzun arte.
noLogDir=Mesedez, 'Log karpeta' arazketa ezaugarria ezarri ezazu log fitxategia sortzeko
noLogFile=Log fitxategia ez da oraindik sortu!
restartForLog=Mesedez, aplikazioa berrabiatu log fitxategia sortzeko
pgpNotSupported=Dirudienez Enigmail PGP 6.x-rekin batera erabiltzen ari zara.\n\nZoritxarrez, PGP 6.x zenbait arazo ditu eta horrek Enigmail gaizki ibiltzea dakar. Hortaz, Enigmail-ek ez du PGP 6.x onartzen; mesedez, horren ordez GnuPG (GPG) erabili ezazu.\n\nGnuPG-ra aldatzeko laguntzarik behar baldin baduzu, Enigmail weborriaren Laguntza atala begiratu ezazu.
avoidInitErr=Mezu hau betirako kentzeko, arazoa konpondu ezazu edo Enigmail desinstalatu ezazu. Laguntza botoian sakatu ezazu xehetasun gehiago behar badituzu.
passphraseCleared=Pasahitza ezabatu egin da.
passphraseCannotBeCleared=Pasahitzak kudeatzeko gpg-agent erabiltzen ari zara. Horregatik, Enigmail-etik ezin da pasahitza ezabatu.
noPhotoAvailable=Ez Dago Argazkirik
# Strings in enigmailMessengerOverlay.js
# Strings in enigmailMsgComposeOverlay.js
# Strings in enigmailMsgHdrViewOverlay.js
usingVersion=Enigmail %S bertsioa martxan dago
usingAgent=%S exekutagarria %s erabiltzen zifratu eta argitzeko
agentError=ERROREA: Ezin izan da Enigmime serbitzuarekin konexioa egin
# Strings in enigmailNavigatorOverlay.js
# Strings in pref-enigmail.js
# Strings used in components/enigmail.js
accessError=Enigmail serbitzura sartzean errore bat gertatu da
onlyGPG=Gako sorrera GnuPG-rekin bakarrik (ez PGP-rekin) dabil!
keygenComplete=Gakoaren sorrera bukatu da! Sinatzeko <%S> nortasuna erabiliko da.
revokeCertRecommended=Gogor gomendatzen dugu zure gakoarentzat ezeztapen ziurtagiri bat sortzea. Ziurtagiri hau zure gakoa ezgaitzeko erabili daiteke, adibidez, zure gako sekretua galdu edo arriskuan badago. Ezeztapen ziurtagiri hau orain sortu nahi al duzu?
keyMan.button.generateCert=&Ziurtagiria Sortu
genCompleteNoSign=Gakoaren sorrera bukatu da!
genGoing=Gakoaren sorrera prozesua dagoeneko martxan dago!
passNoMatch=Pasahitzak ez datoz bat, mesedez, berriz sartu itzazu
passCheckBox=Mesedez, laukitxoa sakatu ezazu gakoarentzak pasahitzik ez badago
passUserName=Mesdez, nortasun honentzako erabiltzailearen izena sartu ezazu
passCharProblem=Zure pasahitzan karaktere bereziak erabiltzen ari zara. Zoritxarrez, honek beste zenbait aplikazioetan arazoak sortu ditzake. Horregatik karaktere hauek bakarik dituen pasahitza aukeratu ezazu:\na-z A-Z 0-9 /.;:-,!?(){}[]%*
changePassFailed=Pasahitzaren aldaketak huts egin du.
removePassphrase=Orain dagoen pasahitza ezabatu nahi al duzu pasahitz berririk sartu gabe?
keyMan.button.removePass=&Pasahitza Ezabatu
keyConfirm='%S'-rentzat gako publiko eta pribatuak sortu nahi al duzu?
keyMan.button.generateKey=Gakoa &Sortu
keyAbort=Gako sorrera geldiarazi nahi al duzu?
keyMan.button.generateKeyAbort=Gako Sorrera &Geldiarazi
keyMan.button.generateKeyContinue=Gako Sorrera &Jarraitu
expiryTooLong=Ezin da 100 urte baino gehiagoko iraungipena duen gakoa sortu.
expiryTooShort=Zure gakoa gutxienez egun baterako balio behar du.
keyGenFailed=Gako sorrerak huts egin du. Xehetasunak ikusteko, mesedez, Enigmail konsola begiratu ezazu (Enigmail Menua > Enigmail Araztu).
# (said file also re-uses some strings from above)
securityInfo=Enigmail Sekurtasun Informazioa\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Mezu honen eranskinak ez dira sinatu edo zifratu*\n\n
possiblyPgpMime=Ziurenik PGP/MIME-k mezua sinatu edo zifratu egin du; Argitu botoia klikatu ezazu egiatzatzeko
noDecrypted=Ez dago argituko mezurik gordetzeko!\nFitxategia menuan dagoen Gorde komandoa erabili ezazu
noMessage=Ez dago mezurik gordetzeko!
useButton=Mesedez Argitu botoia sakatu ezazu mezua argitzeko
saveHeader=Enigmail: Argitutako mezua gorde
saveAttachmentHeader=Enigmail: Argitutako eranskina gorde
noTempDir=Ez da idatzi daitekeen aldi baterako karpetarik aurkitu.\nMesedez, TEMP ingurune aldagaia ezarri ezazu
attachmentPgpKey=Irekitzen ari zaren '%S' eranskina OpenPGP gako fitxategi bat dirudi.\n\n'Inportatu' sakatu ezazu gakoa inportatzeko edo 'Ikusi' sakatu ezazu haren edukia azpian dagoen arakatzailean ikusteko.
beginPgpPart=********* *ZIFRATU edo SINATUTAKO GUNEAREN HASIERA* *********
endPgpPart=********** *ZIFRATU edo SINATUTAKO GUNEAREN BUKAERA* **********
notePartEncrypted=Enigmail: *Mezu honen zati batzuk EZ dira sinatu edo zifratu*
noteCutMessage=Enigmail: *Mezu bloke anitz aurkitu dira -- argitze/egiaztatze prozesua bertan behera utzi da*
decryptOkNoSig=Kontuz\n\nArgitze prozesua ondo bukatu da, baina sinadura ezin izan da ondo egiaztatu.
msgOvl.button.contAnyway=Edonola Ere &Jarraitu
# Strings used in enigmailUserSelection.js
keysToExport=Txertatko Diren OpenPGP Gakoak Aukeratu
keysToUse=%S-rentzat erabiliko den(diren) OpenPGP Gako(ak) aukeratu
pubKey=%S-rentzat gako publikoa\n
windowLocked=Idazteko lehioa blokeatuta dago; bidaltzea ezeztatu da
sendUnencrypted=Enigmail-ek hasieratzerakoan huts egin du.\nMezua zifratu gabe bidali?
composeSpecifyEmail=Mesedez zure lehendabiziko helbide elektronikoa jarri ezazu. Hau bidaliko diren mezuak sinatzeko gakoa aukeratzeko erabiliko da.\nBete gabe uzten baduzu, NORK halbidea erabiliko da sinatzeko gakoa aukeratzeko.
sendingHiddenRcpt=Mezu hau BCC (ezkutuko kopia) hartzaileak ditu. Mezu hau zifratuta bidaltzen bada, BCC hartzaileak ezkutatu ahal daitezke baina produktu batzuen erabiltzaileak (adib. PGP Corp.) ezin izango dute mezua argitu. Hau hartuta, BCC emailak zifratutako mezuekin ez bidaltzea gomendatzen dugu.
sendWithHiddenBcc=BCC hartzaileak ezkutatu
sendWithShownBcc=Normaltasunez zifratu
sendingNews=Zifratutako mezua bidaltzeko operazioa bertan behera utzi da.\n\nMezu hau ezin da zifratu hartzaileen artean berri-taldeak daudelako. Mesedez, mezua zifratu gabe bidali ezazu.
sendToNewsWarning=Kontuz: zifratutako email bat berri-talde batera bidaltzera zoaz.\n\nHau ez dago comendatua, honek bakarrik zentzuzkoa izango da baldin eta hartzaile guztiak mezua argitu dezakete, hau da, mezua hartzaile guztien gakoekin zifratuta badago. Mesedez, mezu hau bidali ezazu bakarrik egiten hari zarenaz ziur bazaude.\n\nJarraitu?
hasHTML=HTML email-aren abisua:\nMezu honek HTML izan dezake, honek sinadura/zifraketa-ren hutsegitea ekar dezake. Etorkizunean hau eragozteko, sinatutako email bat bidaltzeko SHIFT tekla sakatu ezazu Idatzi/Erantzun botoia sakatzerakoan.\nZure aukera lehenetsita email-a sinatzea bada, 'Mezuak HTML-n Idatzi' laukitxoa ezgaitu beharko zenuke HTML posta kontu honetan betirako ezgaitzeko.
strippingHTML=Mezuak HTML formatu informazioa dauka eta hau galuko da sinatu/zifratzeko testu arruntan bilakatzerakoan. Jarraitu nahi al duzu?
msgCompose.button.sendAnyway=&Mezua Bidali Edonola
attachWarning=Mezu honen eranskinak ez dira lokalak eta ezin dira zifratu. Eranskinak zifratu ahal izateko, fitxategi lokal bezala gorde itzazu eta gero erantsi itzazu. Mezua edonola bidali nahi al duzu?
quotedPrintableWarn=Mezuak bidaltzeko 'quoted-printable' kodifikazioa gaitu duzu. Hau zure mezuaren argitze edo/eta egiaztatze okerra ekar dezake.\nMezuak 'quoted-printable' kodifikazioa erabiliz bidaltzeko aukera ezgaitu nahi al duzu?
minimalLineWrapping=Lerroek %S karaktertara iristerakoan salto egitea konfiguratu duzu. Zifraketa eta/edo sinatze on batentzako, balio hau gutxienez 68 izan behar du.\nLerroen gehienezko luzeera 68 karakteretara orain aldatu nahi al duzu?
warning=Kontuz
signIconClicked=Sinadura eskuz aldatu duzu. Hortaz, mezua idazten ari zaren bitartean, sinadura (des)aktibatzea ez dator bat zifraketa (des)aktibatzearekin.
sendAborted=Bidaltze eragiketa bertan bera utzi da\n\n
statPGPMIME=PGP/MIME
statSigned=SINATUTA
statEncrypted=ZIFRATUTA
statPlain=SINATU eta ZIFRATU GABE
offlineSave=%S mezua Bidali Gabeko Mezuen karpetako %S-n gorde nahi al duzu?
onlineSend=%S mezua %S-ri bidali nahi al diozu?
encryptKeysNote=Oharra: mezu hau ondorengo erabiltzaile ID-ak/gakoak erabiliz zifratu da:
signFailed=Enigmail-n errore bat egon da eta zifraketak/sinadurak huts egin du; mezua zifratu gabe bidali nahi al duzu?
msgCompose.button.sendUnencrypted=Mezua Zifratu Gabe &Bidali
acctNotConfigured=Ez duzu nortasun hau Enigmail sekurtasuna erabiltzeko konfiguratu.\nMezua zifratu gabe bidali nahi al duzu?
recipientsSelectionHdr=Zifraketarako Hartzaileak Aukeratu
configureNow=Aukeratutako nortasunarentzat oraindik ez duzu Enigmail sekurtasuna konfiguratu. Orain egin nahi al duzu?
signYes=Mezua sinatuko da
signNo=Mezua ez da sinatuko
# Strings used in enigmailAttachmentDialog.js
# Strings used in am-enigprefs.js
encryptYes=Mezua zifratuko da
encryptNo=Mezua ez da zifratuko
rulesConflict=Hartzaileen arauen artean gatazka dago\n%S\n\nEzarpen hauekin mezua bidali nahi al duzu?
msgCompose.button.configure=&Konfiguratu
msgCompose.button.send=Mezua &Bidali
msgCompose.button.save=Mezua &Gorde
# Strings used in enigmailSingleRcptSettings.js
keyNeeded=%S gako publikoa sinadura egiaztatzeko behar da
clickDecrypt=; Argitu botoia sakatu
clickDecryptRetry=; Argitu botoia sakatu berriz saiatzeko
clickPen=; 'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
clickPenDetails=; 'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
clickQueryPenDetails=; 'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
clickKey=; 'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
clickQueryKeyDetails=;'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
clickKeyDetails=; 'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
clickPenKeyDetails=; 'Xehetasunak' botoian klik egin ezazu informazio gehiago eskuratzeko
msgPart=%S mezuaren zatia
msgSigned=Sinatutako
msgEncrypted=Zifratutako
msgSignedAndEnc=Sinatu eta zifratutako
unverifiedSig=Egiaztatu gabeko sinadura
incompleteDecrypt=Bukatu gabeko argitzea
failedSig=Errorea - sinaduraren egiaztapenak huts egin du
needKey=Errorea - mezua argitzeko gako sekretua behar da
failedDecrypt=Errorea - argitzeak huts egin du
badPhrase=Errorea - pasahitz okerra
failedDecryptVerify=Errorea - argitzeak/egiaztapenak huts egin du
viewInfo=; Xehetasunentzako Ikusi > Mezuaren Sekurtasun Informazioa
decryptedMsg=Argitutako mezua
# Strings used in enigmailRulesEditor.js
testNoSvc=EnigTest: Ezin izan da Enigmail serbitzura konektatu
testNoEmail=EnigTest: Frogarako e-posta helbidea jarri ezazu
testSucceeded=Enigmail ondo funtzionatzen ari da. Xehetasunak nahi badituzu, Enigmail menutik ireki daitekeen kontsola begiratu ezazu
oldGpgVersion=Enigmail-ren hasieraketak huts egin du.\n\nGnuPG %S bertsioa erabiltzen ari zara eta ez dago eguneratua. Enigmailek GnuPG 1.4 bertsioa edo berriago bat behar du. Mesedez, zure GnuPG instalazioa eguneratu ezazu edo Enigmail-k ez du funtzionatuko.
locateGpg=GnuPG programa bilatu
invalidGpgPath=Emandako helbidearekin ezin da GnuPG exekutatu. Hortaz, Enigmail ezgaituta egongo da GnuPG-ren helbidea berriz sartu arte edo aplikazioa berrabiatu arte.
warningsAreReset=Abisu guztiak berrezarri dira.
prefs.gpgFound=GnuPG hemen aurkitu da: %S
prefs.gpgNotFound=Ezin izan da GnuPG aurkitu
prefs.warnAskNever=Kontuz: aukera hau aktibatzen bada hartzaile batentzako gakorik ez badago ez da e-posta zifratuko eta ez da horren abisurik egongo -- Enigmail-k ez dizu hori gertatzen delaren berri emango!
prefEnigmail.oneKeyserverOnly=Errorea - gako-serbitzari bakarra jarri dezakezu falta diren OpenPGP gakoak deskargatzeko.
# Strings used in enigmailSearchKey.js
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
enterPass=Mesedez, zure OpenPGP pasahitza sartu ezazu
enterPassOrPin=Mesedez, zure OpenPGP pasahitza edo zure SmartCard-aren PIN-a sartu ezazu
repeatPass=Mesedez, zure OpenPGP pasahitza berriz sartu ezazu
rememberPass=Pasahitza %S minutuz gogoratu
enterAdminPin=Mesedez, zure SmartCard-aren ADMIN PIN-a sartu ezazu
enterCardPin=Mesedez, zure SmartCard-aren PIN-a sartu ezazu
notInit=Errorea - Enigmail serbitzua ez da oraindik hasieratu
badCommand=Errorea - zifraketa komandoak huts egin du
cmdLine=komando lerroa eta output:
notRequired=Errorea - ez da zifraketarik behar
notComplete=Errorea - gako sorketa ez da oraindik bukatu
invalidEmail=Errorea - baliogabeko e-posta helbidea(k)
noPassphrase=Errorea - ez da pasahitzik sartu
noPGPblock=Errorea - Ez da OpenPGP babestutako datu blokerik aurkitu
unverifiedReply=Mezuaren tabulatutako zatia (erantzuna) ziruenik aldatu zen
decryptToImport=Argitu botoia sakatu ezazu mezuan dagoen gako publikoaren blokea inportatzeko
sigMismatch=Errorea - Sinadurak ez datoz bat
cantImport=Errorea gako publikoa inportatzerakoan\n\n
sc.wrongCardAvailable=Zure irakurgailuan aurkitutako %S SmartCard-a ezin da mezua prozesatzeko erabili.\nMesedez, zure %S SmartCard-a sartu ezazu eta eragiketa errepikatu ezazu.
sc.insertCard=Eragiketak zure %S SmartCard-a behar du.\nMesedez, behar den SmartCard-a sartu ezazu eta eragiketa errepikatu ezazu.
sc.removeCard=Eragiketak irakurgailuan SmartCard-ik ez egotea behar du.\nMesedez, zure SmartCard-a atera ezazu eta eragiketa errepikatu ezazu.
sc.noCardAvailable=Irakurgailuan ez da SmartCard-ik aurkitu.\nMesedez, zure SmartCard-a sartu eta eragiketa errepikatu ezazu.
sc.noReaderAvailable=Zure SmartCard irakurgailua ezin da aurkitu.\nMesedez, zure SmartCard irakurgailua konektatu ezazu, zure txartela sartu eta eragiketa errepikatu ezazu.
gpgNotFound=Ezin izan da '%S' GnuPG programa aurkitu.\nZiurtatu zaitez GnuPG exekutagarriaren helbidea zuzen jarri duzula Enigmail Lehentasunetan.
gpgNotInPath=Ezin izan da PATH-ean GnuPG exekutagarria aurkitu.\nZiurtatu zaitez GnuPG exekutagarriaren helbidea zuzen jarri duzula Enigmail Lehentasunetan.
enigmimeNotAvail=Enigmime Serbitzua ez dago eskuragarri
gpgAgentNotStarted=Zure GnuPG %S bertsiorako behar den gpg-agent-a ezin izan da abiatu.
prefUntrusted=MESFIDAGARRIA
prefRevoked=EZEZTATUTAKO GAKOA
prefExpiredKey=IRAUNGITAKO GAKOA
prefExpired=IRAUNGITA
prefGood=%S-ren sinadura ona
prefBad=%S-ren sinadura OKERRA
failCancel=Errorea - Gakoaren harrera erabiltzaileak utzi egin du
failNoServer=Errorea - Gakoak jasotzeko gako-serbitzari iturubururik ez da jarri
failNoID=Errorea - Ez da jasoko den gakoaren ID-a jarri
failKeyExtract=Errorea - gakoaren aterapen komandoak huts egin du
notFirstBlock=Errorea - Lehendabiziko OpenPGP blokea ez da gako publiko batena
importKeyConfirm=Mezuan txertatuta dauden gakoak inportatu nahi al dituzu?
failKeyImport=Errorea - Gakoaren inportazioak huts egin du
fileWriteFailed=%S fitxategian idazterakoan huts egin du
successKeyImport=Gakoa(k) arazorik gabe inportatu da/dira
importKey=%S gako publikoa gako-serbitzaritik inportatu:
uploadKey=%S gakoa gako-serbitzarira bidali:
keyId=Gakoaren ID-a
keyAndSigDate=Gakoaren ID-a: 0x%S / Sinatuta: %S
keyFpr=Gakoaren hatz-marka: %S
noEmailProvided=Ez duzu e-posta helbiderik eman!
keyAlreadySigned=Gakoa dagoeneko sinatuta dago, ezin duzu bitan sinatu.
# Strings in enigmailEditKeyTrustDlg.xul
selKeyExpired=%S-n iraungita
createdHeader=Sortuta
atLeastOneKey=Ez da gakorik aukeratu! Gutxienez gako bat aukeratu behar duzu lehio hau adosteko
fewerKeysThanRecipients=Hartzaile baino gako gutxiago aukeratu dituzu. Ziru zaude zifratzeko gakoen zerrenda osorik dagoela?
userSel.button.goBack=Gako gehiago aukeratu
userSel.secretKeySel.title=OpenPGP Gako Sekretu Bat Aukeratu Zure Mezuak Sinatzekoa
# Strings in enigmailSignKeyDlg.js
# Strings in enigmailKeyManager.js
pgpMimeNote=OHARRA: PGP/MIME e-posta bezero kopuru txiki batek onartzen du! Windowsen bakarrik Mozilla/Thunderbird, Sylpheed, Pegasus eta Mulberry estandar hau honartzen dute; Lunux/UNIX eta Mac OS X-ko bezero hedatuenak onartzen dute. Ziur ez bazaude, %S aukera hautatu ezazu.
first=lehendabiziko
second=bigarren
# Strings in enigmailViewKeySigDlg.xul
encryptKeyHeader=Zifratzeko OpenPGP Gako Bat Aukeratu
identityName=Nortasuna: %S
# Strings in enigmailManageUidDlg.xul
noEncryption=Zifraketa aktibatu duzu, baina ez duzu gakorik aukeratu. %S-ri bidalitako e-postak zifratzeko, zure gako zerrendaren baliodun gako bat edo gehiago hautatu behar duzu. %S-rentzat zifraketa ezgaitu nahi al duzu?
noKeyToUse=(ezer - zifraketarik ez)
noEmptyRule=Araua agian ez dago hutsik! Mesedez, e-posta helbide bat sartu ezazu Araua eremuan.
invalidAddress=Sartutako e-posta(k) ez dira baliodunak. Ez zenituzke hartzaileen izenak sartu behar, bakarrik helbide elektronikoak. Adib.:\nBaliogabea: Izen Bat \nBalioduna: izen.bat@helbidea.net
noCurlyBrackets=Giltzek {} esanahi berezia daukate eta ez lirateke helbide elektronikoetan erabili behar. Arau honen baterapen portaera aldatu nahi baduzu, 'Araua erabili hartzaileak ...' aukera erabili ezazu.\nInformazio gehiago Laguntza botoian eskuragarri dago.
# Strings in enigmailKeyDetailsDlg.xul
never=Inoiz
always=Beti
possible=Posible
deleteRule=(Hurrengo hartzailea)
negateRule=Ez
# Strings in enigmailGenCardKey.xul
needOnline=Aukeratu duzun ekintza ez dago eskuragarri konexiorik gabe. Mesedez, konektatu zaitez eta berriz saiatu.
protocolNotSupported=Aukeratu duzun '%S://' protokoloa ez dago onartuta OpenPGP gakoak deskargatzeko.
gpgkeysDisabled=Agian 'extensions.enigmail.useGpgKeysTool' aukera gaitzea lagundu dezake.
noKeyserverConn=%S-n dagoen gako-serbitzarira ezin izan da konektatu.
keyDownloadFailed=Gakoa deskargatzerakoan huts egin du. Egoera mezua:\n%S
internalError=Barneko errore bat gertatu da. Gakoak ezin izan dira deskargatu edo inportatu.
noKeyFound=Sentitzen dut baina ezin izan da jarri dituzun bilaketa irizpideekin gakorik aurkitu.\nOhartu zaitez gakoaren ID-a "0x" aurrizkia eraman behar duela (adib.: 0xABCDEF12).
# Strings in enigmailSetCardPin.xul
gpgKeysFailed=Gako-sebritzarian gakoa bilatu edo deskargatzerakoan errore bat egon da: gpgkeys_%S ezin izan da exekutatu.
# Strings in enigRetrieveProgres.xul
setKeyTrustFailed=Jabearekiko konfidantza jartzerakoan huts egin du
# Strings in enigmailSetupWizard
signKeyFailed=Gakoaren sinadurak huts egin du
undefinedError=Errore ezezagun bat gertatu da.
alreadySigned.label= Oharra: %S gakoa dagoeneko aukeratutako gako sekretuarekin sinatuta dago.
# Strings in enigmailAddUidDlg.xul
keyMan.loadingKeys=Gakoak kargatzen, mesedez itxaron ...
keyValid.unknown=ezezaguna
keyValid.invalid=baliogabea
keyValid.disabled=ezgaituta
keyValid.revoked=ezeztatuta
keyValid.expired=iraungita
keyValid.noSubkey=ubgako baliogabea
keyValid.valid=balioduna
keyTrust.untrusted=konfidantzarik ez
keyTrust.marginal=txikia
keyTrust.full=konfidagarria
keyTrust.ultimate=azkenekoa
keyTrust.group=(taldea)
keyType.public=pub
keyType.publicAndSec=pub/seg
keyMan.enableKey=Gakoa Gaitu
keyMan.disableKey=Gakoa Ezgaitu
userAtt.photo=Erabiltzailearen ezaugarria (JPEG irudia)
asciiArmorFile=ASCII Fitxategi Babestuak (*.asc)
gnupgFile=GnuPG Fitxategiak
saveRevokeCertAs=Ezeztapen Ziurtagiria Sortu eta Gorde
revokeCertOK==Ezeztapen ziurtagiria sortu egin da. Zure gako publikoa ezgaitzeko erabili dezakezu, adibidez, zure gako sekretua galtzen baduzu.\n\nMesedez, toki seguru batean gorde daitekeen unitate batean gorde ezazu, CD edo flash memoria gailu batera adibidez. Norbaitek ziurtagiri hau lortuko balu zure gakoa baliogabetu lezake.
revokeCertFailed=Ezeztapen ziurtagiria ezin izan da sortu.
addUidOK=Erabiltzeile IDa gehitu egin da
addUidFailed=Erabiltzaile IDa gehitzerakoan errore bat egon da
noKeySelected=Aukeratutako eragiketa egiteko gutxienez gako bat aukeratu behar duzu
exportToFile=Gako Publikoa Fitxategi Batera Esportatu
exportSecretKey=Gako sekretua OpenPGP gako pribatuan fitxategian gorde nahi al duzu?
saveKeysOK=Gakoak gorde egin dira
saveKeysFailed=Gakoak ezin izan dira gorde
importKeysFailed=Gakoak ezin izan dira inportatu
enableKeyFailed=Gakoak ezin izan dira gaitu/ezgaitu
specificPubKeyFilename=%S (0x%S) pub
specificPubSecKeyFilename=%S (0x%S) pub-sec
defaultPubKeyFilename=Esportatutako gako publikoak
defaultPubSecKeyFilename=Esportatutako gako publiko eta pribatuak
noSecretKeys=Ez da gako sekreturik aurkitu.\n\nZure gakoa orain sortu nahi al duzu?
sendKeysOk=Gakoa(k) bidali egin dira
sendKeysFailed=Gakoak ezin izan dira bidali
receiveKeysOk=Gakoa(k) eguneratu dira
receiveKeysFailed=Gakoak ezin izan dira deskargatu
importFromClip=Arbeletik gakoak inportatu nahi al dituzu?
copyToClipbrdFailed=Aukeratutako gakoak ezin izan dira arbelera kopiatu.
copyToClipbrdOK=Gakoak arbelera kopiatu dira
deleteSecretKey=KONTUZ: Gako pribatu bat ezabatzera zoaz!\nZure gako pribatua ezabatzen baduzu, ezin izango dituzu gako horrentzat zifratu diren mezuak argitu, eta ezin izango duzu zure gakoa ezeztatu.\n\nZiur zaude BI gakoak, gako publikoa eta gako pribatua, ezabatu nahi al dituzula\n'%S'?
deleteMix=KONTUZ: Gako pribatuak ezabatzera zoaz!nZure gako pribatua ezabatzen baduzu, ezin izango dituzu gako horrentzat zifratu diren mezuak argitu.\n\nZiur zaude BI gakoak, aukeratutako gako publiko eta pribatua, ezabatu nahi dituzula?
deletePubKey=Gako publikoa ezabatu nahi al duzu\n'%S'?
deleteSelectedPubKey=Zure gako publikoak ezabatu nahi al dituzu?
deleteKeyFailed=Gakoa ezin izan da ezabatu.
revokeKeyAsk=Funtzio honek ezeztapen ziurtagiria sortu eta inportatzen du. Ziur zaude %S gakoa ezeztatu nahi duzula?
revokeKeyOk=Gakoa ezeztatu egin da. Gakoa gako-serbitzari batean eskuragarri badago, gomendatzenda berriz igotzea, horrela besteek ezeztapena ikusi ahal izango dute.
revokeKeyFailed=Gakoa ezin izan da ezeztatu.
refreshAllQuestion=Ez duzi gakorik aukeratu. Gako GUZTIAK freskatu nahi al dituzu?
refreshKey.warn=Kontuz. Gako kopuruaren arabera eta konexioaren abiaduraren arabera, gako guztiak freskatzea prozesu luzea izan daiteke!
keyMan.button.exportSecKey=Gako &Sekretuak Esportatu
keyMan.button.exportPubKey=Gako &Publikoak Esporatatu
keyMan.button.import=&Inportatu
keyMan.button.refreshAll=Gako Guztiak &Freskatu
keyMan.button.revokeKey=Gakoa &Ezeztatu
keylist.noOtherUids=Ez dauka beste nortasunik
keylist.hasOtherUids=Goitizena
keylist.noPhotos=Ez dago argazkirik
keylist.hasPhotos=Argazkiak
# strings in pref-enigmail.js
keySignatureLocal=Lokala
keySignatureExportable=Esportagarria
keySignatureNoKey=Gakorik ez
userIdNotFound=(Erabiltzaile ID-a ez da aurkitu)
signatureValid=Bai
retrieveKeyConfirm=Gakoa ez dago eskuragarri - gako-serbitzari batetik deskargatu nahi al duzu?
changePrimUidFailed=Erabiltzaile ID primarioa aldatzerakoan huts egin du
changePrimUidOK==Erabiltzaile ID primarioa aldatu egin da
deleteUidFailed=Erabiltzaile ID %S-a ezabatzerakoan huts egin du
deleteUidOK=Erabiltzaile ID %S-a ezabatu egin da
revokeUidFailed=Ezin izan da erabiltzaile ID %S-a ezeztatu
revokeUidOK=Erabiltzaile ID %S-a ezeztatu egin da. Zure gakoa gako-serbitzari batean eskuragarri badago, berriz igotzea gomendatzen da, horrela beste erabiltzaileek ezeztapena ikusi ahal izango dute.
revokeUidQuestion=Ziur zaude %S erabiltzaile ID-a ezeztatu nahi duzula?
deleteUidQuestion=Ziur zaude %S erabiltzaile ID-a ezabatu nahi duzula?\n\nOharra: zure gako publikoa gako-serbitzari batera igo baduzu, zure erabiltzaile ID-a ezabatzeak ez du ezer aldatuko. Kasu horretan 'Erabiltzaile ID-a Ezeztatu' erabili beharko zenuke.
keyTypePublic=gako publikoa
keyTypePrimary=gako primarioa
keyTypeSubkey=sub-gakoa
keyTypePair=gako bikotea
keyExpiryNever=inoiz
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
keyAlgorithm_20=ELG
keygen.started=Mesedez, itxaron gakoa sortzen ari den bitartean ....
keygen.completed=Gakoa sortu da. Gako berriaren ID berria: 0x%S
keygen.keyBackup=Gakoa %S bezela babeskopiatu da
keygen.passRequired=Mesedez, zure SmartCard-aren kanpoan babeskopia sortu nahi baduzu pasahitz bat sartu ezazu.
cardPin.dontMatch=Sartu duzun PIN-a ez dator bat; mesedez berriz sartu
cardPin.minLength=PIN-a gutxienez %S karaktere edo zenbaki izan behar ditu
cardPin.processFailed=PIN-a ezin izan da aldatu
keyserverProgress.refreshing=Gakoak freskatzen, mesedez itxaron...
keyserverProgress.uploading=Gakoak igotzen, mesedez itxaron...
keyserverTitle.refreshing=Gakoak Freskatu
keyserverTitle.uploading=Gakoa Igo
passphrase.min8keys=Zure pasahitzak gutxienez 8 karaktere izan beharko lituzke!
setupWizard.applyAllId=Nortasun guztientzat Enigmail aktibatu
setupWizard.applySomeId=Nortasun hauentzat Enigmail aktibatu: %S
setupWizard.applySingleId=Zure e-posta kontuarentzat Enigmail aktibatu
setupWizard.setAllPrefs=Gomendatutako aplikazioaren ezarpen guztiak aldatu
setupWizard.setSomePrefs=Aukeratu dituzun gomendatutako aplikazioaren ezarpenak aldatu
setupWizard.setNoPrefs=Ez aldatu aplikazioaren ezarpenik
setupWizard.createKey=OpenPGP 2048-biteko gako berria sortu, 5 urteko balioarekin
setupWizard.useKey=Esistitzen den OpenPGP %S gako ID-a erabili sinatzeko
setupWizard.encryptAll=Lehenetsita e-posta guztiak zifratu
setupWizard.encryptNone=Lehenetsita ez zifratu e-postarik
setupWizard.signAll=Lehenetsita e-posta guztiak sinatu
setupWizard.signNone=Lehenetsita ez sinatu e-postarik
setupWizard.reallyCancel=Ziur zaude Enigmail Instalatzaile Laguntzailea itxi nahi duzula?
addUidDlg.nameOrEmailError=Ezena eta helbide elektronikoa bete behar dituzu
addUidDlg.nameMinLengthError=Izenak gutxienez 5 karaktere izan behar ditu
addUidDlg.invalidEmailError=Baliodun helbide elektronikoa sartu behar duzu
addUidDlg.commentError=Parentesiak ez dira komentarioetan onartzen
enigmail-2.0.8/lang/eu/help/ 0000775 0000000 0000000 00000000000 13343027545 0015576 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/eu/help/compose.html 0000664 0000000 0000000 00000010432 13343027545 0020131 0 ustar 00root root 0000000 0000000
Enigmail Laguntza: Mezua Idatzi
Enigmail Laguntza
Enigmail erabiltzen mezuak idazterakoan
Enigmail menua e-posta idazteko lehioan
Mezua sinatu
Mezua sinatuta bidaltzeko aukera gaitu/ezgaitu. Erabiltzaileari ohar bat aterako zaio sinadurak huts egiten badu.
Mezua zifratu
Bidali aurretik hartzaile guztientzat mezua zifratzeko aukera gaitu/ezgaitu. Erabiltzaileari ohar bat aterako zaio zifraketak huts egiten badu.
Aukeraketa behar denean erakutsiLehentasunak -> 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 lehioaLehentasunak -> Gako Aukeraketa fitxan gaituta badago, eta hartzaile zerrendan dagoen hartzaile baten gako publikoa baldin ez baduzu, mezua zifratu gabe bidaliko da.
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
Gako publikoa txertatu
Idatzi lehioan, kurtsorea dagoen tokian ASCII-babestua formatuan gako publiko bloke bat txertatzen du. Txertatuko den/diren gakoen helbide elektronikoak eskatuko zaizkizu. Modu honetan sartzen diren gakoak, heltzerakoan Enigmailek automatikoki detektatuko ditu. Txertatu eta gero, e-posta oraindik sinatu edo zifratu dezakezu. Horretaz gain, ez ezazu gako bloke bat baino gehiago sartu mezu bakoitzeko; helbide elektroniko bat baino gehiago jarri nahi baduzu, eskatzen dizkizunean komen edo espazioen bitartez bereizita sartu itzazu.
Ezabatu gordetako pasahitza
Katxeatu den pasahitza ezabatzen du. Erabilgarria da pasahitz baino gehiago dituzunean.
Laguntza
Laguntza informazio weborria (orri hau) erakusten du.
Arau 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..
OpenPGP Arauak honetarako ezarri
Hartzaileen helbide elektronikoak izango ditu (izenik gabe, hau da, helbidea bakarrik norbait@helbidea.domeinua bezala). Helbide elektroniko bat baino gehiago sartu dezakezu hutsuneekin tartekatuz. Hemen sartzen diren helbideak domeinuaren zatiarekin bakarrik sartu daitezke, horrela domeniu horretako edozein helbide elektronikoarekin bat egingo du, adibidez @helbidea.domeinua domeinua norbait@helbidea.domeinua, edonor@helbidea.domeinua, eta abarrekin bat etorriko da.
Araua aplikatu hartzaileak...
Hoek helbide elektronikoen bateratzea aldatuko du. Helbide bat baino gehiago sartu badira, ezaugarri hau guztietara aplikatuko dira. Azpian dauden adibideak izena@helbidea.domeinua erabiliko dute goian dagoen OpenPGP Arauak eremuan.
Zehazki bada: ezaugarri honekin araua bakarrik aplikatuko da izena@helbidea.domeinua helbidearekin (zehazki, letra larriak eta xeheak ezberdindu gabe).
Badauka: ezaugarri honekin, testu hori daukan edozein helbiderekin bateratuko da, adibidez abizena_izena@helbidea.domeinua edo izena@helbidea.domeinua.net
Honekin hasten da: ezaugarri honekin, testu honekin hasten den edozein helbiderekin bateratuko da, adibidez izena@helbidea.domeinua.net, izena@helbidea.domeinua-izena.com.
Honekin bukatzen da da:ezaugarri honekin, testu honekin bukatzen den edozein helbiderekin bateratuko da, adibidez abizena_izena@helbidea.domeinua , ezizena@helbidea.domeinua.
Bat datozen helbideekin hurrengo arauarekin jarraitu
Funtzio honek arau bat definitzen uzten dizu Hurrengo OpenPGP gakoak erabili: eremuan GakoID-rik zehaztu behar izan gabe, horrela bidaltzeko momentuan helbide elektronikoa erabiliko da gakoa bilatzeko. Horretaz gain, helbide berdinentzat arau gehiago badaude, hauek ere prozesatuko dira.
Ez bilatu arau gehiago bateratutako helbideentzat
Aukera hau gaitzen baduzu, arau honekin bateratzen bada, prozesamenduak ez ditu arau gehiago bilatuko helbide honentzako; hau da, hurrengo hartzailearekin hasiko da.
Hurrengo OpenPGP gakoak erabili:
Gakoa(k) Aukeratu.. botoia erabili ezazu zifratzeko erabiliko diren hartzailearen gakoak aukeratzeko. Goiko ekintzaren moduan, arau honekin baterantzen diren helbideek ez dute prozesua jarraituko.
Sinatzeko Lehenetsita
Mezuaren sinadura gaitu edo ezgaitu. Honek mezua idazteko lehioan jarri duzuna erabili edo jaramonik ez egitea zehazten du. Balioak hauek izan daitezke:
Inoiz: sinadura ezgaitu, nahiz eta mezua idazteko lehioan bestela esanda (beste balioei ez die jaramonik egiten)
Bai, Mezua idazteko lehioan aukeratzen bada: sinadura mezua idazteko lehioan jartzen duen bezela egin
Beti: sinadura gaitu, mezua idazteko lehioan aukera hori gaituta egonez arren
Sinadura ezarpen hauek bateratzen diren arau guztietara aplikatuko da. Arau batek sinadura ezgatzen badu, mezua ez da sinatuko, nahiz eta beste arau batzuk Beti esaten duten.
Zifraketa
Mezuaren zifraketa gaitu edo ezgaitu. Jarri daitezken ezaugarriak eta euren esanahia sinaduran daudenen berdinak dira.
PGP/MIME
PGP/MIME (RFC 3156) mezu kodifikazioa gaitu edo ezgaitu. PGP/MIME ezgaituta badago, mezuak "txertatutako PGP" erabiliz kodifikatuko dira. Jarri daitezken ezaugarriak eta euren esanahia sinaduran daudenen berdinak dira.
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.
enigmail-2.0.8/lang/eu/help/initError.html 0000664 0000000 0000000 00000004651 13343027545 0020447 0 ustar 00root root 0000000 0000000
Enigmail Laguntza: Nola Konpondu OpenPGP Hasieratzerakoan Dauden Arazoak
Enigmail Laguntza
Nola Konpondu OpenPGP Hasieratzerakoan Dauden Arazoak
Arrazoi asko egon daitezke OpenPGP hasieratzerakoan errorea emateko. Ohikoenak azpian agertzen dira; informazio gehiago nahi baduzu, Enigmail Laguntza weborrian aurkitu dezakezu.
GnuPG ezom ozam da aurkitu
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.
Enigmime hasieratzerakoan huts egin du
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.
Botoi hau gauza askotarako erabili daiteke: argitu, egiaztatu edo gako publikoak inportatzeko. Normalean, argitzea/egiaztatzea automatikoki egiten da, baina aukera hau ezgaitu daiteke lehentasun baten bitartez. Honek huts egiten badu, normalean Enigmailen egoera-lerroan mezu motz bat agertuko da. Argitu botoian klik eginez, xehetasun gehiago dituen errore mezua ikusi ahal izango duzu, GnuPG komandoaren irteeera barne.
Idazluma eta Giltza ikonoak Mezuaren Goiburuan
Idazluma eta Giltza ikonoek mezua sinatuta edo/eta zifratuta dagoela erakusten dute, baita sinadura ona bada ere, hau da, mezua sinatu zenetik aldatu baldin ez bada. Mezua aldatu baldin bada, Idazluma ikonoa Idazluma Apurtu batera aldatuko da sinadura oker dagoela adierazteko. Idazluma eta giltza ikonoetan eskubiko klik eginez hurrengo aukerak dituen menua agertuko da:
OpenPGP Sekurtasun informazioa: GnuPG-k mezuarentzat atera duen egoera erakutsiko dizu.
OpenPGP Sekurtasun informazioa kopiatu: GnuPG-k atera duen egorea arbelera kopiatuko du; adibidez, erantzun batean itxasteko e.a.
OpenPGP argazki ID-a ikusi: mezua bidali zuen pertsonaren Argazki ID-a erakutsiko dizu, euren argazkia gako publikoaren barruan txertatu baldin badu.(Aukera hau gaituta agertuko da bakarrik beraren gakoan Argazki ID-a txertatuta baldin badago.)
S/MIME Sekurtasun informazioa: mezuaren S/MIME sekurtasun informazioa erakutsiko dizu.
Zure 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
Zifratutako eranskikak ireki / Erantsitako OpenPGP gakoak inportatu
*.pgp, *.asc eta *.gpg luzapena duten eranskinak Enigmailek bereziak bezala identifikatuko ditu eta tratamendu berezia emango die. Eranskin hauetan eskubiko klik egiten baduzu, laister-menuan bi sarrera berezi agertuko dira: Argitu eta Ireki eta Argitu eta Gorde. Bi menu sarrera hauek erabili itzazu eranskinak ireki edo gorde baino lehen argitu nahi badituzu. Eranskin bat OpenPGP gako fitxategi bat bezela antzematen badu, zure giltzatakoan gakoak inportatzeko aukera emango dizu.
Arau 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:
E-posta
Hartzailea:, Cc: eta Bcc: eremuekin bateratuko den helbide elektronikoa(k). Bateratzea testu zatietan lan egiten du (Xehetasun geiago Araua Editatu lehioan aurkitu daitezke)
OpenPGP Gakoa(s)
hartzailearentzat erabiliko diren OpenPGP gako ID zerrenda
Sinatu
mezuaren sinadura gaitu edo ezgaitu. Honek mezua idazteko lehioan jarrtzen diozunaren arabera edo haiei jaramonik egin gabe lan egin dezake. Balioak honakoak dira:
Inoiz: sinadura ezgaitu, mezua idazteko lehioan gaituta egon arren (beste balioei ez die jaramonik egiten)
Posible: sinadura mezua idazteko lehioan agertzen denaren arabera egingo da
Beti: sinaduar gaitu, mezua idazteko lehioan aukera hori gaituta egon ez arren
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.
Zifratu
mezuaren zifraketa gaitu edo ezgaitu. Onartutako ezarpenak eta euren esanahia sinadurarenak bezalakoak dira.
PGP/MIME
PGP/MIME (RFC 3156) mezu kodifikazioaren erabilera gaitu edo ezgaitu. PGP/MIME ezgaituta badago, mezuak "txertatutako PGP" erabiliz erabiliko dira. Onartutako ezarpenak eta euren esanahia sinadurarenak bezalakoak dira.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/fi/ 0000775 0000000 0000000 00000000000 13343027545 0014633 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/fi/am-enigprefs.properties 0000664 0000000 0000000 00000000125 13343027545 0021324 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=OpenPGP-turvallisuus
enigmail-2.0.8/lang/fi/enigmail.dtd 0000664 0000000 0000000 00000142177 13343027545 0017131 0 ustar 00root root 0000000 0000000
"-merkeillä">
"-merkeillä GnuPG:lle. Poista asetus käytöstä jos vastaanottajilla on vanhoja Hushmail-avaimia.">
Huom: Avaimen luominen voi kestää jopa useita minuutteja. Älä sulje ohjelmaa kun avainta luodaan. Tietokoneen aktiivinen käyttäminen avainta luotaessa lisää avaimen luontiin tarvittavaa satunnaisuutta ja siten nopeuttaa luontiprosessia. Enigmail ilmoittaa kun avain on valmis.">
" on virheellinen">
Huom: Avaimen luominen voi kestää jopa useita minuutteja. Älä sulje ohjelmaa kun avainta luodaan. Enigmail ilmoittaa kun avain on valmis.">
Huom.: Enigmail varmentaa jokaisen sähköpostin
allekirjoitukset riippumatta tilistä tai käyttäjätunnuksesta">
Kiitos Enigmail-tiimin puolesta.">
enigmail-2.0.8/lang/fi/enigmail.properties 0000664 0000000 0000000 00000152071 13343027545 0020544 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Enigmail-hälytys
enigConfirm=Enigmail-vahvistus
# enigInfo=Enigmail Information
enigError=Enigmail-virhe
enigPrompt=Enigmail-kehote
dlgYes=Kyllä
dlgNo=Ei
dlgKeepSetting=Muista vastaukseni, äläkä kysy uudestaan
dlgNoPrompt=Älä näytä tätä huomioikkunaa uudestaan
dlg.button.delete=&Poista
dlg.button.cancel=&Peruuta
dlg.button.close=&Sulje
dlg.button.continue=Jatka
dlg.button.skip=&Ohita
# dlg.button.overwrite=&Overwrite
dlg.button.view=&Näytä
# dlg.button.retry=&Retry
# dlg.button.ignore=&Ignore
# dlg.button.install=&Install
# dlg.button.ok=&OK
repeatPrefix=\n\nTämä hälytys toistetaan %S
repeatSuffixSingular=kerran.
repeatSuffixPlural=kertaa.
noRepeat=\n\nTämä hälytys toistetaan vasta Enigmailin seuraavan päivityksen yhteydessä.
pgpNotSupported=Käytät ilmeisesti PGP 6.x:ä Enigmail:n kanssa.\n\nPGP 6.x:n toiminnassa on kuitenkin ongelmia, joiden takia Enigmail ei toiminut kunnolla ja siksi Enigmail ei enää tue PGP 6.x:ä. Käytä PGP:n sijaan GnuPG:tä.\n\nTarvittaessa Enigmailin kotisivujen ohjesivulta löytyy ohjeita GnuPG:n siirtymisestä
# initErr.howToFixIt=In order to use Enigmail, GnuPG is required. If you did not install GnuPG yet, the easiest way to do this is using the "Setup Wizard" button below.
# initErr.setupWizard.button=&Setup Wizard
passphraseCleared=Salasanamuisti tyhjennettiin.
# cannotClearPassphrase=You are using a non-standard tool (such as gnome-keyring) for passphrase handling. Clearing the passphrase is therefore not possible from within Enigmail.
noPhotoAvailable=Ei kuvaa
debugLog.title=Enigmail Debug Log
error.photoPathNotReadable=Kuvan polku '%S' ei ole luettavissa
# generalError=Error: %S
# Strings in configure.jsm
enigmailCommon.versionSignificantlyChanged=Enigmailin uudessa versiossa on olennaisia muutoksia asetuksissa ja vaihtoehdoissa. Pyrimme siirtämään vanhat asetukset uuteen versioon. Emme kuitenkaan voi varmistaa kaikkia tapauksia automaattisesti. Ole hyvä, tarkista eri asetukset ja vaihtoehdot asennuksen jälkeen.
enigmailCommon.checkPreferences=Tarkista asetukset..
# preferences.defaultToPgpMime=We have changed the default message encoding in Enigmail from Inline-PGP to PGP/MIME. We recommend you keep this as default.\n\nIf you still wish to use Inline-PGP by default, you can do so in the Account Settings under OpenPGP Security.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=Enigmailin versio %S käynnissä
# enigmailPepVersion=Enigmail/p≡p version %S
usingAgent=Salaamiseen ja salauksen purkamiseen käytetään ohjelman %S tiedostoa %S
agentError=VIRHE: Enigmime-palveluun ei saatu yhteyttä
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Virhe käytettäessä Enigmail-palvelua
onlyGPG=Avaimen luominen onnistuu vain GnuPG-ohjelman kanssa (Ei PGP:n kanssa).
keygenComplete=Avain luotu! Käyttäjätieto <%S> käyttää avainta viestien allekirjoittamiseen.
revokeCertRecommended=Mitätöintivarmenteen luominen avaimelle on suositeltua. Avaimen voi mitätöidä sillä jos avain esimerkiksi hukkuu tai joutuu vääriin käsiin. Luodaanko mitätöintivarmenne?
keyMan.button.generateCert=&Luo sertifikaatti
genCompleteNoSign=Avain luotu!
genGoing=Avaimen luonti on jo käynnissä.
passNoMatch=Salasanat eivät täsmää. Kirjoita ne uudelleen
passCheckBox=Valitse, jos avaimelle ei aseteta salasanaa
passUserName=Kirjoita käyttäjätiedoista puuttuva käyttäjätunnus
# keygen.missingUserName=There is no name specified for the selected account/identity. Please enter a value in the field "Your name" in the account settings.
# keygen.passCharProblem=You are using special characters in your passphrase. Unfortunately, this can cause troubles for other applications. We recommend you choose a passphrase consisting only of any of these characters:\na-z A-Z 0-9 /.;:-,!?(){}[]%*
passSpaceProblem=Teknisistä syistä, tunnuslauseen voi aloittaa tai päättää välilyöntiin
changePassFailed=Salasanan vaihtaminen epäonnistui.
keyConfirm=Luodaanko julkinen ja salain avain käyttäjälle "%S"?
keyMan.button.generateKey=&Luo avain
keyAbort=Peruutetaanko avaimen luonti?
keyMan.button.generateKeyAbort=&Keskeytä avainten luonti
keyMan.button.generateKeyContinue=&Jatka varmenteen luontia
expiryTooLong=Avaimen vanhenemisaika ei voi ylittää 100:a vuotta.
expiryTooLongShorter=Et pysty määrittämään avaimen vanhenenemista yli 90 vuoden päähän.
expiryTooShort=Avain ei voi vanheta alle päivässä.
keyGenFailed=Avaimen luonti epäonnistui. Tarkista yksityiskohdat Enigmail-konsolin viesteistä (Valitse Enigmail > Enigmail:n virheenjäljitys).
setKeyExpirationDateFailed=Päättymispäivää ei ole muutettu
# Strings in enigmailMessengerOverlay.js
securityInfo=Enigmail-turvallisuustietoja\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Tämän viestin liitteitä ei ole allekirjoitettu tai salattu*\n\n
possiblyPgpMime=Viesti on mahdollisesti PGP/MIME-salattu tai -allekirjoitettu. Napsauta Pura-painiketta varmistaaksesi
saveAttachmentHeader=Enigmail: Tallenna purettu liitetiedosto
noTempDir=Väliaikaista tallennuskansiota ei löytynyt\nAseta TEMP-ympäristömuuttuja
attachmentPgpKey=Avattava liite "%S" vaikuttaa OpenPGP-avaintiedostolta.\n\nTuo avaimet napsauttamalla Kyllä tai napsauta Ei näyttääksesi tiedoston sisällön
beginPgpPart=********* *SALATTU tai ALLEKIRJOITETTU OSA ALKAA* *********
endPgpPart=********** *SALATTU tai ALLEKIRJOITETTU OSA LOPPUU* **********
notePartEncrypted=Enigmail: *Osia viestistä EI OLE allekirjoitettu tai salattu*
noteCutMessage=Enigmail: *Viesti on jaettu useaan lohkoon -- Salauksen purku tai allekirjoituksen varmistus peruutettiin*
decryptOkNoSig=Varoitus\n\nSalauksen purkaminen onnistui, mutta allekirjoitus ei varmistunut oikein
msgOvl.button.contAnyway=&Jatka
# signature.verifiedOK=The signature for attachment %S was successfully verified
signature.verifyFailed=Allekirjoituksen liitetiedostoja %S ei voitu vahvistaa
# attachment.noMatchToSignature=Could not match attachment '%S' to a signature file
# attachment.noMatchFromSignature=Could not match signature file '%S' to an attachment
# fixBrokenExchangeMsg.failed=Did not succeed to repair message.
# enigmail.msgViewColumn.label=Enigmail
# enigmailPep.msgViewColumn.label=Enigmail/p≡p
# wksNoIdentity=This key is not linked to any of your email accounts. Please add an account for at least one of the following email addresse(s):\n\n%S
# wksConfirmSuccess=Confirmation email sent.
# wksConfirmFailure=Sending the confirmation email failed.
# autocrypt.importSetupKey.accountPreconfigured=Your account is already correctly configured for Autocrypt.\n\nDo you really want to overwrite your settings with this setup message?
# autocrypt.importSetupKey.selfCreated=This message was created by your currently running instance of Enigmail.\n\nPlease switch to the email client to which you want to transfer the settings, and click on the message on that email client to import the settings.
# autocrypt.importSetupKey.invalidMessage=Error - could not read setup message. The message seems to be corrupted. Please try to create a new setup message on your "other" device.
# autocrypt.importSetupKey.invalidKey=Error - the key could not be imported. The key is either not supported by your version of GnuPG, or it got corrupted.
# autocrypt.importSetupKey.wrongPasswd=The password you entered is wrong. Do you want to retry?
# autocrypt.importSetupKey.success=The Autocrypt setup message was processed successfully. Autocrypt is now available for your account '%S'.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Valitse viestiin liitettävät OpenPGP-avaimet
keysToUse=Valitse OpenPGP-avaimet osoitesuotimelle %S
pubKey=Käyttäjätunnuksen %S julkinen avain\n
windowLocked=Viestin kirjoitusikkuna on lukittu. Viestin lähetys peruttu.
sendUnencrypted=Enigmailin alustus epäonnistui.\nLähetetäänkö viesti salaamattomana?
composeSpecifyEmail=Anna ensisijainen sähköpostiosoitteesi, jonka perusteella lähtevien viestien allekirjoitusavain valitaan.\nJos et anna sähköpostiosoitetta, jokaisen viestin allekirjoitusavain valitaan viestin lähettäjäkentän perusteella.
# sendingHiddenRcpt=This message has BCC (blind copy) recipients. If this message is encrypted, it is possible to hide the BCC recipients but users of some products (e.g. PGP Corp.) will not be able to decrypt the message. Given this, we recommend to avoid BCC-emails with encrypted messages.
# sendWithHiddenBcc=Hide BCC recipients
sendWithShownBcc=Salaa normaalisti
sendingNews=Salatun viestin lähetys peruttiin.\n\nTätä viestiä ei voi salata koska yksi vastaanottajista on keskusteluryhmä. Lähetä viesti uudestaan salaamattomana.
sendToNewsWarning=Varoitus: olet aikeissa lähettää salattua sähköpostia uutisryhmään.\n\nTämä ei ole suotavaa. Se on järkevää ainoastaan silloin, kun kaikki ryhmän jäsenet voivat purkaa viestin. Eli viesti on salattu ja avain on kaikilla ryhmään osallistujilla. Lähetä tämä viesti vain, jos tiedät tarkalleen mitä olet tekemässä.\n\nHaluatko jatkaa?
hasHTML=HTML-postin varoitus:\nViesti saattaa sisältää HTML-koodia, jonka vuoksi viestin salaus tai allekirjoitus voi epäonnistua. Voit vastaisuudessa lähettää allekirjoitettuja viestejä painamalla Shift-näppäintä napsauttaessasi Kirjoita viesti tai Vastaa viestiin -painiketta.\nJos allekirjoitat viestisi oletuksena, sinun kannattaa ottaa HTML-muotoisten viestien lähetys pois päältä tiliasetuksista.
strippingHTML=Viestissä on HTML-muotoiluja, jotka katoavat kun viesti muunnetaan allekirjoituksen tai salauksen vuoksi pelkäksi tekstiksi. Jatketaanko muuntoa?
msgCompose.button.sendAnyway=&Lähetä viesti joka tapauksessa
attachWarning=Tämän viestin liitteet ovat linkitettyjä ja niitä ei voi salata. Salataksesi tiedostot, tallenna ne ensin kiintolevyllesi ja liitä ne sitten viestiin. Jatketaanko kaikesta huolimatta?
quotedPrintableWarn=Lähtevien viestien "quoted printable"-koodaus on käytössä. Koodauksen takia viestiesi allekirjoitus ja salaus voidaan tulkita virheelliseksi.\nOtetaanko "quoted-printable"-koodaus pois käytöstä?
minimalLineWrapping=Viestit rivittyvät tällä hetkellä %S merkin leveyteen. Jotta viestejä voi salata tai allekirjoittaa, merkkejä täytyy mahtua riville vähintään 68.\nMuutetaanko riville mahtuvien merkkien määrä 68:ksi?
warning=Varoitus
signIconClicked=Olet muokannut allekirjoitusta. Tämän takia kirjoittaessasi tätä viestiä, allekirjoittaminen ja viestin salaaminen eivät enää riipu toisistaan.
# errorOwnKeyUnusable=The key ID '%S' configured for the current identity does not yield a usable OpenPGP key.\n\nPlease ensure that you have a valid, not expired OpenPGP key and that your account settings point to that key.\nIf your key is not expired, then check if you did set Owner trust to full or ultimate.
# msgCompose.cannotSaveDraft=Error while saving draft
# msgCompose.partiallyEncrypted.short=Beware of leaking sensitive information - partially encrypted email.
# msgCompose.partiallyEncrypted.mimeMsg=The message you are replying to contained both unencrypted and encrypted parts. Some encrypted message parts are invisible to you.\n\nIf the sender was not able to decrypt the hidden message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nWe recommend that you don't reply to the message, but create a new message containing your answer.
# msgCompose.partiallyEncrypted.inlinePGP=The message you are replying to contained both unencrypted and encrypted parts. If the sender was not able to decrypt some message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nPlease consider removing all quoted text from your reply to this sender.
# msgCompose.internalEncryptionError=Internal Error: promised encryption disabled
# msgCompose.internalError=An internal error has occurred.
msgCompose.toolbarTxt.signAndEncrypt=Tämä viesti tullaan allekirjoittamaan ja salataan
# msgCompose.toolbarTxt.signOnly=This message will be signed
# msgCompose.toolbarTxt.encryptOnly=This message will be encrypted
# msgCompose.toolbarTxt.noEncryption=This message will be unsigned and unencrypted
# msgCompose.toolbarTxt.disabled=Enigmail is disabled for the selected identity
# msgCompose.protectSubject.tooltip=Protect the message subject
# msgCompose.noSubjectProtection.tooltip=Do not protect the message subject
# msgCompose.encryptedSubjectStub=Encrypted Message
# msgCompose.protectSubject.dialogTitle=Enable Protection of Subject?
# msgCompose.protectSubject.question=Regular encrypted emails contain the unredacted subject.\n\nWe have established a standard to hide the original subject in the encrypted message\nand replace it with a dummy text, such that the subject is only visible after the email is decrypted.\n\nDo you want to protect the subject in encrypted messages?
# msgCompose.protectSubject.yesButton=&Protect subject
# msgCompose.protectSubject.noButton=&Leave subject unprotected
# msgCompose.detailsButton.label=Details ...
# msgCompose.detailsButton.accessKey=D
# msgCompose.pepSendUnknown=Unknown
# msgCompose.pepSendUnsecure=Unsecure
# msgCompose.pepSendSecure=Secure
# msgCompose.pepSendTrusted=Secure & Trusted
# pep.alert.disabledForIdentity=p≡p is disabled for the current identity. Please enable p≡p via the Enigmail/p≡p preferences.
# pep.alert.weakReply=You’re about to forward or reply to a secure message as insecure. If you choose to proceed, confidential information might be leaked putting you and your communication partner at risk. Are you sure you want to continue?
# note: should end with double newline:
sendAborted=Viestin lähetys peruttiin.\n\n
# details:
# keyNotTrusted=Not enough trust for key '%S'
# keyNotFound=Key '%S' not found
# keyRevoked=Key '%S' revoked
# keyExpired=Key '%S' expired
statPGPMIME=PGP/MIME
# statSMIME=S/MIME
statSigned=ALLEKIRJOITETTU
statEncrypted=SALATTU
statPlain=SELKOKIELINEN
offlineSave=Tallennetaanko %S viesti vastaanottajalle %S lähtevien viestien kansioon?
onlineSend=Lähetä %S viesti vastaanottajalle %S?
encryptKeysNote=Huom.: viesti on salattu seuraavilla käyttäjätunnuksilla / avaimilla: %S
# hiddenKey=
signFailed=Enigmail-virhe. Salaus tai allekirjoitus epäonnistui. Lähetetäänkö viesti salaamatta?
msgCompose.button.sendUnencrypted=Lähetä salaamaton viesti
recipientsSelectionHdr=Valitse vastaanottajat joiden viestit salataan
configureNow=Valittua käyttäjää ei ole asetettu käyttämään Enigmail-turvallisuutta. Muokataanko asetuksia nyt?
# encryption/signing status and associated reasons:
# encryptMessageAuto=Encrypt Message (auto)
# encryptMessageNorm=Encrypt Message
# signMessageAuto=Sign Message (auto)
# signMessageNorm=Sign Message
# encryptOff=Encryption: OFF
# encryptOnWithReason=Encryption: ON (%S)
# encryptOffWithReason=Encryption: OFF (%S)
# encryptOn=Encryption: ON
# signOn=Signing: ON
# signOff=Signing: OFF
# signOnWithReason=Signing: ON (%S)
# signOffWithReason=Signing: OFF (%S)
# reasonEnabledByDefault=enabled by default
# reasonManuallyForced=manually forced
# reasonByRecipientRules=forced by recipient rules
# reasonByAutoEncryption=forced by auto encryption
# reasonByConflict=due to conflict in recipient rules
# reasonByEncryptionMode=due to encryption mode
# should not be used anymore:
encryptYes=Viesti salataan
encryptNo=Viestiä ei salata
# should not be used anymore:
signYes=Viesti allekirjoitetaan
signNo=Viestiä ei allekirjoiteta
# PGP/MIME status:
# pgpmimeNormal=Protocol: PGP/MIME
# inlinePGPNormal=Protocol: Inline PGP
# smimeNormal=Protocol: S/MIME
# pgpmimeAuto=Protocol: PGP/MIME (auto)
# inlinePGPAuto=Protocol: Inline PGP (auto)
# smimeAuto=Protocol: S/MIME (auto)
# should not be used anymore
# pgpmimeYes=PGP/MIME will be used
# pgpmimeNo=Inline PGP will be used
# Attach own key status (tooltip strings):
# attachOwnKeyNo=Your own key will not be attached
# attachOwnKeyYes=Your own key will be attached
# attachOwnKeyDisabled=Your own key cannot be attached. You have to select a specific key\nin the OpenPGP section of the Account Settings to enable this feature.
rulesConflict=Vastaanottajakohtaisissa säännöissä ristiriitoja\n%S\n\nLähetetäänkö viesti näillä asetuksilla?
msgCompose.button.configure=&Määritä
msgCompose.button.send=&Lähetä viesti
msgCompose.button.save=&Talllenna viesti
# Strings in enigmailMsgHdrViewOverlay.js
keyNeeded=Allekirjoituksen varmistamiseen tarvitaan osoitteen %S julkinen avain
# keyUsed=Public key %S used to verify signature
clickDecrypt=. Napsauta Salauksen purkamis -painiketta
clickDecryptRetry=. Napsauta Salauksen purkamis -painiketta yrittääksesi uudestaan
# clickDetailsButton=; click on 'Details' button for more information
# clickImportButton=; click on the 'Import Key' button to import the key
# keyTypeUnsupported=; the key type is not supported by your version of GnuPG
msgPart=Osa viestistä %S
msgSigned=allekirjoitettu
# msgSignedUnkownKey=signed with unknown key
msgEncrypted=salattu
msgSignedAndEnc=allekirjoitettu ja salattu
unverifiedSig=Varmistamaton allekirjoitus
incompleteDecrypt=Salauksen purkaminen ei ole täydellinen
needKey=Virhe - salauksen purkaminen vaatii salaisen avaimen
failedDecrypt=Virhe - salauksen purkaminen epäonnistui
badPhrase=Virhe - väärä salasana
failedDecryptVerify=Virhe - salauksen purkaminen tai viestin varmistus epäonnistui
mdcError=Virhe - viestin eheyttä ei oltu suojattu
viewInfo=. Näytä > Viestin turvallisuustiedot lukeaksesi lisätietoja
decryptedMsg=Viesti, jonka salaus on purettu
# decryptedMsgWithFormatError=Decrypted message (restored broken PGP email format probably caused by an old Exchange server, so that the result might not be perfect to read)
# usedAlgorithms=Used Algorithms: %1$S and %2$S
# pepStatusInfo.text=p≡p Message Status.
# pepStatusInfo.title.m3=Under Attack
# pepStatusInfo.info.m3=This message is not secure and has been tampered with.
# pepStatusInfo.title.m1=Mistrusted
# pepStatusInfo.info.m1=This message has a communication partner that has previously been marked as mistrusted
# pepStatusInfo.title.r0=Unknown
# pepStatusInfo.info.r0=This message does not contain enough information to determine if it is secure.
# pepStatusInfo.title.r1=Cannot Decrypt
# pepStatusInfo.info.r1=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r2=Cannot Decrypt
# pepStatusInfo.info.r2=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r3=Unsecure
# pepStatusInfo.info.r3=This message is unsecure.
# pepStatusInfo.title.r4=Unsecure for Some
# pepStatusInfo.info.r4=This message is unsecure for some communication partners.
# pepStatusInfo.title.r5=Unreliable Security
# pepStatusInfo.info.r5=This message has unreliable protection.
# pepStatusInfo.title.r6=Secure...
# pepStatusInfo.info.r6=This message is secure but you still need to verify the identity of your communication partner.
# pepStatusInfo.title.r7=Secure & Trusted
# pepStatusInfo.info.r7=This message is secure and trusted.
# pepStatusInfo.color.green=Green
# pepStatusInfo.color.yellow=Yellow
# pepStatusInfo.color.red=Red
# pepRevokeTrust.question=Do you really want to cancel the trust for %S?
# pepRevokeMistrust.question=Do you really want to re-trust the key for %S?
# pepRevokeTrust.doRevoke=Cancel &trust
# wksConfirmationReq=Web Key Directory Confirmation Request
# wksConfirmationReq.message=This message has been sent by your email provider to confirm deployment of your OpenPGP public key\nin their Web Key Directory.\nProviding your public key helps others to discover your key and thus being able to encrypt messages to you.\n\nIf you want to deploy your key in the Web Key Directory now, please click on the button "Confirm Request" in the status bar.\nOtherwise, simply ignore this message.
# wksConfirmationReq.button.label=Confirm Request
# autocryptSetupReq=Perform Autocrypt Setup
# autocryptSetupReq.button.label=Start Setup
# autocryptSetupReq.setupMsg.desc=This message contains all information to transfer your Autocrypt settings along with your secret key securely from your original device.
# autocryptSetupReq.setupMsg.backup=You can keep this message and use it as a backup for your secret key. If you want to do this, you should write down the password and store it securely.
# autocryptSetupReq.message.import=To import the settings and key(s) in Enigmail, please click on the "Start Setup" button in the status bar.
# autocryptSetupReq.message.sent=Please click on the message on your new device and follow the instuctions to import the settings.
# strings in pref-enigmail.js
# oldGpgVersion20=Enigmail initialization failed.\n\nYou are using GnuPG version %1$S, which is not supported anymore. Enigmail requires GnuPG version %2$S or newer. Please upgrade your GnuPG installation, or Enigmail will not work.
locateGpg=Osoita GnuPG-ohjelman sijainti
invalidGpgPath=GnuPG:tä ei voida käynnistää annetusta sijainnista. Enigmail on pois käytöstä kunnes GnuPG:n sijainti muutetaan tai ohjelma käynnistetään uudestaan.
warningsAreReset=Kaikki varoitusikkuna-asetukset on nollattu.
prefs.gpgFound=GnuPG:tä ei löytynyt sijainnista %S
prefs.gpgNotFound=GnuPG:tä ei löytynyt
prefs.warnAskNever=Varoitus: Asetuksen seurauksena sähköpostiviestit lähetetään salaamatta siitä erikseen ilmoittamatta jos jollekin vastaanottajista ei löydy avainta!
# prefs.warnIdleTimeForUnknownAgent=Cannot connect to gpg-agent. Maybe your system uses a specialized tool for passphrase handling (e.g. gnome-keyring, seahorse-agent, KDE wallet manager, ...). Unfortunately Enigmail cannot control the passphrase timeout for the tool you are using. Therefore the respective timeout settings in Enigmail are disregarded.
# prefEnigmail.oneKeyserverOnly=Error - you can only specify one keyserver for automatic downloading of missing OpenPGP keys.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Kirjoita älykorttisi ADMIN PIN-koodi
enterCardPin=Kirjoita älykorttisi PIN-koodi
notInit=Virhe - Enigmail-palvelua ei ole vielä alustettu
badCommand=Virhe - salauskomento epäonnistui
cmdLine=-komento ja -tuloste:
notRequired=Virhe - salausta ei vaadita
notComplete=Virhe - avaimen luonti ei ole vielä valmis
invalidEmail=Virhe - virheellisiä sähköpostiosoitteita
noPassphrase=Virhe - salasanaa ei ole annettu
noPGPblock=Virhe - Ei löydetty kelvollista koodattua OpenPGP-dataosiota
unverifiedReply=Viestin sisennettyä osaa (vastausta) on luultavasti muokattu
# keyInMessageBody=Key in message body found. Click 'Import Key' to import the key
sigMismatch=Virhe - Allekirjoitus ei ole täsmää
cantImport=Julkisen avaimen tuonnissa tapahtui virhe\n\n
# doImportOne=Import %1$S (%2$S)?
# doImportMultiple=Import the following keys?\n\n%S
# previewFailed=Can't read public key file.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=Älykorttia %S löydetty, lukija ei osaa käsitellä viestiä\nPyydän lisäämään älykortti %S, toista toimenpide.
sc.insertCard=Toiminta vaatii älykorttin %S.\nOle hyvä ja lisää vaadittava älykortti, toista toimenpide.
# sc.removeCard=The operation requires no SmartCard to be in the reader.\nPlease remove your SmartCard and repeat the operation.
sc.noCardAvailable=Älykorttia ei löydetty lukijasta.\nAseta älykortti kortinlukijaan ja yritä uudestaan
sc.noReaderAvailable=Älykortinlukijaan ei saatu yhteyttä\nKiinnitä älykortinlukija tietokoneeseen, aseta kortti lukijaan ja yritä uudestaan
# keyError.keySpecNotFound=The email address "%S" cannot be matched to a key on your keyring.
# keyError.keyIdNotFound=The configured key ID "%S" cannot be found on your keyring.
# keyError.resolutionAction=Please select a valid key in the OpenPGP section of your Account Settings.
# missingPassphrase=Missing passphrase
# errorHandling.gpgAgentInvalid=Your system is running a version of gpg-agent that is not suitable for your GnuPG version.
# errorHandling.gpgAgentError=GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
# errorHandling.dirmngrError=GnuPG reported an error in the communication with dirmngr (a component of GnuPG).
# errorHandling.pinentryError=GnuPG cannot query your passphrase via pinentry.
# errorHandling.readFaq=This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.\n\nWe strongly recommend that you consult our support web site at https://enigmail.net/faq.
gpgNotFound=GnuPG-ohjelmaa %S ei löytynyt.\nTarkista, että GnuPG:n ohjelmatiedoston kansio on asetettu oikein Enigmail:n asetuksissa
gpgNotInPath=GnuPG-ohjelmaa ei löytynyt PATH-muuttujan kansioista.\\Tarkista, että GnuPG:n ohjelmakansio on asetettu oikein Enigmail:n asetuksissa
# enigmailNotAvailable=Enigmail core Service not available
prefGood=Hyvä allekirjoitus lähettäjältä %S
prefBad=VääRä allekirjoitus lähettäjältä %S
failCancel=Virhe - Avaimen nouto peruutettiin
failNoServer=Virhe - Ei annettu avainpalvelinta, jolta avain noudetaan
failNoID=Virhe - Ei annettu käyttäjätunnusta, jolle avain noudetaan
failKeyExtract=Virhe - avaimen tuonti viestistä epäonnistui
notFirstBlock=Virhe - Ensimmäinen OpenPGP-osio ei ole julkinen avain
importKeyConfirm=Tuodaanko viestiin sisällytetyt avaimet?
failKeyImport=Virhe - avainten tuonti epäonnistui
fileWriteFailed=Kirjoitus tiedostoon %S epäonnistui
importKey=Tuo julkinen avain %S avainpalvelimelta:
uploadKey=Lähetetäänkö julkinen avain %S avainpalvelimelle:
keyId=Avaintunnus
keyAndSigDate=Avaintunnus: 0x%S / Allekirjoitettu: %S
keyFpr=Avaimen sormenjälki: %S
noEmailProvided=Sähköpostiosoitetta ei ole asetettu.
keyAlreadySigned=Avain on jo kertaalleen allekirjoitettu.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=vanhenee %S
createdHeader=Luotu
atLeastOneKey=Avainta ei ole valittu! Valitse ainakin yksi avain ennen kuin suljet ikkunan
# fewerKeysThanRecipients=You have selected a smaller number of keys than recipients. Are you sure that the list of keys to encrypt is complete?
userSel.button.goBack=Valitse lisää avaimia
userSel.secretKeySel.title=Valitse salainen OpenPGP avain jolla allekirjoitat viestit
# userSel.problemNoKey=No valid key
# userSel.problemMultipleKeys=Multiple keys
# should be same as thunderbird ENTITY sendLaterCmd.label:
sendLaterCmd.label=Lähetä myöhemmin
# Strings used in enigmailAttachmentDialog.js
# pgpMimeNote=NOTE: PGP/MIME is not supported by all email clients. If you are unsure, select the %S option.
first=ensimmäinen
second=toinen
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Valitse salaukseen käytettävä OpenPGP-avain
identityName=Käyttäjätiedot: %S
# switchPepMode=You are currently using the 'p≡p Junior' mode of Enigmail.\n\nBy enabling OpenPGP or S/MIME for an account, you are disabling p≡p and use the 'regular' mode of Enigmail without p≡p.
# enableEnigmail=&Disable p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=Salaus on otettu käyttöön, mutta yhtäkään avainta ei ole valittu. Salataksesi osoitteeseen %S lähetettävät viestit, valitse avainlistasta yksi tai useampi voimassaoleva avaimesi. Poistetaanko salaus käytöstä osoitteelle %S?
noKeyToUse=(ei avainta - ei salausta)
noEmptyRule=Sääntö täytyy antaa. Kirjoita sääntökenttään sähköpostiosoite.
invalidAddress=Antamasi sähköpostiosoitteet ovat virheellisesti muotoiltuja. Anna ainoastaan vastaanottajien sähköpostiosoitteet, älä heidän nimiään. Esimerkki:\nVäärin: Joku Nimi \nOikein: joku.nimi@osoite.fi
# noCurlyBrackets=The curly brackets {} have a special meaning and should not be used in an email address. If you want to modify the matching behavior for this rule, use the 'Apply rule if recipient ...' option.\nMore information is available from the Help button.
# Strings used in enigmailRulesEditor.js
never=Ei koskaan
always=Aina
possible=Mahdollisesti
deleteRule=Poistetaanko valittu sääntö?
nextRcpt=(Seuraava vastaanottaja)
negateRule=Ei
# addKeyToRule=Add key %1$S (%2$S) to per-recipient rule
# Strings used in enigmailSearchKey.js
needOnline=Valitsemasi toiminto ei ole käytettävissä ilman verkkoyhteyttä. Siirry verkkoyhteystilaan ja yritä uudelleen.
protocolNotSupported=OpenPGP-avaimia ei voi noutaa käyttäen antamaasi yhteyskäytäntöä "%S://".
gpgkeysDisabled=Asetuksen "extensions.enigmail.useGpgKeysTool" ottaminen käyttöön voisi olla avuksi.
noKeyserverConn=Yhteys avainpalvelimeen %S epäonnistui.
keyDownloadFailed=Avaimen nouto avainpalvelimelta epäonnistui. Virheilmoitus oli:\n%S
internalError=Tapahtui sisäinen virhe. Avainten nouto tai tuonti epäonnistui.
noKeyFound=Ikävä kyllä yhtään avainta annetulle sähköpostiosoitteelle ei löytynyt.
# keyDownload.keyUnavailable=We are sorry, but the key with ID %S is not available on the keyserver. Most likely, the owner of the key did not upload their key to the keyserver.\n\nPlease ask the sender of the message to send you their key by email.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Avainten haku tai nouto avainpalvelimelta epäonnistui: ohjelmaa gpgkeys_%S ei kyetty suorittamaan.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Avaimen omistajan luottamustason asettaminen epäonnistui
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Avaimen allekirjoittaminen epäonnistui
# alreadySigned.label=Note: the key %S is already signed with the selected secret key.
# alreadySignedexportable.label=Note: the key %S is already signed exportable with the selected secret key. A local signature does not make sense.
# partlySigned.label=Note: some user IDs of key %S are already signed with the selected secret key.
# noTrustedOwnKeys=No eligible key found for signing! You need at least one fully trusted secret key in order to sign keys.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=Ladataan avaimia...
keyValid.unknown=tuntematon
keyValid.invalid=virheellinen
keyValid.disabled=ei käytössä
keyValid.revoked=mitätöity
keyValid.expired=vanhentunut
keyValid.noSubkey=ei kelvollista aliavainta
keyTrust.untrusted=ei luotettu
keyTrust.marginal=osittain luotettu
keyTrust.full=luotettu
keyTrust.ultimate=ehdottomasti luotettu
keyTrust.group=(ryhmä)
keyType.public=julk
keyType.publicAndSec=julk/sal
keyMan.enableKey=Ota avain käyttöön
keyMan.disableKey=Poista avain käytöstä
userAtt.photo=Käyttäjätieto (JPEG-kuva)
asciiArmorFile=ASCII-koodatut tiedostot (*.asc)
importKeyFile=Tuo OpenPGP avain tiedoston
gnupgFile=GnuPG-tiedostot
# createKeyOK=Your Key has been generated
saveRevokeCertAs=Luo ja tallenna mitätöintivarmenne
# revokeCertOK=The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
revokeCertFailed=Mitätöintivarmenteen luonti epäonnistui.
addUidOK=Käyttäjätunnuksen lisäys onnistui
addUidFailed=Käyttäjätunnuksen lisäys epäonnistui
noKeySelected=Vähintään yksi avain täytyy valita, jotta operaatio voidaan suorittaa
exportToFile=Valitse tiedostonimi vietäville avaimille
# exportKeypairToFile=Export Secret and Public Key To File
exportSecretKey=Tallennetaanko OpenPGP-tiedostoon myös salainen avaimesi?
saveKeysOK=Avainten tallennus onnistui
saveKeysFailed=Avainten tallennus epäonnistui
importKeysFailed=Avainten tuonti epäonnistui
enableKeyFailed=Avaimen käyttöön otto tai käytöstä poisto epäonnistui
specificPubKeyFilename=%S (0x%S) julk
specificPubSecKeyFilename=%S (0x%S) julk-sal
defaultPubKeyFilename=Viedyt-julkiset-avaimet
defaultPubSecKeyFilename=Viedyt-julkiset-ja-salaiset-avaimet
noSecretKeys=Salaisia avaimia ei löytynyt.\n\nLuodaanko avain nyt?
sendKeysOk=Avaimet lähetittiin onnistuneesti
sendKeysFailed=Avainten lähettäminen epäonnistui
receiveKeysOk=Avainten päivitys onnistui
receiveKeysFailed=Avainten nouto epäonnistui
importFromClip=Tuodaanko leikepöydällä olevat avaimet?
# importFromUrl=Download public key from this URL:
copyToClipbrdFailed=Avainten vienti leikepöydälle epäonnistui.
copyToClipbrdOK=Avaimet kopioitiin leikepöydälle
deleteSecretKey=VAROITUS: Olet poistamassa salaista avainta!\nAvaimelle salattuja viestejä ei voida enää purkaa jos avain poistetaan.\n\nPoistetaanko SEKÄ julkinen ETTÄ salainen avain\n"%S"?
deleteMix=VAROITUS: Olet poistamassa salaisia avaimia!\nAvaimelle salattuja viestejä ei voida enää purkaa jos avain poistetaan.\n\nPoistetaanko SEKÄ valitut julkiset ETTÄ salaiset avaimet?
deletePubKey=Poistetaanko julkinen avain tunnukselle\n%S?
deleteSelectedPubKey=Poistetaanko julkinen avain?
deleteKeyFailed=Avaimen poisto epäonnistui.
# revokeKeyQuestion=You are about to revoke the key '%S'.\n\nYou will no longer be able to sign with this key, and once distributed, others will no longer be able to encrypt with that key. You can still use the key to decrypt old messages.\n\nDo you want to proceed?
revokeKeyOk=Avain on mitätöity. Jos avain on saatavilla avainpalvelimelta, siirrä mitätöity avain palvelimelle, jotta muutkin näkevät mitätöinnin.
revokeKeyFailed=Avaimen mitätöinti epäonnistui.
# revokeKeyNotPresent=You have no key (0x%S) which fits to this revocation certificate!\n\nIf you have lost your key, you must import it (e.g. from a keyserver) before the revocation certificate!
# revokeKeyAlreadyRevoked=The key 0x%S has already been revoked.
refreshAllQuestion=Yhtään avainta ei valittu. Päivitetäänkö kaikki avaimet?
# refreshKeyServiceOn.warn=Warning: Your keys are currently being refreshed in the background as safely as possible.\nRefreshing all your keys at once will unnecessarily reveal information about you.\nDo you really want to do this?
refreshKey.warn=Varoitus: riippuen avainten lukumäärästä ja verkkoyhteyden nopeudesta, kaikkien avainten päivittäminen voi kestää kauan!\n\nJatketaanko?
# downloadContactsKeys.warn=Warning: depending on the number of contacts and the connection speed, downloading all keys could be quite a lengthy process!
downloadContactsKeys.importFrom=Import contacts from address book '%S'?
keyMan.button.exportSecKey=&Export Secret Keys
# keyMan.button.exportPubKey=Export &Public Keys Only
keyMan.button.import=&Tuo
keyMan.button.refreshAll=&Päivitä kaikki avaimet
keyMan.button.revokeKey=&Peruuta avain
keyMan.button.skip=&Ohita avain
keylist.noOtherUids=Ei ole muuta identiteettiä
# keylist.hasOtherUids=Also known as
keylist.noPhotos=Ei valokuvaa saatavilla
keylist.hasPhotos=Valokuvat
keyMan.addphoto.filepicker.title=Valokuva
# keyMan.addphoto.warnLargeFile=The file you have chosen is larger than 25 kB.\nIt is not recommended to add very large files because the keys get very large by this.
# keyMan.addphoto.noJpegFile=The selected file does not appear to be a JPEG file. Please choose a different file.
keyMan.addphoto.failed=Valokuvaa ei voitu lisätä
# noWksIdentity=The key %S does not have a WKS identity.
# keyman.addBlacklistKey.msg=Do you really want p≡p to stop using the key "%1$S (%2$S)" for encrypting messages?
# keyman.removeBlacklistKey.msg=Do you want to allow p≡p to use key "%1$S (%2$S)" for future messages?
# keyman.addBlacklistKey.button=&Blacklist the key
# keyman.removeBlacklistKey.button=&Remove key from Blacklist
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Ensisijaisen käyttäjätunnuksen vaihto epäonnistui
changePrimUidOK=Ensisijaisen käyttäjätunnuksen vaihto onnistui
revokeUidFailed=Käyttäjätunnuksen %S mitätöinti epäonnistui
revokeUidOK=Käyttäjätunnuksen %S mitätöinti onnistui. Jos avain on saatavilla avainpalvelimelta, siirrä mitätöity avain palvelimelle, jotta muutkin näkevät mitätöinnin.
revokeUidQuestion=Mitätöidäänkö käyttäjätunnus %S?
# Strings in enigmailKeyImportInfo.xul
# importInfoTitle=SUCCESS! Keys imported
# importInfoBits=Bits
# importInfoCreated=Created
# importInfoFpr=Fingerprint
# importInfoDetails=(Details)
# importInfoNoKeys=No keys imported.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=julkinen avain
# keyTypePrimary=primary key
keyTypeSubkey=aliavain
keyTypePair=avainpari
keyExpiryNever=ei koskaan
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
# keyAlgorithm_18=ECDH
# keyAlgorithm_19=ECDSA
keyAlgorithm_20=ELG
# keyAlgorithm_22=EDDSA
# keyUsageEncrypt=Encrypt
# keyUsageSign=Sign
# keyUsageCertify=Certify
# keyUsageAuthentication=Authentication
# keyDoesNotExpire=Key does not expire
# Strings in enigmailGenCardKey.xul
keygen.started=Odota avaimen luonnin valmistumista....
keygen.completed=Avain luotu. Uuden avaimen tunnus on: 0x%S
keygen.keyBackup=Avaimesta luotiin varmuuskopio nimellä %S
keygen.passRequired=Kirjoita salasana jos haluat luoda varmuuskopion avaimesta toiselle medialle.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=PIN-koodin vaihtaminen ei onnistunut
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Päivitetään avaimia, ole hyvä ja odota...
keyserverProgress.uploading=Siirretään avaimia avainpalvelimella, ole hyvä ja odota...
# keyserverProgress.wksUploadFailed=Could not upload your key to the Web Key Service
# keyserverProgress.wksUploadCompleted=Your public key was successfully submitted to your provider. You will receive an email to confirm that you initiated the upload.
keyserverTitle.refreshing=Päivitetään avaimia
keyserverTitle.uploading=Avainten siirto
# Strings in enigmailSetupWizard
passphrase.min8keys=Salasanan tulee olla ainakin 8-kirjainta pitkä.
setupWizard.reallyCancel=Peruutetaanko Enigmail:n ohjattu asennus?
# setupWizard.invalidGpg=The file you specified is not a GnuPG executable. Please specify a different file.
# setupWizard.specifyFile=You need to at least specify a public key file in order to proceed.
# setupWizard.installFailed=It seems that the installation was not successful. Please either retry the installation, or install GnuPG manually and locate it using the Browse button.
# setupWizard.downloadForbidden=For your own security, we will not download GnuPG. Please visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.downloadImpossible=We cannot download GnuPG currently. Please try later or visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.hashSumError=The wizard could not verify the integrity of the downloaded file. The file may be broken or manipulated. Do you want to continue the installation anyway?
# setupWizard.importSettingsFile=Specify backup file to load from
# setupWizard.invalidSettingsFile=The specified file is not a correct Enigmail Settings backup file.
# setupWizard.gpgConfExists=The GnuPG config file already exists. Do you want to overwrite it with the one from your old installation?
# setupWizard.noGpgHomeDir=It appears that you configured %S to use for GnuPG. However, this is not a directory - you cannot use it.
# setupWizard.unmachtedIds=The following identities of your old setup could not be matched:\n%S\nThe settings for these identities were skipped.
# Strings in installGnuPG.jsm
# installGnuPG.downloadFailed=An error occurred while trying to download GnuPG. Please check the console log for further details.
# installGnuPG.installFailed=An error occurred while installing GnuPG. Please check the console log for further details.
# Strings in enigmailAddUidDlg.xul
# addUidDlg.nameOrEmailError=You have to fill in a name and an email address
# addUidDlg.nameMinLengthError=The name must at least have 5 characters
# addUidDlg.invalidEmailError=You must specify a valid email address
# Strings in enigmailCardDetails.js
# Carddetails.NoASCII=OpenPGP Smartcards only support ASCII characters in Firstname/Name.
# network error types
# errorType.SecurityCertificate=The security certificate presented by the web service is not valid.
# errorType.SecurityProtocol=The security protocol used by the web service is unknown.
# errorType.Network=A network error has occurred.
# filter stuff
# filter.folderRequired=You must select a target folder.
# filter.decryptMove.label=Decrypt permanently (Enigmail)
# filter.decryptCopy.label=Create decrypted Copy (Enigmail)
# filter.decryptMove.warnExperimental=Warning - the filter action "Decrypt permanently" may lead to destroyed messages.\n\nWe strongly recommend that you first try the "Create decrypted Copy" filter, test the result carefully, and only start using this filter once you are satisified with the result.
# filter.tempPepFilterDesc=Temporary filter to store sent message unencrypted
# filter.term.pgpencrypted.label=OpenPGP Encrypted
# filter.encrypt.label=Encrypt to key (Enigmail)
# filter.keyRequired=You must select a recipient key.
# filter.keyNotFound=Could not find an encryption key for "%S".
# filter.warn.keyNotSecret=Warning - the filter action "Encrypt to key" replaces the recipients.\n\nIf you do not have the secret key for "%S" you will no longer be able to read the emails.
# strings in enigmailConvert.jsm
# converter.decryptBody.failed=Could not decrypt message with subject\n"%S".\nDo you want to retry with a different passphrase or do you want to skip the message?
# converter.decryptAtt.failed=Could not decrypt attachment "%1$S"\nof message with subject\n"%2$S".\nDo you want to retry with a different passphrase or do you want to skip the message?
# saveLogFile.title=Save Log File
# strings in gpg.jsm
# unknownSigningAlg=Unknown signing algorithm (ID: %S)
# unknownHashAlg=Unknown cryptographic hash (ID: %S)
# strings in keyRing.jsm
# keyring.photo=Photo
# keyRing.pubKeyRevoked=The key %1$S (key ID %2$S) is revoked.
# keyRing.pubKeyExpired=The key %1$S (key ID %2$S) has expired.
# keyRing.pubKeyNotForSigning=The key %1$S (key ID %2$S) cannot be used for signing.
# keyRing.pubKeyNotForEncryption=The key %1$S (key ID %2$S) cannot be used for encryption.
# keyRing.keyDisabled=The key %1$S (key ID %2$S) is disabled; it cannot be used.
# keyRing.keyNotTrusted=The key %1$S (key ID %2$S) is not trusted enough. Please set the trust level of your key to "ultimate" to use it for signing.
# keyRing.keyInvalid=The key %1$S (key ID %2$S) is not valid. Please consider verifying it correctly. Alternatively use the Default encryption settings in the Enigmail preferences dialog.
# keyRing.signSubKeysRevoked=All signing-subkeys of key %1$S (key ID %2$S) are revoked.
# keyRing.signSubKeysExpired=All signing-subkeys of key %1$S (key ID %2$S) have expired.
# keyRing.signSubKeysUnusable=All signing-subkeys of key %1$S (key ID %2$S) are revoked, expired or otherwise unusable.
# keyRing.encSubKeysRevoked=All encryption subkeys of key %1$S (key ID %2$S) are revoked.
# keyRing.encSubKeysExpired=All encryption subkeys of key %1$S (key ID %2$S) have expired.
# keyRing.noSecretKey=You do not seem to have the secret key for %1$S (key ID %2$S) on your keyring; you cannot use the key for signing.
# keyRing.encSubKeysUnusable=All encryption subkeys of key %1$S (key ID %2$S) are revoked, expired or otherwise unusable.
#strings in exportSettingsWizard.js
# cannotWriteToFile=Cannot save to file '%S'. Please select a different file.
# dataExportError=An error occurred during exporting your data.
# enigmailSettings=EnigmailSettings
# defaultBackupFileName=Enigmail-export
# specifyExportFile=Specify file name for exporting
# homedirParamNotSUpported=Additional params that configure paths such as --homedir and --keyring are not supported for exporting/restoring your settings. Please use alternative methods such as setting the environment variable GNUPGHOME.
#strings in expiry.jsm
# expiry.keyExpiresSoon=Your key %1$S will expire in less than %2$S days.\n\nWe recommend that you create a new key pair and configure the corresponding accounts to use the new key.
# expiry.keysExpireSoon=The following of your keys will expire in less than %1$S days:\n%2$S We recommend that you create new keys and configure your accounts to use the new keys.
# expiry.keyMissingOwnerTrust=Your secret key %S has missing trust.\n\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.keysMissingOwnerTrust=The following of your secret keys have missing trust.\n%S.\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.OpenKeyManager=Open Enigmail Key Management
# expiry.OpenKeyProperties=Open Key Properties
#strings in pEpDecrypt.jsm
# pEpDecrypt.cannotDecrypt=This is an encrypted message. Unfortunately you don't have the secret key to decrypt the message.
#strings in gpgAgent.jsm
# gpghomedir.notexists=The directory '%S' containing your OpenPGP keys does not exist and cannot be created.
# gpghomedir.notwritable=The directory '%S' containing your OpenPGP keys is not writable.
# gpghomedir.notdirectory=The directory '%S' containing your OpenPGP keys is a file instead of a directory.
# gpghomedir.notusable=Please fix the directory permissions or change the location of your GnuPG "home" directory. GnuPG cannot work correctly otherwise.
#strings in pepTrustWords.js
# pepTrustWords.cannotVerifyOwnId=Cannot verify p≡p Trustwords for own account.
# pepTrustWords.cannotFindKey=Cannot find key for %S.
# pepTrustWords.cannotStoreChange=Could not change trust for %S.
# pepTrustWords.generalFailure=Cannot obtain trustwords for %S.
# pepTrustWords.partnerFingerprint=Fingerprint for %S:
#strings in mimeWkdHandler.jsm
# wkdMessage.body.req=Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.\n\nPlease click the confirmation button in the Enigmail header to complete the publishing of your public key.
# wkdMessage.body.process=This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.\n\nYou do not need to take any manual action at this point.
#strings in pepHandshake.js
# pepPrivacyStatus.RatingBrokenSuggestion=Either you or the sender should resend the message.
# pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=If you composed this message, your key is not available.
# pepPrivacyStatus.RatingMistrustSuggestion=Re-establish the connection with your communication partner and try to complete another handshake.
# pepPrivacyStatus.RatingReliableSuggestion=Complete a handshake with your communication partner by exchanging trustwords in person or over the phone. A handshake is needed only once per partner and will ensure secure and trusted communication.
# pepPrivacyStatus.RatingTrustedSuggestion=No action needed!
# pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Be aware this message may not be secure.
# pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=Please add the necessary information.
# pepPrivacyStatus.RatingUnderAttackSuggestion=Separately verify the content of this message with your communication partner.
# pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Make sure the privacy status for each communication partner listed is at least secure.
# pepPrivacyStatus.RatingUnencryptedSuggestion=Please ask your communication partner to use an encryption solution or install p≡p.
# pepPrivacyStatus.RatingUnreliableSuggestion=This message has no reliable encryption or no signature. Ask your communication partner to upgrade their encryption solution or install p≡p.
# pepPrivacyStatus.RatingBrokenExplanation=This message has broken encryption or formatting.
# pepPrivacyStatus.RatingHaveNoKeyExplanation=This message cannot be decrypted because the key is not available.
# pepPrivacyStatus.RatingMistrustExplanation=This message has a communication partner that has previously been marked as mistrusted.
# pepPrivacyStatus.RatingReliableExplanation=This message is secure but you still need to verify the identity of your communication partner.
# pepPrivacyStatus.RatingTrustedExplanation=This message is secure and trusted.
# pepPrivacyStatus.RatingUndefinedExplanation=This message does not contain enough information to determine if it is secure.
# pepPrivacyStatus.RatingUnderAttackExplanation=This message is not secure and has been tampered with.
# pepPrivacyStatus.RatingUnencryptedExplanation=This message is unsecure.
# pepPrivacyStatus.RatingUnencryptedForSomeExplanation=This message is unsecure for some communication partners.
# pepPrivacyStatus.RatingUnreliableExplanation=This message has unreliable protection.
# pepPrivacyStatus.RatingBrokenText=Broken
# pepPrivacyStatus.RatingHaveNoKeyText=Cannot Decrypt
# pepPrivacyStatus.RatingMistrustText=Mistrusted
# pepPrivacyStatus.RatingReliableText=Secure
# pepPrivacyStatus.RatingTrustedText=Secure & Trusted
# pepPrivacyStatus.RatingUndefinedText=Unknown
# pepPrivacyStatus.RatingUnderAttackText=Under Attack
# pepPrivacyStatus.RatingUnencryptedForSomeText=Unsecure for Some
# pepPrivacyStatus.RatingUnencryptedText=Unsecure
# pepPrivacyStatus.RatingUnreliableText=Unreliable Security
# handshakeDlg.button.initHandshake=Handshake...
# handshakeDlg.button.stopTrust=Stop Trusting
# handshakeDlg.button.reTrust=Stop Mistrusting
# handshakeDlg.label.outgoingMessage=Outgoing message
# handshakeDlg.label.incomingMessage=Incoming message
# handshakeDlg.error.noPeers=Cannot handshake without any correspondents.
# handshakeDlg.error.noProtection=Please enable protection in order to use the Handshake function.
# enigmail.acSetupPasswd.descEnterPasswd=Please enter the setup code that is displayed on the other device
# enigmail.acSetupPasswd.descCopyPasswd=Please enter the setup code below on your other device to proceed with the setup
#strings in autocrypt.jsm
# autocrypt.setupMsg.subject=Autocrypt Setup Message
# autocrypt.setupMsg.msgBody=To set up your new device for Autocrypt, please follow the instuctions that should be presented by your new device.
# autocrypt.setupMsg.fileTxt=This is the Autocrypt setup file used to transfer settings and keys between clients. You can decrypt it using the setup code presented on your old device, and then import the contained key into your keyring.
#strings in upgradeInfo.html
# upgradeInfo.doctitle=What's New in Enigmail v2.0?
# upgradeInfo.welcome1=Welcome to the new Enigmail version 2.0!
# upgradeInfo.welcome2=The release contains a lot of new and changed features. Please take a minute to find out what's new:
# upgradeInfo.encSubject.title=Encrypting the Message Subject
# upgradeInfo.encSubject.desc=We developed a new method that moves the email subject into the encrypted message, and replaces the visible subject with "Encrypted Message". Once such a message is decrypted, the original subject is replaced automatically. Hiding the subject is on by default; there is a preference to turn it off if you don't like it. (Note: this feature requires the message to be sent with PGP/MIME.)
# upgradeInfo.buttons.title=Changed behavior of Encrypt and Sign Buttons
# upgradeInfo.buttons.desc=The Encrypt and Sign buttons in the message composer window now work for both the OpenPGP and S/MIME protocols. If both algorithms are possible, then Enigmail will try to prefer the one for which all keys are available.
# upgradeInfo.autocrypt.title=Support for Autocrypt
# upgradeInfo.autocrypt.desc=Enigmail now supports Autocrypt, a new standard to distribute keys as part of sent messages. Enigmail automatically imports keys from Autocrypt-compliant messages, such that over time more and more emails can be encrypted.
# upgradeInfo.pEp.title=New p≡p Junior Mode (Pretty Easy Privacy)
# upgradeInfo.pEp.desc=Enigmail now contains a p≡p Junior Mode. You currently need to manually install p≡p for this purpose; this will change in a future release. The p≡p Junior Mode allows you to use OpenPGP encryption as transparently as possible; you don't need to care for key management and synchronization of keys between devices anymore.
# upgradeInfo.bottom.desc=Please visit our documentation for help on using Enigmail.
# pep.missingGnuPG=In order to use Enigmail/p≡p, GnuPG is required. As we could not find it, we suggest to download and install it for you.
#strings in enigmailAbout.html
# aboutEnigmail.tabName=About Enigmail
# aboutEnigmail.title=OpenPGP support provided by Enigmail
# aboutEnigmail.team=Enigmail is developed by the Enigmail Team:
# aboutEnigmail.projectLeader=Lead Developer:
# aboutEnigmail.usability=Usability:
# aboutEnigmail.documentation=Documentation:
# aboutEnigmail.testing=Testing:
# aboutEnigmail.userSupport=User Support:
# aboutEnigmail.localization=Localization: See the Enigmail Language Packs page
# aboutEnigmail.Credits=Credits:
# aboutEnigmail.origAuthor=Original author of the Enigmail extension
# aboutEnigmail.icons=Icons:
# aboutEnigmail.formerMembers=Former team members:
# aboutEnigmail.projectHosting=Project hosting:
# aboutEnigmail.licenseSupportTitle=License & Support
# aboutEnigmail.license=Enigmail OpenPGP is open source and licensed under the %S
# aboutEnigmail.support=Support and download is available from www.enigmail.net.
enigmail-2.0.8/lang/fi/help/ 0000775 0000000 0000000 00000000000 13343027545 0015563 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/fi/help/compose.html 0000664 0000000 0000000 00000007125 13343027545 0020123 0 ustar 00root root 0000000 0000000
Enigmailin ohje: Viestien kirjoittamisesta
Enigmailin ohje
Enigmailin käyttö kirjoitettaessa viestejä
Enigmailin valikko Posti tai viestin kirjoitusikkunassa
Allekirjoita viesti: Ota käyttöön tai poista käytöstä viestin allekirjoitus.
Käyttäjälle ilmoitetaan allekirjoituksen epäonnistumisesta.
Salaa viesti: Ota käyttöön tai poista käytöstä viestin salaus kaikille vastaanottajille.
Käyttäjälle ilmoitetaan salaamisen epäonnistumisesta.
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ä.
Käytä PGP/MIME:ä tässä viestissä: Ota käyttöön tai poista käytöstä
PGP/MIME
tässä viestissä.
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:ä.
Kumoa salaus: Jos viestin lähettämisessä tapahtuu jokin
virhe, kuten esimerkiksi POP-palvelinvirhe, Enigmail ei voi tietää sitä ja
salattu viesti jää salatuksi viestin kirjoitusikkunaan. Palauta viesti
selkokieliseksi valitsemalla Kumoa salaus. Kun Enigmail ei virheellisesti pura salausta lainatusta tekstistä kun
salattuun viestiin vastataan, tai salausta ei pureta automaattisesti jostain
muusta syystä, tätä toimintoa voi käyttää väliaikaisena korjauksena.
Yleensä salauksen purku toimii automaattisesti.
Lisää julkinen avain: Lisää julkisen avaimen
ASCII-koodattuna viestiin osoittimen sijainnista alkaen. Avaimeen sisällytettävät
sähköpostiosoitteet kysytään erikseen. Lisää viestiin vain yksi avainosio ja
valitse halutut julkiset avaimet. Jos vastaanottaja käyttää Enigmailia,
avainosio huomataan automaattisesti. Kun avaimet on lisätty, viesti voidaan
vielä salata ja allekirjoittaa.
Tyhjennä salasana muistista: Tyhjentää salasanan
muistista. Toiminto on hyödyllinen, jos sinulla on useita avaimia ja useita
salasanoja.
Sää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.
Aseta OpenPGP-säännöt osoitteille: Kentässä on täydelliset
sähköpostiosoitteet (tai osa osoitteista) joille alla olevat säännöt pätevät
suotimen tavoin. Jos osoitesuotimia on useita, ne erotetaan välilyönnillä.
Suotimet voivat olla esimerkiksi pelkkä verkkoalue @sposti.fi, johon
täsmäisivät kaikki @sposti.fi:n loppuvat osoitteet.
Sääntö pätee jos ylläoleva: Osoitesuotimen käyttäytymisen
voi valita. Jos yllä olevassa kentässä on useita osoitteita, käyttäytymisasetus
pätee kaikille osoitteille. Alla olevissa esimerkeissä osoitesuodinkenttään on
kirjoitettu nieminen@sposti.fi.
on täsmälleen vastaanottajan osoite: Tällä asetuksella sääntö
pätee viesteille, jotka lähetetään osoitteeseen nieminen@sposti.fi
(täsmäys on kirjainkoon huomioiva).
on osa vastaanottajan osoitetta: Tällä asetuksella sääntö
pätee viesteille, jotka lähetetään esim. osoitteisiin
matti.nieminen@sposti.fi, nieminen@sposti.fi.com jne.
ja vastaanottajan osoitteen alku täsmäävät: Tällä asetuksella
sääntö pätee viesteille, jotka lähetetään esim. osoitteeseen
nieminen@sposti.fi.com
ja vastaanottajan osoitteen loppu täsmäävät: Tällä asetuksella
sääntö pätee viesteille, jotka lähetetään esim. osoitteeseen
maija.nieminen@sposti.fi
Jatka seuraavaan sääntöön täsmäävälle osoitteelle
Jos asetus on valittu, Enigmail hakee osoitteeseen kuuluvaa OpenPGP-avainta
vasta viestiä lähetettäessä, ja muut säännöt voivat muuttaa täsmäävien viestien
lähetysasetuksia.
Älä tarkista enää sääntöjä täsmäävälle osoitteelle
Jos asetus on valittu, täsmääviin osoitteisiin ei sovelleta muita sääntöjä.
Täsmäävä osoite jätetään siis huomiotta muita sääntöjä käsiteltäessä.
Käytä seuraavia OpenPGP-avaimia:
Valitse käytettävät vastaanottajien avaimet napsauttamalla Valitse
avaimet-painiketta. Kuten yllä, jos asetus on valittu, muita sääntöjä
ei huomioida täsmääville sähköpostiosoitteille.
Allekirjoittaminen:
Allekirjoita tai älä allekirjoita viestejä tälle vastaanottajalle. Tämä asetus
joko noudattaa viestin kirjoitusikkunassa antamaasi käskyä tai muuttaa sen.
Mahdolliset arvot:
Ei koskaan: Älä ikinä allekirjoita viestiä
vastaanottajalle, huolimatta viestin kirjoitusikkunan asetuksista.
Vain jos valitaan erikseen viestiä kirjoitettaessa: Allekirjoita
viesti jos niin on viestin kirjoitusikkunassa asetettu
Aina: Allekirjoita viestit vastaanottajalle aina, huolimatta
viestin kirjoitusikkunan asetuksista
Jokainen sääntö pätee kaikille täsmääville
viesteille. Jos jokin säännöistä ottaa allekirjoituksen pois päältä, viestiä ei
allekirjoiteta huolimatta siitä, mitä muut säännöt määräisivät.
Salaa: Salaa tai älä
salaa viestiä. Asetusvalinnat ja niiden merkitykset ovat samat kuin viestin
allekirjoitukselle.
PGP/MIME: Ota käyttöön tai poista käytöstä PGP/MIME (RFC
3156) -koodaus. Jos PGP/MIME ei ole käytössä, viestit allekirjoitetaan ja
salataan käyttäen viestinsisäistä PGP:tä. Asetusvalinnat ja niiden merkitykset
ovat samat kuin viestin allekirjoitukselle.
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ä.
enigmail-2.0.8/lang/fi/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020433 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
Pura salaus -painike posti-ikkunassa
Pura-painikkeella voi purkaa salauksen, varmistaa allekirjoituksen tai tuoda
julkisia avaimia. Normaalisti salauksen purku tai allekirjoituksen varmistus
tapahtuu automaattisesti, mutta jos näin ei käy, Enigmailin tilariville ilmestyy
lyhyt virheilmoitus. Pura-painikkeesta saa tarkemman virheilmoituksen jossa
on mukana GnuPG-komennon virheilmoitus.
Allekirjoitus- ja salauskuvakkeet viestin otsaketiedoissa Allekirjoitus (kynä) ja salaus (avain) -kuvakkeet
ovat viestiotsakkeissa riippuen siitä, onko viesti allekirjoitettu hyvin (eli
viestiä ei ole muokattu siirrettäessä) tai salattu. Jos viestiä on jollain tapaa
muutettu siirrettäessä eli sen allekirjoitus on huono, tämä näkyy
allekirjoituskuvakkeessa (se on esimerkiksi rikkinäinen tai yliviivattu kynä).
Napsauttamalla kuvaketta hiiren oikealla painikkeella avautuu ponnahdusvalikko,
jossa on seuraavat kohdat:
Näytä OpenPGP-kuva: Näyttää kuvan, jonka viestin
lähettäjä on liittänyt julkiseen avaimeensa (vain jos kuva on olemassa).
S/MIME-turvallisuustiedot: Näyttää viestin
S/MIME-turvallisuustiedot.
Kun 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ä.
Salattujen liitetiedostojen avaaminen ja liitettyjen OpenPGP-avainten tuonti
Enigmail käsittelee liitteet, joiden tiedostopääte on pgp, asc tai gpg.
Tällaisen liitteen ponnahdusvalikossa (napsauta hiiren oikealla painikkeella
liitettä) on kaksi erityistä valintaa: Pura ja avaa sekä Pura ja
tallenna. Näillä valinnoilla voit purkaa liitteen salauksen ennen kuin
avaat tai tallennat sen. Jos liite tunnistetaan OpenPGP-avaintiedostoksi,
sinulta kysytään haluatko tuoda avaimet.
Sää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ähköpostiosoite:
Osoitteet, joiden vastaanottaja-, kopio- tai piilokopiokentässä on
ehdon täyttävä osoite. Ehto voi koskea myös vain osaa osoitteesta
(lisätietoja muokkaa sääntöjä -ikkunasta)
OpenPGP-avaimet: Lista vastaanottajalle käytettävistä
OpenPGP-avaimista
Allekirjoita: Allekirjoita tai älä allekirjoita viestejä
tälle vastaanottajalle. Tämä asetus joko noudattaa viestin kirjoitusikkunassa
antamaasi käskyä tai muuttaa sen. Mahdolliset arvot:
Ei koskaan: Älä ikinä allekirjoita viestiä vastaanottajalle,
huolimatta viestin kirjoitusikkunan asetuksista.
Mahdollisesti: Allekirjoita viesti jos niin on viestin
kirjoitusikkunassa asetettu
Aina: Allekirjoita viestit vastaanottajalle aina, huolimatta viestin
kirjoitusikkunan asetuksista
Jokainen sääntö pätee kaikille täsmääville
viesteille. Jos jokin säännöistä ottaa allekirjoituksen pois päältä, viestiä ei
allekirjoiteta huolimatta siitä, mitä muut säännöt määräisivät.
Salaa: Salaa tai älä salaa viestiä. Asetusvalinnat ja
niiden merkitykset ovat samat kuin viestin allekirjoitukselle.
PGP/MIME: Ota käyttöön tai poista käytöstä PGP/MIME (RFC
3156) -koodaus. Jos PGP/MIME ei ole käytössä, viestit allekirjoitetaan ja
salataan käyttäen viestinsisäistä PGP:tä. Asetusvalinnat ja niiden merkitykset
ovat samat kuin viestin allekirjoitukselle.
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
enigmail-2.0.8/lang/fr/help/initError.html 0000664 0000000 0000000 00000004764 13343027545 0020452 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/gd/ 0000775 0000000 0000000 00000000000 13343027545 0014627 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/gd/am-enigprefs.properties 0000664 0000000 0000000 00000000127 13343027545 0021322 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=Tèarainteachd OpenPGP
enigmail-2.0.8/lang/gd/enigmail.dtd 0000664 0000000 0000000 00000215150 13343027545 0017115 0 ustar 00root root 0000000 0000000
Mozilla Public License 2.0.">
Iarraidh “Tar-chur na h-iuchrach Autocrypt†gum bi comas Autocrypt aig a’ chliant puist-d air an uidheam eile.
Ged as e am fuasgladh as simplidhe a th’ ann, cha chuir ach cuid a chliantan taic ris aig an à m seo.
’S e “Lethbhreac-glèidhidh ⊠aiseag†dhe na roghainnean agad a tha san dòigh eile.
Cruthaichidh sin faidhle ZIP leis an fhiosrachadh is na h-iuchraichean uile air a bheil feum ’na bhroinn agus ’s urrainn dhut lethbhreac dheth a chur air an uidheam ùr an uairsin.
’S urrainn dha Enigmail na roghainnean sin ion-phortadh gun duilgheadas; airson cliantan puist-d eile, gabhaidh am faidhle ZIP a dhì-dhùmhlachadh agus dèiligeadh ris a là imh.">
â€">
†gus seòlaidhean puist-d a shònrachadh">
†gus seòlaidhean puist-d a shònrachadh airson GnuPG. Cuir à comas ma tha seann-iuchraichean Hushmail aig faightearan.">
“Tèarainteachd OpenPGPâ€)">
AN AIRE: Dh’fhaoidte gun doir e mionaid no dhà gus am bi gintinn nan iuchraichean coileanta. Na fà g an aplacaid fhad ’s a tha iuchair ’ga gintinn. Ma nì thu brabhsadh no obair a bhios feumach air cleachdadh an diosga fhad ’s a tha iuchair ’ga gintinn, cuiridh seo ris a’ “ghoireas thuaireamach†agus nì seo am pròiseas nas luaithe. Gheibh thu brath nuair a bhios gintinn nan iuchraichean coileanta.">
Autocrypt a mhìnicheas ciamar a nithear crioptachadh puist-d o cheann gu ceann a tha furasta cleachdadh. Tha e a’ sònrachadh ciamar a nì prògraman puist-d rèiteachadh air comasan crioptachaidh slighe phost-d à bhaisteach.">
†mì-dhligheach">
AN AIRE: Dh’fhaoidte gun doir e mionaid no dhà gus am bi gintinn nan iuchraichean coileanta. Na fà g an aplacaid fhad ’s a tha iuchair ’ga gintinn. Gheibh thu brath nuair a bhios gintinn nan iuchraichean coileanta.">
An aire: Nì Enigmail dearbhadh air soidhneadh
puist-d airson gach cunntas no dearbh-aithne an-còmhnaidh ge b’ e a chaidh a chur an comas gus nach deach">
iuchair phoblach agad ann do chà ch ach an cuir iad puist-d chrioptaichte thugad. ’S urrainn dhut a sgaoileadh dhan a h-uile duine.">
iuchair phrìobhaideach agad ann dhut fhèin ach an dì-chrioptaich thu na puist-d sin agus gus puist-d le soidhneadh a chur. Na doir do dhuine beò i.">
iuchair phrìobhaideach agad ann dhut fhèin ach an dì-chrioptaich thu na puist-d sin agus gus puist-d le soidhneadh a chur. Na doir do dhuine beò i.
Gus an iuchair phrìobhaideach agad a chumail tèarainte, thèid abairt-fhaire iarraidh ort san da chòmhradh a leanas.">
abairt-fhaire agad a dhìonas an iuchair phrìobhaideach agad. Cuiridh i casg air droch chleachdadh na h-iuchrach prìobhaidich agad.">
Cha mholamaid gun cuireadh tu srà can (m.e. à , ù) no caractaran sònraichte do chà nan innte.">
Thèid iarraidh ort gun cuir thu a-steach am facal-faire agad airson seo. Feuch an tar-chuir thu an teisteanas gu meadhan a ghabhas a stòradh gu sà bhailte, can CD no UB stick. Ma gheibh cuideigin eile greim air an teisteanas seo, ’s urrainn dhaibh an iuchair agad a chur à feum.">
à s-phortaich an dà ta agad on t-seann choimpiutair agad le draoidh à s-phortadh o na roghainnean Enigmailion-phortaich an dà ta dhan choimpiutair ùr agad leis an draoidh seo.
">
Mòran taing airson Enigmail a chleachdadh.">
Dearbhaich an t-iarrtas a gheibh thu sa bhogsa a-steach agad mas e seo a tha thu ag iarraidh.">
à s-phortaich an dà ta agad on t-seann choimpiutair agad leis an draoidh seoion-phortaich an dà ta dhan choimpiutair ùr agad le draoidh an rèiteachaidh.
">
Tagh an cunntas gu h-ìosal gus an iuchair aige a thar-chur.
Seallaidh sinn còd suidheachaidh dhut (facal-faire) air an ath-sgrìn a dh’fheumas tu cur a-steach air an uidheam eile gus an iuchair agad agus na roghainnean ceangailte rithe ion-phortadh.">
Cleachd an t-uidheam eile a-nis agus fosgail an teachdaireachd seo air-san. Thèid còd suidheachaidh iarraidh ort. Sgrìobh na h-à ireamhan seo ann:">
enigmail-2.0.8/lang/gd/enigmail.properties 0000664 0000000 0000000 00000201766 13343027545 0020546 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Caismeachd Enigmail
enigConfirm=Dearbhadh Enigmail
enigInfo=Fiosrachadh Enigmail
enigError=Mearachd Enigmail
enigPrompt=Ceist Enigmail
dlgYes=&Tha
dlgNo=&Chan eil
dlgKeepSetting=Cuir an fhreagairt agam an cuimhne is na faighnich dhìom a-rithist
dlgNoPrompt=Na seall an còmhradh seo a-rithist
dlg.button.delete=&Sguab à s
dlg.button.cancel=&Sguir dheth
dlg.button.close=&Dùin
dlg.button.continue=Lean air adhar&t
dlg.button.skip=Gearr &leum
dlg.button.overwrite=&Sgrìobh thairis air
dlg.button.view=&Seall
dlg.button.retry=Feuch ris a-&rithist
dlg.button.ignore=Le&ig seachad
dlg.button.install=Stà la&ich
dlg.button.ok=&Ceart ma-thÃ
repeatPrefix=\n\nNochdaidh a’ chaismeachd seo a-rithist %S
repeatSuffixSingular=turas eile.
repeatSuffixPlural=tursan/turas eile.
noRepeat=\n\nChan nochd a’ chaismeachd seo a-rithist gus an à rdaich thu Enigmail.
pgpNotSupported=Tha coltas gu bheil thu a’ chleachdadh Enigmail còmhla ri PGP 6.x\n\nGu mì-fhortanach, cha duilgheadasan aig PGP 6.x a dh’adhbharaicheas nach obraich Enigmail mar bu chòir. Mar sin, cha chuir Enigmail taic ri PGP 6.x tuilleadh; cleachd GnuPG (GPG) ’na à ite.\n\nMa tha thu feumach air taic gus atharrachadh gu GnuPG, thoir sùil air earrann na cobharach air an duilleag-dhachaigh aig Enigmail.
initErr.howToFixIt=Tha thu feumach air GnuPG mus urrainn dhut Enigmail a chleachdadh. Mur an do stà laich thu GnuPG fhathast, ’s e an dòigh as fhasa gun cleachd thu putan “Draoidh an rèiteachaidh†gu h-ìosal.
initErr.setupWizard.button=Draoidh an &rèiteachaidh
passphraseCleared=Tha an abairt-fhaire air fhalamhachadh.
cannotClearPassphrase=Tha thu a’ cleachdadh inneal neo-à bhaisteach (mar gnome-keyring) gus abairtean-faire a là imhseachadh. Chan eil Enigmail fhèin comasach air an abairt-fhaire fhalamhachadh air an adhbhar seo.
noPhotoAvailable=Chan eil dealbh ri là imh
debugLog.title=Loga dì-bhugachaidh Enigmail
error.photoPathNotReadable=Cha ghabh slighe an deilbh “%S†leughadh
generalError=Mearachd: %S
# Strings in configure.jsm
enigmailCommon.versionSignificantlyChanged=Thà inig atharrachadh mòr air mar a thèid roghainnean a là imhseachadh leis an tionndadh ùr seo de dh’Enigmail. Dh’fheuch sinn ris na seann roghainnean a thar-aiseag dhan tionndadh ùr seo. Co-dhiù, chan urrainn dhut dèiligeadh ris a h-uile roghainn gu fèin-obrachail. Thoir sùil air na roghainnean ùra a fhuair thu mar thoradh.
enigmailCommon.checkPreferences=Dearbhaich na roghainnean…
preferences.defaultToPgpMime=Dh’atharraich sinn còdachadh tùsail nan teachdaireachdan ann an Enigmail o PGP ion-loidhne gu PGP/MIME. Mholamaid gun cum thu seo mar a’ bhun-roghainn.\n\nNam bu toigh leat PGP ion-loidhne a chleachdadh a ghnà th fhathast, ’s urrainn dhut seo a dhèanamh ann an “Roghainnean nan cunntasan†fo “Tèarainteachd OpenPGPâ€.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=A’ ruith Enigmail tionndadh %S
enigmailPepVersion=Enigmail/p≡p tionndadh %S
usingAgent=A’ chleachdadh faidhle so-ghnìomhaichte %1$S %2$S airson crioptachadh is dì-chrioptachadh
agentError=MEARACHD: Cha deach leinn bun-seirbheis Enigmail inntrigeadh!
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Mearachd le inntrigeadh seirbheis Enigmail
onlyGPG=Chan obraich gintinn iuchraichean ach le GnuPG (chan obraich e le PGP)!
keygenComplete=Tha na h-iuchraichean air an gintinn! Thèid an dearbh-aithne <%S> a chleachdadh airson soidhneadh.
revokeCertRecommended=Mholamaid gun cruthaich thu teisteanas cùl-ghairm dhen iuchair agad. ’S urrainn dhut an teisteanas a chleachdadh gus an iuchair agad a dhèanamh mì-dhligheach, m.e. ma thèid an iuchair phrìobhaideach agad air a call no briseadh a-steach oirre. A bheil thu airson teisteanas cùl-ghairm a chruthachadh an-drà sta?
keyMan.button.generateCert=&Gin teisteanas
genCompleteNoSign=Tha gintinn nan iuchraichean coileanta!
genGoing=Tha iuchraichean ’gan gintinn mar-thà !
passNoMatch=Chan eil an dà abairt-fhaire co-ionnann; cuir a-steach a-rithist iad
passCheckBox=Cuir cromag sa bhogsa mur eil thu ag iarraidh abairt-fhaire airson na h-iuchrach
passUserName=Sònraich ainm cleachdaiche airson na dearbh-aithne seo
keygen.missingUserName=Cha deach ainm a shònrachadh airson a’ chunntais/na h-aithne a thagh thu. Cuir a-steach luach san raon “D’ ainm†ann an roghainnean a’ chunntais.
keygen.passCharProblem=Chleachd thu caractaran sònraichte san abairt-fhaire agad. Gu mì-fhortanach, dh’fhaoidte gun adhbharaich seo trioblaid airson aplacaidean eile. Mholamaid gun tagh thu abairt-fhaire anns nach eil ach na caractaran seo:\na-z A-Z 0-9 /.;:-,!?(){}[]%*
passSpaceProblem=Air adhbharan teicnigeach, chan fhaod an abairt-fhaire agad tòiseachadh no crìochnachadh le beà rn.
changePassFailed=Dh’fhà illig le atharrachadh na h-abairt-fhaire.
keyConfirm=A bheil thu airson iuchraichean poblach is prìobhaideach a ghintinn airson “%S�
keyMan.button.generateKey=&Gin iuchair
keyAbort=A bheil thu airson sgur de ghintinn nan iuchair?
keyMan.button.generateKeyAbort=&Sguir de ghintinn nan iuchair
keyMan.button.generateKeyContinue=&Lean air adhart le gintinn nan iuchair
expiryTooLong=Chan urrainn dhut iuchair a chruthachadh a dh’fhalbhas an ùine air an ceann corr is 100 bliadhna.
expiryTooLongShorter=Chan urrainn dhut iuchair a chruthachadh a dh’fhalbhas an ùine air an ceann corr is 90 bliadhna.
expiryTooShort=Feumaidh an iuchair agad a bhith dligheach fad latha air a char as lugha.
keyGenFailed=Dh’fhà illig le gintinn nan iuchraichean. Thoir sùil air consoil Enigmail (clà r-taice “Enigmail†> “Dì-bhugachadh Enigmailâ€) airson barrachd fiosrachaidh.
setKeyExpirationDateFailed=Cha b’ urrainn dhuinn a’ chrìoch ùine atharrachadh
# Strings in enigmailMessengerOverlay.js
securityInfo=Fiosrachadh tèarainteachd Enigmail\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Cha deach na ceanglachain aig an teachdaireachd seo a shoidhneadh no a chrioptachadh*\r\n\r\n
possiblyPgpMime=Teachdaireachd air a crioptachadh no soidhneadh le PGP/MIME ’s dòcha; cleachd an gleus “Dì-chrioptaich/Dearbhaich†gus a dhearbhadh
saveAttachmentHeader=Enigmail: Sà bhail ceanglachan air a dhì-chrioptachadh
noTempDir=Cha deach leinn pasgan sealach a lorg gus sgrìobhadh ann\nFeuch an suidhich thu an caochladair à rainneachd TEMP
attachmentPgpKey=’S e faidhle iuchrach OpenPGP a tha sa cheanglachan “%S†a tha thu a’ fosgladh a-rèir coltais.\n\nBriog air “Ion-phortaich†gus na h-iuchraichean ’na bhroinn ion-phortadh no air “Seall†gus susbaint an fhaidhle a shealltainn ann an uinneag brabhsair
beginPgpPart=***** *TOISEACH NA PÀIRT CRIOPTAICHTE no AIR A SOIDHNEADH* *****
endPgpPart=***** *DEIREADH NA PÀIRT CHRIOPTAICHTE no AIR A SOIDHNEADH* *****
notePartEncrypted=Enigmail: *CHA DEACH a h-uile pà irt dhen teachdaireachd a shoidhneadh no a chrioptachadh*
noteCutMessage=Enigmail: *Chaidh iomadh bloca teachdaireachd a lorg – chaidh sgur dhen dì-chrioptachadh/dearbhadh*
decryptOkNoSig=Rabhadh\n\nShoirbhich leis an dì-chrioptachadh ach cha b’ urrainn dhuinn an soidhneadh a dhearbhadh mar bu chòir
msgOvl.button.contAnyway=Lean air adhart &co-dhiù
signature.verifiedOK=Chaidh an soidhneadh airson a’ cheanglachain %S a dhearbhadh
signature.verifyFailed=Cha deach leinn an soidhneadh airson a’ cheanglachain %S a dhearbhadh
attachment.noMatchToSignature=Cha deach leinn an ceanglachan “%S†a mhaidseadh ri faidhle soidhnidh
attachment.noMatchFromSignature=Cha deach leinn am faidhle soidhnidh “%S†a mhaidseadh ri ceanglachan
fixBrokenExchangeMsg.failed=Cha deach leinn an teachdaireachd a chà radh.
enigmail.msgViewColumn.label=Enigmail
enigmailPep.msgViewColumn.label=Enigmail/p≡p
wksNoIdentity=Cha deach an iuchair seo ceangal ri gin dhe na cunntasan puist-d agad. Cuir cunntas ris airson co-dhiù aon dhe na seòlaidhean puist-d seo:\n\n%S
wksConfirmSuccess=Chaidh post-d dearbhaidh a chur.
wksConfirmFailure=Dh’fhà illig le cur a’ phuist-d dearbhaidh.
autocrypt.importSetupKey.accountPreconfigured=Chaidh an cunntas agad a rèiteachadh mar bu chòir airson Autocrypt mar-thà .\n\nA bheil thu cinnteach gu bheil thu airson tar-sgrìobhadh air na roghainnean agad leis an teachdaireachd suidheachaidh seo?
autocrypt.importSetupKey.selfCreated=Chaidh an teachdaireachd seo a chruthachadh leis an tionndadh dhe Enigmail a tha ’ga ruith an-drà sta.\n\nGearr leum gun chliant puist-d a tha thu airson na roghainnean a thar-aiseag thuige agus briog air an teachdaireachd sa chliant puist-d ud gus na roghainnean ion-phortadh.
autocrypt.importSetupKey.invalidMessage=Mearachd – cha b’ urrainn dhuinn an teachdaireachd suidheachaidh a leughadh. Tha coltas gu bheil an teachdaireachd coirbte. Feuch an cruthaich thu teachdaireachd suidheachaidh ùr air an uidheam eile agad.
autocrypt.importSetupKey.invalidKey=Mearachd – cha b’ urrainn dhuinn an iuchair ion-phortadh. Cha chuir an tionndadh agad dhe GnuPG taic ris an iuchair air neo tha i coirbte.
autocrypt.importSetupKey.wrongPasswd=Chan eil am facal-faire a chuir thu a-steach mar bu chòir. A bheil thu airson feuchainn ris a-rithist?
autocrypt.importSetupKey.success=Tha teachdaireachd suidheachadh Autocrypt air a pròiseasadh. Tha Autocrypt ri fhaighinn airson a’ chunntais “%S†agad a-nis.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Tagh iuchraichean OpenPGP gus an chur ris
keysToUse=Tagh iuchair/iuchraichean OpenPGP gus an cleachdadh airson %S
pubKey=An iuchair phoblach airson %S\n
windowLocked=Tha an uinneag sgrìobhaidh glaiste; chaidh sgur dhen chur
sendUnencrypted=Dh’fhà illig le tòiseachadh Enigmail.\nA bheil thu airson an teachdaireachd a chur gun chrioptachadh?
composeSpecifyEmail=Sònraich am prìomh sheòladh puist-d agad a chleachdas sinn gus iuchair an t-soidhnidh a thaghadh airson teachdaireachdan a-mach.\nMa dh’fhà gas tu bà n e, thèid an seòladh O aig an teachdaireachd a chleachdadh gus iuchair an t-soidhnidh a thaghadh.
sendingHiddenRcpt=Tha faightearan BCC (lethbhreac dall) aig an teachdaireachd seo. Ma thèid an teachdaireachd seo a chrioptachadh, gabhaidh na faightearan BCC fhalach ach chan urrainn do chuid a bhathair-bhog (can PGP Corp.) a chleachdas faightear ma dh’fhaoidte an teachdaireachd a dhì-chrioptachadh. Air sà illeibh seo, mholamaid gun seachnaich thu puist-d BCC le crioptachadh.
sendWithHiddenBcc=Falaich na faightearan BCC
sendWithShownBcc=Crioptaich gu h-Ã bhaisteach
sendingNews=Chaidh sgur dhen chur chrioptaichte.\n\nChan urrainn dhuinn an teachdaireachd seo a chrioptachadh on a tha faightearan buidhinn-naidheachdan innte. Feuch an cuir thu an teachdaireachd a-rithist gun chrioptachadh.
sendToNewsWarning=Rabhadh: tha thu gu bhith a’ cur post-d crioptaichte gu buidheann-naidheachdan.\n\nCha mholamaid seo air sgà th ’s nach eil e gu ciall sam bith ach mas urrainn dhan a h-uile ball dhen bhuidheann-naidheachdan an teachdaireachd a dhì-chrioptachadh, ’s e seo gum feum thu an teachdaireachd a chrioptachadh le iuchraichean gach buill. Na cuir an teachdaireachd seo ach ma tha thu là n-eòlach air na tha thu a’ dèanamh.\n\nA bheil thu airson leantainn air adhart?
hasHTML=Rabhadh post HTML:\nTha HTML am broinn na teachdaireachd seo ma dh’fhaoidte agus b’ urrainn seo adhbharachadh nach dèid leis an t-soidhneadh/a’ chrioptachadh. Gus seo a sheachnadh san à m ri teachd, cum an iuchair SHIFT sìos fhad ’s a bhios tu a’ briogadh air a’ phutan Sgrìobh/Freagair gus post air a shoidhneadh a chur.\nMa nì thu soidhneadh a’ phuist a ghnà th, bu chòir dhut a’ chromag a thoirt far bogsa na roghainn “Sgrìobh teachdaireachdan ann an cruth HTML†gus post HTML a chur à comas gu buan airson a’ chunntais puist seo.
strippingHTML=Tha fiosrachadh fòrmatadh HTML am broinn na teachdaireachd seo a thèid air chall nuair a thèid iompachadh gu teacsa lom airson an t-soidhnidh/a’ chrioptachaidh. A bheil thu airson leantainn air adhart?
msgCompose.button.sendAnyway=&Cuir an teachdaireachd co-dhiù
attachWarning=Chan eil na ceanglachain aig an teachdaireachd seo ionadail, mar sin cha ghabh an crioptachadh. Gus na ceanglachain a chrioptachadh, glèidh iad ’nam faidhlichean ionadail an toiseach agus cuir na faidhlichean ris ’nan ceanglachan an uairsin. A bheil thu airson an teachdaireachd a chur co-dhiù?
quotedPrintableWarn=Chuir thu còdachadh “quoted-printable†an comas airson cur nan teachdaireachdan. Faodaidh seo dì-chrioptachadh/dearbhadh cearr adhbharachadh airson na teachdaireachd agad.\nA bheil thu airson cur theachdaireachdan “quoted-printable†a chur à comas a-nis?
minimalLineWrapping=Shuidhich thu pasgadh nan loidhnichean air %S caractar. Airson crioptachadh/soidhneadh mar bu chòir, feumaidh an luach seo a bhith 68 no nas motha.\nA bheil thu airson pasgadh nan loidhnichean atharrachadh gu 68 caractar a-nis?
warning=Rabhadh
signIconClicked=Dh’atharraich thu an soidhneadh a là imh. Mar sin, fad ’s a bhios tu a’ sgrìobhadh na teachdaireachd seo, cha bhi cur an/à comas an t-soidhnidh an eisimeil air cur an/à comas a’ chrioptachaidh tuilleadh.
errorOwnKeyUnusable=Cha lìbhrig ID na h-iuchrach “%S†a chaidh a rèiteachadh airson na h-aithne là ithrich iuchair OpenPGP a ghabhas cleachdadh.\n\nDèan cinnteach gu bheil iuchair OpenPGP dhligheach agad nach do dh’fhalbh an ùine oirre agus gun tomh roghainnean a’ chunntais agad ris an iuchair sin.\nMur an do dh’fhalbh an ùine air an iuchair agad, dearbhaich gun do shuidhich thu earbsa an t-seilbheadair air “earbsach†no “cho earbsach ’s a ghabhasâ€.
msgCompose.cannotSaveDraft=Mearachd le sà bhaladh an dreachd
msgCompose.partiallyEncrypted.short=Thoir an aire nach foillsich thu fiosrachadh dìomhair gun fhiosta – chan eil ach pà irt dhen phost-d seo crioptaichte.
msgCompose.partiallyEncrypted.mimeMsg=Chaidh cuid dhen teachdaireachd seo a tha thu a’ freagairt rithe a chrioptachadh is tha cuid eile gun chrioptachadh. Tha cuid chrioptaichte aice nach fhaic thu.\n\nMura deach leis an t-seòladair a chuir thugad i a’ chuid chrioptaichte a dhì-chrioptachadh, dh’fhaoidte gun nochd thu fiosrachadh dìomhair do dhaoine nach deach leis an t-seòladair sin fhèin a dhì-chrioptachadh.\n\nMholamaid nach cuir thu freagairt dhan teachdaireachd seo ach gun cruthaich thu teachdaireachd ùr airson na freagairte agad.
msgCompose.partiallyEncrypted.inlinePGP=Chaidh cuid dhen teachdaireachd seo a tha thu a’ freagairt rithe a chrioptachadh is tha cuid eile gun chrioptachadh. Mura deach leis an t-seòladair a chuir thugad i a’ chuid chrioptaichte a dhì-chrioptachadh, dh’fhaoidte gun nochd thu fiosrachadh dìomhair dha nach deach leis an t-seòladair sin fhèin a dhì-chrioptachadh.\n\nSaoil an doir thu air falbh gach iomradh teacsa on fhreagairt agad dhan t-seòladair sin?
msgCompose.internalEncryptionError=Mearachd taobh a-staigh: Chaidh an crioptachadh geallta a chur à comas
msgCompose.internalError=Thachair mearachd taobh a-staigh.
msgCompose.toolbarTxt.signAndEncrypt=Thèid an teachdaireachd seo a shoidhneadh agus a chrioptachadh
msgCompose.toolbarTxt.signOnly=Thèid an teachdaireachd seo a shoidhneadh
msgCompose.toolbarTxt.encryptOnly=Thèid an teachdaireachd seo a chrioptachadh
msgCompose.toolbarTxt.noEncryption=Cha dèid an teachdaireachd seo a shoidhneadh no a chrioptachadh
msgCompose.toolbarTxt.disabled=Chaidh Enigmail a chur à comas airson na dearbh-aithne a thagh thu
msgCompose.protectSubject.tooltip=Dìon cuspair na teachdaireachd
msgCompose.noSubjectProtection.tooltip=Na dìon cuspair na teachdaireachd
msgCompose.encryptedSubjectStub=Teachdaireachd chrioptaichte
msgCompose.protectSubject.dialogTitle=A bheil thu airson dìon nan cuspairean a chur an coma?
msgCompose.protectSubject.question=Chan fhalaich teachdaireachdan crioptaichte à bhaisteach an cuspair.\n\nStèidhich sinn stannard a dh’fhalaicheas an cuspair tùsail san teachdaireachd chrioptaichte ’s a chuireas teacsa fuadain ’na à ite gus nach faicear an cuspair mus deach am post-d a dhì-chrioptachadh.\n\nA bheil thu airson cuspairean nan teachdaireachdan crioptaichte a dhìon?
msgCompose.protectSubject.yesButton=&Dìon an cuspair
msgCompose.protectSubject.noButton=&Na dìon an cuspair
msgCompose.detailsButton.label=Mion-fhiosrachadh…
msgCompose.detailsButton.accessKey=f
msgCompose.pepSendUnknown=Chan eil fhios
msgCompose.pepSendUnsecure=Neo-thèarainte
msgCompose.pepSendSecure=Tèarainte
msgCompose.pepSendTrusted=Tèarainte ⊠earbsach
pep.alert.disabledForIdentity=Tha p≡p à comas airson na dearbh-aithne là ithrich. Cuir an comas p≡p ann an roghainnean Enigmail/p≡p.
pep.alert.weakReply=Tha thu an impis freagairt do theachdaireachd thèarainte a chur no a sìneadh air adhart mar theachdaireachd nach eil tèarainte tuilleadh. Ma leanas tu air adhart, dh’fhaoidte gun dèid fiosrachadh cugallach fhoillseachadh a chuireas tu fhèin agus an co-sgrìobhaiche agad fo chunnart. A bheil thu cinnteach gu bheil thu airson leantainn air adhart?
# note: should end with double newline:
sendAborted=Chaidh sgur dhen chur.\n\n
# details:
keyNotTrusted=Chan eil earbsa gu leòr san iuchair “%Sâ€
keyNotFound=Cha deach an iuchair “%S†a lorg
keyRevoked=Chaidh an iuchair “%S†a chùl-ghairm
keyExpired=Dh’fhalbh an ùine air an iuchair “%Sâ€
statPGPMIME=PGP/MIME
statSMIME=S/MIME
statSigned=AIR A SHOIDHNEADH
statEncrypted=CRIOPTAICHTE
statPlain=GUN SOIDHNEADH no CRIOPTACHADH
offlineSave=A bheil thu airson an teachdaireachd %1$S a shà bhaladh gu %2$S ann am pasgan nan teachdaireachdan nach deach a chur?
onlineSend=A bheil thu airson an teachdaireachd %1$S a chur gu %2$S?
encryptKeysNote=An aire: Tha an teachdaireachd ’ga crioptachadh le IDan/iuchraichean a’ chleachdaiche seo: %S
hiddenKey=
signFailed=Mearachd le Enigmail; dh’fhà illig leis a’ chrioptachadh/an t-soidhnidh; an cuir sinn an teachdaireachd gun chrioptachadh?
msgCompose.button.sendUnencrypted=&Cuir an teachdaireachd gun chrioptachadh
recipientsSelectionHdr=Tagh na faightearan airson a’ chrioptachaidh
configureNow=Cha do rèitich thu tèarainteachd Enigmail airson na dearbh-aithne a thagh thu fhathast. A bheil thu airson seo a dhèanamh a-nis?
# encryption/signing status and associated reasons:
encryptMessageAuto=Crioptaich an teachdaireachd (fèin-obrachail)
encryptMessageNorm=Crioptaich an teachdaireachd
signMessageAuto=Soidhnich an teachdaireachd (fèin-obrachail)
signMessageNorm=Soidhnich an teachdaireachd
encryptOff=Crioptachadh: DHETH
encryptOnWithReason=Crioptachadh: AIR (%S)
encryptOffWithReason=Crioptachadh: DHETH (%S)
encryptOn=Crioptachadh: AIR
signOn=Soidhneadh: AIR
signOff=Soidhneadh: DHETH
signOnWithReason=Soidhneadh: AIR (%S)
signOffWithReason=Soidhneadh: DHETH (%S)
reasonEnabledByDefault=an comas a ghnà th
reasonManuallyForced=air a sparradh a là imh
reasonByRecipientRules=air a sparradh le riaghailtean an fhaighteir
reasonByAutoEncryption=air a sparradh leis a’ chrioptachadh fhèin-obrachail
reasonByConflict=ri linn còmhstri ann an riaghailtean an fhaighteir
reasonByEncryptionMode=ri linn modh a’ chrioptachaidh
# should not be used anymore:
encryptYes=Thèid an teachdaireachd a chrioptachadh
encryptNo=Cha dèid an teachdaireachd a chrioptachadh
# should not be used anymore:
signYes=Thèid an teachdaireachd a shoidhneadh
signNo=Cha dèid an teachdaireachd a shoidhneadh
# PGP/MIME status:
pgpmimeNormal=Pròtacal: PGP/MIME
inlinePGPNormal=Pròtacal: PGP ion-loidhne
smimeNormal=Pròtacal: S/MIME
pgpmimeAuto=Pròtacal: PGP/MIME (fèin-obrachail)
inlinePGPAuto=Pròtacal: PGP ion-loidhne (fèin-obrachail)
smimeAuto=Pròtacal: S/MIME (fèin-obrachail)
# should not be used anymore
pgpmimeYes=Thèid PGP/MIME a chleachdadh
pgpmimeNo=Thèid PGP ion-loidhne a chleachdadh
# Attach own key status (tooltip strings):
attachOwnKeyNo=Cha dèid an iuchair agad fhèin a chur ris
attachOwnKeyYes=Thèid an iuchair agad fhèin a chur ris
attachOwnKeyDisabled=Chan urrainn dhuinn an iuchair agad fhèin a chur ris mar cheanglachan. Feumaidh tu iuchair shònraichte a thaghadh\nann an earrann OpenPGP aig “Roghainnean nan cunntasan†gus an gleus seo a chur an comas.
rulesConflict=Mhothaich sinn do chòmhstri ann an riaghailtean a-rèir faighteir\n%S\n\nA bheil thu airson an teachdaireachd a chur leis na roghainnean seo?
msgCompose.button.configure=&Rèitich
msgCompose.button.send=&Cuir an teachdaireachd
msgCompose.button.save=&SÃ bhail an teachdaireachd
# Strings in enigmailMsgHdrViewOverlay.js
keyNeeded=Tha feum air an iuchair phoblach %S gus an soidhneadh a dhearbhadh
keyUsed=An iuchair phoblach %S a chaidh a chleachdadh gus an soidhneadh a dhearbhadh
clickDecrypt=; cleachd an gleus “Dì-chrioptaich/Dearbhaichâ€
clickDecryptRetry=; cleachd an gleus “Dì-chrioptaich/Dearbhaich†gus feuchainn ris a-rithist
clickDetailsButton=; briog air a’ phutan “Mion-fhiosrachadh†airson barrachd fiosrachaidh
clickImportButton=; briog air a’ phutan “Ion-phortaich iuchair†gus an iuchair ion-phortadh
keyTypeUnsupported=; cha chuir an tionndadh agad de GhnuPG taic ris an seòrsa iuchrach seo
msgPart=PÃ irt dhen teachdaireachd %S
msgSigned=air a soidhneadh
msgSignedUnkownKey=air a shoidhneadh le iuchair nach aithne dhuinn
msgEncrypted=air a crioptachadh
msgSignedAndEnc=air a soidhneadh is crioptachadh
unverifiedSig=Soidhneadh gun dearbhadh
incompleteDecrypt=Chan eil an dì-chrioptachadh coileanta
needKey=Mearachd - cha deach iuchair phrìobhaideach fhreagarrach a lorg gus an teachdaireachd a dhì-chrioptachadh
failedDecrypt=Mearachd - dh’fhà illig leis an dì-chrioptachadh
badPhrase=Mearachd - droch abairt-fhaire
failedDecryptVerify=Mearachd - dh’fhà illig leis an dì-chrioptachadh/dearbhadh
viewInfo=; Sealladh > Tèarainteachd na teachdaireachd airson barrachd fiosrachaidh
decryptedMsg=Teachdaireachd air a dì-chrioptachadh
decryptedMsgWithFormatError=Teachdaireachd air a dì-chrioptachadh (chaidh fòrmat puist-d PGP briste aiseag a dh’adhbharaich seann fhrithealaiche Exchange ma dh’fhaoidte, mar sin chan eil sinn an dùil gum bi an toradh foirfe ri leughadh)
usedAlgorithms=Algairimean ’gan cleachdadh: %1$S agus %2$S
pepStatusInfo.text=Staid teachdaireachd p≡p.
pepStatusInfo.title.m3=Fo ionnsaigh
pepStatusInfo.info.m3=Chan eil an teachdaireachd seo tèarainte agus bhean cuideigin rithe.
pepStatusInfo.title.m1=Amharasach
pepStatusInfo.info.m1=Tha co-sgrìobhaiche aig an teachdaireachd seo a chaidh a chomharrachadh mar fhear amharasach roimhe
pepStatusInfo.title.r0=Chan eil fhios
pepStatusInfo.info.r0=Chan eil fiosrachadh gu leòr san teachdaireachd seo airson measadh a bheil i tèarainte gus nach eil.
pepStatusInfo.title.r1=Chan urrainn dhuinn a dì-chrioptachadh
pepStatusInfo.info.r1=Cha ghabh an teachdaireachd seo a dhì-chrioptachadh air sgà th ’s nach eil an iuchair ri là imh.
pepStatusInfo.title.r2=Chan urrainn dhuinn a dì-chrioptachadh
pepStatusInfo.info.r2=Cha ghabh an teachdaireachd seo a dhì-chrioptachadh air sgà th ’s nach eil an iuchair ri là imh.
pepStatusInfo.title.r3=Neo-thèarainte
pepStatusInfo.info.r3=Chan eil an teachdaireachd seo tèarainte.
pepStatusInfo.title.r4=Neo-thèarainte do chuid
pepStatusInfo.info.r4=Chan eil an teachdaireachd seo tèarainte do gach co-sgrìobhaiche.
pepStatusInfo.title.r5=Tèarainteachd neo-earbsach
pepStatusInfo.info.r5=Chan eil dìon na teachdaireachd seo earbsach.
pepStatusInfo.title.r6=Tèarainte…
pepStatusInfo.info.r6=Tha an teachdaireachd seo tèarainte ach geumaidh tu aithne a’ cho-sgrìobhaiche agad a dhearbhadh fhathast.
pepStatusInfo.title.r7=Tèarainte ⊠earbsach
pepStatusInfo.info.r7=Tha an teachdaireachd seo tèarainte ’s earbsach.
pepStatusInfo.color.green=Uaine
pepStatusInfo.color.yellow=Buidhe
pepStatusInfo.color.red=Dearg
pepRevokeTrust.question=A bheil thu cinnteach nach eil thu airson earbsa a chur ann an %S tuilleadh?
pepRevokeMistrust.question=A bheil thu airson earbsa a chur san iuchair airson %S a-rithist?
pepRevokeTrust.doRevoke=Cuir crìoch air an &earbsa
wksConfirmationReq=Iarrtas air dearbhadh eòlaire Web Key
wksConfirmationReq.message=Chaidh an teachdaireachd seo a chur leis an t-solaraiche puist-d agad a dhearbhadh gun deach an iuchair phoblach OpenPGP agad a luchdadh suas\ngun eòlaire Web Key aca.\nMa dh’fhoillsicheas tu an iuchair phoblach agad, bidh e nas fhasa do chà ch an iuchair agad a lorg agus teachdaireachdan crioptaichte a chur thugad.\n\nMa tha thu airson an iuchair agad fhoillseachadh san eòlaire Web Key an-rà sta, briog air a’ phutan “Dearbhaich an t-iarrtas†air a’ bhà r-inbhe.\nMur eil, leig seachad an teachdaireachd seo.
wksConfirmationReq.button.label=Dearbhaich an t-iarrtas
autocryptSetupReq=Dèan suidheachadh Autocrypt
autocryptSetupReq.button.label=Tòisich air an rèiteachadh
autocryptSetupReq.setupMsg.desc=Tha am fiosrachadh uile san teachdaireachd seo gus na roghainnean Autocrypt is an iuchair phrìobhaideach agad a thar-aiseag on uidheam tùsail agad gu tèarainte.
autocryptSetupReq.setupMsg.backup=’S urrainn dhut an teachdaireachd seo a chumail ’na lethbhreac-glèidhidh dhen iuchair phrìobhaideach agad. Ma tha thu airson sin a dhèanamh, bu chòir dhut am facal-faire a sgrìobhadh air pìos pà ipeir agus a ghlèidheadh gu tèarainte.
autocryptSetupReq.message.import=Gus na roghainnean is iuchraichean ion-phortadh gu Enigmail, briog air a’ phutan “Tòisich air an rèiteachadh†air a' bhà r-inbhe.
autocryptSetupReq.message.sent=Briog air an teachdaireachd air an uidheam ùr agad agus lean ris an stiùireadh gus na roghainnean ion-phortadh.
# strings in pref-enigmail.js
oldGpgVersion20=Cha deach leinn Enigmail a thòiseachadh.\n\nTha thu a’ cleachdadh GnuPG tionndadh %1$S ris nach cuir sinn taic tuilleadh. Feumaidh Enigmail GnuPG tionndadh %2$S no nas ùire. Chan obraich Enigmail gus an à rdaich thu an stà ladh dhe GnuPG agad.
locateGpg=Lorg prògram GnuPG
invalidGpgPath=Cha ghabh GnuPG a ruith leis an t-slighe a chaidh a shònrachadh. Chaidh Enigmail a chur à comas gus an atharraich thu an t-slighe gu GnuPG a-rithist no gus an tòisich thu an aplacaid às ùr.
warningsAreReset=Chaidh gach rabhadh ath-shuidheachadh.
prefs.gpgFound=Chaidh GnuPG a lorg an-seo: %S
prefs.gpgNotFound=Cha deach GnuPG a lorg
prefs.warnAskNever=Rabhadh: ma chuireas tu an roghainn seo an comas, bidh teachdaireachdan gun chrioptachadh agad gun fhiosrachadh a bharrachd sam bith mur eil iuchair airson aon dhe na faightearan ann -- chan innis Enigmail dhut nuair a thachras seo!
prefs.warnIdleTimeForUnknownAgent=Chan urrainn dhuinn ceangal ri gpg-agent. ’S dòcha gun cleachd an siostam agad inneal sònraichte gus abairtean-faire a là imhseachadh (m.e. gnome-keyring, seahorse-agent, KDE wallet manager, …). Gu mì-fhortanach, chan eil smachd aig Enigmail air nuair a dh’fhalbhas an ùine air abairt-fhaire airson an inneal a tha thu a’ chleachdadh. Mar sin, thèid roghainnean falbh na h-ùine aig Enigmail a leigeil seachad.
prefEnigmail.oneKeyserverOnly=Mearachd - chan urrainn dhut barrachd air aon fhrithealaiche iuchraichean a shònrachadh airson luchdadh a-nuas fèin-obrachail nan iuchraichean OpenPGP a tha a dhìth.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Cuir a-steach PIN an RIANAIRE airson a’ SmartCard agad
enterCardPin=Cuir a-steach PIN a’ SmartCard agad
notInit=Mearachd - chan eil seirbheis Enigmail air a tòiseachadh fhathast
badCommand=Mearachd - dh’fhà illig le à ithne crioptachaidh
cmdLine=loidhne-à ithne is à s-chur:
notRequired=Mearachd - chan eil crioptachadh riatanach
notComplete=Mearachd - chan eil gintinn na h-iuchrach deiseil fhathast
invalidEmail=Mearachd - seòladh no seòlaidhean puist-d mì-dhligheach
noPassphrase=Mearachd - cha deach abairt-fhaire a sholar
noPGPblock=Mearachd - cha deach bloca dà ta OpenPGP armaichte dligheach a lorg
unverifiedReply=Tha amharas oirnn gun deach pà irt dhen teachdaireachd a tha eagaichte (an fhreagairt) atharrachadh
keyInMessageBody=Lorg sinn iuchair ann am bodhaig na teachdaireachd. Briog air “Ion-phortaich iuchair†gus an iuchair ion-phortadh
sigMismatch=Mearachd - soidhneadh neo-ionnann
cantImport=Mearachd le ion-phortadh na h-iuchrach poblaich\n\n
doImportOne=A bheil thu airson %1$S (%2$S) ion-phortadh?
doImportMultiple=A bheil thu airson na h-iuchraichean seo ion-phortadh?\n\n%S
previewFailed=Chan urrainn dhuinn faidhle nan iuchraichean poblach a leughadh.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=Cha ghabh an SmartCard %1$S a lorg sinn san inneal-leughaidh agad cleachdadh gus an teachdaireachd seo a phròiseasadh.\nCuir a-steach an SmartCard %2$S agad is feuch ris a-rithist.
sc.insertCard=Tha an t-obrachadh feumach air a’ SmartCard %S agad.\nCuir a-steach an SmartCard a tha a dhìth is feuch ris a-rithist.
sc.removeCard=Tha an t-obrachadh ag iarraidh nach eil SmartCard san inneal-leughaidh agad.\nThoir air falbh an SmartCard agad is feuch ris a-rithist.
sc.noCardAvailable=Cha deach SmartCard a lorg san inneal-leughaidh agad.\nCuir a-steach an SmartCard agad is feuch ris a-rithist.
sc.noReaderAvailable=Cha b’ urrainn dhuinn an t-inneal-leughaidh SmartCard agad inntrigeadh\nCeangail an t-inneal-leughaidh SmartCard agad, cuir a-steach a’ chairt agad agus feuch ris a-rithist.
keyError.keySpecNotFound=Cha do lorg sinn iuchair air an dul-iuchrach agad a fhreagras ris an t-seòladh puist-d “%Sâ€.
keyError.keyIdNotFound=Cha do lorg sinn ID na h-iuchrach “%S†rèitichte air an dul-iuchrach agad.
keyError.resolutionAction=Tagh iuchair dhligheach ann an earrann OpenPGP dhe “Roghainnean nan cunntasanâ€.
missingPassphrase=Tha abairt-fhaire a dhìth
errorHandling.gpgAgentInvalid=Tha an siostam agad a’ ruith tionndadh dhe gpg-agent nach eil iomchaidh airson an tionndaidh agad dhe GnuPG.
errorHandling.gpgAgentError=Dh’aithris GnuPG mearachd sa chonaltradh le gpg-agent (seo co-phà irt dhe GnuPG).
errorHandling.dirmngrError=Dh’aithris GnuPG mearachd sa chonaltradh le dirmngr (seo co-phà irt dhe GnuPG).
errorHandling.pinentryError=Chan urrainn dha GnuPG an abairt-fhaire agad iarraidh le pinentry.
errorHandling.readFaq=Seo mearachd le suidheachadh no rèiteachadh an t-siostaim nach leig le Enigmail obair mar bu chòir ’s a ghabh a cà radh gu fèin-obrachail.\n\nDian-mholamaid gun doir thu sùil air an là rach-lìn taice againn air https://enigmail.net/faq.
gpgNotFound=Cha deach am prògram GnuPG “%S†a lorg.\nDèan cinnteach gun do shònraich thu slighe an fhaidhle sho-ghnìomhaichte GnuPG mar bu chòir ann an roghainnean Enigmail.
gpgNotInPath=Cha deach prògram GnuPG a lorg am broinn PATH.\nDèan cinnteach gun do shònraich thu slighe an fhaidhle sho-ghnìomhaichte GnuPG mar bu chòir ann an roghainnean Enigmail.
enigmailNotAvailable=Chan eil bun-seirbheis Enigmail ri fhaighinn
prefGood=Deagh shoidhneadh o %S
prefBad=DROCH shoidhneadh o %S
failCancel=Mearachd - chaidh sgur de dh’fhaighinn na h-iuchrach leis a’ chleachdaiche
failNoServer=Mearachd - Cha deach frithealaiche iuchraichean a shònrachadh gus iuchair fhaighinn uaithe
failNoID=Mearachd - Cha deach ID na h-iuchrach a shònrachadh gus iuchair fhaighinn air a son
failKeyExtract=Mearachd - Dh’fhà illig le à ithne à s-tharraing na h-iuchrach
notFirstBlock=Mearachd - Chan eil a’ chiad bhloca OpenPGP ’na bhloca iuchrach poblaich
importKeyConfirm=A bheil thu airson an iuchair/na h-iuchraichean a tha leabaichte san teachdaireachd ion-phortadh?
failKeyImport=Mearachd - Dh’fhà illig le ion-phortachadh iuchrach
fileWriteFailed=Cha deach leinn sgrìobhadh gun fhaidhle %S
importKey=Ion-phortaich an iuchair phoblach %S on fhrithealaiche iuchraichean:
uploadKey=Cuir an iuchair phoblach %S gun fhrithealaiche iuchraichean:
keyId=ID na h-iuchrach
keyAndSigDate=ID na h-iuchrach: 0x%1$S / Chaidh a soidhneadh: %2$S
keyFpr=Lorg-mheòir na h-iuchrach: %S
noEmailProvided=Tha dug thu seòladh puist-d seachad!
keyAlreadySigned=Chaidh an iuchair a shoidhneadh mar-thà , chan urrainn dhut a soidhneadh dà thuras.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=dh’fhalbh an ùine air %S
createdHeader=Air a chruthachadh
atLeastOneKey=Cha deach iuchair a thaghadh! Feumaidh tu iuchair no dhà a thaghadh airson gabhail ris a’ chòmhradh seo
fewerKeysThanRecipients=Thagh thu uiread nas lugha de dh’iuchraichean na tha faightearan ris. A bheil thu cinnteach gu bheil liosta nan iuchraichean crioptachaidh coileanta?
userSel.button.goBack=Tagh barrachd iuchraichean
userSel.secretKeySel.title=Tagh iuchair OpenPGP phrìobhaideach gus na teachdaireachdan agad a shoidhneadh
userSel.problemNoKey=Gun iuchair dhligheach
userSel.problemMultipleKeys=Iomadh iuchair
# should be same as thunderbird ENTITY sendLaterCmd.label:
sendLaterCmd.label=Cuir uaireigin eile
# Strings used in enigmailAttachmentDialog.js
pgpMimeNote=AN AIRE: Cha chuir gach cliant puist-d taic ri PGP/MIME. Ma tha thu mì-chinnteach, tagh an roghainn “%Sâ€.
first=a’ chiad
second=an dà rna
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Tagh iuchair OpenPGP airson a’ chrioptachaidh
identityName=Dearbh-aithne: %S
switchPepMode=Tha thu a’ cleachdadh a’ “mhodh furasta p≡p†aig Enigmail.\n\nMa chuireas tu an comas OpenPGP no S/MIME airson cunntas, cuiridh tu p≡p à comas agus cleachdaidh tu am modh “à bhaisteach†aig Enigmail às aonais p≡p.
enableEnigmail=&Cuir à comas p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=Ghnìomhaich thu an crioptachadh ach cha do thagh thu iuchair. Feumaidh tu iuchair dhligheach no dhà a shònrachadh o liosta nan iuchraichean gus puist-d a chuireas tu gu %1$S a chrioptachadh. A bheil thu airson an crioptachadh a chur à comas airson %2$S?
noKeyToUse=(gun iuchair - gun chrioptachadh)
noEmptyRule=Chan fhaod an riaghailt a bhith falamh! Suidhich seòladh puist-d ann an raon na riaghailt.
invalidAddress=Chan eil an seòladh/na seòlaidhean puist-d a chuir thu a-steach dligheach. Cha bu chòir dhut ainmean nam faightearan a shònrachadh, na sònraich ach na seòlaidhean puist-d fhèin. M.e.:\nMì-dhligheach: Ainm \nDligheach: ainm@seòladh.net
noCurlyBrackets=Tha ciall sònraichte air na camagan dualach {} agus cha bu chòir dhut an cleachdadh ann an seòladh puist-d. Ma tha thu airson atharrachadh cò ris a fhreagras an riaghailt seo, cleachd an roghainn “Cuir an riaghailt an sà s ma … an fhaightearâ€.\nGheibh thu barrachd fiosrachadh le putan na cobharach.
# Strings used in enigmailRulesEditor.js
never=Chan ann idir
always=An-còmhnaidh
possible=Comasach
deleteRule=A bheil thu airson an riaghailt a thagh thu a sguabadh à s?
nextRcpt=(An ath-fhaightear)
negateRule=Gun a bhith
addKeyToRule=Cuir an iuchair %1$S (%2$S) ris an riaghailt a-rèir faighteir
# Strings used in enigmailSearchKey.js
needOnline=Chan eil an gleus a thagh thu ri fhaighinn sa mhodh far loidhne. Rach air loidhne is feuch ris a-rithist.
protocolNotSupported=Cha chuir sinn taic ris a’ phròtacal “%S://†a thagh thu gus iuchraichean OpenPGP a luchdadh a-nuas.
gpgkeysDisabled=’S dòcha gum b’ fheairrde thu an roghainn “extensions.enigmail.useGpgKeysTool†a chur an comas.
noKeyserverConn=Cha b’ urrainn dhuinn ceangal ri frithealaiche iuchraichean air %S.
keyDownloadFailed=Cha deach leinn an iuchair a luchdadh a-nuas on fhrithealaiche iuchraichean. Seo teachdaireachd na staide:\n%S
internalError=Thachair mearachd taobh a-staigh. Cha b’ urrainn dhuinn na h-iuchraichean a luchdadh a-nuas no an ion-phortadh.
noKeyFound=Tha sinn duilich ach cha deach leinn iuchair a lorg a fhreagras ris na faclan-luirg.
keyDownload.keyUnavailable=Tha sinn duilich ach chan eil an iuchair air a bheil ID %S ri faighinn air an fhrithealaiche iuchraichean. Mar as trice ’s ann nach do luchdaich sealbhadair na h-iuchrach suas gun fhrithealaiche iuchraichean i.\n\nIarr air seòladair na teachdaireachd gun cuir iad an iuchair thugad air a’ post-d.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Cha deach leinn an iuchair a lorg no a luchdadh a-nuas on fhrithealaiche iuchraichean: cha b’ urrainn dhuinn gpgkeys_%S a ghnìomhachadh.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Dh’fhà illig le suidheachadh earbsa an t-seilbheadair
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Dh’fhà illig le soidhneadh na h-iuchrach
alreadySigned.label=An aire: chaidh an iuchair %S a shoidhneadh leis an iuchair phrìobhaideach a thagh thu mar-thà .
alreadySignedexportable.label=An aire: chaidh an iuchair %S a shoidhneadh leis an iuchair phrìobhaideach a thagh thu mar thè a ghabhas à s-phortadh. Chan eil soidhneadh ionadail gu ciall sam bith.
partlySigned.label=An aire: chaidh cuid dhe na IDan cleachdaiche aig an iuchair %S a shoidhneadh leis an iuchair phrìobhaideach a thagh thu mar-thà .
noTrustedOwnKeys=Cha deach iuchair iomchaidh a lorg gus a shoidhneadh! Feumaidh iuchair phrìobhaideach le là n-earbsa innte a bhith agad mus urrainn dhut iuchraichean a shoidhneadh.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=A’ luchdadh nan iuchraichean, fuirich greis…
keyValid.unknown=chan eil fhios
keyValid.invalid=mì-dhligheach
keyValid.disabled=Ã comas
keyValid.revoked=air chùl-ghairm
keyValid.expired=dh’fhalbh an ùine air
keyValid.noSubkey=chan eil fo-iuchair dligheach ann
keyTrust.untrusted=gun earbsa ann
keyTrust.marginal=cugallach
keyTrust.full=earbsach
keyTrust.ultimate=cho earbsach ’s a ghabhas
keyTrust.group=(buidheann)
keyType.public=poblach
keyType.publicAndSec=pobl/prìobh
keyMan.enableKey=Cuir an iuchair an comas
keyMan.disableKey=Cuir an iuchair à comas
userAtt.photo=Buadh a’ chleachdaiche (dealbh JPEG)
asciiArmorFile=Faidhlichean ASCII armaichte (*.asc)
importKeyFile=Ion-phortaich faidhle iuchrach OpenPGP
gnupgFile=Faidhlichean GnuPG
createKeyOK=Chaidh an iuchair agad a ghintinn
saveRevokeCertAs=Cruthaich ⊠sà bhail teisteanas cùl-ghairm
revokeCertOK=Chaidh an teisteanas cùl-ghairm a chruthachadh. ’S urrainn dhut a chleachdadh gus comharrachadh nach eil an iuchair phoblach agad dligheach tuilleadh, can ma bhios tu air an iuchair phrìobhaideach agad a chall.
revokeCertFailed=Cha b’ urrainn dhuinn an teisteanas cùl-ghairm a chruthachadh.
addUidOK=Chaidh ID a’ chleachdaiche a chur ris
addUidFailed=Cha deach leinn ID a’ chleachdaiche a chur ris
noKeySelected=Bu chòir dhut iuchair no dhà a thaghadh gus na thagh thu a dhèanamh
exportToFile=Às-phortaich an iuchair phoblach gu faidhle
exportKeypairToFile=Às-phortaich an iuchair phrìobhaideach is phoblach gu faidhle
exportSecretKey=A bheil thu airson an iuchair phrìobhaideach a ghabhail a-steach san fhaidhle iuchrach OpenPGP air a shà bhaladh?
saveKeysOK=Chaidh na h-iuchraichean a shà bhaladh
saveKeysFailed=Cha deach leinn na h-iuchraichean a shà bhaladh
importKeysFailed=Cha deach leinn na h-iuchraichean ion-phortadh
enableKeyFailed=Dh’fhà illig le cur an/à comas nan iuchraichean
specificPubKeyFilename=%1$S (0x%2$S) pobl
specificPubSecKeyFilename=%1$S (0x%2$S) pobl-priobh
defaultPubKeyFilename=Iuchraichean-poblach-air-as-phortadh
defaultPubSecKeyFilename=Iuchraichean-poblach-is-priobhaideach-air-as-phortadh
noSecretKeys=Cha deach iuchair phrìobhaideach a lorg.\n\nA bheil thu airson an iuchair agad fhèin a ghintinn a-nis?
sendKeysOk=Chaidh an iuchair/na h-iuchraichean a chur
sendKeysFailed=Dh’fhà illig le cur nan iuchraichean
receiveKeysOk=Chaidh an iuchair/na h-iuchraichean ùrachadh
receiveKeysFailed=Dh’fhà illig le luchdadh a-nuas nan iuchraichean
importFromClip=A bheil thu airson iuchair no dhà ion-phortadh on stòr-bhòrd?
importFromUrl=Luchdaich a-nuas iuchair phoblach on URL seo:
copyToClipbrdFailed=Cha b’ urrainn dhuinn lethbhreac dhen iuchair/dhe na h-iuchraichean a chur air an stòr-bhòrd.
copyToClipbrdOK=Chaidh lethbhreac dhen iuchair/dhe na h-iuchraichean a chur air an stòr-bhòrd.
deleteSecretKey=RABHADH: Tha thu gu bhith iuchair phrìobhaideach a sguabadh à s!\nMa sguabas tu à s an iuchair phrìobhaideach agad, chan urrainn dhut teachdaireachd sam bith a chaidh a chrioptachadh air a son a dhì-chrioptachadh agus chan urrainn dhut an iuchair agad a chùl-ghairm tuilleadh.\n\nA bheil thu cinnteach gu bheil thu airson AN DÀ CHUID an iuchair phrìobhaideach is an iuchair phoblach\n“%Sâ€\na sguabadh à s?
deleteMix=RABHADH: Tha thu gu bhith iuchraichean prìobhaideach a sguabadh à s!\nMa sguabas tu às iuchair phrìobhaideach agad, chan urrainn dhut teachdaireachd sam bith a chaidh a chrioptachadh air a son a dhì-chrioptachadh tuilleadh.\n\nA bheil thu cinnteach gu bheil thu airson AN DÀ CHUID na h-iuchraichean prìobhaideach is na h-iuchraichean poblach a sguabadh à s?
deletePubKey=A bheil thu airson an iuchair phoblach\n“%Sâ€\na sguabadh à s?
deleteSelectedPubKey=A bheil thu airson na h-iuchraichean poblach a sguabadh à s?
deleteKeyFailed=Cha b’ urrainn dhuinn an iuchair a sguabadh à s.
revokeKeyQuestion=Tha thu gu bhith an iuchair “%S†a chùl-ghairm.\n\nChan urrainn dhut soidhneadh leis an iuchair seo agus nuair a bhios i air a sgaoileadh, chan urrainn do chà ch soidhneadh leatha tuilleadh. ’S urrainn dhut an iuchair a chleachdadh fhathast gus seann theachdaireachdan a dhì-chrioptachadh.\n\nA bheil thu airson leantainn air adhart?
revokeKeyOk=Chaidh an iuchair a chùl-ghairm. Ma tha an iuchair agad ri fhaighinn air frithealaiche iuchraichean, mholamaid gun luchdaidh thu suas a-rithist i ach am faic cà ch gun deach a cùl-ghairm.
revokeKeyFailed=Cha b’ urrainn dhuinn an iuchair a chùl-ghairm.
revokeKeyNotPresent=Chan eil iuchair (0x%S) agad a fhreagras ris an teisteanas cùl-ghairm!\n\nMa chaill thu an iuchair agad, feumaidh tu a h-ion-phortadh (can o fhrithealaiche iuchraichean) ron teisteanas cùl-ghairm!
revokeKeyAlreadyRevoked=Chaidh an iuchair 0x%S a chùl-ghairm mu thrà th.
refreshAllQuestion=Cha do thagh thu iuchair. Am bu toil leat a h-UILE iuchair ath-nuadhachadh?
refreshKeyServiceOn.warn=Rabhadh: Tha na h-iuchraichean agad ’gan ath-nuadhachadh sa chùlaibh air dòigh cho sà bhailte ’s a ghabhas.\nMa nì thu ath-nuadhachadh air na h-iuchraichean uile agad aig an aon à m, nochdaidh sin fiosrachadh mu do dhèidhinn gun fheum air sin.\nA bheil thu cinnteach gu bheil thu airson seo a dhèanamh?
refreshKey.warn=Rabhadh: a-rèir uiread nan iuchraichean is luaths a’ cheangail, dh’fhaoidte gun doir e fada fada gus a h-uile iuchair ath-nuadhachadh!
downloadContactsKeys.warn=Rabhadh: a-rèir uiread an luchd-aithne is luaths a’ cheangail, dh’fhaoidte gun doir e fada fada gus a h-uile iuchair a luchdadh a-nuas!
downloadContactsKeys.importFrom=A bheil thu airson an luchd-aithne o leabhar nan seòladh “%S†ion-phortadh?
keyMan.button.exportSecKey=À&s-phortaich na h-iuchraichean prìobhaideach
keyMan.button.exportPubKey=Na à s-phortaich ach na h-iuchraichean &poblach
keyMan.button.import=&Ion-phortaich
keyMan.button.refreshAll=Ath-nuadhaich a h-uile iuchai&r
keyMan.button.revokeKey=Cùl-ghai&rm an iuchair
keyMan.button.skip=&Gearr leum thar na h-iuchrach
keylist.noOtherUids=Chan eil dearbh-aithne eile aig an neach seo
keylist.hasOtherUids=Tha seo air cuideachd:
keylist.noPhotos=Chan eil dealbh ri là imh
keylist.hasPhotos=Dealbhan
keyMan.addphoto.filepicker.title=Tagh dealbh gus a chur ris
keyMan.addphoto.warnLargeFile=Tha am faidhle a thagh thu nas motha na 25 kB.\nCha mholamaid gun cuir thu faidhle glè mhòr ris on a gheibh thu iuchair glè mhòr an uairsin.
keyMan.addphoto.noJpegFile=Tha coltas nach eil am faidhle a thagh thu ’na fhaidhle JPEG. Feuch an tagh thu faidhle eile.
keyMan.addphoto.failed=Cha b’ urrainn dhuinn an dealbh a chur ris.
noWksIdentity=Chan eil dearbh-aithne WKS aig an iuchair %S.
keyman.addBlacklistKey.msg=A bheil thu airson ’s gun sguir p≡p de chleachdadh na h-iuchrach “%1$S (%2$S)†a chum crioptachadh nan teachdaireachdan?
keyman.removeBlacklistKey.msg=A bheil thu airson cead a thoirt do p≡p gus an iuchair “%1$S (%2$S)†a chleachdadh san à m ri teachd?
keyman.addBlacklistKey.button=Cuir an iuchair ris an &dubh-liosta
keyman.removeBlacklistKey.button=Thoi&r an iuchair far na dubh-liosta
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Dh’fhà illig le atharrachadh prìomh ID a’ chleachdaiche
changePrimUidOK=Chaidh prìomh ID a’ chleachdaiche atharrachadh
revokeUidFailed=Dh’fhà illig le cùl-ghairm ID a’ chleachdaiche %S
revokeUidOK=Chaidh ID a’ chleachdaiche %S a chùl-ghairm. Ma tha an iuchair agad ri fhaighinn air frithealaiche iuchraichean, mholamaid gun luchdaich thu suas a-rithist i ach am faic cà ch gun deach a cùl-ghairm.
revokeUidQuestion=A bheil thu cinnteach gu bheil thu airson ID a’ chleachdaiche %S a chùl-ghairm?
# Strings in enigmailKeyImportInfo.xul
importInfoTitle=DEISEIL! Chaidh na h-iuchraichean ion-phortadh
importInfoBits=Biod
importInfoCreated=Air a chruthachadh
importInfoFpr=Lorg-mheòir
importInfoDetails=(Mion-fhiosrachadh)
importInfoNoKeys=Cha deach iuchair ion-phortadh.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=iuchair phoblach
keyTypePrimary=prìomh iuchair
keyTypeSubkey=fo-iuchair
keyTypePair=cà raid iuchrach
keyExpiryNever=gun chrìoch
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
keyAlgorithm_18=ECDH
keyAlgorithm_19=ECDSA
keyAlgorithm_20=ELG
keyAlgorithm_22=EDDSA
keyUsageEncrypt=Crioptaich
keyUsageSign=Soidhneadh
keyUsageCertify=Teistich
keyUsageAuthentication=Dearbhadh
keyDoesNotExpire=Chan fhalbh an ùine air an iuchair
# Strings in enigmailGenCardKey.xul
keygen.started=Fuirich greis fhad ’s a tha an iuchair ga gintinn…
keygen.completed=Chaidh an iuchair a ghintinn. Seo ID na h-iuchrach ùire: 0x%S
keygen.keyBackup=Chaidh lethbhreac-glèidhidh dhen iuchair a dhèanamh mar %S
keygen.passRequired=Sònraich abairt-fhaire ma tha thu airson lethbhreac-glèidhidh dhen iuchair agad a chruthachadh taobh a-muigh a’ SmartCard agad.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=Cha deach leinn am PIN atharrachadh
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Ag ath-nuadhachadh nan iuchraichean, fuirich greis…
keyserverProgress.uploading=A’ luchdadh suas nan iuchraichean, fuirich greis…
keyserverProgress.wksUploadFailed=Cha b’ urrainn dhuinn an iuchair agad a luchdadh suas gu seirbheis Web Key
keyserverProgress.wksUploadCompleted=Chaidh an iuchair phoblach agad a chur a-null dhan t-solaraiche agad. Gheibh thu post-d a dhearbhas gun do rinn thu fhèin air an luchdadh suas.
keyserverTitle.refreshing=Ath-nuadhaich na h-iuchraichean
keyserverTitle.uploading=Luchdadh suas iuchraichean
# Strings in enigmailSetupWizard
passphrase.min8keys=Bu chòir do 8 caractaran a bhith san abairt-fhaire agad air a char a lugha!
setupWizard.reallyCancel=A bheil thu cinnteach gu bheil thu airson draoidh an rèiteachaidh Enigmail a dhùnadh?
setupWizard.invalidGpg=Chan eil am faidhle a shònraich thu ’na fhaidhle so-ghnìomhaichte GnuPG. Feuch an sònraich thu faidhle eile.
setupWizard.specifyFile=Feumaidh tu faidhle iuchrach poblaich a shònrachadh mus urrainn dhut leantainn air adhart.
setupWizard.installFailed=Tha coltas nach do shoirbhich leis an stà ladh. Feuch ris an stà ladh a-rithist no stà laich GnuPG a là imh agus lorg e leis a’ phutan “Rùraichâ€.
setupWizard.downloadForbidden=A chum do thèarainteachd fhèin, cha luchdaich sinn a-nuas GnuPG. Tadhail air https://gnupg.org/ a luchdadh a-nuas GnuPG.
setupWizard.downloadImpossible=Chan urrainn dhuinn GnuPG a luchdadh a-nuas an-drà sta. Feuch ris a-rithist an ceann greis no tadhail air https://gnupg.org/ gus GnuPG a luchdadh a-nuas.
setupWizard.hashSumError=Cha b’ urrainn dhan draoidh treibhdhireas an fhaidhle air a luchdadh a-nuas a dhearbhadh. Dh’fhaoidte gu bheil am faidhle briste no gun deach beantainn ris. A bheil thu airson leantainn air adhart leis an stà ladh co-dhiù?
setupWizard.importSettingsFile=Sònraich faidhle lethbhric-ghlèidhidh gus a luchdadh uaithe
setupWizard.invalidSettingsFile=Chan eil am faidhle a shònraich thu ’na fhaidhle lethbhric-ghlèidhidh cheart airson roghainnean Enigmail.
setupWizard.gpgConfExists=Tha faidhle rèiteachaidh GnuPG ann mar-thà . A bheil thu airson sgrìobhadh thairis air leis an fhear on t-seann-stà ladh agad?
setupWizard.noGpgHomeDir=Tha coltas gun do rèitich thu %S airson cleachdadh le GnuPG. Gidheadh, chan e pasgan a tha seo – chan urrainn dhut a chleachdadh.
setupWizard.unmachtedIds=Tha aithne no dhà san t-seann shuidheachadh agad nach b’ urrainn dhuinn a mhaidseadh:\n%S\nLeum sinn thairis air na roghainnean aca-san.
# Strings in installGnuPG.jsm
installGnuPG.downloadFailed=Thachair mearachd rè luchdadh a-nuas GnuPG. Thoir sùil air loga na consoil airson barrachd fiosrachaidh.
installGnuPG.installFailed=Thachair mearachd rè stà ladh GnuPG. Thoir sùil air loga na consoil airson barrachd fiosrachaidh.
# Strings in enigmailAddUidDlg.xul
addUidDlg.nameOrEmailError=Feumaidh tu ainm is seòladh puist-d a chur a-steach
addUidDlg.nameMinLengthError=Feumaidh 5 caractaran a bhith san ainm air a char as lugha
addUidDlg.invalidEmailError=Feumaidh tu seòladh puist-d dligheach a thoirt seachad
# Strings in enigmailCardDetails.js
Carddetails.NoASCII=Cha chuir SmartCard OpenPGP taic ach ri caractaran ASCII san ainm is sloinneadh.
# network error types
errorType.SecurityCertificate=Chan eil an teisteanas tèarainteachd a thug an t-seirbheis-lìn seachad dligheach.
errorType.SecurityProtocol=Chan aithne dhuinn am pròtacal tèarainteachd a chleachdas an t-seirbheis-lìn.
errorType.Network=Thachair mearachd lìonraidh.
# filter stuff
filter.folderRequired=Feumaidh tu pasgan-uidhe a thaghadh.
filter.decryptMove.label=Dì-chrioptaich gu buan (Enigmail)
filter.decryptCopy.label=Cruthaich lethbhreac dì-chrioptaichte dheth (Enigmail)
filter.decryptMove.warnExperimental=Rabhadh - dh’fhaoidte gum mill an roghainn criathraidh “Dì-chrioptaich gu buan†teachdaireachdan.\n\nDian-mholamaid gum feuch thu ris a’ chriathrag “Cruthaich lethbhreac dì-chrioptaichte†an toiseach, gun dearbhaich thu an toradh gu cùramach agus nach cleachd thu a’ chriathrag seo ach ma tha thu toilichte leis an toradh.
filter.tempPepFilterDesc=Criathrag shealach gus an teachdaireachd air a cur a stòradh gun chrioptachadh
filter.term.pgpencrypted.label=Le crioptachadh OpenPGP
filter.encrypt.label=Crioptaich gu iuchair (Enigmail)
filter.keyRequired=Feumaidh tu iuchair an fhaighteir a thaghadh.
filter.keyNotFound=Cha do lorg sinn iuchair crioptachaidh airson “%Sâ€.
filter.warn.keyNotSecret=Rabhadh – cuiridh an gnìomh criathraidh “Crioptaich gu iuchair†faightear eile an à ite nam faightearan tùsail.\n\nMur eil an iuchair phrìobhaideach airson “%S†agad, chan urrainn dhut na puist-d a leughadh tuilleadh.
# strings in enigmailConvert.jsm
converter.decryptBody.failed=Cha deach leinn an teachdaireachd a dhì-chrioptachadh air a bheil an cuspair\n“%Sâ€.\nA bheil thu airson feuchainn ris a-rithist le abairt-fhaire eile no a bheil thu airson leum a ghearradh thar na teachdaireachd?
converter.decryptAtt.failed=Cha deach leinn an ceanglachan “%1$Sâ€\na dhì-chrioptachadh aig an teachdaireachd air a bheil an cuspair\n“%2$Sâ€.\nA bheil thu airson feuchainn ris a-rithist le abairt-fhaire eile no a bheil thu airson leum a ghearradh thar na teachdaireachd?
saveLogFile.title=SÃ bhail faidhle loga
# strings in gpg.jsm
unknownSigningAlg=Algairim soidhnidh nach aithne dhuinn (ID: %S)
unknownHashAlg=Hais chrioptografach nach aithne dhuinn (ID: %S)
# strings in keyRing.jsm
keyring.photo=Dealbh-camara
keyRing.pubKeyRevoked=Chaidh an iuchair %1$S (ID na h-iuchrach: %2$S) a chùl-ghairm.
keyRing.pubKeyExpired=Dh’fhalbh an ùine air an iuchair %1$S (ID na h-iuchrach>: %2$S).
keyRing.pubKeyNotForSigning=Cha ghabh an iuchair %1$S (ID na h-iuchrach: %2$S) cleachdadh airson soidhneadh.
keyRing.pubKeyNotForEncryption=Cha ghabh an iuchair %1$S (ID na h-iuchrach: %2$S) cleachdadh airson crioptachadh.
keyRing.keyDisabled=Chaidh an iuchair %1$S (ID na h-iuchrach: %2$S) a chur à comas; cha ghabh a cleachdadh.
keyRing.keyNotTrusted=Chan eil earbsa gu leòr san iuchair %1$S (ID na h-iuchrach: %2$S). Suidhich ìre earbsa na h-iuchrach agad air “cho earbsach ’s a ghabhas†gus a cleachdadh airson soidhneadh.
keyRing.keyInvalid=Chan eil an iuchair %1$S (ID na h-iuchrach %2$S) dhligheach. Feuch an dearbhaich thu i mar bu chòir no cleachd “Roghainnean crioptachaidh furastaâ€.
keyRing.signSubKeysRevoked=Chaidh gach fo-iuchair soidhnidh aig an iuchair %1$S (ID na h-iuchrach: %2$S) a chùl-ghairm.
keyRing.signSubKeysExpired=Dh’fhalbh an ùine air gach fo-iuchair soidhnidh aig an iuchair %1$S (ID na h-iuchrach: %2$S).
keyRing.signSubKeysUnusable=Chaidh gach fo-iuchair soidhnidh aig an iuchair %1$S (ID na h-iuchrach: %2$S) a chùl-ghairm, dh’fhalbh an ùine orra no cha ghabh an cleachdadh air adhbhar air choireigin eile.
keyRing.encSubKeysRevoked=Chaidh gach fo-iuchair crioptachaidh aig an iuchair %1$S (ID na h-iuchrach: %2$S) a chùl-ghairm.
keyRing.encSubKeysExpired=Dh’fhalbh an ùine air gach fo-iuchair crioptachaidh aig an iuchair %1$S (ID na h-iuchrach: %2$S).
keyRing.noSecretKey=Chan eil an iuchair phrìobhaideach airson %1$S (ID na h-iuchrach: %2$S) air an dul-iuchrach agad a-rèir coltais; chan urrainn dhut an iuchair a chleachdadh airson soidhneadh.
keyRing.encSubKeysUnusable=Chaidh gach fo-iuchair crioptachaidh aig an iuchair %1$S (ID na h-iuchrach: %2$S) a chùl-ghairm, dh’fhalbh an ùine orra no cha ghabh an cleachdadh air adhbhar air choireigin eile.
#strings in exportSettingsWizard.js
cannotWriteToFile=Chan urrainn dhuinn sà bhaladh dhan fhaidhle “%Sâ€. Feuch an tagh thu faidhle eile.
dataExportError=Tachair mearachd rè à s-phortadh an dà ta agad.
enigmailSettings=RoghainneanEnigmail
defaultBackupFileName=Enigmail-Ã s-phortadh
specifyExportFile=Sònraich ainm faile airson an à s-phortaidh
homedirParamNotSUpported=Cha chuir sinn taic ri paramadairean a bharrachd a rèiticheas slighean, can --homedir agus --keyring rè à s-phortadh/aiseag nan roghainnean agad. Cleachd dòighean eile, can suidheachadh a’ chaochladair à rainneachd GNUPGHOME.
#strings in expiry.jsm
expiry.keyExpiresSoon=Falbhaidh an ùine air an iuchair %1$S agad ro %2$S là (ithean).\n\nMholamaid gun cruthaich thu cà raid iuchrach ùr ’s gun rèitich thu na cunntasan a fhreagras rithe ach an cleachd iad an iuchair ùr.
expiry.keysExpireSoon=Falbhaidh an ùine air na h-iuchraichean seo agad ro %1$S là (ithean):\n%2$S. Mholamaid gun cruthaich thu iuchraichean ùra ’s gun rèitich thu na cunntasan agad ach an cleachd iad na h-iuchraichean ùra.
expiry.keyMissingOwnerTrust=Tha earbsa a dhìth air an iuchair phrìobhaideach %S agad.\n\nMholamaid gun cuir thu “Cho earbsach ’s a ghabhas“ air “Tha thu ag earbsadh nan teisteanasan†ann an roghainnean na h-iuchrach.
expiry.keysMissingOwnerTrust=Tha earbsa a dhìth air na h-iuchraichean prìobhaideachd seo agad:\n%S.\nMholamaid gun cuir thu “Cho earbsach ’s a ghabhas“ air “Tha thu ag earbsadh nan teisteanasan†ann an roghainnean na h-iuchrach.
expiry.OpenKeyManager=Fosgail stiùireadh nan iuchraichean Enigmail
expiry.OpenKeyProperties=Fosgail roghainnean na h-iuchrach
#strings in pEpDecrypt.jsm
pEpDecrypt.cannotDecrypt=Seo teachdaireachd chrioptaichte. Gu mì-fhortanach, chan eil an iuchair phrìobhaideach agad gus an teachdaireachd a dhì-chrioptachadh.
#strings in gpgAgent.jsm
gpghomedir.notexists=Chan eil am pasgan “%S†far a bheil na h-iuchraichean OpenPGP agad ann ’s cha ghabh a chruthachadh.
gpghomedir.notwritable=Gha ghabh sgrìobhadh sa phasgan “%S†sa bheil na h-iuchraichean OpenPGP agad.
gpghomedir.notdirectory=’S e faidhle seach pasgan a th’ ann an “%S†far a bheil na h-iuchraichean OpenPGP agad ann.
gpghomedir.notusable=Cà raich ceadan a’ phasgain no atharraich an t-ionad “dachaigh†aig a’ GnuPG agad- Chan obraich GnuPG mar bu chòir mura dèan thu seo.
#strings in pepTrustWords.js
pepTrustWords.cannotVerifyOwnId=Chan urrainn dhuinn na faclan-earbsa p≡p airson a’ chunntais agad fhèin a dhearbhadh.
pepTrustWords.cannotFindKey=Chan urrainn dhuinn an iuchair airson %S a lorg.
pepTrustWords.cannotStoreChange=Cha b’ urrainn dhuinn an earbsa a thaobh %S atharrachadh.
pepTrustWords.generalFailure=Chan urrainn dhuinn na faclan-earbsa airson %S fhaighinn.
pepTrustWords.partnerFingerprint=An lorg-mheòir airson %S:
#strings in mimeWkdHandler.jsm
wkdMessage.body.req=Tha an solaraiche agad air an iuchair phoblach agad a chur ri eòlaire Web Key OpenPGP\n\nBriog air a’ phutan dearbhaidh ann am bann-cinn Enigmail gus foillseachadh na h-iuchrach poblaich agad a choileanadh.
wkdMessage.body.process=Seo post-d co-cheangailte ris a’ phròiseasadh fhèin-obrachail a luchdadh suas na h-iuchrach poblaich agad gu eòlaire Web Key OpenPGP.
Cha leig thu leas dad a dhèanamh aig an à m seo.
#strings in pepHandshake.js
pepPrivacyStatus.RatingBrokenSuggestion=Bu chòir dhut fhèin no an seòladair an teachdaireachd a chur a-rithist.
pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=Ma sgrìobh thu fhèin an teachdaireachd seo, chan eil an iuchair agad ri là imh.
pepPrivacyStatus.RatingMistrustSuggestion=Dèan ceangal leis a’ cho-sgrìobhaiche agad a-rithist is sibh a’ feuchainn ri crathadh-là imhe eile a choileanadh.
pepPrivacyStatus.RatingReliableSuggestion=Coilean crathadh-là imhe leis a’ cho-sgrìobhaiche agad a thoirt faclan-earbsa ri chèile gu pearsanta no air a’ fòn. Cha leig thu leas crathadh-là imhe a dhèanamh le gach co-sgrìobhaiche ach aon turas agus nì sin cinnteach gum bi an conaltradh earbsach tèarainte.
pepPrivacyStatus.RatingTrustedSuggestion=Chan fheum thu dad a dhèanamh!
pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Thoir an aire nach eil an teachdaireachd seo tèarainte ma dh’fhaoidte.
pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=Cuir ris am fiosrachadh a tha a dhìth
pepPrivacyStatus.RatingUnderAttackSuggestion=Dearbhaich susbaint na teachdaireachd seo gu sònraichte leis a’ cho-sgrìobhaiche agad.
pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Dèan cinnteach gu bheil ìre “Tèarainte†air a char as lugha air staid na prìobhaideachd airson gach co-sgrìobhaiche air an liosa.
pepPrivacyStatus.RatingUnencryptedSuggestion=Iarr air a’ cho-sgrìobhaiche agad gun cleachd iad dòigh crioptachaidh no gun stà laich iad p≡p.
pepPrivacyStatus.RatingUnreliableSuggestion=Chan eil crioptachadh no soidhneadh earbsach aig an teachdaireachd seo. Iarr air a’ cho-sgrìobhaiche agad gun à rdaich iad an dòigh crioptachaidh aca no gun stà laich iad p≡p.
pepPrivacyStatus.RatingBrokenExplanation=Tha crioptachadh no fòrmatadh briste air an teachdaireachd seo.
pepPrivacyStatus.RatingHaveNoKeyExplanation=Cha ghabh an teachdaireachd seo a dhì-chrioptachadh air sgà th ’s nach eil an iuchair ri là imh.
pepPrivacyStatus.RatingMistrustExplanation=Tha co-sgrìobhaiche aig an teachdaireachd seo a chaidh a chomharrachadh mar fhear amharasach roimhe.
pepPrivacyStatus.RatingReliableExplanation=Tha an teachdaireachd seo tèarainte ach geumaidh tu aithne a’ cho-sgrìobhaiche agad a dhearbhadh fhathast.
pepPrivacyStatus.RatingTrustedExplanation=Tha an teachdaireachd seo tèarainte ’s earbsach.
pepPrivacyStatus.RatingUndefinedExplanation=Chan eil fiosrachadh gu leòr san teachdaireachd seo airson measadh a bheil i tèarainte gus nach eil.
pepPrivacyStatus.RatingUnderAttackExplanation=Chan eil an teachdaireachd seo tèarainte agus bhean cuideigin rithe.
pepPrivacyStatus.RatingUnencryptedExplanation=Chan eil an teachdaireachd seo tèarainte.
pepPrivacyStatus.RatingUnencryptedForSomeExplanation=Chan eil an teachdaireachd seo tèarainte do gach co-sgrìobhaiche.
pepPrivacyStatus.RatingUnreliableExplanation=Chan eil dìon na teachdaireachd seo earbsach.
pepPrivacyStatus.RatingBrokenText=Briste
pepPrivacyStatus.RatingHaveNoKeyText=Chan urrainn dhuinn a dì-chrioptachadh
pepPrivacyStatus.RatingMistrustText=Amharasach
pepPrivacyStatus.RatingReliableText=Tèarainte
pepPrivacyStatus.RatingTrustedText=Tèarainte ⊠earbsach
pepPrivacyStatus.RatingUndefinedText=Chan eil fhios
pepPrivacyStatus.RatingUnderAttackText=Fo ionnsaigh
pepPrivacyStatus.RatingUnencryptedForSomeText=Neo-thèarainte do chuid
pepPrivacyStatus.RatingUnencryptedText=Neo-thèarainte
pepPrivacyStatus.RatingUnreliableText=Tèarainteachd neo-earbsach
handshakeDlg.button.initHandshake=Crathadh-là imhe…
handshakeDlg.button.stopTrust=Na cuir earbsa ann tuilleadh
handshakeDlg.button.reTrust=Thoir air falbh an t-an-amharas
handshakeDlg.label.outgoingMessage=Teachdaireachd a-mach
handshakeDlg.label.incomingMessage=Teachdaireachd a-steach
handshakeDlg.error.noPeers=Cha ghabh crathadh-là imhe a dhèanamh às aonais co-sgrìobhaiche.
handshakeDlg.error.noProtection=Cuir an dìon an comas ach an cleachd thu gleus nan crathaidhean-là imhe.
enigmail.acSetupPasswd.descEnterPasswd=Cuir a-steach an còd suidheachaidh a chì thu air an uidheam eile
enigmail.acSetupPasswd.descCopyPasswd=Cuir a-steach an còd suidheachadh a chì thu gu h-ìosal air an uidheam eile agad gus leantainn air adhart leis an t-suidheachadh
#strings in autocrypt.jsm
autocrypt.setupMsg.subject=Teachdaireachd suidheachadh Autocrypt
autocrypt.setupMsg.msgBody=Gus Autocrypt a shuidheachadh air an uidheam ùr agad, lean ris an stiùireadh a bu chòir dhut fhaicinn air an uidheam ùr agad.
autocrypt.setupMsg.fileTxt=Seo faidhle suidheachadh Autocrypt a thèid a chleachdadh gus roghainnean is iuchraichean a thar-aiseag eadar cliantan. ’S urrainn dhut a dì-chrioptachadh leis a’ chòd shuidheachaidh a chì thu air an t-seann-uidheam agad agus an iuchair a tha ’na broinn ion-phortadh dhan dul-iuchrach agad an uairsin.
#strings in upgradeInfo.html
upgradeInfo.doctitle=Na tha ùr ann an Enigmail v2.0
upgradeInfo.welcome1=Fà ilte gun Enigmail ùr, tionndadh 2.0!
upgradeInfo.welcome2=Tha iomadh gleus ùr no air atharrachadh san sgaoileadh seo. Thoir sùil air na tha ùr:
upgradeInfo.encSubject.title=Crioptachadh air cuspair na teachdaireachd
upgradeInfo.encSubject.desc=Leasaich sinn dòigh ùr a ghluaiseas cuspair a’ phuist-d dhan teachdaireachd chrioptaichte ’s a chuireas “Teachdaireachd le crioptachadh†an à ite a’ chuspair a chithear. Nuair a thèid teachdaireachd dhen leithid a dhì-chrioptachadh, thèid an cuspair tùsail a chur ’na à ite gu fèin-obrachail. Tha falach nan cuspairean an comas a ghnà th; tha roghainn ann gus a chur dheth mura còrd e riut. (Thoir an aire: iarraidh an gleus seo gun cuir thu an teachdaireachd le PGP/MIME.)
upgradeInfo.buttons.title=Chaidh an dòigh a dh’obraicheas na putanan crioptachaidh is soidhnidh atharrachadh
upgradeInfo.buttons.desc=Obraichidh na putanan Crioptaich is Soidhnich ann an uinneag an sgrìobhaidh an dà chuid le pròtacal OpenPGP agus S/MIME. Ma tha an dà chuid comasach, feuchaidh Enigmail am pròtacal a chleachdadh dhan a bheil a h-uile iuchair ri fhaighinn.
upgradeInfo.autocrypt.title=Taic ri Autocrypt
upgradeInfo.autocrypt.desc=Cuiridh Enigmail taic ri Autocrypt a-nis, seo stannard ùr a chum sgaoileadh iuchraichean mar phà irt de theachdaireachdan a thèid a chur. Ion-phortaichidh Enigmail iuchraichean o theachdaireachdan a ghèilleas ri Autocrypt gu fèin-obrachail ach an gabh barrachd phost-d a chrioptachadh san à m ri teachd.
upgradeInfo.pEp.title=Modh p≡p furasta ùr (Pretty Easy Privacy)
upgradeInfo.pEp.desc=Tha modh furasta p≡p aig Enigmail a-nis. Feumaidh tu p≡p a stà ladh a là imh aig an à m seo; tha sinn ag amas piseach a chur air sin san à m ri teachd. Leigidh am modh furasta p≡p leat crioptachadh OpenPGP a chleachdadh air dòigh as soilleire; cha leig thu leas bodraigeadh le stiùireadh no sioncronachadh nan iuchraichean eadar uidheaman tuilleadh.
upgradeInfo.bottom.desc=Tadhail air an docamaideadh againn airson cobhair le cleachdadh Enigmail.
pep.missingGnuPG=Feumaidh GnuPG a bhith agad mus urrainn dhut Enigmail/p≡p a chleachdadh. Cha do lorg sinn e agus mholamaid gun luchdaich sinn a-nuas is gun stà laich sinn e air do shon.
#strings in enigmailAbout.html
aboutEnigmail.tabName=Mu Enigmail
aboutEnigmail.title=Tha an taic ri OpenPGP ’ga sholar le Enigmail
aboutEnigmail.team=Tha Enigmail ’ga leasachadh le sgioba leasachaidh Enigmail:
aboutEnigmail.projectLeader=Prìomh neach-leasachaidh:
aboutEnigmail.usability=So-chleachdachd:
aboutEnigmail.documentation=Docamaideadh:
aboutEnigmail.testing=Deuchainnean:
aboutEnigmail.userSupport=Taic:
aboutEnigmail.localization=Eadar-theangachadh: Faic duilleag nam pacaidean cà nain Enigmail
aboutEnigmail.Credits=Urram:
aboutEnigmail.origAuthor=Ùghdar tùsail leudachan Enigmail
aboutEnigmail.icons=ÃŒomhaigheagan:
aboutEnigmail.formerMembers=Seann-bhuill an sgioba:
aboutEnigmail.projectHosting=Òstadh a’ phròiseict:
aboutEnigmail.licenseSupportTitle=Ceadachas ⊠taic
aboutEnigmail.license=’S e bathar-bog le tùs fosgailte a th’ ann an Enigmail OpenPGP agus fo cheadachas %S
aboutEnigmail.support=Tha taic is luchdaidhean a-nuas ri am faighinn air www.enigmail.net.
enigmail-2.0.8/lang/gd/help/ 0000775 0000000 0000000 00000000000 13343027545 0015557 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/gd/help/compose.html 0000664 0000000 0000000 00000010076 13343027545 0020116 0 ustar 00root root 0000000 0000000
Enigmail Help: Message Composition
Enigmail Help
Using Enigmail when composing messages
Enigmail menu in Mail/Compose window
Sign message
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit Per-Recipient Rule
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.
Set Enigmail Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the Enigmail Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
Decrypt button in main Mail window
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Opening encrypted attachments / importing attached OpenPGP keys
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
enigmail-2.0.8/lang/gd/help/initError.html 0000664 0000000 0000000 00000004552 13343027545 0020430 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing Enigmail
Enigmail Help
How to Resolve Problems with Initializing Enigmail
There 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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of Enigmail to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Menú de Enigmail na ventá de Composición de correo
Asinar mensaxe: Activa/Desactiva o envío de correo asinado. O
usuario ou usuaria son notificados se a sinatura falla.
Cifrar mensaxe: Activar/Desactiva o cifrado a todos os destinatarios
ou destinatarias antes do envío. Notifícase en caso de que se produza un erro no
cifrado.
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.
Usar PGP/MIME para esta mensaxe: Activa/Desactiva o uso de PGP/MIME
para esta mensaxe.
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.
Opcións predeterminadas para a composición: Submenú.
Opcións de Sinatura/Cifrado...: atallo a Configuración das contas ->
Opcións OpenPGP.
Opcións de envío...: atallo á pestana Preferencias ->
Envío.
Opcións de selección de chaves...: atallo á pestana Preferencias ->
Selección de chaves.
Opcións PGP/MIME...: atallo á pestana Preferencias ->
PGP/MIME.
Desfacer cifrado: Se hai un fallo ao enviar un correo, como o
servidor POP que non acepta unha solicitude, Enigmail non pode sabelo, e a
mensaxe cifrada seguirá na ventá de composición. Escollendo este elemento do
menú desfarase o cifrado/sinatura, volvendo o texto orixial á ventá de
composición. Como un arranxo temporal, esta opción pode utilizarse para descifrar o
texto comentado ao responder mensaxes cifradas. Enigmail debería descifrar
a mensaxe automaticamente, mais se falla por algunha razón, pode utilizar
este elemento do menú para forzalo.
Inserir chave pública: insire a chave pública nun bloque ASCII-armado
na posición actual do cursos na ventá de composición. Pediráselle o enderezo da
chave que quere inserir. As chaves inseridas desta maneira serán recoñecidas
automaticamente ao seren recividas por Enigmail. Despois da inserción da chave,
pode tamén escoller asinar/cifrar o correo se é preciso. De todos xeitos, non
insira máis dun bloque de chaves nunha mensaxe; simplemente especifique múltiples
enderezos de correo, separados por comas ou espazos, cando se lle pregunte.
Limpar contrasinais gardados: Limpa os contrasinais gardados en caché.
Útil se ten múltiples contrasinais.
Axuda: Mostra información de axuda desde o sitio web (esta páxina).
Usando o Editor de regras de Enigmail Rules Editor: Editar regra OpenPGP
No 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.
Definiar regras OpenPGP para: Contén os
enderezos de correo dos destinos (sen nomes, p.e. so un enderezo como
alguen@correo.dominio). Pode especificar varios enderezos de correo,
separados por espazos. O enderezo especificado aquí pode consistir só na parte do
dominio de xeito que calquera enderezo deste dominio coincidirá,
p.e. @correo.dominio funcionará con calquera@correo.dominio,
algun@correo.dominio, algunha@correo.dominio, etc.
Aplicar regra se o/a destinatario/a ...:
Isto modifica a coincidencia dos enderezos de correo. Se se introducen múltiples
enderezos, a configuración aplicaráselles a todos eles. Os seguintes exemplos están
baseados en calquera@correo.dominio introducidos no seguinte campo de
Regras OpenPGP.
É exactamente: con esta configuración, a regra só se dispara con
correos a calquera@correo.dominio (exacto, coincidencia sensíbel a maiúsculas)
Contén: con esta configuración, calquera correo que conteña a cadea coincide
p.e son.calquera@correo.dominio ou calquera@correo.dominio.net
Comeza por: con esta configuración, calquera correo que comece coa cadea
coincidirá, p.e. calquera@correo.dominio.net,
calquera@correo.dominio-nome.com.
Remata con: con esta configuración, calquera enderezo que remate coa cadea
coincidirá, p.e. soncalquera@correo.dominio, nonson.calquera@correo.dominio.
Continuar coa seguinte regra que coincida co enderezo
Activando esta función permitirase definir unha regra sen ter que especificar un
ID de chave no campo Usar as seguintes chaves OpenPGP:, de xeito que
o enderezo se utilizar para buscar unha chave no momento do envío. Tamén se
procesarán outras regras para o(s) mesmo(s) enderezos igualmente.
Non comprobar outras regras para os enderezos que coinciden
Activando esta función párase o procesamento de outras regras para un enderezo que xa
coincidiu; p.e. o procesado de regras continúa co seguinte destinatario
Usar as seguintes chaves OpenPGP:
Use o botón Seleccionar chave(s).. para seleccionar as chaves dos/as
destinatarios/as que utilizar para o cifrado. Como na anterior acción, non se
procesan máis regras para enderezos que xa coincidiron.
Predeterminado para sinatura:
activa ou desactiva a sinatura de mensaxes. Isto afirmar ou anula o que especificou na ventá
de composición de mensaxe. Os valores son:
Nunca: desactiva a sintaura, aínda que estea activada na ventá de composición
da mensaxe (anula outros valores)
Si, se está seleccionado na Composición da mensaxe: deixa a sinatura
tal e como se especificou na ventá de composición da mensaxe
Sempre: activa a sinatura, aínda que non estea activada na ventá de composición da mensaxe
Esta configuració de sinatura aplícase para todas
as regras que coincidan. Se unha das regras desactiva a sinatura, a mensaxe non se
asina, a pesar do que especifiquen outras regras Sempre.
Cifrado: activa ou desactiva o cifrado
de mensaxes. As configuracións permitidas e o seu significado é o mesmo que para
a sinatura.
PGP/MIME: activar ou desactivar o uso
da codificación de mensaxes PGP/MIME (RFC 3156).
Se PGP/MIME está desactivado, as mensaxes codifícanse usando "PGP en liña". Os valores
permitidos e os seus significados son os mesmos que para a sinatura.
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.
enigmail-2.0.8/lang/gl/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020437 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
enigmail-2.0.8/lang/gl/help/messenger.html 0000664 0000000 0000000 00000011007 13343027545 0020444 0 ustar 00root root 0000000 0000000
Axuda de Enigmail: Lectura de mensaxes
Axuda de Enigmail
Usando Enigmail para ler o correo
Botón Descifra na ventá principal do correo
Este botón pode utilizarse para diferentes propósitos: descifrar, verificar,
ou importar chaves públicas. Normalmente o descifrado/verificación sucede
de xeito automático, mais isto pode desactivarse a través das preferencias.
De todos xeitos, se isto falla, normalmente aparecerá unha mensaxe de erro na
liañ de estdo de Enigmail. Se fai clic no botón Descifrar, poderá ver unha
mensaxe de erro máis detallada, incluída a saída do comando GnuPG.
Iconas do lápis e a chave na cabeceira da mensaxe
As iconas do lápis e a chave ca cabeceira da mensaxe indican que
a mensaxe que está a ler está asinada e/ou cifrada e que a sinatura é correcta,
p.e. a mensaxe non mudou desde que foi asinada. Se a mensaxe tivese mudado, a icona
do lápis mudaría nun láspis roto para indicar que a sinatura non é
correcta. Se fai clic co botón dereito sobre o lápis ou a chave aparecerá un menú
coas seguintes opcións:
Información de seguridade OpenPGP: permite ver o estado da saída de GnuPG
para esta mensaxe.
Copiar información de seguridade OpenPGP: copia o estado da saída de
GnuPG ao portarretallos; para pegala nunha mensaxe de resposta, etc.
Ver ID de foto OpenPGP: permite ver o ID de fotoda persoa que
enviou a mensaxe, se é que tiña unha foto integrada na súa chave pública
(Esta opción só estará activada se hai un ID de foto na chave.)
Información de seguridade S/MIME: permite ver a información sobre
seguridade S/MIME para a mensaxe.
Se 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.
Abrir ficheiros adxuntos cifrados / importar chaves OpenPGP adxuntas
Anexos nomeados *.pgp, *.asc e *.gpg son recoñecidos como anexos que poden ser
manexados especialmente por Enigmail. Facendo clic co botón dereito neses ficheiros
adxuntos actívanse dous elementos de menú especiais no menú contextual: Descifrar
e abrir e Descifrar e gardar. Use estes dous elementos do menú se quere
que Enigmail descifre un anexo antes de abrilo ou gardalo. Se un anexo é recoñecido como
un ficheiro de chave OpenPGP, ofreceráselle importar as chaves no seu anel de chaves.
enigmail-2.0.8/lang/gl/help/rulesEditor.html 0000664 0000000 0000000 00000006530 13343027545 0020762 0 ustar 00root root 0000000 0000000
Axuda de Enigmail: Editor de regras
Axuda de Enigmail
Usando o Editor de regras de Enigmail
No 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:
Correo: os campos de remite do(s) correo(s)
o Para:, Cc: e Cco:the To:, Cc: and Bcc: que teñen que coincidir.
A coincidencia funciona en subcadeas (Pódense consultar máis detalles
no diálogo de edición da regra)
Chave(s) OpenPGP: unha lista de ID's de chaves
para utilizar cos enderezos destinatarios
Asinar: activa ou desactiva a
sinatura de mensaxes. Isto afirma ou anula o que especificou na ventá de composición
da mensaxe. Os valores son:
Nunca: desactiva a sinatura, aínda que estea activa na ventá de
composición da mensaxe (anular outros valores)
Posíbel: deixa a sinatura tal e como se especificou na ventá de
composición da mensaxe.
Sempre: activa a sinatura, aínda que non estea activada na ventá de composición da mensaxe
Estas configuracións da sinatura aplícanse para
todas as regras que coincidan. Se algunha das regras desactiva a sinatura, a mensaxe
non se asinará, a pesar do que digan outras regras Sempre.
Cifrar: activa ou desactiva o
cifrado de mensaxes. As configuracións permitidas e o seu significado é o
mesmo que para as sinaturas.
PGP/MIME: activa ou desactiva o
uso da codificación de mensaxes PGP/MIME (RFC 3156).
Se PGP/MIME está desactivado, as mensaxes codifícanse usando "PGP en-liña".
Os valores permitidos e o seu significado son os mesmos que para a sinatura.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/hr/ 0000775 0000000 0000000 00000000000 13343027545 0014646 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/hr/am-enigprefs.properties 0000664 0000000 0000000 00000000205 13343027545 0021336 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=Nizovi koriÅ¡teni u Mozilla upravitelju raÄuna\n\nOpenPGP sigurnost
enigmail-2.0.8/lang/hr/enigmail.dtd 0000664 0000000 0000000 00000161710 13343027545 0017136 0 ustar 00root root 0000000 0000000
' da bi odredili email adrese">
' znakove da bi odredili email adrese za GnuPG. Onesposobite ako primatelji imaju stare Hushmail kljuÄeve.">
OpenPGP sigurnost)">
NAPOMENA: Generiranje kljuÄeva može trajati nekoliko minuta. Ne izlazite iz aplikacije dok se kljuÄevi generiraju. Aktivno pregledavanje interneta ili provoÄ‘enje operacija koje su zahtjevne za disk prilikom generiranja kljuÄeva će napuniti 'bazen nasumiÄnosti' i ubrzati proces. Bit će te obavijeÅ¡teni kad je generiranje kljuÄeva gotovo.">
' nije važeće">
NAPOMENA: Generiranje kljuÄa može potrajati nekoliko minuta. Ne izlazite iz aplikacije dok se kljuÄ generira. Bit će te obavijeÅ¡teni kad je deneriranje zavrÅ¡eno.">
Obavijest: Enigmail će uvijek provjeravati potpise
na email-ovima za svaki raÄun i identitet, bez obzira da li je omogućen ili ne">
javni kljuÄ je za druge da Vam poÅ¡alju enkriptirane email-ove. Možete ga distribuirati svima.">
privatni kljuÄ je za Vas tako da možete dekriptirati i slati potpisane email-ove.
Ne bi ga trebali dati nikom.">
privatni kljuÄ je za Vas da bi dekriptirali ove email-ove i slali potpisane email-ove.
Ne bi ga trebali dati nikom.
Da bi osigurali VaÅ¡ privatni kljuÄ, bit ćete upitani za lozinku u sljedeća dva dijaloga.">
lozinka je lozinka za zaÅ¡titu VaÅ¡eg privatnog kljuÄa. SprijeÄava zloupotrebu VaÅ¡eg privatnog kljuÄa.">
nisu preporuÄeni.">
izvezite svoje podatke sa svog starog raÄunala koristeći Äarobnjak za sigurnosne kopije iz Enigmail postavkiuvezite podatke na novo raÄunalo koristeći ovaj Äarobnjak.
">
Hvala Vam što koristite Enigmail.">
izvezite svoje podatke sa starog raÄunala koristeći ovaj Äarobnjakuvezite podatke na novo raÄunalo koristeći ÄŒarobnjak za postavljanje.
">
enigmail-2.0.8/lang/hr/enigmail.properties 0000664 0000000 0000000 00000152576 13343027545 0020571 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Enigmail upozorenje
enigConfirm=Enigmail potvrda
# enigInfo=Enigmail Information
enigError=Enigmail greška
enigPrompt=Enigmail prompt
dlgYes=&Da
dlgNo=&Ne
dlgKeepSetting=Zapamti moj odgovor i ne pitaj me više
dlgNoPrompt=Ne pokazuj mi ovaj okvir ponovno
dlg.button.delete=&Obriši
dlg.button.cancel=&Otkaži
dlg.button.close=&Zatvori
dlg.button.continue=Nastavi
dlg.button.skip=&PreskoÄi
dlg.button.overwrite=&Prepiši
dlg.button.view=&Pregledaj
dlg.button.retry=&Pokušaj ponovno
dlg.button.ignore=&Ignoriraj
# dlg.button.install=&Install
# dlg.button.ok=&OK
repeatPrefix=\n\nOvo upozorenje će se ponoviti još %S
repeatSuffixSingular=put.
repeatSuffixPlural=puta.
noRepeat=\n\nOvo upozorenje se neće ponavljati dok ne nadogradite Enigmail.
pgpNotSupported=Izgleda da koristite Enigmail zajedno s PGP 6.x\n\nNažalost, PGP 6.x ima niz problema koji sprijeÄavaju Enigmail da radi ispravno. Zbog toga Enigmail ne podržava PGP 6.x viÅ¡e; molimo Vas da se prebacite na GnuPG (GPG) umjesto toga.\n\nAko Vam treba pomoć pri prebacivanju na GnuPG, provjerite dio Enigmail naslovne stranice na kojem se nalazi Pomoć.
initErr.howToFixIt=Da bi koristili Enigmail morate imati GnuPG. Ako joÅ¡ niste instalirali GnuPG, najjednostavniji naÄin da to napravite je koristeći "ÄŒarobnjak postavljanja" gumb niže.
initErr.setupWizard.button=&ÄŒarobnjak postavljanja
passphraseCleared=Lozinka je oÄišćena.
cannotClearPassphrase=Koristite ne standardni alat (npr. gnome-keyring) za upravljanje lozinkama. Zbog toga Äišćenje lozinke nije moguće iz Enigmail-a.
noPhotoAvailable=Slika nije dostupna
debugLog.title=Enigmail zapis o otklanjanju pogreške
error.photoPathNotReadable=Putanja '%S' slike nije Äitljiva
# generalError=Error: %S
# Strings in configure.jsm
enigmailCommon.versionSignificantlyChanged=Ova nova verzija Enigmail-a ima znaÄajne promjene u rukovanju postavki i opcija. PokuÅ¡ali smo prenijeti stare postavke na ovu novu verziju, no ne možemo pokriti sve sluÄajeve automatski. Molimo Vas da provjerite nove postavke i opcije.
enigmailCommon.checkPreferences=Provjeri postavke...
preferences.defaultToPgpMime=Promjenili smo zadano enkodiranje poruka u Enigmail-u sa Inline-PGP-a u PGP/MIME. PreporuÄamo Vam da to zadržite kao zadano.\n\nAko i dalje želite koristiti Inline-PGP kao zadani, možete to napraviti u postavkama raÄunaa, pod OpenPGP sigurnost.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=Koristim Enigmail verziju %S
# enigmailPepVersion=Enigmail/p≡p version %S
usingAgent=Koristim %1$S izvršnu datoteku %2$S za enkripciju i dekripciju
agentError=POGREÅ KA: Pristup Enigmime usluzi nije uspio!
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Pogreška u pristupanju Enigmail usluzi
onlyGPG=Generiranje kljuÄeva radi jedino s GnuPG-om (ne s PGP-om)!
keygenComplete=Generiranje kljuÄa zavrÅ¡eno! Identitet <%S> će biti koriÅ¡ten za potpisivanje.
revokeCertRecommended=PreporuÄamo stvaranje certifikata za opoziv za VaÅ¡ kljuÄ. Ovaj certifikat se može iskoristiti za poniÅ¡tavanje VaÅ¡eg kljuÄa u sluÄaju da se VaÅ¡ tajni kljuÄ izgubi ili postane kompromitiran. Želite li stvoriti certifikat za opoziv sad?
keyMan.button.generateCert=&Generiraj certifikat
genCompleteNoSign=Generiranje kljuÄa zavrÅ¡eno!
genGoing=Generiranje kljuÄa je već u tijeku!
passNoMatch=Lozinke se ne podudaraju; molimo Vas da ih ponovno unesete
passCheckBox=OznaÄite kvaÄicom kutiju ako ne odreÄ‘ujete lozinku za kljuÄ
passUserName=Molimo Vas da odredite korisniÄko ime za ovaj identitet
keygen.missingUserName=Nije odreÄ‘eno ime za odabranu državu/identitet. Molimo unesite vrijednost u polje "VaÅ¡e ime" u postavkama raÄunama.
keygen.passCharProblem=Koristite posebne znakove u svojoj lozinci. Nažalost, ovo može prouzroÄiti probleme drugim aplikacijama. PreporuÄamo da odaberete lozinku koja se sastoji jedino od ovih znakova:\na-z A-Z 0-9 /.;:,!?(){}[]%*
passSpaceProblem=Zbog tehniÄkih razloga VaÅ¡a lozinka ne može zapoÄeti ili zavrÅ¡iti s razmakom.
changePassFailed=Promjena lozinke nije uspjela.
keyConfirm=Generiraj javni i privatni kljuÄ za '%S'?
keyMan.button.generateKey=&Generiraj kljuÄ
keyAbort=Prekini generiranje kljuÄa?
keyMan.button.generateKeyAbort=&Prekini generiranje kljuÄa
keyMan.button.generateKeyContinue=&Nastavi generiranje kljuÄa
expiryTooLong=Ne možete stvoriti kljuÄ koji istiÄe za viÅ¡e od 100 godina.
expiryTooLongShorter=Ne možete stvoriti kljuÄ koji istiÄe za viÅ¡e od 90 godina.
expiryTooShort=VaÅ¡ kljuÄ mora biti valjan za najmanje jedan dan.
keyGenFailed=Generiranje kljuÄa nije uspjelo. Molimo Vas provjerite Enigmail konzolu (Izbornik Enigmail > Otklanjanje pogreÅ¡ki Enigmail-a) za detalje.
setKeyExpirationDateFailed=Datum isteka nije mogao biti promjenjen
# Strings in enigmailMessengerOverlay.js
securityInfo=Enigmail sigurnosne informacije\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Privitci ove poruke nisu potpisani ili enkriptirani*\n\n
possiblyPgpMime=Potencionalno PGP/MIME enkriptirana ili potpisana poruka; kliknite gumb Dekriptiraj za provjeru
saveAttachmentHeader=Enigmail: Pohrani dekriptirani privitak
noTempDir=Nije pronađena privremena mapa u koju se piše\nMolimo Vas da postavite TEMP varijablu
attachmentPgpKey=ÄŒini se da je privitak '%S' koji otvarate datoteka OpenPGP kljuÄa.\n\nKliknte 'Uvezi' da bi uveli kljuÄeve ili 'Pregledaj' da bi pregledali sadržaj datoteke u prozoru preglednika
beginPgpPart=********* *POÄŒNI ENKRIPTRANI ili POTPISANI DIO* *********
endPgpPart=********** *ZAVRÅ I ENKRIPTIRANI ili POTPISANI DIO* **********
notePartEncrypted=Enigmail: *Dijelovi poruke NISU potpisani ili enkriptirani*
noteCutMessage=Enigmail: *Pronađeni višestruki blokovi poruke -- dekripcija/provjera prekinuta*
decryptOkNoSig=Upozorenje!\n\nDekripcija je provedena uspjeÅ¡no, ali potpisa nije mogao biti provjeren toÄno
msgOvl.button.contAnyway=&Svejedno nastavi
signature.verifiedOK=Potpis za privitak %S je uspješno provjeren
signature.verifyFailed=Potpis za privitak %S nije moguće provjeriti
attachment.noMatchToSignature=Nije moguće usporediti privitak '%S' s potpisnom datotekom
attachment.noMatchFromSignature=Nije moguće usporediti potpisnu datoteku '%S' s privitkom
fixBrokenExchangeMsg.failed=Popravak poruke nije uspio.
# enigmail.msgViewColumn.label=Enigmail
# enigmailPep.msgViewColumn.label=Enigmail/p≡p
# wksNoIdentity=This key is not linked to any of your email accounts. Please add an account for at least one of the following email addresse(s):\n\n%S
# wksConfirmSuccess=Confirmation email sent.
# wksConfirmFailure=Sending the confirmation email failed.
# autocrypt.importSetupKey.accountPreconfigured=Your account is already correctly configured for Autocrypt.\n\nDo you really want to overwrite your settings with this setup message?
# autocrypt.importSetupKey.selfCreated=This message was created by your currently running instance of Enigmail.\n\nPlease switch to the email client to which you want to transfer the settings, and click on the message on that email client to import the settings.
# autocrypt.importSetupKey.invalidMessage=Error - could not read setup message. The message seems to be corrupted. Please try to create a new setup message on your "other" device.
# autocrypt.importSetupKey.invalidKey=Error - the key could not be imported. The key is either not supported by your version of GnuPG, or it got corrupted.
# autocrypt.importSetupKey.wrongPasswd=The password you entered is wrong. Do you want to retry?
# autocrypt.importSetupKey.success=The Autocrypt setup message was processed successfully. Autocrypt is now available for your account '%S'.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Odaberite OpenPGP kljuÄeve za umetanje
keysToUse=Odabeirte OpenPGP kljuÄ(eve) za uporabu za %S
pubKey=Javni kljuÄ za %S\n
windowLocked=Prozor stvaranja poruke je zakljuÄan; slanje otkazano
sendUnencrypted=Inicijalizacija Enigmail-a nije uspjela.\nPoslati neenkriptiranu poruku?
composeSpecifyEmail=Molimo Vas da odredite svoju primarnu email adresu koja će biti koriÅ¡tena pri odabiru potpisnog kljuÄa za odlazne poruke.\nAko ostavite prazno, OD adresa poruke će biti iskoriÅ¡tena za odabir potpisnog kljuÄa.
sendingHiddenRcpt=Ova poruka ima BCC (slijepe kopije - skrivene) primatelje. Ukoliko je ova poruka enkriptirana moguće je sakriti BCC primatelje ali korisnici nekih proizvoda (npr. PGP Corp.) neće biti u mogućnosti dekriptirati poruku. S tim na umu, savjetujemo Vam da izbjegavate BCC email-ove kad radite s enkriptiranim porukama.
sendWithHiddenBcc=Sakrij BCC primatelje
sendWithShownBcc=Enkriptiraj normalno
sendingNews=Operacija Enkriptiranog slanja prekinuta.\n\nOva poruka ne može biti dekriptirana jer postoje grupe primatelja. Molimo Vas da ponovno pošaljete poruku bez enkripcije.
sendToNewsWarning=Upozorenje: poslati ćete neenkriptirani email grupi primatelja.\n\nOvo se ne potiÄe jer ima smisla jedino ako svi Älanovi grupe mogu dekriptirati poruku, odnosno poruka mora biti enkriptirana s kljuÄevima svih Älanova grupe. PoÅ¡aljite ovu poruku jedino ako znate toÄno Å¡to radite.\n\nNastaviti?
hasHTML=HTML mail upozorenje:\nOva poruka može sadržavati HTML, Å¡to bi moglo prouzroÄiti neuspjeh potpisivanja/enkripcije. Da bi se to izbjeglo, u budućnosti bi trebali pritisnuti SHIFT tipku kad klikćete na Stvori/Odgovori gumb tako da poÅ¡aljete potpisan email.\nAko potpisujete email pod zadano, trebali bi odznaÄiti 'Stvori poruku u HTML-u' tako da trajno onemogućite HTML mail za ovaj raÄun.
strippingHTML=Poruka sadrži HTML informacije formatiranja koje će biti izgubljene prilikom pretvorbe u obiÄan tekst za potpisivanje/enkripciju. Želite li nastaviti?
msgCompose.button.sendAnyway=&Pošalji poruku svejedno
attachWarning=Privitci ovoj poruci nisu lokalni, ne mogu biti enkriptirani. Da bi enkriptirali te privitke prvo ih pohranite kao lokalne datoteke, a zatim dodajte kao privitke. Želite li svejedno poslati poruku?
quotedPrintableWarn=Omogućili ste enkodiranje 'citirano - pogodno za ispis' za poruke koje se Å¡alju. Ovo može rezultirati netoÄnom dekripcijom i/ili provjerom VaÅ¡e poruke.\nŽelite li iskljuÄiti slanje takvih poruka sad?
minimalLineWrapping=Postavili ste omatanje linije na %S znakova. Za ispravnu enkripciju i/ili potpisivanje, ova vrijednost mora biti najmanje 68.\nŽelite li promjeniti omatanje linije na 68 znakova sad?
warning=Upozorenje
signIconClicked=RuÄno ste modificirali potpisivanje, stoga, dok stvarate ovu poruku, (de)aktiviranje potpisivanja ne ovisi viÅ¡e o (de)aktiviranju enkripcije.
errorOwnKeyUnusable=ID '%S' kljuÄa konfiguriranog za trenutni identitet ne daje iskoristiv OpenPGP kljuÄ.\n\nUvjerite se da imate važeći, ne istekli OpenPGP kljuÄ i da postavke VaÅ¡eg raÄuna pokazuju na taj kljuÄ.\nAko VaÅ¡ kljuÄ nije istekao, provjerite jeste li postavili povjerenje prema vlasniku na puno ili ultimativno.
msgCompose.cannotSaveDraft=Pogreška prilikom spremanja predloška
# msgCompose.partiallyEncrypted.short=Beware of leaking sensitive information - partially encrypted email.
# msgCompose.partiallyEncrypted.mimeMsg=The message you are replying to contained both unencrypted and encrypted parts. Some encrypted message parts are invisible to you.\n\nIf the sender was not able to decrypt the hidden message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nWe recommend that you don't reply to the message, but create a new message containing your answer.
# msgCompose.partiallyEncrypted.inlinePGP=The message you are replying to contained both unencrypted and encrypted parts. If the sender was not able to decrypt some message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nPlease consider removing all quoted text from your reply to this sender.
msgCompose.internalEncryptionError=Interna pogreška: obećana enkripcija onemogućena
msgCompose.internalError=Došlo je do interne pogreške.
msgCompose.toolbarTxt.signAndEncrypt=Ova poruka će biti potpisana i enkriptirana
msgCompose.toolbarTxt.signOnly=Ova poruka će biti potpisana
msgCompose.toolbarTxt.encryptOnly=Ova poruka će biti enkriptirana
msgCompose.toolbarTxt.noEncryption=Ova poruka će biti nepotpisana i neenkriptirana
msgCompose.toolbarTxt.disabled=Enigmail je onemogućen za odabrani identitet
# msgCompose.protectSubject.tooltip=Protect the message subject
# msgCompose.noSubjectProtection.tooltip=Do not protect the message subject
msgCompose.encryptedSubjectStub=Enkriptirana poruka
# msgCompose.protectSubject.dialogTitle=Enable Protection of Subject?
# msgCompose.protectSubject.question=Regular encrypted emails contain the unredacted subject.\n\nWe have established a standard to hide the original subject in the encrypted message\nand replace it with a dummy text, such that the subject is only visible after the email is decrypted.\n\nDo you want to protect the subject in encrypted messages?
# msgCompose.protectSubject.yesButton=&Protect subject
# msgCompose.protectSubject.noButton=&Leave subject unprotected
msgCompose.detailsButton.label=Detalji...
msgCompose.detailsButton.accessKey=D
# msgCompose.pepSendUnknown=Unknown
# msgCompose.pepSendUnsecure=Unsecure
# msgCompose.pepSendSecure=Secure
# msgCompose.pepSendTrusted=Secure & Trusted
# pep.alert.disabledForIdentity=p≡p is disabled for the current identity. Please enable p≡p via the Enigmail/p≡p preferences.
# pep.alert.weakReply=You’re about to forward or reply to a secure message as insecure. If you choose to proceed, confidential information might be leaked putting you and your communication partner at risk. Are you sure you want to continue?
# note: should end with double newline:
sendAborted=Operacija slanja prekinuta.\n\n
# details:
keyNotTrusted=Nema dovoljno povjerenja za kljuÄ '%S'
keyNotFound=KljuÄ '%S' nije pronaÄ‘en
keyRevoked=KljuÄ '%S' opozvan
keyExpired=KljuÄ '%S' je istekao
statPGPMIME=PGP/MIME
# statSMIME=S/MIME
statSigned=POTPISANO
statEncrypted=ENKRIPTIRANO
statPlain=NEPOTPISANO i NEENKRIPTIRANO
offlineSave=Pohrani %1$S poruku za %2$S u mapi neposlanih poruka?
onlineSend=Pošalji %1$S poruku %2$S?
encryptKeysNote=Napomena: poruka je enkriptirana za sljedeće ID-e korisnika / kljuÄeve: %S
hiddenKey=
signFailed=Pogreška u Enigmail-u; Enkripcija/potpisivanje nije uspjelo; pošalji neenkriptiranu poruku?
msgCompose.button.sendUnencrypted=&Pošalji neenkriptiranu poruku
recipientsSelectionHdr=Odaberi primatelje za enkripciju
configureNow=JoÅ¡ niste postavili Enigmail sigurnost za odabrani identitet. Želite li to uÄiniti sad?
# encryption/signing status and associated reasons:
encryptMessageAuto=Enkriptiraj poruku (automatski)
encryptMessageNorm=Enkriptiraj poruku
signMessageAuto=Potpiši poruku (automatski)
signMessageNorm=Potpiši poruku
encryptOff=Enkripcija: ISKLJUÄŒENA
encryptOnWithReason=Enkripcija: UKLJUÄŒENA (%S)
encryptOffWithReason=Enkripcija: ISKLJUÄŒENA (%S)
encryptOn=Enkripcija: UKLJUÄŒENA
signOn=Potpisivanje: UKLJUÄŒENO
signOff=Potpisivanje: ISKLJUÄŒENO
signOnWithReason=Potpisivanje: UKLJUÄŒENO (%S)
signOffWithReason=Potpisivanje: ISKLJUÄŒENO (%S)
reasonEnabledByDefault=omogućeno pod zadano
reasonManuallyForced=prisiljeno ruÄno
reasonByRecipientRules=prisiljeno po pravilima primatelja
reasonByAutoEncryption=prisiljeno po auto enkripciji
reasonByConflict=zbog sukoba u pravilima primatelja
reasonByEncryptionMode=zbog enkripcijskog naÄina rada
# should not be used anymore:
encryptYes=Poruka će biti enkriptirana
encryptNo=Poruka neće biti enkriptirana
# should not be used anymore:
signYes=Poruka će biti potpisana
signNo=Poruka neće biti potpisana
# PGP/MIME status:
pgpmimeNormal=Protokol: PGP/MIME
inlinePGPNormal=Protokol: Inline PGP
# smimeNormal=Protocol: S/MIME
pgpmimeAuto=Protokol: PGP/MIME (automatski)
inlinePGPAuto=Protokol: Inline PGP (automatski)
# smimeAuto=Protocol: S/MIME (auto)
# should not be used anymore
pgpmimeYes=PGP/MIME će biti korišten
pgpmimeNo=Inline PGP će biti korišten
# Attach own key status (tooltip strings):
attachOwnKeyNo=VaÅ¡ kljuÄ neće biti privijen
attachOwnKeyYes=VaÅ¡ kljuÄ Ä‡e biti privijen
attachOwnKeyDisabled=VaÅ¡ kljuÄ ne može biti privijen. Morate odabrati specifiÄan kljuÄ\nu OpenPGP sekciji Postavki raÄuna kako bi omogućili ovu znaÄajku.
rulesConflict=Otkrivena konfliktna pravila po primatelju\n%S\n\nPošalji poruku s ovim postavkama?
msgCompose.button.configure=&Postavi
msgCompose.button.send=&Pošalji poruku
msgCompose.button.save=&Spremi poruku
# Strings in enigmailMsgHdrViewOverlay.js
keyNeeded=Potreban je javni kljuÄ %S da bi verificirali potpis
keyUsed=Javni kljuÄ %S koriÅ¡ten za provjeru potpisa
clickDecrypt=; kliknite Dekriptiraj gumb
clickDecryptRetry=; kliknite Dekriptiraj gumb da bi pokušali ponovno
clickDetailsButton=; kliknite na 'Detalji' za više informacija
clickImportButton=; kliknite na 'Uvezi kljuÄ' da bi preuzeli kljuÄ
keyTypeUnsupported=; vrsta kljuÄa nije podržana od strane VaÅ¡e verzije GnuPG-a
msgPart=Dio poruke %S
msgSigned=potpisan
msgSignedUnkownKey=potpisano nepoznatim kljuÄem
msgEncrypted=enkriptiran
msgSignedAndEnc=potpisan i enkriptiran
unverifiedSig=Neverificiran potpis
incompleteDecrypt=Dekripcija nepotpuna
needKey=GreÅ¡ka - nije pronaÄ‘en odgovarajući privatni/tajni kljuÄ za dekripciju poruke
failedDecrypt=Greška - dekripcija nije uspjela
badPhrase=Greška - loša lozinka
failedDecryptVerify=Greška - dekripcija/verifikacija nije uspjela
viewInfo=; Pogledajte > Informacije o sigurnosti poruke za detalje
decryptedMsg=Dekriptiraj poruku
decryptedMsgWithFormatError=Dekriptirana poruka (obnovljen potrgani PGP email format vjerovatno uzrokovan starim Exchange poslužitelje, tako da bi rezultat mogao biti nesavrÅ¡en za Äitanje)
usedAlgorithms=Korišteni algoritmi: %S i %S
# pepStatusInfo.text=p≡p Message Status.
# pepStatusInfo.title.m3=Under Attack
# pepStatusInfo.info.m3=This message is not secure and has been tampered with.
# pepStatusInfo.title.m1=Mistrusted
# pepStatusInfo.info.m1=This message has a communication partner that has previously been marked as mistrusted
# pepStatusInfo.title.r0=Unknown
# pepStatusInfo.info.r0=This message does not contain enough information to determine if it is secure.
# pepStatusInfo.title.r1=Cannot Decrypt
# pepStatusInfo.info.r1=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r2=Cannot Decrypt
# pepStatusInfo.info.r2=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r3=Unsecure
# pepStatusInfo.info.r3=This message is unsecure.
# pepStatusInfo.title.r4=Unsecure for Some
# pepStatusInfo.info.r4=This message is unsecure for some communication partners.
# pepStatusInfo.title.r5=Unreliable Security
# pepStatusInfo.info.r5=This message has unreliable protection.
# pepStatusInfo.title.r6=Secure...
# pepStatusInfo.info.r6=This message is secure but you still need to verify the identity of your communication partner.
# pepStatusInfo.title.r7=Secure & Trusted
# pepStatusInfo.info.r7=This message is secure and trusted.
# pepStatusInfo.color.green=Green
# pepStatusInfo.color.yellow=Yellow
# pepStatusInfo.color.red=Red
# pepRevokeTrust.question=Do you really want to cancel the trust for %S?
# pepRevokeMistrust.question=Do you really want to re-trust the key for %S?
# pepRevokeTrust.doRevoke=Cancel &trust
# wksConfirmationReq=Web Key Directory Confirmation Request
# wksConfirmationReq.message=This message has been sent by your email provider to confirm deployment of your OpenPGP public key\nin their Web Key Directory.\nProviding your public key helps others to discover your key and thus being able to encrypt messages to you.\n\nIf you want to deploy your key in the Web Key Directory now, please click on the button "Confirm Request" in the status bar.\nOtherwise, simply ignore this message.
# wksConfirmationReq.button.label=Confirm Request
# autocryptSetupReq=Perform Autocrypt Setup
# autocryptSetupReq.button.label=Start Setup
# autocryptSetupReq.setupMsg.desc=This message contains all information to transfer your Autocrypt settings along with your secret key securely from your original device.
# autocryptSetupReq.setupMsg.backup=You can keep this message and use it as a backup for your secret key. If you want to do this, you should write down the password and store it securely.
# autocryptSetupReq.message.import=To import the settings and key(s) in Enigmail, please click on the "Start Setup" button in the status bar.
# autocryptSetupReq.message.sent=Please click on the message on your new device and follow the instuctions to import the settings.
# strings in pref-enigmail.js
# oldGpgVersion20=Enigmail initialization failed.\n\nYou are using GnuPG version %1$S, which is not supported anymore. Enigmail requires GnuPG version %2$S or newer. Please upgrade your GnuPG installation, or Enigmail will not work.
locateGpg=Lociraj GnuPG program
invalidGpgPath=GnuPG ne može biti izvršen s danom putanjom. Enigmail je deaktiviran dok ne promjenite putanju za GnuPG ili ne pokrenete ponovno aplikaciju.
warningsAreReset=Sva upozorenja su ponovno postavljena.
prefs.gpgFound=GnuPG je pronađen u %S
prefs.gpgNotFound=Nije pronađen GnuPG
prefs.warnAskNever=Upozorenje: aktiviranje ove opcije će rezultirati neenkriptiranim email-ovima bez daljnjih informacija u sluÄaju nedostatka kljuÄa za nekog od primatelja -- Enigmail Vas neće obavijestiti ako se to dogodi!
prefs.warnIdleTimeForUnknownAgent=Nije moguće spajanje s gpg-agent. Možda Vaš sustav koristi specijalizirani alat za upravljanje lozinkama (npr. gnome-keyring, seahorse-agent, KDE wallet manager...). Nažalost Enigmail ne može kontrolirati timeout lozinki za alat koji koristite. Zbog toga su pripadajuće postavke timeout-a u Enigmailu zanemarene.
prefEnigmail.oneKeyserverOnly=PogreÅ¡ka - možete odrediti samo jedan poslužitelj kljuÄeva za automatsko preuzimanje OpenPGP kljuÄeva koji nedostaju.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Molimo unesite administratorski PIN Vaše SmartCard
enterCardPin=Molimo unesite svoj SmartCard PIN
notInit=Pogreška - Enigmail usluga još nije inicijalizirana
badCommand=Pogreška - naredba enkripcije nije uspjela
cmdLine=naredbena linija i izlaz:
notRequired=Pogreška - enkripcija nije zahtjevana
notComplete=PogreÅ¡ka - generiranje kljuÄa joÅ¡ nije zavrÅ¡eno
invalidEmail=Pogreška - pogrešna email adresa ili adrese
noPassphrase=Pogreška - nije dana lozinka
noPGPblock=Pogreška - nije pronađen valjan oklopljeni OpenPGP blok podataka
unverifiedReply=UvuÄeni dio poruke (odgovor) je vjerovatno modificiran
keyInMessageBody=PronaÄ‘en kljuÄ u tjelu poruke. Stisnite 'Uvezi kljuÄ' kako bi uvezli kljuÄ
sigMismatch=Pogreška - potpisi se ne slažu
cantImport=PogreÅ¡ka pri uvozu javnog kljuÄa\n\n
doImportOne=Uvezi %1$S (%2$S)?
doImportMultiple=Uvezi sljedeće kljuÄeve?\n\n%S
previewFailed=Ne mogu proÄitati datoteku javnog kljuÄa.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=SmartCard %1$S pronaÄ‘ena u VaÅ¡em ÄitaÄu ne može biti koriÅ¡tena za obradu poruke.\nMolimo umetnite svoju SmartCard %S i ponovite operaciju.
sc.insertCard=Operacija zahtjeva Vašu SmartCard %S.\nMolimo umetnite zahtjevanu SmartCard i ponovite operaciju.
sc.removeCard=Operacija ne zahtjeva SmartCard u ÄitaÄu.\nMolimo uklonite svoju SmartCard i ponovite operaciju.
sc.noCardAvailable=Nije pronaÄ‘ena nijedna SmartCard u VaÅ¡em ÄitaÄu\nMolimo Vas umetnite SmartCard i ponovite operaciju.
sc.noReaderAvailable=VaÅ¡oj SmartCard se ne može pristupiti\nMolimo spojite VaÅ¡ SmartCard ÄitaÄ, umetnite karticu i ponovite operaciju.
keyError.keySpecNotFound=Email adresa "%S" ne može biti usporeÄ‘ena sa kljuÄem na VaÅ¡em privjesku kljuÄeva.
keyError.keyIdNotFound=Konfigurirani ID "%S" kljuÄa ne može biti pronaÄ‘en na VaÅ¡em privjesku kljuÄeva.
keyError.resolutionAction=Molimo odaberite ispravan kljuÄ u OpenPGP odjelu u Postavkama raÄuna.
missingPassphrase=Nedostaje lozinka
errorHandling.gpgAgentInvalid=Vaš sustav koristi verziju gpg-agent koja ne odgovara Vašoj GnuPG verziji.
errorHandling.gpgAgentError=GnuPG je prijavio pogrešku u komunikaciji s gpg-agent -om (komponenta GnuPG-a).
errorHandling.dirmngrError=GnuPG je prijavio pogrešku u komunikaciji s dirmngr-om (komponenta GnuPG-a).
errorHandling.pinentryError=GnuPG ne može poslati upit za Vašu lozinku putem unosa pin-a.
errorHandling.readFaq=Ovo je greÅ¡ka sustava ili konfiguracije koja onemogućava da Enigmail radi ispravno i ne može biti popravljena automatski.\n\nPreporuÄamo da se posavjetujete s naÅ¡om stranicom https://enigmail.net/faq.
gpgNotFound=Nije pronaÄ‘en GnuPG program '%S'.\nBudite sigurni da ste postavili toÄnu putanju do izvrÅ¡ne datoteke u Enigmail postavkama.
gpgNotInPath=Nije pronaÄ‘ena GnuPG izvrÅ¡na datoteka na PUTANJI.\nBudite sigurni da ste postavili toÄnu putanju do izvrÅ¡ne datoteke u Enigmail postavkama.
enigmailNotAvailable=Enigmail jezgrena usluga nije dostupna
prefGood=Dobar potpis od %S
prefBad=LOÅ potpis od %S
failCancel=PogreÅ¡ka - primanje kljuÄa otkazano od strane korisnika
failNoServer=PogreÅ¡ka - nije odreÄ‘en poslužitelj kljuÄeva s kojeg bi se preuzeo kljuÄ
failNoID=PogreÅ¡ka - nije odreÄ‘en ID kljuÄa za koji se preuzima kljuÄ
failKeyExtract=PogreÅ¡ka - naredba ekstrakcije kljuÄa nije uspjela
notFirstBlock=PogreÅ¡ka - Prvi OpenPGP blok nije blok javnog kljuÄa
importKeyConfirm=Uvezi javni kljuÄ(eve) ugraÄ‘en(e) u poruku?
failKeyImport=PogreÅ¡ka - uvoz kljuÄa nije uspio
fileWriteFailed=Pisanje u datoteku %S nije uspjelo
importKey=Uvezi javni kljuÄ %S sa poslužitelja kljuÄeva:
uploadKey=PoÅ¡alji javni kljuÄ %S na poslužitelj kljuÄeva:
keyId=ID kljuÄa
keyAndSigDate=ID kljuÄa: 0x%1$S / potpisan: %2$S
keyFpr=Otisak prsta kljuÄa: %S
noEmailProvided=Niste dali email adresu!
keyAlreadySigned=KljuÄ je već potpisan, ne možete ga potpisati dva puta.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=istekao %S
createdHeader=Stvoren
atLeastOneKey=Nije odabran kljuÄ! Morate odabrati najmanje jedan kljuÄ da bi prihvatili ovaj dijalog
fewerKeysThanRecipients=Odabrali ste manji broj kljuÄeva nego primatelja. Jeste li sigurni da je popis kljuÄeva za enkripciju potpun?
userSel.button.goBack=Odaberi viÅ¡e kljuÄeva
userSel.secretKeySel.title=Odabei tajni OpenPGP kljuÄ za potpisivanje poruka
userSel.problemNoKey=Nema važećih kljuÄeva
userSel.problemMultipleKeys=ViÅ¡estruki kljuÄevi
# should be same as thunderbird ENTITY sendLaterCmd.label:
sendLaterCmd.label=Pošalji kasnije
# Strings used in enigmailAttachmentDialog.js
# pgpMimeNote=NOTE: PGP/MIME is not supported by all email clients. If you are unsure, select the %S option.
first=prvu
second=drugu
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Odaberite OpenPGP kljuÄ za enkripciju
identityName=Identitet: %S
# switchPepMode=You are currently using the 'p≡p Junior' mode of Enigmail.\n\nBy enabling OpenPGP or S/MIME for an account, you are disabling p≡p and use the 'regular' mode of Enigmail without p≡p.
# enableEnigmail=&Disable p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=Aktivirali ste enkripciju ali niste odabrali kljuÄ. Kako bi enkriptirali email-ove poslane prema %1$S morate odrediti jedan ili viÅ¡e važećih kljuÄeva iz VaÅ¡eg popisa kljuÄeva. Želite li onemogućiti enkripciju za %2$S?
noKeyToUse=(ništa - bez enkripcije)
noEmptyRule=Pravilo ne smije biti prazno! Molimo Vas postavite email adresu u polju Pravila.
invalidAddress=Jedna ili više email adresa koje ste unijeli nisu valjane. Ne bi trebali postavljati imena primatelja, samo email adrese. Npr:\nNeispravno: Neko Ime \nIspravno: neko.ime@adresa.net
# noCurlyBrackets=The curly brackets {} have a special meaning and should not be used in an email address. If you want to modify the matching behavior for this rule, use the 'Apply rule if recipient ...' option.\nMore information is available from the Help button.
# Strings used in enigmailRulesEditor.js
never=Nikad
always=Uvijek
possible=Moguće
deleteRule=Stvarno obrisati odabrano pravilo?
nextRcpt=(Sljedeći primatelj)
negateRule=Ne
addKeyToRule=Dodaj kljuÄ %1$S (%2$S) pravilu po primatelju
# Strings used in enigmailSearchKey.js
needOnline=Funkcija koju ste odabrali nije dostupna u izvanmrežnom naÄinu rada. Molimo Vas da se povežete s mrežom i probate opet.
protocolNotSupported=Protokol '%S://' koji ste odabrali nije podržan za preuzimanje OpenPGP kljuÄeva.
gpgkeysDisabled=Možda bi pomoglo da omogućite opciju 'extensions.enigmail.useGpgKeysTool'.
noKeyserverConn=Spajanje na poslužitelj kljuÄeva %S nije uspjelo.
keyDownloadFailed=Preuzimanje kljuÄa s poslužitelja kljuÄeva nije uspjelo. Poruka je:\n%S
internalError=Dogodila se interna pogreÅ¡ka. KljuÄevi se nisu mogli preuzeti ili uvesti.
noKeyFound=Žao nam je, ali nismo mogli pronaći kljuÄ koji odgovara zadanim kriterijima pretrage.\nMolimo Vas da obratite pozornost da bi ID kljuÄa trebao poÄeti s "0x= (npr. 0xABCDEF12).
# keyDownload.keyUnavailable=We are sorry, but the key with ID %S is not available on the keyserver. Most likely, the owner of the key did not upload their key to the keyserver.\n\nPlease ask the sender of the message to send you their key by email.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Pretraga ili preuzimanje kljuÄa sa poslužitelja kljuÄeva nijo uspjelo: gpgkeys_%S nije moguće izvrÅ¡iti.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Postavljanje povjerenja valsnika nije uspjelo
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Potpisivanje kljuÄa nije uspjelo
alreadySigned.label=Napomena: kljuÄ %S je već potpisan s odabranim tajnim kljuÄem.
alreadySignedexportable.label=Napomena: kljuÄ %S je već potpisan za izvoz sa odabranim privatnim kljuÄem. Lokalni potpis nema smisla.
partlySigned.label=Napomena: neki ID-evi korisnika kljuÄa %S su već potpisani s odabranim tajnim kljuÄem.
noTrustedOwnKeys=Nije pronaÄ‘en kvalificirani kljuÄ za potpisivanje! Trebate barem jedan privatni kljuÄ kojem se potpuno vjeruje kako bi potpisivali kljuÄeve.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=UÄitavam kljuÄeve, priÄekajte...
keyValid.unknown=nepoznat
keyValid.invalid=neisprava
keyValid.disabled=onemogućen
keyValid.revoked=opozvan
keyValid.expired=istekao
keyValid.noSubkey=nema valjanog podkljuÄa
keyTrust.untrusted=nesiguran
keyTrust.marginal=marginalan
keyTrust.full=siguran
keyTrust.ultimate=ultimativan
keyTrust.group=(grupa)
keyType.public=javni
keyType.publicAndSec=javni/tajni
keyMan.enableKey=Omogući kljuÄ
keyMan.disableKey=Onemogući kljuÄ
userAtt.photo=Koristi atribut (JPEG slike)
asciiArmorFile=ASCII oklopljene datoteke (*.asc)
importKeyFile=Uvezi OpenPGP datoteku kljuÄa
gnupgFile=GnuPG datoteke
# createKeyOK=Your Key has been generated
saveRevokeCertAs=Stvori i pohrani certifikat za opoziv
# revokeCertOK=The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
revokeCertFailed=Certifikat za opoziv nije mogao biti stvoren.
addUidOK=KorisniÄki ID uspjeÅ¡no dodan
addUidFailed=Dodavanje korisniÄkog ID-a nije uspjelo
noKeySelected=Trebali bi odabrati barem jedan kljuÄ kako bi proveli odabranu operaciju
exportToFile=Izvezi javni kljuÄ u datoteku
exportKeypairToFile=Izvezi tajni i javni kljuÄ u datoteku
exportSecretKey=Želite li ukljuÄiti tajni kljuÄ u pohranjenu OpenPGP datoteku kljuÄa?
saveKeysOK=KljuÄevi uspjeÅ¡no pohranjeni
saveKeysFailed=Pohrana kljuÄeva nije uspjela
importKeysFailed=Uvoz kljuÄeva nije uspio
enableKeyFailed=Omogućivanje/onemogućivanje kljuÄeva nije uspjelo
specificPubKeyFilename=%1$S (0x%2$S) javni
specificPubSecKeyFilename=%1$S (0x%2$S) javni-tajni
defaultPubKeyFilename=Izvezeni-javni-kljuÄevi
defaultPubSecKeyFilename=Izvezeni-javni-i-tajni-kljuÄevi
noSecretKeys=Nisu pronaÄ‘eni tajni kljuÄevi.\n\nŽelite li generirati svoj kljuÄ sad?
sendKeysOk=KljuÄ(evi) poslan(i) uspjeÅ¡no
sendKeysFailed=Slanje kljuÄeva nije uspjelo
receiveKeysOk=KljuÄ(evi) uspjeÅ¡no ažuriran(i)
receiveKeysFailed=Preuzimanje kljuÄeva nije uspjelo
importFromClip=Želite li uvesti neke kljuÄeve iz meÄ‘uspremnika?
importFromUrl=Preuzmite javni kljuÄ sa ovog URL-a:
copyToClipbrdFailed=Kopiranje odabranih kljuÄeva u meÄ‘uspremnik nije moguće.
copyToClipbrdOK=KljuÄ(evi) kopiran(i) u meÄ‘uspremnik
deleteSecretKey=UPOZORENJE: PokuÅ¡avate obrisati tajni kljuÄ!\nAko obriÅ¡ete tajni kljuÄ, nećete viÅ¡e moći dekriptirati poruke enkriptirane za taj kljuÄ, i nećete viÅ¡e moći opozvati svoj kljuÄ.\n\nŽelite li uistinu obrisati OBA kljuÄa, tajni i javni?\n'%S'
deleteMix=UPOZORENJE: PokuÅ¡avate obrisati tajne kljuÄeve!\nAko obriÅ¡ete tajni kljuÄ, nećete viÅ¡e moći dekriptirati poruke enkriptirane za taj kljuÄ.\n\nŽelite li uistinu obrisati odabrane kljuÄeve, tajne i javne?
deletePubKey=Želite li obrisati javni kljuÄ\n'%S'?
deleteSelectedPubKey=Želite li obrisati javne kljuÄeve?
deleteKeyFailed=KljuÄ se ne može obrisati.
revokeKeyQuestion=Opozvati će te kljuÄ '%S'.\n\nViÅ¡e nećete biti u mogućnosti potpisivati ovim kljuÄem, i jednom distribuirano, ostali neće moći dekriptirati s tim kljuÄem. JoÅ¡ uvjek možete koristit kljuÄ za dekripciju starih poruka.\n\nŽelite li nastaviti?
revokeKeyOk=KljuÄ je opozvan. Ako je VaÅ¡ kljuÄ dostupan na poslužitelju kljuÄeva, preporuÄa se ponovno postavljanje tako da drugi mogu vidjeti opoziv.
revokeKeyFailed=KljuÄ se ne može opozvati.
# revokeKeyNotPresent=You have no key (0x%S) which fits to this revocation certificate!\n\nIf you have lost your key, you must import it (e.g. from a keyserver) before the revocation certificate!
# revokeKeyAlreadyRevoked=The key 0x%S has already been revoked.
refreshAllQuestion=Niste odabrali nijedan kljuÄ. Želite li osvježiti SVE kljuÄeve?
# refreshKeyServiceOn.warn=Warning: Your keys are currently being refreshed in the background as safely as possible.\nRefreshing all your keys at once will unnecessarily reveal information about you.\nDo you really want to do this?
refreshKey.warn=Upozorenje: ovisno o broju kljuÄeva i brzini veze, osvježenje svih kljuÄeva može biti dugotrajan proces!
downloadContactsKeys.warn=Upozorenje: ovisno o broju kontakta i brzini veze, preuzimanje kljuÄeva može biti dugotrajan proces!
downloadContactsKeys.importFrom=Uvesti kontakte iz adresara '%S'?
keyMan.button.exportSecKey=Izvezi &Tajne kljuÄeve
keyMan.button.exportPubKey=Izvezi samo &Javne kljuÄeve
keyMan.button.import=&Uvezi
keyMan.button.refreshAll=&Osvježi sve kljuÄeve
keyMan.button.revokeKey=&Opozovi kljuÄ
keyMan.button.skip=&PreskoÄi kljuÄ
keylist.noOtherUids=Nema drugih identiteta
keylist.hasOtherUids=Također poznat kao
keylist.noPhotos=Slika nije dostupna
keylist.hasPhotos=Slike
keyMan.addphoto.filepicker.title=Odaberite sliku za dodavanje
keyMan.addphoto.warnLargeFile=Datoteka koju ste odabrali je veća od 25 kB.\nNije preporuÄeno dodavati vrlo velike datoteke jer se tako povećavaju kljuÄevi.
keyMan.addphoto.noJpegFile=Izgleda da odabrana datoteka nije JPEG datoteka. Molimo Vas da odaberete drugu datoteku.
keyMan.addphoto.failed=Slika se ne može dodati.
# noWksIdentity=The key %S does not have a WKS identity.
# keyman.addBlacklistKey.msg=Do you really want p≡p to stop using the key "%1$S (%2$S)" for encrypting messages?
# keyman.removeBlacklistKey.msg=Do you want to allow p≡p to use key "%1$S (%2$S)" for future messages?
# keyman.addBlacklistKey.button=&Blacklist the key
# keyman.removeBlacklistKey.button=&Remove key from Blacklist
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Mijenjanje primarnog korisniÄkog ID-a nije uspjelo
changePrimUidOK=Primarni korisniÄki ID uspjeÅ¡no promijenjen
revokeUidFailed=Opoziv korisniÄkog ID-a %S nije uspio
revokeUidOK=KorisniÄki ID %S je uspjeÅ¡no opozvan. Ako je VaÅ¡ kljuÄ dostupan na poslužitelju kljuÄeva, preporuÄa se ponovno postavljanje, tako da ostali mogu vidjeti opoziv.
revokeUidQuestion=Želite li stvarno opozvati korisniÄki ID %S?
# Strings in enigmailKeyImportInfo.xul
importInfoTitle=USPJEH! KljuÄevi uvedeni
importInfoBits=Bitovi
importInfoCreated=Stvoreno
importInfoFpr=Otisak prsta
importInfoDetails=(Detalji)
importInfoNoKeys=Nema uvedenih kljuÄeva.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=javni kljuÄ
keyTypePrimary=primarni kljuÄ
keyTypeSubkey=podkljuÄ
keyTypePair=par kljuÄeva
keyExpiryNever=nikad
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
keyAlgorithm_18=ECC
keyAlgorithm_19=ECC
keyAlgorithm_20=ELG
keyAlgorithm_22=EDDSA
keyUsageEncrypt=Enkriptiraj
keyUsageSign=Potpiši
keyUsageCertify=Certificiraj
keyUsageAuthentication=Autentikacija
keyDoesNotExpire=KljuÄ ne istiÄe
# Strings in enigmailGenCardKey.xul
keygen.started=Molimo priÄekajte dok se kljuÄ generira...
keygen.completed=KljuÄ generiran. Novi ID kljuÄa je: 0x%S
keygen.keyBackup=Sigurnosna kopija kljuÄa je %S
keygen.passRequired=Molimo Vas da odredite lozinku ako želite stvoriti sigurnosnu kopiju VaÅ¡eg kljuÄa izvan SmartCard-a.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=Promjena PIN-a nije uspjela
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Osvježujem kljuÄeve, priÄekajte...
keyserverProgress.uploading=Postavljam kljuÄeve, priÄekajte...
# keyserverProgress.wksUploadFailed=Could not upload your key to the Web Key Service
# keyserverProgress.wksUploadCompleted=Your public key was successfully submitted to your provider. You will receive an email to confirm that you initiated the upload.
keyserverTitle.refreshing=Osvježi kljuÄeve
keyserverTitle.uploading=Postavljanje kljuÄa
# Strings in enigmailSetupWizard
passphrase.min8keys=Vaša lozinka bi trebala sadržavati najmanje 8 znakova!
setupWizard.reallyCancel=Želite li stvarno zatvoriti Enigmail Äarobnjak za postavljanje?
setupWizard.invalidGpg=Datoteka koju ste odredili nije izvršna datoteka GnuPG-a. Molimo odredite drugu datoteku.
setupWizard.specifyFile=Morate odrediti barem javni kljuÄ da bi nastavili.
setupWizard.installFailed=Izgleda da instalacija nije uspjela. Ili ponovno pokuÅ¡ajte ili instalirajte GnuPG ruÄno te ga locirajte koristeći Pregledaj gumb.
# setupWizard.downloadForbidden=For your own security, we will not download GnuPG. Please visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.downloadImpossible=We cannot download GnuPG currently. Please try later or visit https://gnupg.org/ in order to download GnuPG.
setupWizard.hashSumError=Čarobnjak nije mogao potvrditi integritet preuzete datoteke. Datoteka može biti oštećena ili obrađivana od treće strane. Želite li svejedno nastaviti instalaciju?
setupWizard.importSettingsFile=Odredite datoteku sigurnosne kopije iz koje će se uÄitavati
setupWizard.invalidSettingsFile=Specificirana datoteka nije toÄna Enigmail datoteka sigurnosne kopije postavki.
setupWizard.gpgConfExists=Datoteka GnuPG postavki već postoji. Želite li ju prepisati s onom iz stare instalacije?
# setupWizard.noGpgHomeDir=It appears that you configured %S to use for GnuPG. However, this is not a directory - you cannot use it.
# setupWizard.unmachtedIds=The following identities of your old setup could not be matched:\n%S\nThe settings for these identities were skipped.
# Strings in installGnuPG.jsm
installGnuPG.downloadFailed=Dogodila se pogreška pri preuzimanju GnuPG-a. Molimo provjerite konzolni zapis za daljnje detalje.
installGnuPG.installFailed=Dogodila se pogreška prilikom instalacije GnuPG-a. Provjerite konzolni zapis za daljnje detalje.
# Strings in enigmailAddUidDlg.xul
addUidDlg.nameOrEmailError=Morate ispuniti ime i email adresu.
addUidDlg.nameMinLengthError=Ime mora imati minimalno 5 znakova
addUidDlg.invalidEmailError=Morate odrediti valjanu email adresu
# Strings in enigmailCardDetails.js
Carddetails.NoASCII=OpenPGP SmartCard podržava jedino ASCII znakove u imenu/prezimenu.
# network error types
errorType.SecurityCertificate=Sigurnosni certifikat pružen od strane web usluge nije valjan.
errorType.SecurityProtocol=Sigurnosni protokol korišten od strane web usluge je nepoznat.
errorType.Network=Dogodila se mrežna pogreška.
# filter stuff
filter.folderRequired=Morate odabrati ciljnu mapu.
filter.decryptMove.label=Dekriptiraj trajno (Enigmail)
filter.decryptCopy.label=Kreiraj dekriptiranu kopiju (Enigmail)
filter.decryptMove.warnExperimental=Upozorenje - filter akcija "Dekriptiraj trajno" može dovesti do uniÅ¡tenih poruka.\n\nSnažno preporuÄamo da prvo probate filter "Kreiraj dekriptiranu kopiju", pozorno testirate rezultate, te poÄnete koristit ovaj filter tek kad ste zadovoljni rezultatima.
# filter.tempPepFilterDesc=Temporary filter to store sent message unencrypted
# filter.term.pgpencrypted.label=OpenPGP Encrypted
# filter.encrypt.label=Encrypt to key (Enigmail)
# filter.keyRequired=You must select a recipient key.
# filter.keyNotFound=Could not find an encryption key for "%S".
# filter.warn.keyNotSecret=Warning - the filter action "Encrypt to key" replaces the recipients.\n\nIf you do not have the secret key for "%S" you will no longer be able to read the emails.
# strings in enigmailConvert.jsm
converter.decryptBody.failed=Nije uspjelo dekriptiranje poruke s predmetom\n"%S".\nŽelite li pokuÅ¡ati ponovno s drugom lozinkom ili želite preskoÄiti poruku?
converter.decryptAtt.failed=Nije uspjelo dekriptiranje privitka "%1$S"\nporuke s predmetom\n"%2$S".\nŽelite li pokuÅ¡ati ponovno s drugom lozinkom ili želite preskoÄiti poruku?
saveLogFile.title=Pohrani datoteku zapisa
# strings in gpg.jsm
unknownSigningAlg=Nepoznat algoritam potpisivanja (ID: %S)
unknownHashAlg=Nepoznat kriptografski hash (ID: %S)
# strings in keyRing.jsm
keyring.photo=Slika
keyRing.pubKeyRevoked=KljuÄ %1$S (ID kljuÄa %2$S) je opozvan.
keyRing.pubKeyExpired=KljuÄ %1$S (ID kljuÄa %2$S) je istekao.
keyRing.pubKeyNotForSigning=KljuÄ %1$S (ID kljuÄa %2$S) ne može biti koriÅ¡ten za potpisivanje.
keyRing.pubKeyNotForEncryption=KljuÄ %1$S (ID kljuÄa %2$S) ne može biti koriÅ¡ten za enkripciju.
keyRing.keyDisabled=KljuÄ %1$S (ID kljuÄa %2$S) je onemogućen; ne može biti koriÅ¡ten.
keyRing.keyNotTrusted=KljuÄu %1$S (ID kljuÄa %2$S) se ne vjeruje dovoljno. Molimo postavite razinu povjerenja na "ultimativno" kako bi ga koristili za potpisivanje.
keyRing.keyInvalid=KljuÄ %1$S (ID kljuÄa %2$S) je nevažeći (možda nema samo-potpis).
keyRing.signSubKeysRevoked=Svi poptisni podkljuÄevi kljuÄa %1$S (ID kljuÄa %2$S) su opozvani.
keyRing.signSubKeysExpired=Svi poptisni podkljuÄevi kljuÄa %1$S (ID kljuÄa %2$S) su istekli.
keyRing.signSubKeysUnusable=Svi poptisni podkljuÄevi kljuÄa %1$S (ID kljuÄa %2$S) su opozvani, istekli ili drugaÄije neiskoristivi.
keyRing.encSubKeysRevoked=Svi enkripcijski podkljuÄevi kljuÄa %1$S (ID kljuÄa %2$S) su opozvani.
keyRing.encSubKeysExpired=Svi enkripcijski podkljuÄevi kljuÄa %1$S (ID kljuÄa %2$S) su istekli.
keyRing.noSecretKey=Izgleda da nemate tajni kljuÄ za %1$S (ID kljuÄa %2$S) na VaÅ¡em privjesku kljuÄeva; ne možete koristiti taj kljuÄ za potpisivanje.
keyRing.encSubKeysUnusable=Svi enkripcijski podkljuÄevi kljuÄa %1$S (ID kljuÄa %2$S) su opozvani, istekli ili drugaÄije neiskoristivi.
#strings in exportSettingsWizard.js
cannotWriteToFile=Ne može se spremiti u datoteku '%S'. Molimo odredite drugu datoteku.
dataExportError=Došlo je do greške prilikom izvoza Vaših podataka.
enigmailSettings=EnigmailPostavke
defaultBackupFileName=Enigmail-izvoz
specifyExportFile=Odredite ime za izvoz
homedirParamNotSUpported=Dodatni parametri koji konfiguriraju putanje, primjerice --homedir i --keyring nisu podržani za izvoz/uvoz Vaših postavki. Molimo koristite alternativne metode, primjerice postavite varijablu okoline na GNUPGHOME.
#strings in expiry.jsm
expiry.keyExpiresSoon=VaÅ¡ kljuÄ %1$S istiÄe za manje od %2$S dana.\n\nPreporuÄamo da stvorite novi par kljuÄeva i postavite raÄune tako da ih koriste.
# expiry.keysExpireSoon=The following of your keys will expire in less than %1$S days:\n%2$S We recommend that you create new keys and configure your accounts to use the new keys.
# expiry.keyMissingOwnerTrust=Your secret key %S has missing trust.\n\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.keysMissingOwnerTrust=The following of your secret keys have missing trust.\n%S.\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.OpenKeyManager=Open Enigmail Key Management
# expiry.OpenKeyProperties=Open Key Properties
#strings in pEpDecrypt.jsm
# pEpDecrypt.cannotDecrypt=This is an encrypted message. Unfortunately you don't have the secret key to decrypt the message.
#strings in gpgAgent.jsm
# gpghomedir.notexists=The directory '%S' containing your OpenPGP keys does not exist and cannot be created.
# gpghomedir.notwritable=The directory '%S' containing your OpenPGP keys is not writable.
# gpghomedir.notdirectory=The directory '%S' containing your OpenPGP keys is a file instead of a directory.
# gpghomedir.notusable=Please fix the directory permissions or change the location of your GnuPG "home" directory. GnuPG cannot work correctly otherwise.
#strings in pepTrustWords.js
# pepTrustWords.cannotVerifyOwnId=Cannot verify p≡p Trustwords for own account.
# pepTrustWords.cannotFindKey=Cannot find key for %S.
# pepTrustWords.cannotStoreChange=Could not change trust for %S.
# pepTrustWords.generalFailure=Cannot obtain trustwords for %S.
# pepTrustWords.partnerFingerprint=Fingerprint for %S:
#strings in mimeWkdHandler.jsm
# wkdMessage.body.req=Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.\n\nPlease click the confirmation button in the Enigmail header to complete the publishing of your public key.
# wkdMessage.body.process=This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.\n\nYou do not need to take any manual action at this point.
#strings in pepHandshake.js
# pepPrivacyStatus.RatingBrokenSuggestion=Either you or the sender should resend the message.
# pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=If you composed this message, your key is not available.
# pepPrivacyStatus.RatingMistrustSuggestion=Re-establish the connection with your communication partner and try to complete another handshake.
# pepPrivacyStatus.RatingReliableSuggestion=Complete a handshake with your communication partner by exchanging trustwords in person or over the phone. A handshake is needed only once per partner and will ensure secure and trusted communication.
# pepPrivacyStatus.RatingTrustedSuggestion=No action needed!
# pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Be aware this message may not be secure.
# pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=Please add the necessary information.
# pepPrivacyStatus.RatingUnderAttackSuggestion=Separately verify the content of this message with your communication partner.
# pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Make sure the privacy status for each communication partner listed is at least secure.
# pepPrivacyStatus.RatingUnencryptedSuggestion=Please ask your communication partner to use an encryption solution or install p≡p.
# pepPrivacyStatus.RatingUnreliableSuggestion=This message has no reliable encryption or no signature. Ask your communication partner to upgrade their encryption solution or install p≡p.
# pepPrivacyStatus.RatingBrokenExplanation=This message has broken encryption or formatting.
# pepPrivacyStatus.RatingHaveNoKeyExplanation=This message cannot be decrypted because the key is not available.
# pepPrivacyStatus.RatingMistrustExplanation=This message has a communication partner that has previously been marked as mistrusted.
# pepPrivacyStatus.RatingReliableExplanation=This message is secure but you still need to verify the identity of your communication partner.
# pepPrivacyStatus.RatingTrustedExplanation=This message is secure and trusted.
# pepPrivacyStatus.RatingUndefinedExplanation=This message does not contain enough information to determine if it is secure.
# pepPrivacyStatus.RatingUnderAttackExplanation=This message is not secure and has been tampered with.
# pepPrivacyStatus.RatingUnencryptedExplanation=This message is unsecure.
# pepPrivacyStatus.RatingUnencryptedForSomeExplanation=This message is unsecure for some communication partners.
# pepPrivacyStatus.RatingUnreliableExplanation=This message has unreliable protection.
# pepPrivacyStatus.RatingBrokenText=Broken
# pepPrivacyStatus.RatingHaveNoKeyText=Cannot Decrypt
# pepPrivacyStatus.RatingMistrustText=Mistrusted
# pepPrivacyStatus.RatingReliableText=Secure
# pepPrivacyStatus.RatingTrustedText=Secure & Trusted
# pepPrivacyStatus.RatingUndefinedText=Unknown
# pepPrivacyStatus.RatingUnderAttackText=Under Attack
# pepPrivacyStatus.RatingUnencryptedForSomeText=Unsecure for Some
# pepPrivacyStatus.RatingUnencryptedText=Unsecure
# pepPrivacyStatus.RatingUnreliableText=Unreliable Security
# handshakeDlg.button.initHandshake=Handshake...
# handshakeDlg.button.stopTrust=Stop Trusting
# handshakeDlg.button.reTrust=Stop Mistrusting
# handshakeDlg.label.outgoingMessage=Outgoing message
# handshakeDlg.label.incomingMessage=Incoming message
# handshakeDlg.error.noPeers=Cannot handshake without any correspondents.
# handshakeDlg.error.noProtection=Please enable protection in order to use the Handshake function.
# enigmail.acSetupPasswd.descEnterPasswd=Please enter the setup code that is displayed on the other device
# enigmail.acSetupPasswd.descCopyPasswd=Please enter the setup code below on your other device to proceed with the setup
#strings in autocrypt.jsm
# autocrypt.setupMsg.subject=Autocrypt Setup Message
# autocrypt.setupMsg.msgBody=To set up your new device for Autocrypt, please follow the instuctions that should be presented by your new device.
# autocrypt.setupMsg.fileTxt=This is the Autocrypt setup file used to transfer settings and keys between clients. You can decrypt it using the setup code presented on your old device, and then import the contained key into your keyring.
#strings in upgradeInfo.html
# upgradeInfo.doctitle=What's New in Enigmail v2.0?
# upgradeInfo.welcome1=Welcome to the new Enigmail version 2.0!
# upgradeInfo.welcome2=The release contains a lot of new and changed features. Please take a minute to find out what's new:
# upgradeInfo.encSubject.title=Encrypting the Message Subject
# upgradeInfo.encSubject.desc=We developed a new method that moves the email subject into the encrypted message, and replaces the visible subject with "Encrypted Message". Once such a message is decrypted, the original subject is replaced automatically. Hiding the subject is on by default; there is a preference to turn it off if you don't like it. (Note: this feature requires the message to be sent with PGP/MIME.)
# upgradeInfo.buttons.title=Changed behavior of Encrypt and Sign Buttons
# upgradeInfo.buttons.desc=The Encrypt and Sign buttons in the message composer window now work for both the OpenPGP and S/MIME protocols. If both algorithms are possible, then Enigmail will try to prefer the one for which all keys are available.
# upgradeInfo.autocrypt.title=Support for Autocrypt
# upgradeInfo.autocrypt.desc=Enigmail now supports Autocrypt, a new standard to distribute keys as part of sent messages. Enigmail automatically imports keys from Autocrypt-compliant messages, such that over time more and more emails can be encrypted.
# upgradeInfo.pEp.title=New p≡p Junior Mode (Pretty Easy Privacy)
# upgradeInfo.pEp.desc=Enigmail now contains a p≡p Junior Mode. You currently need to manually install p≡p for this purpose; this will change in a future release. The p≡p Junior Mode allows you to use OpenPGP encryption as transparently as possible; you don't need to care for key management and synchronization of keys between devices anymore.
# upgradeInfo.bottom.desc=Please visit our documentation for help on using Enigmail.
# pep.missingGnuPG=In order to use Enigmail/p≡p, GnuPG is required. As we could not find it, we suggest to download and install it for you.
#strings in enigmailAbout.html
# aboutEnigmail.tabName=About Enigmail
# aboutEnigmail.title=OpenPGP support provided by Enigmail
# aboutEnigmail.team=Enigmail is developed by the Enigmail Team:
# aboutEnigmail.projectLeader=Lead Developer:
# aboutEnigmail.usability=Usability:
# aboutEnigmail.documentation=Documentation:
# aboutEnigmail.testing=Testing:
# aboutEnigmail.userSupport=User Support:
# aboutEnigmail.localization=Localization: See the Enigmail Language Packs page
# aboutEnigmail.Credits=Credits:
# aboutEnigmail.origAuthor=Original author of the Enigmail extension
# aboutEnigmail.icons=Icons:
# aboutEnigmail.formerMembers=Former team members:
# aboutEnigmail.projectHosting=Project hosting:
# aboutEnigmail.licenseSupportTitle=License & Support
# aboutEnigmail.license=Enigmail OpenPGP is open source and licensed under the %S
# aboutEnigmail.support=Support and download is available from www.enigmail.net.
enigmail-2.0.8/lang/hr/help/ 0000775 0000000 0000000 00000000000 13343027545 0015576 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/hr/help/compose.html 0000664 0000000 0000000 00000010076 13343027545 0020135 0 ustar 00root root 0000000 0000000
Enigmail Help: Message Composition
Enigmail Help
Using Enigmail when composing messages
Enigmail menu in Mail/Compose window
Sign message
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit Per-Recipient Rule
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.
Set Enigmail Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the Enigmail Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
Decrypt button in main Mail window
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Opening encrypted attachments / importing attached OpenPGP keys
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
enigmail-2.0.8/lang/hr/help/initError.html 0000664 0000000 0000000 00000004552 13343027545 0020447 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing Enigmail
Enigmail Help
How to Resolve Problems with Initializing Enigmail
There 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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of Enigmail to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit Per-Recipient Rule
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.
Set Enigmail Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the Enigmail Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
Decrypt button in main Mail window
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Opening encrypted attachments / importing attached OpenPGP keys
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
enigmail-2.0.8/lang/hu/help/initError.html 0000664 0000000 0000000 00000004552 13343027545 0020452 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing Enigmail
Enigmail Help
How to Resolve Problems with Initializing Enigmail
There 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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of Enigmail to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Usare Enigmail durante la composizione dei messaggi
Menu di Enigmail nella finestra di Composizione dei messaggi
Firma il messaggio: Abilita/disabilita l'invio del messaggio firmato. L'utente viene avvertito se l'operazione di firma fallisce.
Cifra il messaggio: Abilita/disabilita la cifratura per tutti i destinatari prima dell'invio. L'utente viene avvertito se l'operazione di cifratura fallisce.
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.
Usa PGP/MIME per questo messaggio: Abilita/disabilita l'uso del formato PGP/MIME
per il messaggio corrente.
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.
Impostazioni predefinite per la composizione: Sotto-menu.
Impostazioni di firma/cifratura...: scorciatoia per Configurazione account posta ->
OpenPGP.
Impostazioni di invio...: scorciatoia per Impostazioni ->
invio.
Impostazioni per la scelta della chiave...: scorciatoia per Impostazioni ->
Scelta della chiave.
Impostazioni PGP/MIME...: scorciatoia per Impostazioni ->
PGP/MIME.
Annulla cifratura: Se si verifica un problema durante l'invio
del messaggio, se ad esempio il server rifiuta la richiesta, Enigmail non
avrà modo di saperlo e il messaggio continuerà ad
essere mostrato in formato cifrato nella finestra di composizione. Scegliendo
questa voce di menu, la firma/cifratura verranno annullate e nella
finestra di composizione apparirà nuovamente il testo in chiaro. Come soluzione temporanea, questa opzione può anche essere usata per
decifrare il testo quotato quando si risponde a un messaggio cifrato. Enigmail
dovrebbe decifrare automaticamente il messaggio quotato, ma se cioò non
dovesse funzionare per qualche ragione, puoi usare questa voce di menu.
Inserisci chiave pubblica: inserisci una chiave pubblica in formato
ASCII-armored a partire dalla posizione corrente del cursore nella finestra di
composizione. Ti verranno chiesti gli indirizzi email delle chiavi da inserire.
Le chiavi inserite in questo modo saranno automaticamente riconosciute da
Enigmail sul computer del destinatario. Dopo l'inserimento della chiave,
puoi ancora scegliere di cifrare/firmare il messaggio, se necessario. Attenzione
a non inserire più di un blocco di chiavi pubbliche in un messaggio;
specifica nel caso più indirizzi email, separati da virgole o spazi, per
lo stesso blocco.
Cancella la passphrase memorizzata: Cancella la passphrase salvata in memoria. Utile se hai più di una passphrase.
Aiuto: Mostra le informazioni di aiuto (questa pagina).
Usare l'editor delle regole di Enigmail: Modifica di una regola OpenPGP
Nell'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.
Imposta regole OpenPGP per : Contiene gli
indirizzi email dei destinatari (senza i nomi, ovvero solo indirizzi del tipo
nome.cognome@indirizzo.email). Puoi specificare indirizzi multipli,
separati sa spazi.
Gli indirizzi specificati qui possono consistere anche del solo dominio, in modo da
comprendere tutti i destinatari di quel dominio, ad esempio @indirizzo.email
corrisponderà sia a nome@indirizzo.email,
nome2@indirizzo.email, nome3@indirizzo.email, ecc.
Applica la regola se il destinatario ...:
Questo modifica la corrispondenza dell'indirizzo email.
Se sono stati specificati indirizzi multipli, l'impostazione si applica a tutti.
Gli esempi qui sotto assumono che si stato immesso l'indirizzo nome@indirizzo.email
nel campo Regole OpenPGP sopra.
È esattamente: con questa impostazione, la regola viene
applicata solo ai messaggi indirizzati a nome@indirizzo.email
(corrispondenza esatta, maiuscole/minuscole ignorate).
Contiene: con questa impostazione, la regola si applica a ogni
indirizzo contenente quello specificato,
ad esempio tuo.nome@indirizzo.email o altro.nome@indirizzo.email.suo
Comincia con: con questa impostazione, la regola viene applicata a
ogni indirizzo che inizia con quello specificato, ad esempio
nome@indirizzo.email.suo, nome@indirizzo.email-2.suo.
Finisce con: Con questa impostazione la regola viene applicata a
ogni indirizzo che finisce con quello specificato, ad esempio
tuonome@indirizzo.email o altro.nome@indirizzo.email
Continua con la regola successiva per l'indirizzo corrispondente
Abilitare questa funzione ti permette di definire una regola senza dover specificare
un ID chiave nel campo Usa le seguenti chiavi OpenPGP:. In tal caso la
chiave da usare sarà scelta al momento dell'invio in base all'indirizzo email
del destinatario. Inoltre, saranno anche applicate le eventuali ulteriori regole per
lo stesso indirizzo.
Non controllare le regole successive per l'indirizzo corrispondente
Abilitando questa funzione si impedisce l'applicazione di qualunque altra regola per
gli indirizzi corrispondenti, se questa regola viene applicata; il controllo delle
regole passa al destinatario seguente.
Usa le seguenti chiavi OpenPGP:
Usa il pulsante Seleziona chiave/i.. per scegliere la chiave pubblica del
destinatario da usare per la cifratura. Come nel caso precedente, nessuna ulteriore
regola viene applicata allo stesso indirizzo.
Impostazioni predefinite per... Firma:
abilita o disabilita
l'invio di messaggi firmati. Questa impostazione usa o ha la precedenza su
quella specificata nella finestra di composizione del messaggio. I valori
possibili sono:
Mai: disabilita la firma, anche se è attivata nella
finestra di composizione del messaggio (ha la precedenza sulle altre
impostazioni)
Sì, se selezionato durante la composizione del messaggio:
usa l'impostazione specificata nella finestra
di composizione del messaggio
Sempre: abilita la firma, anche se essa non è abilitata nella
finestra di composizione del messaggio
Le impostazioni sulla firma vengono
applicate per tutte le regole che corrispondono. Se una regola disabilita
la firma, il messaggio non verrà firmato, indipendentemente dalle
altre eventuali regole che specificano Sempre.
Impostazioni predefinite per... Cifratura: abilita o disabilita
la cifratura del messaggio. Le possibili impostazioni sono le stesse della
firma e hanno lo stesso significato.
Impostazioni predefinite per...
PGP/MIME:abilita o disabilita
l'uso della codifica PGP/MIME (RFC 3156) per il messaggio.
Se PGP/MIME è disabilitato, i messaggi saranno codificati
usando "inline PGP". Le possibili impostazioni sono le stesse della
firma e hanno lo stesso significato.
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.
enigmail-2.0.8/lang/it/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020451 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
Pulsante Decifra nella finestra principale della posta
Questo pulsante può essere usato per molti scopi: decifrare,
verificare, o importare chiavi pubbliche. Di solito, la decifratura/verifica
dei messaggi viene fatta automaticamente, anche se questo può essere
disabilitato nelle impostazioni. Tuttavia, in caso di errori, apparirebbe
solo un breve messaggio nella barra di stato di Enigmail. Se premi il pulsante
Decifra, verrà mostrato un messaggio di errore più dettagliato,
che include anche l'output esatto di GnuPG.
Icone della penna e della chiave tra le intestazioni del messaggio
Le icone Penna e Chiave tra le intestazioni del messaggio
indicano se esso è stato cifrato/firmato e se la firma è valida,
cioè se il messaggio non è stato modificato dopo la firma. Se ci
sono state modifiche, l'icona Penna apparirà come una Penna
spezzata per indicare che la firma non è valida. Premendo con il tasto
destro sulla penna o sulla chiave si visualizzerà un menu con le
seguenti opzioni:
Informazioni di sicurezza OpenPGP: mostra l'output di GnuPG per il
messaggio.
Copia le informazioni di sicurezza OpenPGP: copia l'output di GnuPG
negli appunti, ad esempio per incollarlo in un messaggio, ecc.
Mostra la foto-ID OpenPGP: Visualizza la Foto-ID del
mittente del messaggio, se una foto è presente nella sua chiave pubblica.
(Questa opzione è attiva solo se c'è una foto nella chiave
pubblica.)
Informazioni di sicurezza S/MIME: mostra le informazioni di sicurezza
S/MIME per il messaggio.
Se 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.
Apertura di allegati cifrati / importazioni di chiavi OpenPGP allegate
Gli allegati con estensioni *.pgp, *.asc e *.gpg sono riconosciuti da Enigmail
come allegati da trattare in modo speciale. Premendo con il tasto destro su tali
allegati, appariranno due speciali voci del menu contestuale: Decifra e
apri e Decifra e salva. Usa queste due voci se vuoi che Enigmail
decifri un allegato prima di aprirlo o salvarlo. Se un allegato è riconosciuto
essere una chiave OpenPGP, ti sarà offerta la possibilità di importarla
nel tuo portachiavi.
Nell'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:
Email: L'indirizzo email che
compare nei campi A:, Cc: e Bcc:. La corrispondenza funziona anche per
sottostringhe (Ulteriori dettagli
possono essere trovati nella finestra di dialogo Modifica regola)
Chiave/i OpenPGP: una lista di ID
chiave OpenPGP da usare per il destinatario
Firma: abilita o disabilita
l'invio di messaggi firmati. Questa impostazione usa o ha la precedenza su
quella specificata nella finestra di composizione del messaggio. I valori
possibili sono:
Mai: disabilita la firma, anche se è attivata nella
finestra di composizione del messaggio (ha la precedenza sulle altre
impostazioni)
Possibile: usa l'impostazione specificata nella finestra
di composizione del messaggio
Sempre: abilita la firma, anche se essa non è abilitata nella
finestra di composizione del messaggio
Le impostazioni sulla firma vengono
applicate per tutte le regole che corrispondono. Se una regola disabilita
la firma, il messaggio non verrà firmato, indipendentemente dalle
altre eventuali regole che specificano Sempre.
Cifra: abilita o disabilita
la cifratura del messaggio. Le possibili impostazioni sono le stesse della
firma e hanno lo stesso significato.
PGP/MIME: abilita o disabilita
l'uso della codifica PGP/MIME (RFC 3156) per il messaggio.
Se PGP/MIME è disabilitato, i messaggi saranno codificati
usando "inline PGP". Le possibili impostazioni sono le stesse della
firma e hanno lo stesso significato.
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
enigmail-2.0.8/lang/ko/help/initError.html 0000664 0000000 0000000 00000004430 13343027545 0020442 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/lt/ 0000775 0000000 0000000 00000000000 13343027545 0014654 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/lt/am-enigprefs.properties 0000664 0000000 0000000 00000000121 13343027545 0021341 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=OpenPGP saugumas
enigmail-2.0.8/lang/lt/enigmail.dtd 0000664 0000000 0000000 00000174525 13343027545 0017154 0 ustar 00root root 0000000 0000000
"Mozilla" viešąją licenciją 2.0.">
"">
“ nurodant el. pašto adresus">
“ simbolius, siekiant nurodyti el. pašto adresus, skirtus GnuPG. Išjunkite, jei gavėjai turi senus „Hushmail“ raktus.">
OpenPGP saugumas)">
PASTABA: Rakto generavimas gali užtrukti kelias minutes. Neužverkite programos, kol vyksta rakto generavimas. Aktyviai naršant ar atliekant operacijas, kurios reikalauja intensyvaus disko naudojimo, rakto generavimo metu padės sukurti atsitiktinesnį raktą ir pagreitins procesą. Jums bus pranešta, kai rakto generavimas bus baigtas.">
“ yra netinkamas">
PASTABA: Rakto generavimas gali užtrukti kelias minutes. Neužverkite programos, kol generuojamas raktas. Jums bus pranešta, kai raktas bus sugeneruotas.">
Pastaba: Enigmail visada patikrins visų paskyrų ir tapatybių parašus
nepaisant ar įjungta ar išjungta">
viešasis raktas yra skirtas kitiems, kad jie siųstų jums šifruotus laiškus. Jūs galite juo dalintis su visais.">
privatusis raktas yra skirtas jums, kad iššifruotumėte šiuos el. laiškus ir siųstumėte pasirašytus el. laiškus.
Jūs neturėtumėte jo niekam perduoti.">
privatusis raktas yra skirtas jums, kad iššifruotumėte šiuos el. laiškus ir siųstumėte pasirašytus el. laiškus.
Jūs neturėtumėte jo niekam perduoti.
Norint apsaugoti jūsų privatųjį raktą, kituose dviejuose dialogo languose jūsų bus paklausta slaptafrazės.">
slaptafrazė yra slaptažodis, skirtas apsaugoti jūsų privatųjį raktą. Jis neleidžia netinkamai naudoti jūsų privatųjį raktą.">
nerekomenduojami.">
Šiam reikalui jūsų bus paprašyta įvesti slaptažodį. Perkelkite liudijimą į laikmeną, kaip pavyzdžiui, CD ar USB atmintukas, kurį gali būti saugiai atskirai laikoma. Jei koks nors asmuo gaus prieigą prie šio liudijimo, jis galės padaryti jūsų raktą netinkamą naudoti.">
eksportuokite savo duomenis iš seno kompiuterio, naudodami atsarginės kopijos vediklį, esantį Enigmail nuostatoseimportuokite duomenis į savo naująjį kompiuterį, naudodami šį vediklį.
">
DÄ—kui jog naudojate Enigmail.">
eksportuokite savo duomenis iš seno kompiuterio, naudodami šį vediklįimportuokite duomenis į savo naująjį kompiuterį, naudodami sąrankos vediklį.
">
enigmail-2.0.8/lang/lt/enigmail.properties 0000664 0000000 0000000 00000154144 13343027545 0020570 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Enigmail įspėjimas
enigConfirm=Enigmail patvirtinimas
enigInfo=Enigmail informacija
enigError=Enigmail klaida
enigPrompt=Enigmail įvedimas
dlgYes=&Taip
dlgNo=&Ne
dlgKeepSetting=Prisiminti atsakymÄ… ir daugiau nebeklausti
dlgNoPrompt=Daugiau neberodyti šio pranešimo
dlg.button.delete=&Ištrinti
dlg.button.cancel=&Atsisakyti
dlg.button.close=&Užverti
dlg.button.continue=&Tęsti
dlg.button.skip=&Praleisti
dlg.button.overwrite=&Perrašyti
dlg.button.view=Rod&ymas
dlg.button.retry=&Bandyti dar kartÄ…
dlg.button.ignore=&Nepaisyti
# dlg.button.install=&Install
dlg.button.ok=&Gerai
repeatPrefix=\n\nŠis įspėjimas bus kartojamas %S
repeatSuffixSingular=kartÄ….
repeatSuffixPlural=kartus.
noRepeat=\n\nŠis įspėjimas nebus rodomas kol neatnaujinsite Enigmail.
pgpNotSupported=Atrodo, kad naudojate Enigmail kartu su PGP 6.x\n\nDeja, PGP 6.x turi daug problemų, kurios neleidžia Enigmail teisingai veikti. Be to, Enigmail daugiau nebepalaiko PGP 6.x; vietoj to, naudokite GnuPG (GPG).\n\nJei reikia pagalbos pradedant naudoti GnuPG, žiūrėkite pagalbos sekciją Enigmail internetinėje svetainėje.
initErr.howToFixIt=Norint naudoti Enigmail, reikalinga GnuPG. Jeigu jÅ«s dar neįdiegÄ—te GnuPG, lengviausias bÅ«das tai padaryti yra pasinaudoti žemiau esanÄiu mygtuku "SÄ…rankos vediklis".
initErr.setupWizard.button=&SÄ…rankos vediklis
passphraseCleared=Slaptafrazė išvalyta.
# cannotClearPassphrase=You are using a non-standard tool (such as gnome-keyring) for passphrase handling. Clearing the passphrase is therefore not possible from within Enigmail.
noPhotoAvailable=NÄ—ra nuotraukos
debugLog.title=Enigmail derinimo žurnalas
error.photoPathNotReadable=Kelias iki nuotraukos „%S“ neperskaitomas
generalError=Klaida: %S
# Strings in configure.jsm
enigmailCommon.versionSignificantlyChanged=Å i nauja Enigmail versija turi daug pakeitimų nustatymuose ir parinktyse. Mes bandÄ—me perkelti senus nustatymus į Å¡iÄ… naujÄ… versijÄ…. TaÄiau negalime apraÅ¡yti visų situacijų. PeržiÅ«rÄ—kite visus nustatymus ir parinktis.
enigmailCommon.checkPreferences=Tikrinti nustatymus...
preferences.defaultToPgpMime=Mes pakeitėme numatytąjį laiškų kodavimą programoje Enigmail iš įterptojo PGP į PGP/MIME. Rekomenduojame jums tai palikti kaip numatytąjį nustatymą.\n\nJeigu vis tik pagal numatymą norite naudoti įterptąjį PGP, tuomet galite tai nustatyti Paskyros nustatymuose, skyrelyje OpenPGP saugumas.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=Enigmail versija %S
enigmailPepVersion=Enigmail/p≡p versija %S
usingAgent=Šifravimui ir iššifravimui naudojamas %S sukompiliuotas failas %S
agentError=KLAIDA: Nepavyko pasiekti Enigmime tarnybos!
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Klaida bandant pasiekti Enigmail tarnybÄ…
onlyGPG=Rakto generavimas veikia tik su GnuPG (ne su PGP)!
keygenComplete=Raktas sugeneruotas! Pasirašymui bus naudojama <%S> tapatybė.
revokeCertRecommended=Mes primygtinai rekomenduojame savo raktui sukurti panaikinimo liudijimÄ…. Å is liudijimas galÄ—s bÅ«ti naudojamas paversti jÅ«sų raktÄ… negaliojanÄiu, pvz., jei prarasite savo slaptÄ… raktÄ… ar jis bus sukompromituotas. Ar norite dabar sukurti tokį liudijimÄ…?
keyMan.button.generateCert=&Generuoti liudijimÄ…
genCompleteNoSign=Raktas sÄ—kmingai sugeneruotas!
genGoing=Raktas generuojamas!
passNoMatch=Slaptafrazės nesutampa; įveskite dar kartą
passCheckBox=Pažymėkite žymimąjį langelį jei raktui nenurodote slaptafrazės
passUserName=Nurodykite naudotojo vardą, šiai tapatybei
# keygen.missingUserName=There is no name specified for the selected account/identity. Please enter a value in the field "Your name" in the account settings.
keygen.passCharProblem=Jūs savo slaptafrazėje naudojate specialius simbolius. Deja, tai gali sukelti problemų kitoms programoms. Rekomenduojame jums pasirinkti slaptafrazę, kurioje būtų tik kurie nors iš šių simbolių:\na-z A-Z 0-9 /.;:-,!?(){}[]%*
passSpaceProblem=DÄ—l techninių priežasÄių, jÅ«sų slaptafrazÄ— negali prasidÄ—ti ar baigtis tarpu.
changePassFailed=Nepavyko pakeisti slaptafrazÄ—s.
keyConfirm=Sugeneruoti viešąjį ir privatųjį raktus, skirtus „%S“?
keyMan.button.generateKey=&Generuoti raktÄ…
keyAbort=Nutraukti raktų generavimą?
keyMan.button.generateKeyAbort=&Nutraukti raktų generavimą?
keyMan.button.generateKeyContinue=&Tęsti raktų generavimą?
expiryTooLong=Negalite sukurti rakto, kurio galiojimas baigsis daugiau nei po 100 metų.
expiryTooLongShorter=Negalite sukurti rakto, kurio galiojimas baigsis daugiau nei po 90 metų.
expiryTooShort=Jūsų raktas turi galioti bent vieną dieną.
keyGenFailed=Sugeneruoti rakto nepavyko. Patikrinkite Enigmail pultÄ… (Meniu Enigmail > Enigmail derinimas) jei norite gauti daugiau informacijos.
setKeyExpirationDateFailed=Nepavyko pakeisti galiojimo pabaigos datos
# Strings in enigmailMessengerOverlay.js
securityInfo=Enigmail saugumo informacija\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Šiam laiškui skirti priedai nebuvo pasirašyti ar šifruoti*\r\n\r\n
possiblyPgpMime=Galimai PGP/MIME šifruotas ar pasirašytas laiškas; norėdami patikrinti, naudokite „Iššifruoti/Patikrinti“ funkciją
saveAttachmentHeader=Enigmail: Įrašyti iššifruotą priedą
noTempDir=Nepavyko rasti laikino aplanko į kurį galima būtų rašyti\nNustatykite TEMP aplinkos kintamąjį
attachmentPgpKey=Priedas „%S“, kurį bandote atverti yra OpenPGP rakto failas.\n\nSpustelÄ—kite „Importuoti“, norÄ—dami importuoti visus jame esanÄius raktus arba „Rodymas“ ir narÅ¡yklÄ—s lange bus parodytas failo turinys
beginPgpPart=**********ŠIFRUOTOS ar PASIRAŠYTOS DALIES PRADŽIA**********
endPgpPart=**********Å IFRUOTOS ar PASIRAÅ YTOS DALIES PABAIGA**********
notePartEncrypted=Enigmail: *Laiško dalys NEBUVO pasirašytos ar užšifruotos*
noteCutMessage=Enigmail: *Rastos kelios laiško dalys -- iššifravimas/tikrinimas nutrauktas*
decryptOkNoSig=Įspėjimas\n\nIššifravimas buvo sėkmingas, bet nepavyko patikrinti parašo
msgOvl.button.contAnyway=&Vis tiek tęsti
signature.verifiedOK=Priedo %S parašas sėkmingai patvirtintas
signature.verifyFailed=Nepavyko patvirtinti priedo %S parašo
attachment.noMatchToSignature=Nepavyko rasti atitinkamo priedo „%S“, skirto parašo failui
attachment.noMatchFromSignature=Nepavyko rasti atitinkamo parašo failo „%S“, skirto priedui
fixBrokenExchangeMsg.failed=Nepavyko pataisyti laiško.
enigmail.msgViewColumn.label=Enigmail
enigmailPep.msgViewColumn.label=Enigmail/p≡p
# wksNoIdentity=This key is not linked to any of your email accounts. Please add an account for at least one of the following email addresse(s):\n\n%S
wksConfirmSuccess=Patvirtinimo el. laiškas išsiųstas.
wksConfirmFailure=Patvirtinimo el. laiško siuntimas nepavyko.
# autocrypt.importSetupKey.accountPreconfigured=Your account is already correctly configured for Autocrypt.\n\nDo you really want to overwrite your settings with this setup message?
# autocrypt.importSetupKey.selfCreated=This message was created by your currently running instance of Enigmail.\n\nPlease switch to the email client to which you want to transfer the settings, and click on the message on that email client to import the settings.
# autocrypt.importSetupKey.invalidMessage=Error - could not read setup message. The message seems to be corrupted. Please try to create a new setup message on your "other" device.
autocrypt.importSetupKey.invalidKey=Klaida - nepavyko importuoti rakto. Raktas yra arba nepalaikomas jūsų GnuPG versijos, arba jis susigadino.
autocrypt.importSetupKey.wrongPasswd=Jūsų įvestas slaptažodis yra neteisingas. Ar norite bandyti dar kartą?
# autocrypt.importSetupKey.success=The Autocrypt setup message was processed successfully. Autocrypt is now available for your account '%S'.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Pasirinkite OpenPGP raktus kuriuos įterpti
keysToUse=Pasirinkite kurį OpenPGP raktą(-us) naudoti %S
pubKey=Viešasis raktas skirtas %S\n
windowLocked=Rašymo langas užrakintas; siuntimas atšauktas
sendUnencrypted=Nepavyko inicijuoti Enigmail.\nSiųsti nešifruotą laišką?
composeSpecifyEmail=Nurodykite savo pagrindinį el. paÅ¡to adresÄ…, kuris bus naudojamas pasirenkant raktÄ… iÅ¡einantiems laiÅ¡kams.\nJei paliksite tuÅ¡ÄiÄ…, NUO laukelio adresas bus naudojamas pasirinkti raktÄ….
sendingHiddenRcpt=Šis laiškas turi BCC(nematomą kopiją) gavėjų. Jei šis laiškas šifruotas, įmanoma paslėpti BCC gavėjus, bet kai kurių programų naudotojai (pvz. PGP Corp) negalės iššifruoti laiško. Mes rekomenduojame vengti BCC laiškų su šifruotais pranešimais.
sendWithHiddenBcc=SlÄ—pti BCC gavÄ—jus
sendWithShownBcc=Šifruoti įprastai
sendingNews=Užšifruoto siuntimo operacija atšaukta.\n\nšis laiškas negali būti užšifruotas, nes yra naujienų grupių gavėjų. Persiųskite šį laišką nešifruojant.
sendToNewsWarning=Įspėjimas: jūs tuoj išsiųsite užšifruotą laišką naujienų grupei.\n\nTai nepatartina, nes toks veiksmas turi prasmę tik tada jei visi nariai gali iššifruoti laišką t.y. laiškas turi būti šifruotas su visų grupės narių raktais. šį laišką siųskite tik tada jei žinote ką darote.\n\nTęsti?
hasHTML=HTML laiško įspėjimas:\nšiame laiške gali būti HTML, kuri gali sukelti problemų pasirašant/šifruojant. Norint to išvengti ateityje, jūs turėtumėte laikyti SHIFT kai spaudžiate „Rašyti/Atsakyti“ mygtuką, pasirašytam laiškui išsiųsti.\nJei visada pasirašote laišką, nustatymuose turėtumėte atžymėti „Kurti laiškus su HTML“, norint visam laikui išjungti HTML laiškus šiai pašto paskyrai.
strippingHTML=Laiške yra HTML formatavimo informacija, kuri bus prarasta konvertuojant į paprastą tekstą, pasirašymo/šifravimo metu. Tęsti?
msgCompose.button.sendAnyway=&Vistiek siųsti
attachWarning=Šio laiško priedai nėra vietiniai, jie negali būti užšifruoti. Norėdami užšifruoti šiuos priedus, įrašykite juos savo kompiuteryje ir tuomet pridėkite failus. Ar vis tiek norite siųsti šį laišką?
quotedPrintableWarn=JÅ«s įjungÄ—te „quoted-printable“ kodavimÄ… siunÄiamiems laiÅ¡kams. Tai gali įtakoti neteisingÄ… jÅ«sų laiÅ¡ko iššifravimÄ… ir/ar patikrinimÄ….\nAr norite dabar iÅ¡jungti „quoted-printable“ siunÄiamiems laiÅ¡kams?
minimalLineWrapping=JÅ«s nustatÄ—te eiluÄių laužymÄ… %S simboliais. Norint teisingai užšifruoti ar/ir pasiraÅ¡yti, Å¡i vertÄ— turi bÅ«ti bent 68.\nAr norite dabar nustatyti eiluÄių laužymÄ… ties 68 simboliais?
warning=Įspėjimas
signIconClicked=Jūs pakeitėte pasirašymą. Nepaisant to, kol jūs rašote šį laišką, pasirašymo (de)aktyvavimas daugiau nepriklauso nuo šifravimo (de)aktyvacijos.
# errorOwnKeyUnusable=The key ID '%S' configured for the current identity does not yield a usable OpenPGP key.\n\nPlease ensure that you have a valid, not expired OpenPGP key and that your account settings point to that key.\nIf your key is not expired, then check if you did set Owner trust to full or ultimate.
msgCompose.cannotSaveDraft=Klaida, įrašant juodraštį
# msgCompose.partiallyEncrypted.short=Beware of leaking sensitive information - partially encrypted email.
# msgCompose.partiallyEncrypted.mimeMsg=The message you are replying to contained both unencrypted and encrypted parts. Some encrypted message parts are invisible to you.\n\nIf the sender was not able to decrypt the hidden message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nWe recommend that you don't reply to the message, but create a new message containing your answer.
# msgCompose.partiallyEncrypted.inlinePGP=The message you are replying to contained both unencrypted and encrypted parts. If the sender was not able to decrypt some message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nPlease consider removing all quoted text from your reply to this sender.
msgCompose.internalEncryptionError=Vidinė klaida: žadėtas šifravimas išjungtas
msgCompose.internalError=Įvyko vidinė klaida.
msgCompose.toolbarTxt.signAndEncrypt=Šis laiškas bus pasirašytas ir šifruotas
msgCompose.toolbarTxt.signOnly=Šis laiškas bus pasirašytas
msgCompose.toolbarTxt.encryptOnly=Šis laiškas bus šifruotas
msgCompose.toolbarTxt.noEncryption=Šis laiškas bus nepasirašytas ir nešifruotas
msgCompose.toolbarTxt.disabled=Enigmail pasirinktai tapatybei yra išjungta
# msgCompose.protectSubject.tooltip=Protect the message subject
# msgCompose.noSubjectProtection.tooltip=Do not protect the message subject
msgCompose.encryptedSubjectStub=Šifruotas laiškas
# msgCompose.protectSubject.dialogTitle=Enable Protection of Subject?
# msgCompose.protectSubject.question=Regular encrypted emails contain the unredacted subject.\n\nWe have established a standard to hide the original subject in the encrypted message\nand replace it with a dummy text, such that the subject is only visible after the email is decrypted.\n\nDo you want to protect the subject in encrypted messages?
# msgCompose.protectSubject.yesButton=&Protect subject
# msgCompose.protectSubject.noButton=&Leave subject unprotected
msgCompose.detailsButton.label=Išsamiau ...
# msgCompose.detailsButton.accessKey=D
msgCompose.pepSendUnknown=Nežinoma
# msgCompose.pepSendUnsecure=Unsecure
# msgCompose.pepSendSecure=Secure
# msgCompose.pepSendTrusted=Secure & Trusted
# pep.alert.disabledForIdentity=p≡p is disabled for the current identity. Please enable p≡p via the Enigmail/p≡p preferences.
pep.alert.weakReply=Jūs ketinate persiųsti ar atsakyti į saugų laišką, kaip į nesaugų. Jei pasirinksite tęsti, gali būti atskleista konfidenciali informacija, kuri sukels pavojų jums ir jūsų bendravimo partneriui. Ar tikrai norite tęsti?
# note: should end with double newline:
sendAborted=Siuntimo operacija nutraukta.\n\n
# details:
# keyNotTrusted=Not enough trust for key '%S'
keyNotFound=Raktas "%S" nerastas
keyRevoked=Raktas "%S" panaikintas
keyExpired=PasibaigÄ— "%S" rakto galiojimas
statPGPMIME=PGP/MIME
statSMIME=S/MIME
statSigned=PASIRAÅ YTAS
statEncrypted=Å IFRUOTAS
statPlain=NEPASIRAÅ YTAS ir NEÅ IFRUOTAS
offlineSave=Įrašyti %S laišką į %S neišsiųstų laiškų aplanke?
onlineSend=Išsiųsti %S laišką į %S?
encryptKeysNote=Pastaba: laiškas užšifruotas su šio naudotojo ID/Raktu: %S
hiddenKey=
signFailed=Klaida Enigmail; Nepavyko užšifruoti/pasirašyti; siųsti nešifruotą laišką?
msgCompose.button.sendUnencrypted=&Siųsti nešifruotą laišką
recipientsSelectionHdr=Pasirinkite gavėjus šifravimui
configureNow=Pasirinktai tapatybei jūs nenustatėte Enigmail saugumo. Ar norite tai padaryti dabar?
# encryption/signing status and associated reasons:
encryptMessageAuto=Šifruoti laišką (automatiškai)
encryptMessageNorm=Šifruoti laišką
signMessageAuto=Pasirašyti laišką (automatiškai)
signMessageNorm=Pasirašyti laišką
encryptOff=Å ifravimas: IÅ JUNGTAS
encryptOnWithReason=Šifravimas: ĮJUNGTAS (%S)
encryptOffWithReason=Å ifravimas: IÅ JUNGTAS (%S)
encryptOn=Šifravimas: ĮJUNGTAS
signOn=Pasirašymas: ĮJUNGTAS
signOff=Pasirašymas: IŠJUNGTAS
signOnWithReason=Pasirašymas: ĮJUNGTAS (%S)
signOffWithReason=Pasirašymas: IŠJUNGTAS (%S)
reasonEnabledByDefault=įjungta pagal numatymą
# reasonManuallyForced=manually forced
# reasonByRecipientRules=forced by recipient rules
# reasonByAutoEncryption=forced by auto encryption
reasonByConflict=dėl konflikto gavėjų taisyklėse
reasonByEncryptionMode=dėl šifravimo veiksenos
# should not be used anymore:
encryptYes=Laiškas bus užšifruotas
encryptNo=Laiškas nebus užšifruotas
# should not be used anymore:
signYes=Laiškas bus pasirašytas
signNo=Laiškas nebus pasirašytas
# PGP/MIME status:
pgpmimeNormal=Protokolas: PGP/MIME
inlinePGPNormal=Protokolas: Įterptasis PGP
smimeNormal=Protokolas: S/MIME
pgpmimeAuto=Protokolas: PGP/MIME (automatiškai)
inlinePGPAuto=Protokolas: Įterptasis PGP (automatiškai)
smimeAuto=Protokolas: S/MIME (automatiškai)
# should not be used anymore
pgpmimeYes=Bus naudojama PGP/MIME
pgpmimeNo=Bus naudojamas įterptasis PGP
# Attach own key status (tooltip strings):
attachOwnKeyNo=JÅ«sų paÄių raktas nebus pridÄ—tas
attachOwnKeyYes=Bus pridÄ—tas jÅ«sų paÄių raktas
attachOwnKeyDisabled=Nepavyko pridÄ—ti jÅ«sų paÄių rakto. NorÄ—dami įjungti Å¡iÄ… ypatybÄ™,\nturite Paskyros nustatymuose, OpenPGP sekcijoje pasirinkti tam tikrÄ… raktÄ….
rulesConflict=Aptiktos nesuderinamos kiekvienam-gavėjui taisyklės\n%S\n\nSiųsti laišką su šiais nustatymais?
msgCompose.button.configure=&Konfigūruoti
msgCompose.button.send=&Siųsti laišką
msgCompose.button.save=Į&rašyti laišką
# Strings in enigmailMsgHdrViewOverlay.js
# keyNeeded=Public key %S needed to verify signature
# keyUsed=Public key %S used to verify signature
clickDecrypt=; naudokite „Iššifruoti/Patikrinti“ funkciją
clickDecryptRetry=; norėdami bandyti dar kartą, naudokite „Iššifruoti/Patikrinti“ funkciją
clickDetailsButton=; išsamesnei informacijai, spustelėkite ant mygtuko "Išsamiau"
clickImportButton=; norÄ—dami importuoti raktÄ…, spustelÄ—kite ant mygtuko "Importuoti raktÄ…"
keyTypeUnsupported=; jūsų GnuPG versija nepalaiko rakto tipo
msgPart=%S laiško dalis
msgSigned=pasirašytas
msgSignedUnkownKey=pasirašytas, naudojant nežinomą raktą
msgEncrypted=užšifruotas
msgSignedAndEnc=pasirašyta ir užšifruota
unverifiedSig=Nepatvirtintas parašas
incompleteDecrypt=Iššifravimas nepilnas
needKey=Klaida - laiÅ¡ko iššifravimui nerasta jokio privaÄiojo/slapto rakto
failedDecrypt=Klaida - nepavyko iššifruoti
badPhrase=Klaida - bloga slaptafrazÄ—
failedDecryptVerify=Klaida - iššifravimas/patikrinimas nepavyko
viewInfo=; Rodymas > Laiško saugumo informacija, išsamesnei informacijai
decryptedMsg=Iššifruotas laiškas
decryptedMsgWithFormatError=Iššifruotas laiÅ¡kas (atkurtas sugadintas PGP laiÅ¡ko formatas, jį greiÄiausiai sugadino senas Exchange serveris, gali bÅ«ti neįmanoma perskaityti laiÅ¡ko)
usedAlgorithms=Naudoti algoritmai: %1$S ir %2$S
pepStatusInfo.text=p≡p laiško būsena.
# pepStatusInfo.title.m3=Under Attack
# pepStatusInfo.info.m3=This message is not secure and has been tampered with.
# pepStatusInfo.title.m1=Mistrusted
pepStatusInfo.info.m1=Å iame laiÅ¡ke yra bendravimo partneris, kuris anksÄiau buvo pažymÄ—tas kaip nepatikimas
pepStatusInfo.title.r0=Nežinoma
pepStatusInfo.info.r0=Šiame laiške nėra pakankamai informacijos, kad būtų nuspręsta ar jis yra saugus ar ne.
pepStatusInfo.title.r1=Nepavyksta iššifruoti
pepStatusInfo.info.r1=Šis laiškas negali būti iššifruotas, nes raktas nėra prieinamas.
pepStatusInfo.title.r2=Nepavyksta iššifruoti
pepStatusInfo.info.r2=Šis laiškas negali būti iššifruotas, nes raktas nėra prieinamas.
pepStatusInfo.title.r3=Nesaugus
pepStatusInfo.info.r3=Šis laiškas yra nesaugus.
# pepStatusInfo.title.r4=Unsecure for Some
pepStatusInfo.info.r4=Kai kuriems bendravimo partneriams šis laiškas yra nesaugus.
pepStatusInfo.title.r5=Nepatikimas saugumas
pepStatusInfo.info.r5=Šiame laiške yra nepatikima apsauga.
# pepStatusInfo.title.r6=Secure...
pepStatusInfo.info.r6=Å is laiÅ¡kas yra saugus, taÄiau vis tiek turite patvirtinti savo bendravimo partnerio tapatybÄ™.
# pepStatusInfo.title.r7=Secure & Trusted
pepStatusInfo.info.r7=Šis laiškas yra saugus ir patikimas.
pepStatusInfo.color.green=Žalia
pepStatusInfo.color.yellow=Geltona
pepStatusInfo.color.red=Raudona
# pepRevokeTrust.question=Do you really want to cancel the trust for %S?
# pepRevokeMistrust.question=Do you really want to re-trust the key for %S?
# pepRevokeTrust.doRevoke=Cancel &trust
# wksConfirmationReq=Web Key Directory Confirmation Request
# wksConfirmationReq.message=This message has been sent by your email provider to confirm deployment of your OpenPGP public key\nin their Web Key Directory.\nProviding your public key helps others to discover your key and thus being able to encrypt messages to you.\n\nIf you want to deploy your key in the Web Key Directory now, please click on the button "Confirm Request" in the status bar.\nOtherwise, simply ignore this message.
wksConfirmationReq.button.label=Patvirtinti užklausą
# autocryptSetupReq=Perform Autocrypt Setup
autocryptSetupReq.button.label=PradÄ—ti sÄ…rankÄ…
# autocryptSetupReq.setupMsg.desc=This message contains all information to transfer your Autocrypt settings along with your secret key securely from your original device.
# autocryptSetupReq.setupMsg.backup=You can keep this message and use it as a backup for your secret key. If you want to do this, you should write down the password and store it securely.
autocryptSetupReq.message.import=Norėdami importuoti nustatymus ir raktą(-us) į Enigmail, spustelėkite būsenos juostoje ant mygtuko "Pradėti sąranką".
# autocryptSetupReq.message.sent=Please click on the message on your new device and follow the instuctions to import the settings.
# strings in pref-enigmail.js
oldGpgVersion20=Enigmail inicijavimas patyrė nesėkmę.\n\nJūs naudojate GnuPG versiją %1$S, kuri yra daugiau nebepalaikoma. Enigmail reikalauja GnuPG versijos %2$S arba naujesnės. Prašome atnaujinti savo GnuPG įdiegimą arba kitu atveju Enigmail neveiks.
locateGpg=Surasti GnuPG programÄ…
invalidGpgPath=Nurodytam kelyje GnuPG negali būti įvykdyta. Enigmail išjungta kol jūs pakeisite kelią iki GnuPG arba iš naujo paleisite programą.
warningsAreReset=Visi įspėjimai buvo atstatyti.
prefs.gpgFound=GnuPG rasta kataloge %S
prefs.gpgNotFound=Nepavyko rasti GnuPG
prefs.warnAskNever=Įspėjimas: įjungus šią parinktį nebus pranešama jei vienam iš gavėjų nėra rakto ir laiškas nešifruotas!
prefs.warnIdleTimeForUnknownAgent=Nepavyko prisijungti prie gpg-agent. Gal jūsų sistema slaptafrazės įvedimui naudoja specialų įrankį, tokį kaip gnome-keyring ar seahorse-agent. Dėja Enigmail negali valdyti įvedimo laiko jūsų įrankyje. Laiko nustatymai Enigmail programoje yra ignoruojami.
prefEnigmail.oneKeyserverOnly=Klaida - automatiniam trūkstamų OpenPGP raktų atsiuntimui galite nurodyti tik vieną raktų serverį.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Įveskite SmartCard ADMIN PIN
enterCardPin=Įveskite SmartCard PIN
notInit=Klaida - Enigmail tarnyba kol kas neinicijuota
badCommand=Klaida - šifravimo komanda nepavyko
cmdLine=komandų eilutė ir išvestis:
notRequired=Klaida - šifravimas nereikalingas
notComplete=Klaida - rakto generavimas dar nebaigtas
invalidEmail=Klaida - netinkamas el. pašto adresas(-ai)
noPassphrase=Klaida - nepateikta slaptafrazÄ—
noPGPblock=Klaida - nerastas tinkamas „armored OpenPGP“ duomenų blokas
unverifiedReply=Cituojama laiško dalis (atsakyme) turbūt buvo pakeista
keyInMessageBody=Pagrindinėje laiško dalyje rastas raktas. Norėdami importuoti raktą, spustelėkite "Importuoti raktą"
sigMismatch=Klaida - parašas nesutampa
cantImport=Klaida importuojant viešąjį raktą\n\n
doImportOne=Importuoti %1$S (%2$S)?
doImportMultiple=Importuoti šiuos raktus?\n\n%S
previewFailed=Nepavyksta perskaityti viešojo rakto failo.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=Rasta SmartCard %S jūsų įrenginyje negali būti panaudota skaitant laišką.\nĮdėkite savo SmartCard %S ir pakartokite operaciją.
sc.insertCard=Operacijai atlikti reikia SmartCard %S.\nĮdėkite reikalingą SmartCard ir pakartokite operaciją.
sc.removeCard=Operacijai atlikti reikia jog SmartCard nebūtų įrenginyje.\nIšimkite SmartCard ir pakartokite operaciją.
sc.noCardAvailable=Jūsų įrenginyje SmartCard nerasta\nĮdėkite jūsų SmartCard ir pakartokite operaciją.
sc.noReaderAvailable=Jūsų SmartCard skaitytuvas nepasiekiamas\nPrijunkite SmartCard skaitytuvą, įdėkite kortelę ir pakartokite operaciją.
# keyError.keySpecNotFound=The email address "%S" cannot be matched to a key on your keyring.
# keyError.keyIdNotFound=The configured key ID "%S" cannot be found on your keyring.
keyError.resolutionAction=Pasirinkite savo Paskyros nustatymuose, OpenPGP sekcijoje, galiojantį raktą.
missingPassphrase=Trūksta slaptafrazės
errorHandling.gpgAgentInvalid=Jūsų sistemoje yra paleista gpg-agent versija, kuri nėra tinkama jūsų GnuPG versijai.
# errorHandling.gpgAgentError=GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
errorHandling.dirmngrError=GnuPG pranešė apie klaida susisiekime su dirmngr (GnuPG komponentu).
# errorHandling.pinentryError=GnuPG cannot query your passphrase via pinentry.
# errorHandling.readFaq=This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.\n\nWe strongly recommend that you consult our support web site at https://enigmail.net/faq.
gpgNotFound=Nepavyko rasti GnuPG programos „%S“.\nĮsitikinkite jog Enigmail nustatymuose nurodėte teisingą GnuPG kelią.
gpgNotInPath=Nepavyko rasti GnuPG vykdomojo failo PATH.\nĮsitikinkite jog Enigmail nustatymuose nurodėte teisingą GnuPG kelią.
# enigmailNotAvailable=Enigmail core Service not available
prefGood=GERAS parašas iš %S
prefBad=BLOGAS parašas iš %S
failCancel=Klaida - rakto gavimą atšaukė naudotojas
failNoServer=Klaida - nenurodytas raktų serveris iš kurio reikia gauti raktą
failNoID=Klaida - nenurodyta rakto ID kurį reikia gauti
failKeyExtract=Klaida - rakto išgavimo komanda nepavyko
notFirstBlock=Klaida - pirmas OpenPGP blokas nėra viešasis raktas
importKeyConfirm=Importuoti viešąjį(-uosius) raktą(-us) įterptus laiške?
failKeyImport=Klaida - nepavyko importuoti rakto
fileWriteFailed=Nepavyko įrašyti į failą %S
importKey=Importuoti iš raktų serverio viešąjį raktą %S:
uploadKey=Siųsti viešąjį raktą %S į raktų serverį:
keyId=Rakto ID
keyAndSigDate=Rakto ID: 0x%S / Pasirašyta: %S
keyFpr=Rakto kontrolinis kodas: %S
noEmailProvided=Jūs nepateikėte el. pašto adreso!
keyAlreadySigned=Raktas jau pasirašytas, negalite jo pasirašyti antrą kartą.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=pasibaigęs galiojimas %S
createdHeader=Sukurtas
atLeastOneKey=Nepasirinktas raktas! Turite pasirinkti bent vieną raktą patvirtinant šį dialogą
fewerKeysThanRecipients=Jūs pasirinkote mažiau raktų nei yra gavėjų. Ar jūs įsitikinę jog raktų, kuriuos reikia užšifruoti, sąrašas pilnas?
userSel.button.goBack=Pasirinkti daugiau raktų
userSel.secretKeySel.title=Pasirinkite slaptą OpenPGP raktą laiškų pasirašymui
# userSel.problemNoKey=No valid key
# userSel.problemMultipleKeys=Multiple keys
# should be same as thunderbird ENTITY sendLaterCmd.label:
sendLaterCmd.label=Siųsti vėliau
# Strings used in enigmailAttachmentDialog.js
# pgpMimeNote=NOTE: PGP/MIME is not supported by all email clients. If you are unsure, select the %S option.
first=pirmas
second=antras
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Pasirinkite OpenPGP raktą šifravimui
identityName=TapatybÄ—: %S
# switchPepMode=You are currently using the 'p≡p Junior' mode of Enigmail.\n\nBy enabling OpenPGP or S/MIME for an account, you are disabling p≡p and use the 'regular' mode of Enigmail without p≡p.
# enableEnigmail=&Disable p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=JÅ«s įjungÄ—te Å¡ifravimÄ…, bet nepasirinkote rakto. Norint užšifruoti laiÅ¡kus siunÄiamus %S, jÅ«s turite nurodyti vienÄ… ar kelis tinkamus raktus iÅ¡ jÅ«sų raktų sÄ…raÅ¡o. Ar norite iÅ¡jungti Å¡ifravimÄ… skirtÄ… %S?
noKeyToUse=(nėra - be šifravimo)
noEmptyRule=TaisyklÄ— negali bÅ«ti tuÅ¡Äia! Nurodykite el. paÅ¡to adresÄ… taisyklÄ—s laukelyje.
invalidAddress=El. pašto adresas(-ai) kuriuos įvedėte yra neteisingi. Jūs neturėtumėte nurodyti gavėjų vardų, o tik el. pašto adresus. Pvz.:\nNeteisingas: Vardenis Pavardenis \nTeisingas: vardenis.pavardenis@adresas.lt
# noCurlyBrackets=The curly brackets {} have a special meaning and should not be used in an email address. If you want to modify the matching behavior for this rule, use the 'Apply rule if recipient ...' option.\nMore information is available from the Help button.
# Strings used in enigmailRulesEditor.js
never=Niekada
always=Visada
possible=Įmanoma
deleteRule=Tikrai ištrinti pasirinktą taisyklę?
nextRcpt=(Kitas gavÄ—jas)
negateRule=Ne
addKeyToRule=Pridėti raktą %S (%S) į kiekvienam-gavėjui taisyklę
# Strings used in enigmailSearchKey.js
needOnline=Pasirinkta funkcija neprieinama dirbant atsijungus. Prisijunkite ir bandykite dar kartÄ….
protocolNotSupported=Jūsų pasirinktas protokolas „%S://“ nėra palaikomas OpenPGP raktų atsiuntimui.
gpgkeysDisabled=Turėtų pagelbėti „extensions.enigmail.useGpgKeysTool“ parinkties įjungimas.
noKeyserverConn=Nepavyko prisijungti prie raktų serverio %S.
keyDownloadFailed=Nepavyko atsisiųsti rakto iš raktų serverio. Būsenos pranešimas:\n%S
internalError=Kilo vidinė klaida. Raktų importuoti ar atsisiųsti nepavyko.
noKeyFound=Apgailestaujame, nepavyko rasti rakto kuris atitiktų jūsų nurodytus kriterijus.\nTurėkite omeny jog rakto ID turi prasidėti „0x“ (pvz. 0xABCDEF12).
# keyDownload.keyUnavailable=We are sorry, but the key with ID %S is not available on the keyserver. Most likely, the owner of the key did not upload their key to the keyserver.\n\nPlease ask the sender of the message to send you their key by email.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Nepavyko surasti ar atsisiųsti rakto iš raktų serverio: nepavyko įvykdyti gpgkeys_%S.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Nepavyko nustatyti savininko patikimumo
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Rakto pasirašyti nepavyko
alreadySigned.label=Pastaba: raktas %S jau pasiraÅ¡ytas pasirinktu privaÄiuoju raktu.
# alreadySignedexportable.label=Note: the key %S is already signed exportable with the selected secret key. A local signature does not make sense.
partlySigned.label=Pastaba: kai kurie rakto %S naudotojų ID jau pasiraÅ¡yti pasirinktu privaÄiuoju raktu.
# noTrustedOwnKeys=No eligible key found for signing! You need at least one fully trusted secret key in order to sign keys.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=Įkraunami raktai, prašome palaukti ...
keyValid.unknown=nežinomas
keyValid.invalid=netinkamas
keyValid.disabled=išjungtas
keyValid.revoked=panaikintas
keyValid.expired=nebegaliojantis
keyValid.noSubkey=nÄ—ra tinkamo porakÄio
keyTrust.untrusted=nepatikimas
keyTrust.marginal=dalinai patikimas
keyTrust.full=patikimas
keyTrust.ultimate=visiškas
keyTrust.group=(grupÄ—)
keyType.public=viešas
keyType.publicAndSec=viešas/saugus
keyMan.enableKey=Įjungti raktą
keyMan.disableKey=Išjungti raktą
userAtt.photo=Naudotojo savybÄ— (JPEG paveikslas)
asciiArmorFile=ASCII Armored failai (*.asc)
importKeyFile=Importuoti OpenPGP rakto failÄ…
gnupgFile=GnuPG failai
createKeyOK=Jūsų raktas buvo sugeneruotas
saveRevokeCertAs=Sukurti ir įrašyti panaikinimo liudijimą
revokeCertOK=Panaikinimo liudijimas buvo sÄ—kmingai sukurtas. Galite jį naudoti, norÄ—dami paversti savo viešąjį raktÄ… negaliojanÄiu, pvz., tuo atveju, jei prarasite savo slaptÄ…jį raktÄ….
revokeCertFailed=Nepavyko sukurti panaikinimo liudijimo.
addUidOK=Naudotojo ID sÄ—kmingai pridÄ—ta
addUidFailed=PridÄ—ti naudotojo ID nepavyko
noKeySelected=Pasirinktai operacijai atlikti jūs turite pasirinkti bent vieną raktą
exportToFile=Eksportuoti viešąjį raktą į failą
# exportKeypairToFile=Export Secret and Public Key To File
exportSecretKey=Ar norite įtraukti slaptą raktą į įrašytą OpenPGP rakto failą?
saveKeysOK=Raktai sėkmingai įrašyti
saveKeysFailed=Raktų įrašyti nepavyko
importKeysFailed=Raktų importuoti nepavyko
enableKeyFailed=Raktų įjungti/išjungti nepavyko
specificPubKeyFilename=%S (0x%S) viešas
specificPubSecKeyFilename=%S (0x%S) viešas-saugus
defaultPubKeyFilename=Eksportuoti-viešieji-raktai
defaultPubSecKeyFilename=Eksportuoti-viešieji-ir-slapti-raktai
noSecretKeys=Slaptų raktų nerasta.\n\nAr norite sugeneruoti savo raktą dabar?
sendKeysOk=Raktas(-ai) sėkmingai išsiųsti
sendKeysFailed=Raktų išsiųsti nepavyko
receiveKeysOk=Raktas(-ai) sÄ—kmingai atnaujinti
receiveKeysFailed=Raktų atsiuntimas nepavyko
importFromClip=Ar norite importuoti raktą(-us) iš iškarpinės?
importFromUrl=Atsisiųsti viešąjį raktą iš šio URL:
copyToClipbrdFailed=Nepavyko nukopijuoti pasirinkto rakto(-ų) į iškarpinę.
copyToClipbrdOK=Raktas(-ai) nukopijuoti į iškarpinę
deleteSecretKey=ĮSPĖJIMAS: Jūs ketinate ištrinti slaptą raktą!\nJei ištrinsite savo slaptą raktą, nebegalėsite iššifruoti laiškų užšifruotų tuo raktu ir nebegalėsite to rakto panaikinti.\n\nAr tikrai norite ištrinti ABU (slaptą ir viešąjį) raktus\n„%S“?
deleteMix=ĮSPĖJIMAS: Jūs ketinate ištrinti slaptus raktus!\nJeigu ištrinsite savo slaptą raktą, nebegalėsite iššifruoti laiškų užšifruotų tuo raktu.\nAr tikrai norite ištrinti ABU (pasirinktą slaptą ir viešąjį) raktus?
deletePubKey=Ar tikrai norite ištrinti viešąjį raktą\n„%S“?
deleteSelectedPubKey=Ar norite ištrinti viešuosius raktus?
deleteKeyFailed=Nepavyko ištrinti rakto.
# revokeKeyQuestion=You are about to revoke the key '%S'.\n\nYou will no longer be able to sign with this key, and once distributed, others will no longer be able to encrypt with that key. You can still use the key to decrypt old messages.\n\nDo you want to proceed?
revokeKeyOk=Raktas panaikintas. Jeigu jūsų raktas yra prieinamas raktų serveryje, rekomenduojama jį įkelti iš naujo, kad kiti matytų, jog jis buvo panaikintas.
revokeKeyFailed=Nepavyko panaikinti rakto.
revokeKeyNotPresent=Jūs neturite jokio rakto (0x%S), kuris tiktų į šį panaikinimo liudijimą!\n\nJeigu praradote savo raktą, tuomet privalote jį importuoti (pvz., iš raktų serverio) prieš panaikinimo liudijimą!
revokeKeyAlreadyRevoked=Raktas 0x%S jau buvo panaikintas.
refreshAllQuestion=Nepasirinkote jokio rakto. Ar norite atnaujinti VISUS raktus?
refreshKeyServiceOn.warn=Įspėjimai: Šiuo metu jūsų raktai kaip įmanoma saugiau yra fone įkeliami iš naujo.\nVisų raktų įkėlimas iš naujo vienu metu gali bereikalingai atskleisti informaciją apie jus.\nAr tikrai norite tai padaryti?
refreshKey.warn=Ä®spÄ—jimas: priklausomai nuo raktų skaiÄiaus ir interneto greiÄio, raktų atnaujinimas gali užtrukti!
downloadContactsKeys.warn=Ä®spÄ—jimas: priklausomai nuo raktų skaiÄiaus ir interneto greiÄio, raktų atnaujinimas gali užtrukti!
downloadContactsKeys.importFrom=Importuoti kontaktus iš „%S“ adresų knygutės?
keyMan.button.exportSecKey=Eksportuoti &slaptus raktus
keyMan.button.exportPubKey=Eksportuoti tik &viešuosius raktus
keyMan.button.import=&Importuoti
keyMan.button.refreshAll=&Iš naujo įkelti visus raktus
keyMan.button.revokeKey=&Panaikinti raktÄ…
keyMan.button.skip=&Praleisti raktÄ…
keylist.noOtherUids=Neturi kitų tapatybių
keylist.hasOtherUids=Taip pat žinomas kaip
keylist.noPhotos=NÄ—ra nuotraukos
keylist.hasPhotos=Nuotraukos
keyMan.addphoto.filepicker.title=Pasirinkite nuotraukÄ… kuri bus pridÄ—ta
keyMan.addphoto.warnLargeFile=Jūsų pasirinktas failas yra didesnis nei 25 kB.\nNerekomenduotina pridėti didelių failų, nes raktai tampa labai dideli.
keyMan.addphoto.noJpegFile=Pasirinktas failas nÄ—ra JPEG failas. Pasirinkite kitÄ… failÄ….
keyMan.addphoto.failed=Nepavyko pridÄ—ti nuotraukos.
noWksIdentity=Raktas %S neturi WKS tapatybÄ—s.
# keyman.addBlacklistKey.msg=Do you really want p≡p to stop using the key "%1$S (%2$S)" for encrypting messages?
# keyman.removeBlacklistKey.msg=Do you want to allow p≡p to use key "%1$S (%2$S)" for future messages?
keyman.addBlacklistKey.button=Į&traukti raktą į juodąjį sąrašą
keyman.removeBlacklistKey.button=Š&alinti raktą iš juodojo sąrašo
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Nepavyko pakeisti pagrindinio naudotojo ID
changePrimUidOK=Pagrindinio naudotojo ID sÄ—kmingai pakeistas
revokeUidFailed=Naudotojo ID %S panaikinimas nepavyko
revokeUidOK=Naudotojo ID %S sėkmingai panaikintas. Jeigu jūsų raktas prieinamas raktų serveryje, rekomenduojama jį įkelti pakartotinai, kad kiti žinotų, jog jis panaikintas.
revokeUidQuestion=Ar tikrai norite panaikinti naudotojo ID %S?
# Strings in enigmailKeyImportInfo.xul
importInfoTitle=PAVYKO! Raktai importuoti
# importInfoBits=Bits
importInfoCreated=Sukurtas
importInfoFpr=Kontrolinis kodas
importInfoDetails=(Išsamiau)
importInfoNoKeys=Neimportuota jokių raktų.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=viešasis raktas
keyTypePrimary=pirminis raktas
keyTypeSubkey=poraktis
keyTypePair=raktų pora
keyExpiryNever=niekada
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
keyAlgorithm_18=ECDH
keyAlgorithm_19=ECDSA
keyAlgorithm_20=ELG
keyAlgorithm_22=EDDSA
keyUsageEncrypt=Å ifravimas
keyUsageSign=Pasirašymas
# keyUsageCertify=Certify
keyUsageAuthentication=TapatybÄ—s patvirtinimas
keyDoesNotExpire=Raktas neturi galiojimo pabaigos
# Strings in enigmailGenCardKey.xul
keygen.started=Palaukite kol bus sugeneruotas raktas...
keygen.completed=Raktas sugeneruotas. Naujas rakto ID yra: 0x%S
keygen.keyBackup=Rakto atsarginÄ— kopija padaryta kaip %S
keygen.passRequired=Nurodykite slaptafrazę jei norite sukurti savo rakto atsarginę kopiją už SmartCard ribų.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=Nepavyko pakeisti PIN
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Raktai įkeliami iš naujo, prašome palaukti...
keyserverProgress.uploading=Raktai įkeliami, palaukite...
# keyserverProgress.wksUploadFailed=Could not upload your key to the Web Key Service
# keyserverProgress.wksUploadCompleted=Your public key was successfully submitted to your provider. You will receive an email to confirm that you initiated the upload.
keyserverTitle.refreshing=Atnaujinti raktus
keyserverTitle.uploading=Įkelti raktą
# Strings in enigmailSetupWizard
passphrase.min8keys=Jūsų slaptafrazė turi būti sudaryta bent iš 8 simbolių!
setupWizard.reallyCancel=Ar tikrai norite užverti Enigmail sąrankos vediklį?
setupWizard.invalidGpg=Jūsų pasirinktas failas nėra GnuPG vykdomasis failas. Pasirinkite kitą failą.
setupWizard.specifyFile=Norėdami tęsti, turite nurodyti bent jau viešąjį raktą.
setupWizard.installFailed=Atrodo diegimas nepavyko. Pabandykite iš naujo arba įdiekite GnuPG rankiniu būdu ir pasirinkite jį su naršymo mygtuku.
setupWizard.downloadForbidden=JÅ«sų paÄių saugumui, mes nesiųsime GnuPG. NorÄ—dami atsisiųsti GnuPG, apsilankykite https://gnupg.org/ .
setupWizard.downloadImpossible=Šiuo metu mums nepavyko atsisiųsti GnuPG. Bandykite vėliau arba, norėdami atsisiųsti GnuPG, apsilankykite https://gnupg.org/ .
setupWizard.hashSumError=Vedikliui nepavyko patikrinti atsiųsto failo vietisumo. Failas gali būti netinkamai atsiųstas arba pakeistas. Ar vis tiek norite tęsti diegimą?
setupWizard.importSettingsFile=Nurodykite atsarginės kopijos failą, iš kurio įkelti
setupWizard.invalidSettingsFile=Nurodytas failas nėra teisingas Enigmail nustatymų atsarginės kopijos failas.
setupWizard.gpgConfExists=GnuPG konfigūracijos failas jau yra. Ar norite jį perrašyti konfigūracijos failu iš savo senojo diegimo?
setupWizard.noGpgHomeDir=Atrodo, kad esate sukonfigÅ«ravÄ™ %S, kad naudotų GnuPG. TaÄiau tai nÄ—ra katalogas - jÅ«s negalite jo naudoti.
setupWizard.unmachtedIds=Šioms jūsų senos sąrankos tapatybėms nepavyko rasti atitikmenų:\n%S\nNustatymai šioms tapatybėms buvo praleisti.
# Strings in installGnuPG.jsm
installGnuPG.downloadFailed=AtsiunÄiant GnuPG įvyko klaida. Tolimesnei informacijai, žiÅ«rÄ—kite pulto žurnalÄ….
installGnuPG.installFailed=Diegiant GnuPG įvyko klaida. Tolimesnei informacijai, žiūrėkite pulto žurnalą.
# Strings in enigmailAddUidDlg.xul
addUidDlg.nameOrEmailError=Turite užpildyti vardą ir el. pašto adresą
addUidDlg.nameMinLengthError=VardÄ… turi sudaryti bent 5 simboliai
addUidDlg.invalidEmailError=Turite nurodyti teisingą el. pašto adresą
# Strings in enigmailCardDetails.js
Carddetails.NoASCII=OpenPGP SmartCards Varde/PavardÄ—je palaiko tik ASCII simbolius.
# network error types
errorType.SecurityCertificate=Interneto tarnybos pateiktas saugumo liudijimas negalioja.
errorType.SecurityProtocol=Saugumo protokolas kurį naudoja tarnyba yra nežinomas.
errorType.Network=Įvyko tinklo klaida.
# filter stuff
filter.folderRequired=Privalote pasirinkti paskirties aplankÄ….
filter.decryptMove.label=Iššifruoti visam laikui (Enigmail)
filter.decryptCopy.label=Sukurti iššifruotą kopiją (Enigmail)
filter.decryptMove.warnExperimental=Įspėjimas - filtro veiksmas "Iššifruoti visam laikui" gali privesti prie sunaikintų laiškų.\n\nPrimygtinai jums rekomenduojame, iš pradžių, išbandyti filtrą "Sukurti iššifruotą kopiją", atsargiai išbandyti rezultatą ir pradėti naudoti šį filtrą tik tuomet, kai būsite patenkinti rezultatu.
# filter.tempPepFilterDesc=Temporary filter to store sent message unencrypted
# filter.term.pgpencrypted.label=OpenPGP Encrypted
# filter.encrypt.label=Encrypt to key (Enigmail)
# filter.keyRequired=You must select a recipient key.
# filter.keyNotFound=Could not find an encryption key for "%S".
# filter.warn.keyNotSecret=Warning - the filter action "Encrypt to key" replaces the recipients.\n\nIf you do not have the secret key for "%S" you will no longer be able to read the emails.
# strings in enigmailConvert.jsm
converter.decryptBody.failed=Nepavyko iššifruoti laiško, kurio tema\n"%S".\nAr norėtumėte bandyti dar kartą, naudojant kitą slaptafrazę, ar norite praleisti laišką?
converter.decryptAtt.failed=Nepavyko iššifruoti priedo "%1$S"\nlaiÅ¡ke, kurio tema\n"%2$S".\nAr norite bandyti dar kartÄ…, naudojant kitÄ… slaptafrazÄ™, ar verÄiau praleisti laiÅ¡kÄ…?
saveLogFile.title=Įrašyti žurnalo failą
# strings in gpg.jsm
unknownSigningAlg=Nežinomas pasirašymo algoritmas (ID: %S)
unknownHashAlg=Nežinoma šifravimo maiša (ID: %S)
# strings in keyRing.jsm
keyring.photo=Nuotrauka
keyRing.pubKeyRevoked=Raktas %1$S (rakto ID %2$S) yra panaikintas.
keyRing.pubKeyExpired=PasibaigÄ— rakto %1$S (rakto ID %2$S) galiojimas.
keyRing.pubKeyNotForSigning=Raktas %1$S (rakto ID %2$S) negali būti naudojamas pasirašymui.
keyRing.pubKeyNotForEncryption=Raktas %1$S (rakto ID %2$S) negali būti naudojamas šifravimui.
keyRing.keyDisabled=Raktas %1$S (rakto ID %2$S) yra išjungtas; jis negali būti naudojamas.
# keyRing.keyNotTrusted=The key %1$S (key ID %2$S) is not trusted enough. Please set the trust level of your key to "ultimate" to use it for signing.
# keyRing.keyInvalid=The key %1$S (key ID %2$S) is not valid. Please consider verifying it correctly. Alternatively use the Default encryption settings in the Enigmail preferences dialog.
keyRing.signSubKeysRevoked=Visi rakto %1$S (rakto ID %2$S) pasiraÅ¡ymo porakÄiai yra panaikinti.
keyRing.signSubKeysExpired=Visų rakto %1$S (rakto ID %2$S) pasiraÅ¡ymo porakÄių galiojimas yra pasibaigÄ™s.
keyRing.signSubKeysUnusable=Visi rakto %1$S (rakto ID %2$S) pasiraÅ¡ymo porakÄiai yra panaikinti, yra pasibaigÄ™s jų galiojimas ar jie yra kitaip netinkami naudoti.
keyRing.encSubKeysRevoked=Visi rakto %1$S (rakto ID %2$S) Å¡ifravimo porakÄiai yra panaikinti.
keyRing.encSubKeysExpired=PasibaigÄ— visų rakto %1$S (rakto ID %2$S) porakÄių galiojimas.
# keyRing.noSecretKey=You do not seem to have the secret key for %1$S (key ID %2$S) on your keyring; you cannot use the key for signing.
keyRing.encSubKeysUnusable=Visi rakto %1$S (rakto ID %2$S) Å¡ifravimo porakÄiai yra panaikinti, yra pasibaigÄ™s jų galiojimas ar jie yra kitaip netinkami naudoti.
#strings in exportSettingsWizard.js
cannotWriteToFile=Nepavyksta įrašyti į failą "%S". Prašome pasirinkti kitą failą.
dataExportError=Jūsų duomenų eksportavimo metu įvyko klaida.
# enigmailSettings=EnigmailSettings
defaultBackupFileName=Enigmail-eksportavimas
specifyExportFile=Nurodykite failo pavadinimÄ… eksportavimui
# homedirParamNotSUpported=Additional params that configure paths such as --homedir and --keyring are not supported for exporting/restoring your settings. Please use alternative methods such as setting the environment variable GNUPGHOME.
#strings in expiry.jsm
# expiry.keyExpiresSoon=Your key %1$S will expire in less than %2$S days.\n\nWe recommend that you create a new key pair and configure the corresponding accounts to use the new key.
expiry.keysExpireSoon=Šie jūsų raktai nustos galioti mažiau nei po %1$S dienų:\n%2$S Rekomenduojame sukurti naujus raktus ir sukonfigūruoti savo paskyras naudoti naujus raktus.
# expiry.keyMissingOwnerTrust=Your secret key %S has missing trust.\n\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.keysMissingOwnerTrust=The following of your secret keys have missing trust.\n%S.\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
expiry.OpenKeyManager=Atverti Enigmail raktų tvarkymą
expiry.OpenKeyProperties=Atverti rakto savybes
#strings in pEpDecrypt.jsm
pEpDecrypt.cannotDecrypt=Tai yra Å¡ifruotas laiÅ¡kas. Deja, jÅ«s neturite Å¡io laiÅ¡ko iššifravimui skirto privaÄiojo rakto.
#strings in gpgAgent.jsm
gpghomedir.notexists=Katalogo "%S" su jūsų OpenPGP raktais nėra ir jis negali būti sukurtas.
gpghomedir.notwritable=Katalogas "%S", kuriame yra jūsų OpenPGP raktai, nėra skirtas rašymui.
gpghomedir.notdirectory=Katalogas "%S", kuriame yra jūsų your OpenPGP raktai, iš tiesų, yra failas, o ne katalogas.
# gpghomedir.notusable=Please fix the directory permissions or change the location of your GnuPG "home" directory. GnuPG cannot work correctly otherwise.
#strings in pepTrustWords.js
# pepTrustWords.cannotVerifyOwnId=Cannot verify p≡p Trustwords for own account.
pepTrustWords.cannotFindKey=Nepavyksta rasti rakto, skirto %S.
# pepTrustWords.cannotStoreChange=Could not change trust for %S.
# pepTrustWords.generalFailure=Cannot obtain trustwords for %S.
pepTrustWords.partnerFingerprint=%S kontrolinis kodas:
#strings in mimeWkdHandler.jsm
# wkdMessage.body.req=Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.\n\nPlease click the confirmation button in the Enigmail header to complete the publishing of your public key.
# wkdMessage.body.process=This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.\n\nYou do not need to take any manual action at this point.
#strings in pepHandshake.js
pepPrivacyStatus.RatingBrokenSuggestion=Arba jūs, arba siuntėjas turėtų išsiųsti laišką iš naujo.
pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=Jeigu jūs parašėte šį laišką, tuomet jūsų raktas yra neprieinamas.
# pepPrivacyStatus.RatingMistrustSuggestion=Re-establish the connection with your communication partner and try to complete another handshake.
# pepPrivacyStatus.RatingReliableSuggestion=Complete a handshake with your communication partner by exchanging trustwords in person or over the phone. A handshake is needed only once per partner and will ensure secure and trusted communication.
pepPrivacyStatus.RatingTrustedSuggestion=Nereikalingas joks veiksmas!
pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Turėkite omenyje, kad šis laiškas gali būti nesaugus.
pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=PridÄ—kite reikiamÄ… informacijÄ….
# pepPrivacyStatus.RatingUnderAttackSuggestion=Separately verify the content of this message with your communication partner.
# pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Make sure the privacy status for each communication partner listed is at least secure.
# pepPrivacyStatus.RatingUnencryptedSuggestion=Please ask your communication partner to use an encryption solution or install p≡p.
# pepPrivacyStatus.RatingUnreliableSuggestion=This message has no reliable encryption or no signature. Ask your communication partner to upgrade their encryption solution or install p≡p.
pepPrivacyStatus.RatingBrokenExplanation=Šiame laiške yra sugadintas šifravimas ar formatavimas.
pepPrivacyStatus.RatingHaveNoKeyExplanation=Šis laiškas negali būti iššifruotas, nes raktas nėra prieinamas.
pepPrivacyStatus.RatingMistrustExplanation=Å iame laiÅ¡ke yra bendravimo partneris, kuris anksÄiau buvo pažymÄ—tas kaip nepatikimas.
pepPrivacyStatus.RatingReliableExplanation=Å is laiÅ¡kas yra saugus, taÄiau vis tiek turite patvirtinti savo bendravimo partnerio tapatybÄ™.
pepPrivacyStatus.RatingTrustedExplanation=Šis laiškas yra saugus ir patikimas.
pepPrivacyStatus.RatingUndefinedExplanation=Šiame laiške nėra pakankamai informacijos, kad būtų nuspręsta ar jis yra saugus ar ne.
# pepPrivacyStatus.RatingUnderAttackExplanation=This message is not secure and has been tampered with.
pepPrivacyStatus.RatingUnencryptedExplanation=Šis laiškas yra nesaugus.
# pepPrivacyStatus.RatingUnencryptedForSomeExplanation=This message is unsecure for some communication partners.
pepPrivacyStatus.RatingUnreliableExplanation=Šiame laiške yra nepatikima apsauga.
# pepPrivacyStatus.RatingBrokenText=Broken
pepPrivacyStatus.RatingHaveNoKeyText=Nepavyksta iššifruoti
# pepPrivacyStatus.RatingMistrustText=Mistrusted
pepPrivacyStatus.RatingReliableText=Saugus
# pepPrivacyStatus.RatingTrustedText=Secure & Trusted
pepPrivacyStatus.RatingUndefinedText=Nežinoma
# pepPrivacyStatus.RatingUnderAttackText=Under Attack
# pepPrivacyStatus.RatingUnencryptedForSomeText=Unsecure for Some
pepPrivacyStatus.RatingUnencryptedText=Nesaugus
pepPrivacyStatus.RatingUnreliableText=Nepatikimas saugumas
handshakeDlg.button.initHandshake=Išankstinis suderinimas...
# handshakeDlg.button.stopTrust=Stop Trusting
# handshakeDlg.button.reTrust=Stop Mistrusting
# handshakeDlg.label.outgoingMessage=Outgoing message
# handshakeDlg.label.incomingMessage=Incoming message
# handshakeDlg.error.noPeers=Cannot handshake without any correspondents.
# handshakeDlg.error.noProtection=Please enable protection in order to use the Handshake function.
enigmail.acSetupPasswd.descEnterPasswd=Įveskite kitame įrenginyje rodomą sąrankos kodą
enigmail.acSetupPasswd.descCopyPasswd=Norėdami tęsti sąranką, įveskite žemiau esantį sąrankos kodą savo kitame įrenginyje
#strings in autocrypt.jsm
# autocrypt.setupMsg.subject=Autocrypt Setup Message
autocrypt.setupMsg.msgBody=Norėdami nusistatyti savo naujajame įrenginyje Autocrypt, sekite instrukciją, kurią turėtų pateikti jūsų naujasis įrenginys.
# autocrypt.setupMsg.fileTxt=This is the Autocrypt setup file used to transfer settings and keys between clients. You can decrypt it using the setup code presented on your old device, and then import the contained key into your keyring.
#strings in upgradeInfo.html
upgradeInfo.doctitle=Kas naujo Enigmail v2.0?
upgradeInfo.welcome1=Sveiki atvykę į naująją Enigmail versiją 2.0!
upgradeInfo.welcome2=Šioje laidoje yra daug naujų ir pakeistų ypatybių. Skirkite minutėlę ir sužinokite kas naujo:
# upgradeInfo.encSubject.title=Encrypting the Message Subject
# upgradeInfo.encSubject.desc=We developed a new method that moves the email subject into the encrypted message, and replaces the visible subject with "Encrypted Message". Once such a message is decrypted, the original subject is replaced automatically. Hiding the subject is on by default; there is a preference to turn it off if you don't like it. (Note: this feature requires the message to be sent with PGP/MIME.)
# upgradeInfo.buttons.title=Changed behavior of Encrypt and Sign Buttons
# upgradeInfo.buttons.desc=The Encrypt and Sign buttons in the message composer window now work for both the OpenPGP and S/MIME protocols. If both algorithms are possible, then Enigmail will try to prefer the one for which all keys are available.
upgradeInfo.autocrypt.title=Autocrypt palaikymas
upgradeInfo.autocrypt.desc=Dabar, Enigmail palaiko Autocrypt, naują standartą, skirtą platinti raktus kaip išsiųstų laiškų dalį. Enigmail automatiškai importuoja raktus iš su Autocrypt suderinamų laiškų ir tokiu būdu, bėgant laikui, gali būti šifruota vis daugiau ir daugiau laiškų.
# upgradeInfo.pEp.title=New p≡p Junior Mode (Pretty Easy Privacy)
# upgradeInfo.pEp.desc=Enigmail now contains a p≡p Junior Mode. You currently need to manually install p≡p for this purpose; this will change in a future release. The p≡p Junior Mode allows you to use OpenPGP encryption as transparently as possible; you don't need to care for key management and synchronization of keys between devices anymore.
upgradeInfo.bottom.desc=Norėdami gauti pagalbos, naudojantis Enigmail, apsilankykite mūsų dokumentacijos puslapyje.
# pep.missingGnuPG=In order to use Enigmail/p≡p, GnuPG is required. As we could not find it, we suggest to download and install it for you.
#strings in enigmailAbout.html
# aboutEnigmail.tabName=About Enigmail
aboutEnigmail.title=Enigmail pateikiamas OpenPGP palaikymas
aboutEnigmail.team=Enigmail kuria Enigmail komanda:
# aboutEnigmail.projectLeader=Lead Developer:
aboutEnigmail.usability=Naudojimosi patogumas:
aboutEnigmail.documentation=Dokumentacija:
aboutEnigmail.testing=Testavimas:
aboutEnigmail.userSupport=Naudotojų palaikymas:
aboutEnigmail.localization=Lokalizavimas: Žiūrėkite Enigmail kalbų paketų puslapį
aboutEnigmail.Credits=PadÄ—kos:
aboutEnigmail.origAuthor=Pradinis Enigmail plÄ—tinio autorius
aboutEnigmail.icons=Piktogramos:
aboutEnigmail.formerMembers=BuvÄ™ komandos nariai:
# aboutEnigmail.projectHosting=Project hosting:
aboutEnigmail.licenseSupportTitle=Licencija ir palaikymas
aboutEnigmail.license=Enigmail OpenPGP atvirojo kodo ir yra licencijuota pagal %S
aboutEnigmail.support=Palaikymas ir atsiuntimai yra prieinami iš www.enigmail.net.
enigmail-2.0.8/lang/lt/help/ 0000775 0000000 0000000 00000000000 13343027545 0015604 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/lt/help/compose.html 0000664 0000000 0000000 00000010076 13343027545 0020143 0 ustar 00root root 0000000 0000000
Enigmail Help: Message Composition
Enigmail Help
Using Enigmail when composing messages
Enigmail menu in Mail/Compose window
Sign message
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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.
Set OpenPGP Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the OpenPGP Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
Decrypt button in main Mail window
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
OpenPGP Security info: allows you to view the output status from GnuPG for the message.
Copy OpenPGP Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Opening encrypted attachments / importing attached OpenPGP keys
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
enigmail-2.0.8/lang/lt/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020454 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
OpenPGP Security info: allows you to view the output status from GnuPG for the message.
Copy OpenPGP Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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.
Set OpenPGP Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the OpenPGP Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
enigmail-2.0.8/lang/nb-NO/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020746 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
OpenPGP Security info: allows you to view the output status from GnuPG for the message.
Copy OpenPGP Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enigmail gebruiken bij het opstellen van een bericht
Enigmail menu in het Mail/Opstellen venster
Onderteken bericht
Ondertekende mail verzenden in- of uitschakelen. De gebruiker wordt gewaarschuwd als het ondertekenen mislukt.
Versleutel bericht
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.
Gebruik PGP/MIME voor dit bericht
Het gebruik van PGP/MIME voor dit bericht in- of uitschakelen.
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.
Standaardopties voor berichtcompositie
Ondertekening/versleuteling opties...: snelkoppeling naar de Accountinstellingen -> OpenPGP opties.
Verzenden opties...: snelkoppeling naar de Voorkeuren -> Verzend tab.
Sleutelselectie opties...: snelkoppeling naar de Voorkeuren -> Sleutelselectie tab.
PGP/MIME opties...: snelkoppeling naar de Voorkeuren -> PGP/MIME tab.
Versleuteling ongedaan maken
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.
De Enigmail regeleditor gebruiken: PGP regels bewerken
In 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.
Stel PGP regels in voor
bevat de e-mailadressen van de ontvangers (zonder namen, d.w.z. enkel een adres zoals persoon@email.domain). U kan meerdere e-mailadressen opgeven, gescheiden door spaties. Het opgegeven e-mailadres kan bestaan uit enkel de domeinnaam zodat alle e-mailadressen van dit domein ermee overeenkomen. Bijvoorbeeld @email.domain zal overeenkomen met per@email.domain,soon@email.domain, persoon@email.domain, enz.
Pas regel toe als ontvanger ...
Dit past de vergelijking van de e-mailadressen aan. Als er meerdere e-mailadressen opgegeven zijn, zal de instelling betrekking hebben op alle e-mailadressen. De voorbeelden hieronder zijn gebaseerd op persoon@email.domain ingegeven in het PGP regels veld erboven.
Is exact met deze instelling heeft de regel enkel betrekking op e-mails naar persoon@email.domain (exact, niet hoofdlettergevoelig).
Bevat met deze instelling zal de regel toegepast worden op elk e-mailadres dat deze tekenreeks bevat. B.v. persoon@email.domain or soon@email.domain.net
Begint met met deze instelling wordt de regel toegepast op e-mailadressen die beginnen met de opgegeven tekenreeks. B.v. per@email.domain.net, per@email.domain-name.com.
Eindigt met met deze instelling wordt de regel toegpast op e-mailadressen die eindigen met de opgegeven tekenreeks. B.v. persoon@email.domain, soon@email.domain.
Ga verder met de volgende regel voor het overeenstemmende adres
Het inschakelen van deze functie staat u toe om een regel te definiëren zonder een KeyID in het Gebruik de volgende OpenPGP sleutel: veld, zodat het e-mailadres gebruikt wordt om de sleutel te controleren op het moment van verzenden. Verdere regels voor hetzelfde adres zullen ook uitgevoerd worden.
Controleer verdere regels voor het overeenstemmende adres niet
Het inschakelen van deze functie zorgt ervoor dat andere regels niet uitgevoerd worden als het adres met deze regel overeenstemd. Er wordt dus direct naar de volgende ontvanger overgeschakeld.
Gebruik de volgende OpenPGP sleutels
Gebruik de Selecteer sleutel(s).. knop om de sleutel van de ontvanger te kiezen die u wilt gebruiken voor versleuteling. Net zoals bij de bovenstaande actie zullen er geen verdere regels voor het overeenstemmende adres uitgevoerd worden.
Standaard voor ondertekening
Ondertekening in- of uitschakelen. Dit gebruikt of overschrijft datgene dat u opgegeven hebt in het berichtopstel venster. Mogelijke waarden zijn:
Nooit: ondertekening uitschakelen, zelf al is het ingeschakeld in het berichtopstelvenster (overschrijft de andere waarden)
Ja, als het geselecteerd is bij Berichtopstelling: laat ondertekening zoals opgegeven in het berichtopstelvenster
Altijd: ondertekening inschakelen, zelfs al is het niet ingeschakeld in het berichtopstelvenster
berichtversleuteling in- of uitschakelen. De toegestane instellingen en hun betekening zijn dezelfde als voor berichtondertekening.
PGP/MIME
Het gebruik van PGP/MIME (RFC 3156) berichtencodering in- of uitschakelen. Als PGP/MIME uitgeschakeld is, worden de berichten met "inline PGP) ondertekend of versleuteld. De toegestane waarden en hun betekenis zijn dezelfde als deze voor berichtondertekening.
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.
enigmail-2.0.8/lang/nl/help/initError.html 0000664 0000000 0000000 00000005040 13343027545 0020440 0 ustar 00root root 0000000 0000000
Enigmail help: Het oplossen van problemen met de OpenPGP initialisatie
OpenPGP Help
Het oplossen van problemen met de OpenPGP initialisatie
Er 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.
Kon GnuPG niet vinden
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).
Initialisatie van EnigMIME is mislukt
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.
Deze knop kan gebruikt worden voor verschillende doelen: ontcijferen, verifiëren of publieke sleutels importeren. Normaalgesproken gebeurt ontcijfering/verificatie automatisch, maar dit kan uitgeschakeld worden door middel van een instelling. Hoewel, als dit mislukt, wordt er een kort foutbericht weergegeven in de Enigmail statusregel. Als u op de Ontcijferknop klikt, zal u een meer gedetailleerd foutbericht zien, samen met de uitvoer van het GPG commando.
Pen- en sleuteliconen in de berichtkop
Het Pen en Sleutel icoon in de berichtkop toont of het bericht dat u aan het lezen bent ondertekend en/of versleuteld was en of de ondertekening goed is, d.w.z. als het bericht niet gewijzigd is sinds de ondertekening. Als het bericht toch gewijzigd is, zal het Pen icoon veranderen naar een Gebroken pen om aan te geven dat de ondertekening ongeldig is. Een rechtermuisklik op het Pen- of Sleutelicoon geeft een menu met de volgende opties:
OpenPGP beveiligingsinfo: staat u toe de outputstatus van GPG voor het bericht te bekijken.
Kopieer OpenPGP beveiligingsinfo: kopieert de output status van GPG naar het klembord; om in een antwoord te plakken, enz.
Bekijk PGP foto ID: staat u toe om het Foto ID van de persoon die u het bericht gezonden heeft te bekijken, als er natuurlijk een foto ingebed zit in de publieke sleutel. (Deze optie is enkel beschikbaar als er een Foto ID bestaat in de gebruikte sleutel.)
S/MIME beveilingsinfo: staat u toe om de S/MIME beveilingsinfo van het bericht te bekijken.
Als 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.
Bijlagen met de extensie *.pgp, *.asc en *.gpg worden herkend door Enigmail en worden speciaal behandeld. Bij een rechtermuisklik op zo een bijlage krijg je twee speciale menu items in het contextmenu: Ontcijfer en open en Ontcijfer en sla op als.... Gebruik deze twee menu items als u wilt dat Enigmail de bijlage ontcijfert voor deze te openen of op te slaan. Als een bijlage herkend word als een OpenPGP sleutelbestand, krijg je de kans om de sleutels in je sleutelbos te importeren.
In 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:
E-mail
De e-mail(s) van de Aan:, Cc: and Bcc: velden om te controleren. De controle werkt op subreeksen (Verdere details kunnen gevonden worden in het Bewerk regel dialoogvenster).
PGP sleutel(s)
een lijst van PGP sleutel ID's om te gebruiken voor de ontvanger
Onderteken
berichtondertekening in- of uitschakelen. Dit gebruikt of overschrijft de instelling die u gebruikt in het berichtenopstelvenster. De waarden zijn:
Nooit: ondertekening uitschakelen, zelf al is het ingeschakeld in het berichtopstelvenster (overschrijft de andere waarden)
Mogelijk: laat ondertekening als opgegeven in het berichtopstelvenster
Altijd: ondertekening inschakelen, zelfs al is het niet ingeschakeld in het berichtopstelvenster
berichtversleuteling in- of uitschakelen. De toegestane instellingen zijn dezelfde als voor berichtondertekening.
PGP/MIME
het gebruik van PGP/MIME (RFC 3156) in- of uitschakelen. Als PGP/MIME uitgeschakeld is, zullen de berichten versleuteld of ondertekend worden met "inline PGP". De toegestane waarden en hun betekenis zijn dezelfde als voor berichtondertekening.
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
Voorkeuren instellen om versleutelde e-mail te versturen
Bij de Verzenden voorkeuren kunt u het algemene model en de voorkeuren voor versleuteling kiezen.
Handige versleuteling
Met deze instellingen worden e-mails zonder bevestiging versleuteld, indien mogelijk.
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.
Handmatige versleuteling
Met deze instellingen kunt u de verschillende voorkeuren voor versleuteling handmatig aan uw behoefte aanpassen. U kunt opgeven:
of antwoorden op versleutelde/ondertekende e-mails ook automatisch versleuteld/ondertekend moeten worden;
of u het vertrouwensmodel van OpenPGP wilt gebruiken om sleutels te accepteren (dit betekent dat u om een sleutel te kunnen gebruiken, u deze sleutel moet ondertekenen, of dat er genoeg andere personen zijn die u vertrouwt die de sleutel ondertekend hebben);
of u automatisch alle e-mails versleuteld wilt versturen als alle sleutels geaccepteerd zijn;
of en wanneer u eindelijk wilt bevestigen dat u een e-mail wilt versturen.
Als u het belangrijk vindt dat inhoud die u versleutelt niet door andere personen of organisaties gelezen kan worden, dan dient u de handmatige instellingen te kiezen en op zijn minst de optie te selecteren om alleen sleutels te accepteren als u of andere mensen ze ondertekend hebben. Hoewel dit model het risico op vervalste sleutels vermindert, moet u wel actief sleutels ondertekenen en het eigenaarsvertrouwen aangeven via sleutelbeheer.
enigmail-2.0.8/lang/pl/ 0000775 0000000 0000000 00000000000 13343027545 0014650 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/pl/am-enigprefs.properties 0000664 0000000 0000000 00000000110 13343027545 0021333 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=OpenPGP
enigmail-2.0.8/lang/pl/enigmail.dtd 0000664 0000000 0000000 00000154255 13343027545 0017146 0 ustar 00root root 0000000 0000000
Mozilla Public License 2.0.">
"Transfer kluczy Autocrypt" wymaga, aby klient poczty e-mail na drugim urządzeniu był zgodny z Autocrypt.
Chociaż jest to łatwiejsze rozwiązanie, tylko kilka aplikacji obsługuje ten standard.
Innym sposobem jest "Utworzenie i przywrócenie kopii zapasowej" swoich ustawień.
Spowoduje to utworzenie pliku ZIP zawierającego wszystkie wymagane informacje i klucze, które można skopiować na nowe urządzenie.
Enigmail może bezpośrednio zaimportować te ustawienia; w przypadku innych klientów poczty e-mail plik ZIP można rozpakować i obsłużyć ręcznie.">
">
do oznaczania adresów e-mail dla GnuPG. Wyłącz tę funkcję, jeżeli adresaci posiadają stare klucze Hushmail.">
Konfiguracja kont -> OpenPGP).">
Uwaga! Tworzenie klucza może potrwać kilka minut. Nie zamykaj programu w trakcie działania generatora. Aktywne używanie przeglądarki lub wykonywanie intensywnych operacji dyskowych podczas tworzenia klucza przyspieszy proces. Koniec procesu zostanie zasygnalizowany odpowiednim komunikatem.">
†jest nieprawidłowy">
Uwaga! Generowanie klucza może potrwać kilka minut. Nie zamykaj programu w trakcie działania generatora. Koniec procesu zostanie zasygnalizowany odpowiednim komunikatem.">
Uwaga! Enigmail będzie zawsze weryfikować podpisy w wiadomościach dla wszystkich tożsamości i kont, niezależnie od tego czy obsługa Enigmail jest włączona, czy nie">
Dziękujemy za wybór Enigmail Enigmail!">
enigmail-2.0.8/lang/pl/enigmail.properties 0000664 0000000 0000000 00000154440 13343027545 0020563 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Ostrzeżenie Enigmail
enigConfirm=Potwierdzenie Enigmail
# enigInfo=Enigmail Information
enigError=Błąd Enigmail
enigPrompt=Wprowadź dane Enigmail
dlgYes=&Tak
dlgNo=&Nie
dlgKeepSetting=Zapamiętaj mój wybór i nie wyświetlaj ponownie
dlgNoPrompt=Nie wyświetlaj więcej tego okna
dlg.button.delete=&Usuń
dlg.button.cancel=&Anuluj
dlg.button.close=&Zamknij
dlg.button.continue=&Kontynuuj
dlg.button.skip=&Pomiń
dlg.button.overwrite=Przepisać
dlg.button.view=Po&dglÄ…d
dlg.button.retry=Znowu
dlg.button.ignore=&Ignorować
# dlg.button.install=&Install
# dlg.button.ok=&OK
repeatPrefix=\n\nTo ostrzeżenie będzie powtórzone %S
repeatSuffixSingular=raz.
repeatSuffixPlural=razy.
noRepeat=\n\nTo ostrzeżenie nie pojawi się dopóki nie zaktualizujesz Enigmail.
pgpNotSupported=Wygląda na to, że używasz Enigmail razem z PGP 6.x\n\nNiestety, PGP 6.x ma dużo właściwości, które powodują niepoprawne działanie Enigmail. Dlatego też, PGP 6.x nie będzie dłużej obsługiwane. Zamiast tego zalecane jest zainstalowanie GnuPG (GPG).\n\nJeżeli potrzebujesz pomocy przy instalacji GnuPG, sprawdź sekcję „Pomoc†na stronie domowej Enigmail.
# initErr.howToFixIt=In order to use Enigmail, GnuPG is required. If you did not install GnuPG yet, the easiest way to do this is using the "Setup Wizard" button below.
initErr.setupWizard.button=Kreator Konfiguracji
passphraseCleared=Szyfr został usunięty z pamięci.
# cannotClearPassphrase=You are using a non-standard tool (such as gnome-keyring) for passphrase handling. Clearing the passphrase is therefore not possible from within Enigmail.
noPhotoAvailable=Brak zdjęcia
debugLog.title=Dziennik zdarzeń debugowania Enigmail
error.photoPathNotReadable=Nie można odczytać Å›cieżki „%Sâ€
# generalError=Error: %S
# Strings in configure.jsm
enigmailCommon.versionSignificantlyChanged=Ta wersja Enigmail wprowadza istotne zmiany w obsłudze preferencji i opcji. Dołożyliśmy wszelkich starań, aby przenieść ustawienia z poprzednich wersji do aktualnej, tam gdzie było to możliwe. Prosimy o dokładne sprawdzenie nowych preferencji i opcji.
enigmailCommon.checkPreferences=Sprawdź preferencje...
# preferences.defaultToPgpMime=We have changed the default message encoding in Enigmail from Inline-PGP to PGP/MIME. We recommend you keep this as default.\n\nIf you still wish to use Inline-PGP by default, you can do so in the Account Settings under OpenPGP Security.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=Uruchomiono Enigmail, wersja %S
# enigmailPepVersion=Enigmail/p≡p version %S
usingAgent=Szyfrowanie i weryfikacja programem %S: %S
agentError=Błąd! Nie można uzyskać dostępu do usługi Enigmime!
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Wystąpił błąd podczas próby uzyskania dostępu do usługi Enigmail
onlyGPG=Tworzenie kluczy działa tylko z GnuPG (nie działa z PGP)!
keygenComplete=Zakończono tworzenie klucza!\nTożsamość <%S> będzie używana do podpisywania.
revokeCertRecommended=Zaleca się utworzenie certyfikatu unieważnienia dla tego klucza. Certyfikat ten posłuży do unieważnienia klucza, np. jeżeli zaginie klucz prywatny lub zostanie on wykradziony. Czy utworzyć teraz taki certyfikat?
keyMan.button.generateCert=&Utwórz certyfikat
genCompleteNoSign=Zakończono tworzenie klucza!
genGoing=Trwa tworzenie klucza…!
passNoMatch=Wprowadzone szyfry są niezgodne – wprowadź ponownie
passCheckBox=Proszę zaznaczyć pole, jeśli nie podano szyfru do klucza
passUserName=Podaj nazwę użytkownika dla tej tożsamości
# keygen.missingUserName=There is no name specified for the selected account/identity. Please enter a value in the field "Your name" in the account settings.
# keygen.passCharProblem=You are using special characters in your passphrase. Unfortunately, this can cause troubles for other applications. We recommend you choose a passphrase consisting only of any of these characters:\na-z A-Z 0-9 /.;:-,!?(){}[]%*
passSpaceProblem=Z powodów technicznych szyfr nie może zaczynać się lub kończyć spacją.
changePassFailed=Nie udało się zmienić szyfru.
keyConfirm=Utworzyć klucz publiczny i prywatny dla „%S�
keyMan.button.generateKey=&Utwórz klucz
keyAbort=Czy przerwać tworzenie klucza?
keyMan.button.generateKeyAbort=&Przerwij tworzenie klucza
keyMan.button.generateKeyContinue=&Kontynuuj tworzenie klucza
expiryTooLong=Nie można tworzyć kluczy ważnych dłużej niż 100 lat.
expiryTooLongShorter=Nie można tworzyć kluczy, których okres ważności jest dłuższy niż 90 lat.
expiryTooShort=Klucz musi być ważny przynajmniej jeden dzień.
keyGenFailed=Nie udało się utworzyć klucza. Szczegóły wykonywanej operacji można znaleźć w konsoli Enigmail (menu Enigmail -> Debugowanie Enigmail).
setKeyExpirationDateFailed=Data wygaśnięcia nie mogła zostać zmieniona
# Strings in enigmailMessengerOverlay.js
securityInfo=Informacja Enigmail\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Załączniki do tej wiadomości nie zostały podpisane ani zaszyfrowane*\n\n
possiblyPgpMime=Wiadomość prawdopodobnie podpisana/zaszyfrowana za pomocą PGP/MIME – naciśnij przycisk Odszyfruj/Weryfikuj, aby to sprawdzić
saveAttachmentHeader=Enigmail: Zapisz odszyfrowany załącznik
noTempDir=Nie można znaleźć katalogu plików tymczasowych.\nProszę ustawić odpowiednią ścieżkę jako wartość zmiennej systemowej TEMP.
attachmentPgpKey=Otwierany załącznik „%S†jest plikiem klucza OpenPGP.\n\nNaciÅ›nij przycisk „Importâ€, aby zaimportować zawarty w nim klucz lub „PodglÄ…dâ€, aby wyÅ›wietlić zawartość w oknie przeglÄ…darki.
beginPgpPart=********* *POCZATEK CZESCI SZYFROWANEJ / PODPISANEJ* *********
endPgpPart=********** *KONIEC CZESCI SZYFROWANEJ / PODPISANEJ* **********
notePartEncrypted=Enigmail: *Niektóre fragmenty wiadomości NIE zostały podpisane lub zaszyfrowane*
noteCutMessage=Enigmail: *Znaleziono bloki wielu wiadomości – przerwano odszyfrowanie/weryfikację*
decryptOkNoSig=Uwaga!\n\nWiadomość została odszyfrowana, ale nie można prawidłowo zweryfikować podpisu.
msgOvl.button.contAnyway=Czy chcesz &kontynuować?
signature.verifiedOK=Podpis załącznika %S został pomyślnie zweryfikowany
signature.verifyFailed=Nie można zweryfikować podpisu załącznika %S
attachment.noMatchToSignature=Nie można dopasować załącznika %S do pliku podpisu
attachment.noMatchFromSignature=Nie można dopasować pliku podpisu %S do załącznika
fixBrokenExchangeMsg.failed=Nie uda się naprawić wiadomość.
# enigmail.msgViewColumn.label=Enigmail
# enigmailPep.msgViewColumn.label=Enigmail/p≡p
# wksNoIdentity=This key is not linked to any of your email accounts. Please add an account for at least one of the following email addresse(s):\n\n%S
# wksConfirmSuccess=Confirmation email sent.
# wksConfirmFailure=Sending the confirmation email failed.
# autocrypt.importSetupKey.accountPreconfigured=Your account is already correctly configured for Autocrypt.\n\nDo you really want to overwrite your settings with this setup message?
# autocrypt.importSetupKey.selfCreated=This message was created by your currently running instance of Enigmail.\n\nPlease switch to the email client to which you want to transfer the settings, and click on the message on that email client to import the settings.
# autocrypt.importSetupKey.invalidMessage=Error - could not read setup message. The message seems to be corrupted. Please try to create a new setup message on your "other" device.
# autocrypt.importSetupKey.invalidKey=Error - the key could not be imported. The key is either not supported by your version of GnuPG, or it got corrupted.
# autocrypt.importSetupKey.wrongPasswd=The password you entered is wrong. Do you want to retry?
# autocrypt.importSetupKey.success=The Autocrypt setup message was processed successfully. Autocrypt is now available for your account '%S'.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Wybierz klucze OpenPGP do wstawienia
keysToUse=Wybierz klucze OpenPGP używane dla %S
pubKey=Klucz publiczny dla %S\n
windowLocked=Okno tworzenia wiadomości jest zablokowane – wysyłanie anulowane
sendUnencrypted=Nie udało się zainicjować Enigmail.\nWysłać niezaszyfrowaną wiadomość?
composeSpecifyEmail=Wybierz swój adres e-mail, według którego wybierany będzie klucz do podpisywania wysyłanych wiadomości.\n Jeżeli zostawisz to pole niewypełnione, zostanie użyty adres z pola OD: wysyłanej wiadomości.
sendingHiddenRcpt=Ta wiadomość zawiera adresy w polu Ukryta kopia. Jeżeli wiadomość jest szyfrowana, możliwe jest ukrycie odbiorców ukrytej kopii, ale użytkownicy niektórych produktów, np. PGP Corp. nie będą mogli odszyfrować takiej wiadomości. Z tego powodu zaleca się nie korzystać z pól Ukryta kopia w szyfrowanych wiadomościach.
sendWithHiddenBcc=Ukryj odbiorców ukrytej kopii
sendWithShownBcc=Zaszyfruj normalnie
sendingNews=Operacja wysyłania szyfrowanej wiadomości została przerwana.\n\nWiadomości tej nie można zaszyfrować, ponieważ na liście odbiorców jest grupa dyskusyjna. Należy ponownie wysyłać wiadomość bez szyfrowania.
sendToNewsWarning=Uwaga. Wysyłasz zaszyfrowaną wiadomość na adres grupy dyskusyjnej.\n\nOdradzamy takie działanie, ponieważ ma ono sens tylko wtedy, gdy wszyscy użytkownicy grupy mogą odszyfrować taką wiadomość, tzn. wiadomość taka musiałaby być zaszyfrowana kluczami wszystkich użytkowników grupy. Wyślij wiadomość tylko, jeżeli wiesz dokładnie co robisz.\n\nKontynuować?
hasHTML=Ostrzeżenie o wiadomoÅ›ci w formacie HTML:\nTa wiadomość może zawierać kod HTML, co może uniemożliwić podpisanie/szyfrowanie wiadomoÅ›ci. Aby zapobiec temu w przyszÅ‚oÅ›ci, wciÅ›nij klawisz SHIFT, gdy naciskasz przycisk komponowania/odpowiedzi, żeby wysyÅ‚ać podpisane wiadomoÅ›ci.\nJeżeli domyÅ›lnie wysyÅ‚asz podpisane wiadomoÅ›ci, należy w ustawieniach odznaczyć funkcjÄ™ „Podczas tworzenia wiadomoÅ›ci używaj edytora HTMLâ€, aby na staÅ‚e wyłączyć wiadomoÅ›ci HTML dla tego konta pocztowego.
strippingHTML="Wiadomość zawiera informację o formatowaniu w HTML, która zostanie utracona po konwersji do zwykłego tekstu przy podpisywaniu/szyfrowaniu. Czy chcesz kontynuować?
msgCompose.button.sendAnyway=&Wyślij wiadomość
attachWarning=Załączniki do tej wiadomości nie są zapisane lokalnie i nie mogą być zaszyfrowane. Aby je zaszyfrować, należy zapisać załączniki jako pliki lokalne i następnie dołączyć do wiadomości. Czy na pewno wysłać wiadomość?
quotedPrintableWarn=Włączono kodowanie „quoted-printable†dla wysyłanych wiadomości. Może to spowodować nieprawidłowe odszyfrowanie lub weryfikację wiadomości.\nCzy wyłączyć to kodowanie?
minimalLineWrapping=Ustawiono zawijanie wierszy dłuższych niż %S znaków. Aby poprawnie szyfrować lub podpisywać wiadomości, ta wartość musi wynosić co najmniej 68.\nCzy ustawić zawijanie wiersza powyżej 68 znaków?
warning=Uwaga
signIconClicked=Zmieniono ręcznie opcje podpisywania. Dlatego też, podczas komponowania tej wiadomości dezaktywacja/aktywacja podpisywania nie zależy od dezaktywacji/aktywacji szyfrowania.
# errorOwnKeyUnusable=The key ID '%S' configured for the current identity does not yield a usable OpenPGP key.\n\nPlease ensure that you have a valid, not expired OpenPGP key and that your account settings point to that key.\nIf your key is not expired, then check if you did set Owner trust to full or ultimate.
msgCompose.cannotSaveDraft=Błąd podczas zapisywania projektu
# msgCompose.partiallyEncrypted.short=Beware of leaking sensitive information - partially encrypted email.
# msgCompose.partiallyEncrypted.mimeMsg=The message you are replying to contained both unencrypted and encrypted parts. Some encrypted message parts are invisible to you.\n\nIf the sender was not able to decrypt the hidden message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nWe recommend that you don't reply to the message, but create a new message containing your answer.
# msgCompose.partiallyEncrypted.inlinePGP=The message you are replying to contained both unencrypted and encrypted parts. If the sender was not able to decrypt some message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nPlease consider removing all quoted text from your reply to this sender.
msgCompose.internalEncryptionError=Błąd wewnętrzny: obiecał szyfrowanie wyłączone
msgCompose.internalError=Wystąpił błąd wewnętrzny.
msgCompose.toolbarTxt.signAndEncrypt=Ta wiadomość zostanie podpisana i zaszyfrowana
msgCompose.toolbarTxt.signOnly=Ten komunikat zostanie podpisana
msgCompose.toolbarTxt.encryptOnly=Ten komunikat zostanie zaszyfrowana
msgCompose.toolbarTxt.noEncryption=Ten komunikat będzie niepodpisane i nieszyfrowane
msgCompose.toolbarTxt.disabled=Enigmail jest wyłączona dla wybranej tożsamości
# msgCompose.protectSubject.tooltip=Protect the message subject
# msgCompose.noSubjectProtection.tooltip=Do not protect the message subject
msgCompose.encryptedSubjectStub=Zaszyfrowaną Wiadomość
# msgCompose.protectSubject.dialogTitle=Enable Protection of Subject?
# msgCompose.protectSubject.question=Regular encrypted emails contain the unredacted subject.\n\nWe have established a standard to hide the original subject in the encrypted message\nand replace it with a dummy text, such that the subject is only visible after the email is decrypted.\n\nDo you want to protect the subject in encrypted messages?
# msgCompose.protectSubject.yesButton=&Protect subject
# msgCompose.protectSubject.noButton=&Leave subject unprotected
msgCompose.detailsButton.label=Detale ...
msgCompose.detailsButton.accessKey=D
# msgCompose.pepSendUnknown=Unknown
# msgCompose.pepSendUnsecure=Unsecure
# msgCompose.pepSendSecure=Secure
# msgCompose.pepSendTrusted=Secure & Trusted
# pep.alert.disabledForIdentity=p≡p is disabled for the current identity. Please enable p≡p via the Enigmail/p≡p preferences.
# pep.alert.weakReply=You’re about to forward or reply to a secure message as insecure. If you choose to proceed, confidential information might be leaked putting you and your communication partner at risk. Are you sure you want to continue?
# note: should end with double newline:
sendAborted=Operacja wysyłania zostaa anulowana.\n\n
# details:
keyNotTrusted=Za mało zaufania dla klucza '%S'
keyNotFound=Klucz '%S' nie znaleziono
keyRevoked=Klucz '%S' odwołane
keyExpired=Klucz '%S' upłynął
statPGPMIME=PGP/MIME
# statSMIME=S/MIME
statSigned=PODPISANÄ„
statEncrypted=ZASZYFROWANÄ„
statPlain=NIEPODPISANÄ„ i NIEZASZYFROWANÄ„
offlineSave=Zapisać wiadomość %S do %S w folderze „Niewysłane�
onlineSend=Wysłać wiadomość %S do %S?
encryptKeysNote=Informacja. Wiadomość zaszyfrowana za pomocą następującego ID użytkownika/klucza: %S
hiddenKey=
signFailed=Błąd w Enigmail! Szyfrowanie/podpisanie się nie powiodło. Wysłać wiadomość bez szyfrowania/podpisu?
msgCompose.button.sendUnencrypted=&Wyślij niezaszyfrowaną wiadomość
recipientsSelectionHdr=Wybierz odbiorców do szyfrowania
configureNow=Nie włączono jeszcze zabezpieczeń Enigmail dla tej tożsamości. Czy chcesz to zrobić teraz?
# encryption/signing status and associated reasons:
encryptMessageAuto=Szyfrowanie wiadomości (automatyczny)
encryptMessageNorm=Szyfrowanie Wiadomości
signMessageAuto=Znak Wiadomość (automatyczny)
signMessageNorm=Znak Wiadomość
encryptOff=Szyfrowanie: OFF
encryptOnWithReason=Szyfrowanie: ON (%S)
encryptOffWithReason=Szyfrowanie: OFF (%S)
encryptOn=Szyfrowanie: ON
signOn=Podpisanie: ON
signOff=Podpisanie: OFF
signOnWithReason=Podpisanie: ON (%S)
signOffWithReason=Podpisanie: OFF (%S)
reasonEnabledByDefault=domyślnie włączone
reasonManuallyForced=ręcznie zmuszony
reasonByRecipientRules=wymuszone przez przepisy otrzymujÄ…cych
reasonByAutoEncryption=zmuszony przez szyfrowanie automatyczny
reasonByConflict=z powodu konfliktu w przepisach otrzymujÄ…cych
reasonByEncryptionMode=ze względu na tryb szyfrowania
# should not be used anymore:
encryptYes=Wiadomość zostanie zaszyfrowana
encryptNo=Wiadomość nie zostanie zaszyfrowana
# should not be used anymore:
signYes=Wiadomość zostanie podpisana
signNo=Wiadomość nie zostanie podpisana
# PGP/MIME status:
pgpmimeNormal=Protokół: PGP/MIME
inlinePGPNormal=Protokół: PGP Inline
# smimeNormal=Protocol: S/MIME
pgpmimeAuto=Protokół: PGP/MIME (automatyczny)
inlinePGPAuto=Protokół: PGP Inline (automatyczny)
# smimeAuto=Protocol: S/MIME (auto)
# should not be used anymore
pgpmimeYes=Zostanie użyte PGP/MIME
pgpmimeNo=Zostanie użyte PGP/Inline
# Attach own key status (tooltip strings):
attachOwnKeyNo=Twój własny klucz nie zostanie dołączony
attachOwnKeyYes=Własny klucz zostanie dołączony
# attachOwnKeyDisabled=Your own key cannot be attached. You have to select a specific key\nin the OpenPGP section of the Account Settings to enable this feature.
rulesConflict=Wykryto kolizję reguł Enigmail dla odbiorcy\n%S\n\nCzy wysłać wiadomość z tymi ustawieniami?
msgCompose.button.configure=&Konfiguruj
msgCompose.button.send=&Wyślij wiadomość
msgCompose.button.save=&Zapisz wiadomość
# Strings in enigmailMsgHdrViewOverlay.js
keyNeeded=Wymagany jest klucz publiczny %S, aby zweryfikować podpis
keyUsed=Klucz publiczny %S służy do weryfikacji podpisu
clickDecrypt=; naciśnij przycisk Odszyfruj
clickDecryptRetry=; naciśnij przycisk Odszyfruj, aby ponowić próbę
clickDetailsButton=; kliknij na przycisk 'Detale', aby uzyskać więcej informacji
# clickImportButton=; click on the 'Import Key' button to import the key
# keyTypeUnsupported=; the key type is not supported by your version of GnuPG
msgPart=Część wiadomości %S
msgSigned=podpisana
msgSignedUnkownKey=podpisana nieznanym kluczem
msgEncrypted=zaszyfrowana
msgSignedAndEnc=podpisana i zaszyfrowana
unverifiedSig=Podpis bez weryfikacji
incompleteDecrypt=Odszyfrowanie nie zostało zakończone
needKey=Błąd – potrzebny klucz, aby odszyfrować wiadomość
failedDecrypt=Błąd – nie powiodło się odszyfrowanie
badPhrase=Błąd – nieprawidłowy szyfr
failedDecryptVerify=Błąd – nie powiodło się odszyfrowanie/weryfikacja
mdcError=Błąd – wiadomość nie była zabezpieczona przed manipulacją
viewInfo=; Widok » Informacje o zabezpieczeniach wiadomości, aby zobaczyć szczegóły
decryptedMsg=Odszyfrowana wiadomość
decryptedMsgWithFormatError=Rozszyfrowana wiadomość (formatowanie uszkodzone prawdopodobnie przez serwer Exchange, wiadomość może być trudna do odczytania).
usedAlgorithms=Używane Algorytmy: %S i %S
# pepStatusInfo.text=p≡p Message Status.
# pepStatusInfo.title.m3=Under Attack
# pepStatusInfo.info.m3=This message is not secure and has been tampered with.
# pepStatusInfo.title.m1=Mistrusted
# pepStatusInfo.info.m1=This message has a communication partner that has previously been marked as mistrusted
# pepStatusInfo.title.r0=Unknown
# pepStatusInfo.info.r0=This message does not contain enough information to determine if it is secure.
# pepStatusInfo.title.r1=Cannot Decrypt
# pepStatusInfo.info.r1=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r2=Cannot Decrypt
# pepStatusInfo.info.r2=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r3=Unsecure
# pepStatusInfo.info.r3=This message is unsecure.
# pepStatusInfo.title.r4=Unsecure for Some
# pepStatusInfo.info.r4=This message is unsecure for some communication partners.
# pepStatusInfo.title.r5=Unreliable Security
# pepStatusInfo.info.r5=This message has unreliable protection.
# pepStatusInfo.title.r6=Secure...
# pepStatusInfo.info.r6=This message is secure but you still need to verify the identity of your communication partner.
# pepStatusInfo.title.r7=Secure & Trusted
# pepStatusInfo.info.r7=This message is secure and trusted.
# pepStatusInfo.color.green=Green
# pepStatusInfo.color.yellow=Yellow
# pepStatusInfo.color.red=Red
# pepRevokeTrust.question=Do you really want to cancel the trust for %S?
# pepRevokeMistrust.question=Do you really want to re-trust the key for %S?
# pepRevokeTrust.doRevoke=Cancel &trust
# wksConfirmationReq=Web Key Directory Confirmation Request
# wksConfirmationReq.message=This message has been sent by your email provider to confirm deployment of your OpenPGP public key\nin their Web Key Directory.\nProviding your public key helps others to discover your key and thus being able to encrypt messages to you.\n\nIf you want to deploy your key in the Web Key Directory now, please click on the button "Confirm Request" in the status bar.\nOtherwise, simply ignore this message.
# wksConfirmationReq.button.label=Confirm Request
# autocryptSetupReq=Perform Autocrypt Setup
# autocryptSetupReq.button.label=Start Setup
# autocryptSetupReq.setupMsg.desc=This message contains all information to transfer your Autocrypt settings along with your secret key securely from your original device.
# autocryptSetupReq.setupMsg.backup=You can keep this message and use it as a backup for your secret key. If you want to do this, you should write down the password and store it securely.
# autocryptSetupReq.message.import=To import the settings and key(s) in Enigmail, please click on the "Start Setup" button in the status bar.
# autocryptSetupReq.message.sent=Please click on the message on your new device and follow the instuctions to import the settings.
# strings in pref-enigmail.js
# oldGpgVersion20=Enigmail initialization failed.\n\nYou are using GnuPG version %1$S, which is not supported anymore. Enigmail requires GnuPG version %2$S or newer. Please upgrade your GnuPG installation, or Enigmail will not work.
locateGpg=Znajdź program GnuPG
invalidGpgPath=Nie udało się uruchomić GnuPG z podanej ścieżki. Dlatego też Enigmail będzie nieaktywne, dopóki nie zostanie zmieniona ścieżka do programu GnuPG lub dopóki nie zrestartujesz aplikacji.
warningsAreReset=Wszystkie ostrzeżenia będą pokazywane od nowa.
prefs.gpgFound=GnuPG znaleziono w katalogu %S
prefs.gpgNotFound=Nie można znależć GnuPG
prefs.warnAskNever=Ostrzeżenie! Włączenie tej opcji oznacza niezaszyfrowane wiadomości bez żadnej informacji o brakującym kluczu dla któregoś z odbiorców – Enigmail nie poinformuje o takim przypadku!
prefs.warnIdleTimeForUnknownAgent=Twój system używa specjalistycznych narzędzi do obsługi szyfru, takich jak gnome-keyring lub seahorse-agent. Niestety Enigmail nie może kontrolować limitu czasu szyfru używanego narzędzia. Dlatego poszczególne ustawienia limitu czasu w Enigmail są pomijane.
prefEnigmail.oneKeyserverOnly=Błąd – w ustawieniach automatycznego pobierania brakujących kluczy OpenPGP można wskazać tylko jeden serwer kluczy.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Wprowadź ADMIN PIN swojej karty SmartCard
enterCardPin=Wprowadź PIN swojej karty SmartCard
notInit=Błąd – usługa Enigmail nie zainicjowana
badCommand=Błąd – nie powiodło się polecenie szyfrowania
cmdLine=składnia i wynik polecenia:
notRequired=Błąd – szyfrowanie nie jest wymagane
notComplete=Błąd – generowanie kluczy nie jest jeszcze zakończone
invalidEmail=Błąd – nieprawidłowe adresy e-mail
noPassphrase=Błąd – nie podano szyfru
noPGPblock=Błąd – nie znaleziono prawidłowego bloku danych OpenPGP
unverifiedReply=Cytowana część wiadomości (odpowiedzi) została prawdopodobnie zmodyfikowana
# keyInMessageBody=Key in message body found. Click 'Import Key' to import the key
sigMismatch=Błąd – podpis nie pasuje
cantImport=Błąd przy importowaniu klucza publicznego\n\n
# doImportOne=Import %1$S (%2$S)?
# doImportMultiple=Import the following keys?\n\n%S
# previewFailed=Can't read public key file.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=Karta SmartCard %S znaleziona w czytniku nie może być użyta do przetworzenia wiadomości.\nWłóż kartę %S i ponów operację.
sc.insertCard=Ta operacja wymaga karty SmartCard %S.\nWłóż wymaganą kartę i ponów operację.
sc.removeCard=Ta operacja wymaga usunięcia karty SmartCard z czytnika.\nUsuń kartę i ponów operację.
sc.noCardAvailable=Nie znaleziono karty SmartCard w czytniku\nWłóż kartę do czytnika i ponów operację
sc.noReaderAvailable=Brak dostępu do czytnika kart SmartCard\nPodłącz czytnik, włóż swoją kartę i ponów operację
# keyError.keySpecNotFound=The email address "%S" cannot be matched to a key on your keyring.
# keyError.keyIdNotFound=The configured key ID "%S" cannot be found on your keyring.
# keyError.resolutionAction=Please select a valid key in the OpenPGP section of your Account Settings.
# missingPassphrase=Missing passphrase
# errorHandling.gpgAgentInvalid=Your system is running a version of gpg-agent that is not suitable for your GnuPG version.
# errorHandling.gpgAgentError=GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
# errorHandling.dirmngrError=GnuPG reported an error in the communication with dirmngr (a component of GnuPG).
# errorHandling.pinentryError=GnuPG cannot query your passphrase via pinentry.
# errorHandling.readFaq=This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.\n\nWe strongly recommend that you consult our support web site at https://enigmail.net/faq.
gpgNotFound=Nie odnaleziono programu GnuPG „%Sâ€.\nSprawdź w ustawieniach Enigmail czy jest okreÅ›lona prawidÅ‚owa Å›cieżka do programu GnuPG.
gpgNotInPath=W podanym położeniu nie znaleziono programu GnuPG.\nSprawdź w ustawieniach Enigmail czy jest określona prawidłowa ścieżka do programu GnuPG.
# enigmailNotAvailable=Enigmail core Service not available
prefGood=Prawidłowy podpis od %S
prefBad=NIEPRAWIDÅOWY podpis od %S
failCancel=Błąd – użytkownik anulował odbiór klucza
failNoServer=Błąd – nie wprowadzono nazwy serwera kluczy
failNoID=Błąd – brak ID klucza do pobrania
failKeyExtract=Błąd – nie powiodło się uzyskanie klucza
notFirstBlock=Błąd – pierwszy blok OpenPGP nie jest blokiem klucza publicznego
importKeyConfirm=Czy zaimportować klucze publiczne osadzone w wiadomości?
failKeyImport=Błąd – nie powiodło się zaimportowanie klucza
fileWriteFailed=Błąd zapisu do pliku %S
importKey=Importowanie klucza publicznego %S z serwera kluczy:
uploadKey=Eksportowanie klucza publicznego %S do serwera:
keyId=ID klucza
keyAndSigDate=ID klucza: 0x%S / Podpisano dnia: %S
keyFpr=Odcisk klucza: %S
noEmailProvided=Nie podano adresu e-mail!
keyAlreadySigned=Ten klucz jest już podpisany, nie można podpisać go ponownie.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=przedawniony %S
createdHeader=Utworzony
atLeastOneKey=Nie wybrano klucza! Należy zaznaczyć co najmniej jedną pozycję.
fewerKeysThanRecipients=Zaznaczono mniejszą liczbę kluczy niż odbiorców. Czy na pewno ten zestaw kluczy do szyfrowania jest kompletny?
userSel.button.goBack=Wybierz więcej kluczy
userSel.secretKeySel.title=Wybierz klucz prywatny OpenPGP, aby podpisać wiadomość
userSel.problemNoKey=Nie ważne kluczem
userSel.problemMultipleKeys=Wiele kluczy
# should be same as thunderbird ENTITY sendLaterCmd.label:
sendLaterCmd.label=Wyślij później
# Strings used in enigmailAttachmentDialog.js
# pgpMimeNote=NOTE: PGP/MIME is not supported by all email clients. If you are unsure, select the %S option.
first=pierwszÄ…
second=drugÄ…
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Wybierz klucz OpenPGP do szyfrowania
identityName=Tożsamość: %S
# switchPepMode=You are currently using the 'p≡p Junior' mode of Enigmail.\n\nBy enabling OpenPGP or S/MIME for an account, you are disabling p≡p and use the 'regular' mode of Enigmail without p≡p.
# enableEnigmail=&Disable p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=Uaktywniono szyfrowanie, ale nie wybrano żadnego klucza. Aby szyfrować wiadomości wysyłane do %S, należy wybrać co najmniej jeden ważny klucz z listy dostępnych. Czy chcesz wyłączyć szyfrowanie wiadomości do %S?
noKeyToUse=(brak – bez szyfrowania)
noEmptyRule=Reguła nie może być pusta! Wprowadź adres e-mail w polu edycji reguły.
invalidAddress=Wprowadzone adresy e-mail są niepoprawne. Nie należy wpisywać nazwy adresata, tylko sam adres. Np.\nNieprawidłowo: Jan Kowalski \nPrawidłowo: jakis.adres@poczta.pl
# noCurlyBrackets=The curly brackets {} have a special meaning and should not be used in an email address. If you want to modify the matching behavior for this rule, use the 'Apply rule if recipient ...' option.\nMore information is available from the Help button.
# Strings used in enigmailRulesEditor.js
never=Nigdy
always=Zawsze
possible=Możliwe
deleteRule=Czy usunąć wybraną regułę?
nextRcpt=(Następny adresat)
negateRule=Nie
addKeyToRule=Dodaj klucz %S (%S) do reguły dla adresata
# Strings used in enigmailSearchKey.js
needOnline=Wybrana funkcja nie jest dostępna w trybie offline. Włącz tryb online i spróbuj ponownie.
protocolNotSupported=Przy użyciu wybranego protokołu „%S://†pobranie kluczy OpenPGP nie jest możliwe.
gpgkeysDisabled=Pomóc może włączenie opcji „extensions.enigmail.useGpgKeysToolâ€.
noKeyserverConn=Nie można połączyć się z serwerem kluczy %S.
keyDownloadFailed=Nie powiodło się pobieranie kluczy z serwera. Status wiadomości:\n%S
internalError=Wystąpił wewnętrzny błąd. Nie można pobrać/zaimportować kluczy.
noKeyFound=Niestety nie udało się znaleźć kluczy pasujących do podanych kryteriów wyszukiwania.\nIdentyfikatory kluczy (ID) powinny być poprzedzone znakami „0x†(np. 0xABCDEF12).
# keyDownload.keyUnavailable=We are sorry, but the key with ID %S is not available on the keyserver. Most likely, the owner of the key did not upload their key to the keyserver.\n\nPlease ask the sender of the message to send you their key by email.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Nie powiodło się wyszukiwanie lub pobieranie kluczy z serwera – nie można uruchomić programu gpgkeys_%S.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Nie powiodło się ustawienie poziomu zaufania dla właściciela
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Nie udało się podpisać klucza
alreadySigned.label=Informacja. Klucz %S jest już podpisany za pomocą wybranego klucza prywatnego.
# alreadySignedexportable.label=Note: the key %S is already signed exportable with the selected secret key. A local signature does not make sense.
partlySigned.label=Informacja: niektóre numery ID klucza %S zostały już podpisane przez wybrany klucz prywatny.
# noTrustedOwnKeys=No eligible key found for signing! You need at least one fully trusted secret key in order to sign keys.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=Wczytywanie kluczy… Proszę czekać.
keyValid.unknown=nieznany
keyValid.invalid=niepoprawny
keyValid.disabled=wyłączony
keyValid.revoked=unieważniony
keyValid.expired=przeterminowany
keyValid.noSubkey=brak podklucza
keyTrust.untrusted=brak
keyTrust.marginal=ograniczone
keyTrust.full=pełne
keyTrust.ultimate=absolutne
keyTrust.group=(grupa)
keyType.public=pub
keyType.publicAndSec=pub/pryw
keyMan.enableKey=Włącz klucz
keyMan.disableKey=Wyłącz klucz
userAtt.photo=Atrybuty użytkownika (obraz JPEG)
asciiArmorFile=Opakowanie ASCII (*.asc)
importKeyFile=Import plik klucza OpenPGP
gnupgFile=Pliki GnuPG
# createKeyOK=Your Key has been generated
saveRevokeCertAs=Utwórz i zapisz certyfikat unieważnienia
# revokeCertOK=The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
revokeCertFailed=Nie udało się utworzyć certyfikatu unieważnienia.
addUidOK=Nowe ID zostało dodane
addUidFailed=Nie udało się dodać nowego ID
noKeySelected=Aby wykonać wybraną operację, należy zaznaczyć co najmniej jeden klucz
exportToFile=Eksport klucza publicznego do pliku
exportKeypairToFile=Eksport tajne i klucza publicznego do pliku
exportSecretKey=Czy chcesz dołączyć klucz prywatny do zapisywanego pliku z kluczami OpenPGP?
saveKeysOK=Klucze zostały zapisane
saveKeysFailed=Nie udało się zapisać kluczy
importKeysFailed=Nie udało się zaimportować kluczy
enableKeyFailed=Nie udało się włączenie/wyłączenie kluczy
specificPubKeyFilename=%S (0x%S) pub
specificPubSecKeyFilename=%S (0x%S) pub-pryw
defaultPubKeyFilename=Eksportowane-klucze-publiczne
defaultPubSecKeyFilename=Eksportowane-klucze-publiczne-i-prywatne
noSecretKeys=Nie znaleziono klucza prywatnego.\n\nCzy chcesz wygenerować własny klucz?
sendKeysOk=Klucze zostały wysyłane
sendKeysFailed=Nie udało się wysłać kluczy
receiveKeysOk=Klucze zostały zaktualizowane
receiveKeysFailed=Nie udało się pobrać kluczy
importFromClip=Czy chcesz zaimportować klucze ze schowka?
# importFromUrl=Download public key from this URL:
copyToClipbrdFailed=Nie udało się skopiować wybranych kluczy do schowka.
copyToClipbrdOK=Skopiowano klucze do schowka
deleteSecretKey=Uwaga! Zamierzasz usunąć klucz prywatny!\nJeśli usuniesz ten klucz, nie będziesz mieć możliwości odszyfrowania wiadomości zaszyfrowanych tym kluczem ani unieważnienia tego klucza.\n\nCzy na pewno chcesz usunąć obydwa klucze, prywatny i publiczny\n„%S�
deleteMix=Uwaga! Zamierzasz usunąć klucze prywatne!\nJeśli usuniesz ten klucz, nie będziesz mieć możliwości odszyfrowania wiadomości zaszyfrowanych tym kluczem.\n\nCzy na pewno chcesz usunąć wszystkie zaznaczone klucze prywatne i publiczne?
deletePubKey=Czy chcesz usunąć klucz publiczny\n„%S�
deleteSelectedPubKey=Czy chcesz usunąć wybrane klucze publiczne?
deleteKeyFailed=Nie udało się usunąć tego klucza.
# revokeKeyQuestion=You are about to revoke the key '%S'.\n\nYou will no longer be able to sign with this key, and once distributed, others will no longer be able to encrypt with that key. You can still use the key to decrypt old messages.\n\nDo you want to proceed?
revokeKeyOk=Klucz został unieważniony. Jeżeli klucz jest dostępny na serwerze kluczy, zalecane jest ponowne wysłanie go na serwer, tak aby inni użytkownicy otrzymali informację o unieważnieniu.
revokeKeyFailed=Nie udało się unieważnić tego klucza.
# revokeKeyNotPresent=You have no key (0x%S) which fits to this revocation certificate!\n\nIf you have lost your key, you must import it (e.g. from a keyserver) before the revocation certificate!
# revokeKeyAlreadyRevoked=The key 0x%S has already been revoked.
refreshAllQuestion=Nie wybrano żadnego klucza. Czy chcesz odświeżyć wszystkie klucze?
# refreshKeyServiceOn.warn=Warning: Your keys are currently being refreshed in the background as safely as possible.\nRefreshing all your keys at once will unnecessarily reveal information about you.\nDo you really want to do this?
refreshKey.warn=Uwaga! W zależności od liczby kluczy i parametrów połączenia, odświeżenie wszystkich kluczy może być długą operacją!
downloadContactsKeys.warn=Uwaga! W zależności od liczby kontaktów i parametrów połączenia, pobieranie wszystkich kluczy może byc długa operacją!
downloadContactsKeys.importFrom=Importuj kontakty z książki adresowej "%S"
keyMan.button.exportSecKey=&Eksportuj klucze prywatne
keyMan.button.exportPubKey=Eksportuj tylko klucze &publiczne
keyMan.button.import=&Importuj
keyMan.button.refreshAll=&Odśwież wszystkie klucze
keyMan.button.revokeKey=&Unieważnij klucz
keyMan.button.skip=Pomiń klucz
keylist.noOtherUids=Nie ma innych tożsamości
keylist.hasOtherUids=Także znany jako
keylist.noPhotos=Brak zdjęcia
keylist.hasPhotos=Zdjęcia
keyMan.addphoto.filepicker.title=Wybierz zdjęcie do dodania
keyMan.addphoto.warnLargeFile=Wybrany plik jest większy niż 25 kB.\nNie zaleca się dodawania bardzo dużych plików, ponieważ klucz będzie wówczas bardzo duży.
keyMan.addphoto.noJpegFile=Wybrany plik nie jest w formacie JPEG. Wybierz inny plik.
keyMan.addphoto.failed=Nie można dodać zdjęcia.
# noWksIdentity=The key %S does not have a WKS identity.
# keyman.addBlacklistKey.msg=Do you really want p≡p to stop using the key "%1$S (%2$S)" for encrypting messages?
# keyman.removeBlacklistKey.msg=Do you want to allow p≡p to use key "%1$S (%2$S)" for future messages?
# keyman.addBlacklistKey.button=&Blacklist the key
# keyman.removeBlacklistKey.button=&Remove key from Blacklist
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Nie udało się zmienić głównego identyfikatora użytkownika
changePrimUidOK=Zmieniono główny identyfikator użytkownika
revokeUidFailed=Nie udało się unieważnić ID %S
revokeUidOK=ID %S został unieważniony. Jeżeli klucz jest dostępny na serwerze kluczy, zalecane jest ponowne wysłanie go na serwer, tak aby inni użytkownicy otrzymali informację o unieważnieniu.
revokeUidQuestion=Czy na pewno chcesz unieważnić ID %S?
# Strings in enigmailKeyImportInfo.xul
# importInfoTitle=SUCCESS! Keys imported
# importInfoBits=Bits
# importInfoCreated=Created
# importInfoFpr=Fingerprint
# importInfoDetails=(Details)
# importInfoNoKeys=No keys imported.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=klucz publiczny
keyTypePrimary=klucz główny
keyTypeSubkey=podklucz
keyTypePair=para kluczy
keyExpiryNever=nigdy
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
keyAlgorithm_18=ECDH
keyAlgorithm_19=ECDSA
keyAlgorithm_20=ELG
# keyAlgorithm_22=EDDSA
keyUsageEncrypt=Szyfruj
keyUsageSign=Podpisz
keyUsageCertify=Certyfikuj
keyUsageAuthentication=Uwierzytelnianie
# keyDoesNotExpire=Key does not expire
# Strings in enigmailGenCardKey.xul
keygen.started=Proszę czekać. Trwa proces generowania klucza…
keygen.completed=Klucz został wygenerowany. Nowe ID klucza to: 0x%S.
keygen.keyBackup=Klucz został zapisany jako %S
keygen.passRequired=Określ szyfr, jeśli chcesz utworzyć kopię zapasową swojego klucza poza kartą SmartCard.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=Nie udało się zmienić numeru PIN
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Trwa odświeżanie kluczy… Proszę czekać.
keyserverProgress.uploading=Trwa wysyłanie kluczy… Proszę czekać.
# keyserverProgress.wksUploadFailed=Could not upload your key to the Web Key Service
# keyserverProgress.wksUploadCompleted=Your public key was successfully submitted to your provider. You will receive an email to confirm that you initiated the upload.
keyserverTitle.refreshing=Odświeżanie kluczy
keyserverTitle.uploading=Wysyłanie kluczy
# Strings in enigmailSetupWizard
passphrase.min8keys=Szyfr powinien zawierać co najmniej 8 znaków!
setupWizard.reallyCancel=Czy na pewno chcesz zamknąć Asystenta ustawień Enigmail?
setupWizard.invalidGpg=Wybrany plik GnuPG nie jest plikiem wykonywalnym. Wybierz inny plik.
setupWizard.specifyFile=Aby kontynuować, musisz określić przynajmniej plik klucza publicznego.
setupWizard.installFailed=Wygląda na to, że instalacja się nie powiodła. Spróbuj ponownie uruchomić instalację lub zainstaluj GnuPG ręcznie i zlokalizować go, używając przycisku Przeglądaj…
# setupWizard.downloadForbidden=For your own security, we will not download GnuPG. Please visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.downloadImpossible=We cannot download GnuPG currently. Please try later or visit https://gnupg.org/ in order to download GnuPG.
setupWizard.hashSumError=Asystent nie może zweryfikować spójności pobranego pliku. Plik może być uszkodzony lub został zmieniony. Czy mimo wszystko chcesz kontynuować instalację?
# setupWizard.importSettingsFile=Specify backup file to load from
# setupWizard.invalidSettingsFile=The specified file is not a correct Enigmail Settings backup file.
# setupWizard.gpgConfExists=The GnuPG config file already exists. Do you want to overwrite it with the one from your old installation?
# setupWizard.noGpgHomeDir=It appears that you configured %S to use for GnuPG. However, this is not a directory - you cannot use it.
# setupWizard.unmachtedIds=The following identities of your old setup could not be matched:\n%S\nThe settings for these identities were skipped.
# Strings in installGnuPG.jsm
installGnuPG.downloadFailed=Podczas pobierania GnuPG wystąpił błąd. Otwórz dziennik błędów, by zobaczyć szczegółowe informacje.
installGnuPG.installFailed=Podczas instalowania GnuPG wystąpił błąd. Otwórz dziennik błędów, by zobaczyć szczegółowe informacje.
# Strings in enigmailAddUidDlg.xul
addUidDlg.nameOrEmailError=Należy uzupełnić nazwę i adres e-mail
addUidDlg.nameMinLengthError=Nazwa musi zawierać co najmniej 5 znaków
addUidDlg.invalidEmailError=Należy podać poprawny adres e-mail
# Strings in enigmailCardDetails.js
Carddetails.NoASCII=Karta SmartCard obsługuje jedynie znaki ASCII w polach "Imię i nazwisko"/"Nazwa".
# network error types
errorType.SecurityCertificate=Usługa przedstawia nieważny certyfikat zabezpieczeń.
errorType.SecurityProtocol=Usługa używa nieznanego protokołu zabezpieczeń.
errorType.Network=Wystąpił błąd sieci.
# filter stuff
filter.folderRequired=Musisz wybrać folder docelowy.
filter.decryptMove.label=Odszyfrować stałe (Enigmail)
filter.decryptCopy.label=Tworzenie kopii szyfrowanego (Enigmail)
# filter.decryptMove.warnExperimental=Warning - the filter action "Decrypt permanently" may lead to destroyed messages.\n\nWe strongly recommend that you first try the "Create decrypted Copy" filter, test the result carefully, and only start using this filter once you are satisified with the result.
# filter.tempPepFilterDesc=Temporary filter to store sent message unencrypted
# filter.term.pgpencrypted.label=OpenPGP Encrypted
# filter.encrypt.label=Encrypt to key (Enigmail)
# filter.keyRequired=You must select a recipient key.
# filter.keyNotFound=Could not find an encryption key for "%S".
# filter.warn.keyNotSecret=Warning - the filter action "Encrypt to key" replaces the recipients.\n\nIf you do not have the secret key for "%S" you will no longer be able to read the emails.
# strings in enigmailConvert.jsm
# converter.decryptBody.failed=Could not decrypt message with subject\n"%S".\nDo you want to retry with a different passphrase or do you want to skip the message?
# converter.decryptAtt.failed=Could not decrypt attachment "%1$S"\nof message with subject\n"%2$S".\nDo you want to retry with a different passphrase or do you want to skip the message?
saveLogFile.title=Zapisz plik dziennika
# strings in gpg.jsm
# unknownSigningAlg=Unknown signing algorithm (ID: %S)
# unknownHashAlg=Unknown cryptographic hash (ID: %S)
# strings in keyRing.jsm
# keyring.photo=Photo
# keyRing.pubKeyRevoked=The key %1$S (key ID %2$S) is revoked.
# keyRing.pubKeyExpired=The key %1$S (key ID %2$S) has expired.
# keyRing.pubKeyNotForSigning=The key %1$S (key ID %2$S) cannot be used for signing.
# keyRing.pubKeyNotForEncryption=The key %1$S (key ID %2$S) cannot be used for encryption.
# keyRing.keyDisabled=The key %1$S (key ID %2$S) is disabled; it cannot be used.
# keyRing.keyNotTrusted=The key %1$S (key ID %2$S) is not trusted enough. Please set the trust level of your key to "ultimate" to use it for signing.
# keyRing.keyInvalid=The key %1$S (key ID %2$S) is not valid. Please consider verifying it correctly. Alternatively use the Default encryption settings in the Enigmail preferences dialog.
# keyRing.signSubKeysRevoked=All signing-subkeys of key %1$S (key ID %2$S) are revoked.
# keyRing.signSubKeysExpired=All signing-subkeys of key %1$S (key ID %2$S) have expired.
# keyRing.signSubKeysUnusable=All signing-subkeys of key %1$S (key ID %2$S) are revoked, expired or otherwise unusable.
# keyRing.encSubKeysRevoked=All encryption subkeys of key %1$S (key ID %2$S) are revoked.
# keyRing.encSubKeysExpired=All encryption subkeys of key %1$S (key ID %2$S) have expired.
# keyRing.noSecretKey=You do not seem to have the secret key for %1$S (key ID %2$S) on your keyring; you cannot use the key for signing.
# keyRing.encSubKeysUnusable=All encryption subkeys of key %1$S (key ID %2$S) are revoked, expired or otherwise unusable.
#strings in exportSettingsWizard.js
# cannotWriteToFile=Cannot save to file '%S'. Please select a different file.
# dataExportError=An error occurred during exporting your data.
# enigmailSettings=EnigmailSettings
# defaultBackupFileName=Enigmail-export
# specifyExportFile=Specify file name for exporting
# homedirParamNotSUpported=Additional params that configure paths such as --homedir and --keyring are not supported for exporting/restoring your settings. Please use alternative methods such as setting the environment variable GNUPGHOME.
#strings in expiry.jsm
# expiry.keyExpiresSoon=Your key %1$S will expire in less than %2$S days.\n\nWe recommend that you create a new key pair and configure the corresponding accounts to use the new key.
# expiry.keysExpireSoon=The following of your keys will expire in less than %1$S days:\n%2$S We recommend that you create new keys and configure your accounts to use the new keys.
# expiry.keyMissingOwnerTrust=Your secret key %S has missing trust.\n\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.keysMissingOwnerTrust=The following of your secret keys have missing trust.\n%S.\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.OpenKeyManager=Open Enigmail Key Management
# expiry.OpenKeyProperties=Open Key Properties
#strings in pEpDecrypt.jsm
# pEpDecrypt.cannotDecrypt=This is an encrypted message. Unfortunately you don't have the secret key to decrypt the message.
#strings in gpgAgent.jsm
# gpghomedir.notexists=The directory '%S' containing your OpenPGP keys does not exist and cannot be created.
# gpghomedir.notwritable=The directory '%S' containing your OpenPGP keys is not writable.
# gpghomedir.notdirectory=The directory '%S' containing your OpenPGP keys is a file instead of a directory.
# gpghomedir.notusable=Please fix the directory permissions or change the location of your GnuPG "home" directory. GnuPG cannot work correctly otherwise.
#strings in pepTrustWords.js
# pepTrustWords.cannotVerifyOwnId=Cannot verify p≡p Trustwords for own account.
# pepTrustWords.cannotFindKey=Cannot find key for %S.
# pepTrustWords.cannotStoreChange=Could not change trust for %S.
# pepTrustWords.generalFailure=Cannot obtain trustwords for %S.
# pepTrustWords.partnerFingerprint=Fingerprint for %S:
#strings in mimeWkdHandler.jsm
# wkdMessage.body.req=Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.\n\nPlease click the confirmation button in the Enigmail header to complete the publishing of your public key.
# wkdMessage.body.process=This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.\n\nYou do not need to take any manual action at this point.
#strings in pepHandshake.js
# pepPrivacyStatus.RatingBrokenSuggestion=Either you or the sender should resend the message.
# pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=If you composed this message, your key is not available.
# pepPrivacyStatus.RatingMistrustSuggestion=Re-establish the connection with your communication partner and try to complete another handshake.
# pepPrivacyStatus.RatingReliableSuggestion=Complete a handshake with your communication partner by exchanging trustwords in person or over the phone. A handshake is needed only once per partner and will ensure secure and trusted communication.
# pepPrivacyStatus.RatingTrustedSuggestion=No action needed!
# pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Be aware this message may not be secure.
# pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=Please add the necessary information.
# pepPrivacyStatus.RatingUnderAttackSuggestion=Separately verify the content of this message with your communication partner.
# pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Make sure the privacy status for each communication partner listed is at least secure.
# pepPrivacyStatus.RatingUnencryptedSuggestion=Please ask your communication partner to use an encryption solution or install p≡p.
# pepPrivacyStatus.RatingUnreliableSuggestion=This message has no reliable encryption or no signature. Ask your communication partner to upgrade their encryption solution or install p≡p.
# pepPrivacyStatus.RatingBrokenExplanation=This message has broken encryption or formatting.
# pepPrivacyStatus.RatingHaveNoKeyExplanation=This message cannot be decrypted because the key is not available.
# pepPrivacyStatus.RatingMistrustExplanation=This message has a communication partner that has previously been marked as mistrusted.
# pepPrivacyStatus.RatingReliableExplanation=This message is secure but you still need to verify the identity of your communication partner.
# pepPrivacyStatus.RatingTrustedExplanation=This message is secure and trusted.
# pepPrivacyStatus.RatingUndefinedExplanation=This message does not contain enough information to determine if it is secure.
# pepPrivacyStatus.RatingUnderAttackExplanation=This message is not secure and has been tampered with.
# pepPrivacyStatus.RatingUnencryptedExplanation=This message is unsecure.
# pepPrivacyStatus.RatingUnencryptedForSomeExplanation=This message is unsecure for some communication partners.
# pepPrivacyStatus.RatingUnreliableExplanation=This message has unreliable protection.
# pepPrivacyStatus.RatingBrokenText=Broken
# pepPrivacyStatus.RatingHaveNoKeyText=Cannot Decrypt
# pepPrivacyStatus.RatingMistrustText=Mistrusted
# pepPrivacyStatus.RatingReliableText=Secure
# pepPrivacyStatus.RatingTrustedText=Secure & Trusted
# pepPrivacyStatus.RatingUndefinedText=Unknown
# pepPrivacyStatus.RatingUnderAttackText=Under Attack
# pepPrivacyStatus.RatingUnencryptedForSomeText=Unsecure for Some
# pepPrivacyStatus.RatingUnencryptedText=Unsecure
# pepPrivacyStatus.RatingUnreliableText=Unreliable Security
# handshakeDlg.button.initHandshake=Handshake...
# handshakeDlg.button.stopTrust=Stop Trusting
# handshakeDlg.button.reTrust=Stop Mistrusting
# handshakeDlg.label.outgoingMessage=Outgoing message
# handshakeDlg.label.incomingMessage=Incoming message
# handshakeDlg.error.noPeers=Cannot handshake without any correspondents.
# handshakeDlg.error.noProtection=Please enable protection in order to use the Handshake function.
# enigmail.acSetupPasswd.descEnterPasswd=Please enter the setup code that is displayed on the other device
# enigmail.acSetupPasswd.descCopyPasswd=Please enter the setup code below on your other device to proceed with the setup
#strings in autocrypt.jsm
# autocrypt.setupMsg.subject=Autocrypt Setup Message
# autocrypt.setupMsg.msgBody=To set up your new device for Autocrypt, please follow the instuctions that should be presented by your new device.
# autocrypt.setupMsg.fileTxt=This is the Autocrypt setup file used to transfer settings and keys between clients. You can decrypt it using the setup code presented on your old device, and then import the contained key into your keyring.
#strings in upgradeInfo.html
# upgradeInfo.doctitle=What's New in Enigmail v2.0?
# upgradeInfo.welcome1=Welcome to the new Enigmail version 2.0!
# upgradeInfo.welcome2=The release contains a lot of new and changed features. Please take a minute to find out what's new:
# upgradeInfo.encSubject.title=Encrypting the Message Subject
# upgradeInfo.encSubject.desc=We developed a new method that moves the email subject into the encrypted message, and replaces the visible subject with "Encrypted Message". Once such a message is decrypted, the original subject is replaced automatically. Hiding the subject is on by default; there is a preference to turn it off if you don't like it. (Note: this feature requires the message to be sent with PGP/MIME.)
# upgradeInfo.buttons.title=Changed behavior of Encrypt and Sign Buttons
# upgradeInfo.buttons.desc=The Encrypt and Sign buttons in the message composer window now work for both the OpenPGP and S/MIME protocols. If both algorithms are possible, then Enigmail will try to prefer the one for which all keys are available.
# upgradeInfo.autocrypt.title=Support for Autocrypt
# upgradeInfo.autocrypt.desc=Enigmail now supports Autocrypt, a new standard to distribute keys as part of sent messages. Enigmail automatically imports keys from Autocrypt-compliant messages, such that over time more and more emails can be encrypted.
# upgradeInfo.pEp.title=New p≡p Junior Mode (Pretty Easy Privacy)
# upgradeInfo.pEp.desc=Enigmail now contains a p≡p Junior Mode. You currently need to manually install p≡p for this purpose; this will change in a future release. The p≡p Junior Mode allows you to use OpenPGP encryption as transparently as possible; you don't need to care for key management and synchronization of keys between devices anymore.
# upgradeInfo.bottom.desc=Please visit our documentation for help on using Enigmail.
# pep.missingGnuPG=In order to use Enigmail/p≡p, GnuPG is required. As we could not find it, we suggest to download and install it for you.
#strings in enigmailAbout.html
# aboutEnigmail.tabName=About Enigmail
# aboutEnigmail.title=OpenPGP support provided by Enigmail
# aboutEnigmail.team=Enigmail is developed by the Enigmail Team:
# aboutEnigmail.projectLeader=Lead Developer:
# aboutEnigmail.usability=Usability:
# aboutEnigmail.documentation=Documentation:
# aboutEnigmail.testing=Testing:
# aboutEnigmail.userSupport=User Support:
# aboutEnigmail.localization=Localization: See the Enigmail Language Packs page
# aboutEnigmail.Credits=Credits:
# aboutEnigmail.origAuthor=Original author of the Enigmail extension
# aboutEnigmail.icons=Icons:
# aboutEnigmail.formerMembers=Former team members:
# aboutEnigmail.projectHosting=Project hosting:
# aboutEnigmail.licenseSupportTitle=License & Support
# aboutEnigmail.license=Enigmail OpenPGP is open source and licensed under the %S
# aboutEnigmail.support=Support and download is available from www.enigmail.net.
enigmail-2.0.8/lang/pl/help/ 0000775 0000000 0000000 00000000000 13343027545 0015600 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/pl/help/compose.html 0000664 0000000 0000000 00000011012 13343027545 0020126 0 ustar 00root root 0000000 0000000
Pomoc dla Enigmail: Tworzenie wiadomości
Pomoc dla Enigmail
Używanie Enigmail w oknie tworzenia wiadomości
Menu Enigmail w oknie tworzenia wiadomości
Podpisz wiadomość
Włącza/wyłącza podpisywanie wiadomości. Użytkownik jest powiadamiany, jeśli podpisywanie się nie powiodło.
Szyfruj wiadomość
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.
Użyj PGP/MIME dla tej wiadomości
Włącza/wyłącza użycie PGP/MIME dla danej wiadomości.
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/MIMEZezwalaj na używanie PGP/MIME lub Zawsze używaj PGP/MIME.
Domyślne opcje tworzenia wiadomości
Opcje podpisu/szyfrowania… – skrót do Konfiguracja kont » OpenPGP.
Wysyłanie wiadomości… – skrót do karty Ustawienia » Wysyłanie.
Opcje wyboru kluczy… – skrót do do karty Ustawienia » Wybór kluczy.
Opcje PGP/MIME… – skrót do do karty Ustawienia » PGP/MIME.
Cofnij szyfrowanie
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.
Wstaw klucz publiczny
Wstawia w oknie tworzenia wiadomości blok klucza publicznego w aktualnej pozycji kursora. Użytkownik będzie proszony o podanie adresu e-mail wstawianego klucza. Klucze wstawiane w ten sposób będą u odbiorcy automatycznie rozpoznawane przez Enigmail. Po wstawieniu klucza można nadal wybrać podpisanie/szyfrowanie wiadomości. Nie należy do wiadomości wstawiać więcej niż jeden blok klucza, wystarczy, gdy pojawi się monit, podać wiele adresów e-mail, oddzielając je przecinkami lub spacjami.
Wyczyść zapisane hasło
Czyści zbuforowane szyfry. Użyteczne, jeśli masz wiele szyfrów.
Pomoc
Wyświetla pomocne informacje z witryny internetowej (tę stronę).
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail-2.0.8/lang/pl/help/editRcptRule.html 0000664 0000000 0000000 00000012327 13343027545 0021101 0 ustar 00root root 0000000 0000000
Pomoc dla Enigmail: Edycja reguł OpenPGP
Pomoc dla Enigmail
Używanie edytora reguł Enigmail: Edycja reguł OpenPGP
W 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.
Pole „OkreÅ›l reguÅ‚y OpenPGP dlaâ€
Reguły zawierają adresy e-mail odbiorcy (bez nazwisk, po prostu adres, jak: somebody@nazwa_domeny). Możesz podać kilka adresów e-mail, rozdzielając je spacjami. Podany tutaj adres może składać się tylko z domeny, np. @nazwa_domeny. Reguła będzie wówczas pasowała do wszystkich adresów w tej domenie, np. @nazwa_domeny będzie pasować do body@nazwa_domenyl, somebody@nazwa_domeny, anybody@nazwa_domeny itd.
Zastosuj regułę, gdy adresat…
Ustawienie to modyfikuje dopasowanie adresów e-mail. Jeśli jest podane wiele adresów, ustawienie będzie miało zastosowanie do wszystkich. Przykłady są oparte na przykładowym adresie body@nazwa_domeny podanym w powyższym polu.
Jest taki sam, jak – reguła będzie miała zastosowanie tylko do wiadomości adresowanych do body@nazwa_domeny (wielkość znaków musi się zgadzać).
Zawiera – będzie pasował każdy adres wiadomości zawierający podany ciąg znaków, np. anybody@nazwa_domeny lub body@nazwa_domeny.net.
Rozpoczyna się od – będzie pasował każdy adres wiadomości rozpoczynający się podanym ciągiem znaków, np. body@nazwa_domeny.net, body@nazwa_domeny-nazwa.com.
Kończy się na – będzie pasował każdy adres wiadomości kończący się podanym ciągiem znaków, np. anybody@nazwa_domeny, somebody@nazwa_domeny.
Przejdź do następnej reguły pasującej do adresu
Włączenie tej funkcji umożliwi zdefiniowanie reguły, ale nie trzeba określać klucza w polu Użyj następujących kluczy OpenPGP:, więc adres e-mail jest wykorzystywany do sprawdzania klucza w momencie wysyłania. Dla tego adresu będą również przetwarzane inne reguły.
Nie sprawdzaj kolejnych reguł pasujących do adresu
Włączenie tej funkcji, jeśli reguła pasuje, zatrzyma przetwarzanie innych reguł dla pasujących adresów, na przykład kontynuowanie przetwarzania reguły dla następnego odbiorcy.
Użyj następujących kluczy OpenPGP:
Użyj przycisku Wybierz klucze, by wybrać klucze odbiorcy, które będą używane do szyfrowania. Oprócz czynności określonej powyżej żadne inne reguły nie są przetwarzane.
Wysyłając wiadomości włącz…
Włącza lub wyłącza podpisywanie wiadomości. Funkcja ta używa lub zastępuje to, co zostało określone w oknie tworzenia wiadomości. Ustawienia są następujące:
Nigdy – wyłącza podpisywanie, nawet jeśli zostało włączone w oknie tworzenia wiadomości (zastępuje wszystkie inne wartości reguł),
Tak, jeśli zaznaczono taką opcję tworzenia wiadomości – pozostawia sposób podpisywania określony w oknie tworzenia wiadomości,
Zawsze – włącza podpisywanie, nawet jeśli nie zostało włączone w oknie tworzenia wiadomości.
Te ustawienia podpisywania są stosowane do wszystkich reguł, do których pasują. Jeśli jedna z reguł wyłącza podpisywanie, wiadomość nie będzie podpisywana, pomimo że inne reguły mają ustawienie zawsze.
Szyfrowanie
Włącza lub wyłącza szyfrowanie wiadomości. Ustawienia i ich znaczenie są takie same jak dla podpisywania wiadomości.
PGP/MIME
Włącza lub wyłącza kodowanie wiadomoÅ›ci w formacie PGP/MIME (RFC 3156). JeÅ›li PGP/MIME jest wyłączone, wiadomoÅ›ci sÄ… kodowane za pomocÄ… „inline PGPâ€. Ustawienia i ich znaczenie sÄ… takie same jak dla podpisywania wiadomoÅ›ci.
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-2.0.8/lang/pl/help/initError.html 0000664 0000000 0000000 00000005011 13343027545 0020440 0 ustar 00root root 0000000 0000000
Pomoc dla Enigmail: Jak rozwiązać problemy z zainicjowaniem OpenPGP
Pomoc dla Enigmail
Jak rozwiązać problemy z zainicjowaniem OpenPGP
Zainicjowanie 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.
Nie można znaleźć GnuPG
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.
Nie udało się zainicjować Enigmime
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-2.0.8/lang/pl/help/messenger.html 0000664 0000000 0000000 00000011344 13343027545 0020461 0 ustar 00root root 0000000 0000000
Pomoc dla Enigmail: Czytanie wiadomości
Pomoc dla Enigmail
Używanie Enigmail podczas czytania wiadomości
Przycisk Deszyfruj w głównym oknie wiadomości
Przycisk ten może być używany do różnych celów: deszyfrowania, weryfikowania lub importowania kluczy publicznych. Normalnie deszyfrowanie/weryfikowanie odbywa się automatycznie i może być wyłączone w ustawieniach. Jeśli automatyczne deszyfrowanie/weryfikowanie się nie powiedzie, w pasku statusu Enigmail zostanie wyświetlona informacja o błędzie. Po naciśnięciu przycisku Deszyfruj zostaną wyświetlone szczegółowe informacje dotyczące tego błędu zawierające polecenia z GnuPG.
Ikony pióra i klucza wyświetlane w nagłówku wiadomości
Ikony pióra i klucza wyświetlane w nagłówku wiadomości informują, czy aktualnie czytana wiadomość została podpisana i/lub zaszyfrowana i czy podpis jest prawidłowy, np. że wiadomość nie została zmieniona od czasu jej podpisania. Jeśli wiadomość została zmieniona, kolor ikony pióra zostanie zmieniony na czerwony, informując, że podpis jest nieprawidłowy. Kliknięcie prawym przyciskiem myszy którejś z tych ikon, spowoduje wyświetlenie menu zawierającego następujące opcje:
Informacje OpenPGP… – umożliwia podgląd statusu elementów wyjściowych z GnuPG dla wiadomości.
Kopiuj informacje OpenPGP – kopiuje status elementów wyjściowych z GnuPG do schowka, by następnie można było wstawić je do odpowiedzi na wiadomość itp.
Pokaż zdjęcie – umożliwia podgląd zdjęcia osoby, która wysłała wiadomość, jeśli zdjęcie zostało dołączone do klucza publicznego. (Ta funkcja będzie włączona tylko, jeśli zdjęcie jest w kluczu danego nadawcy).
Informacje S/MIME… – umożliwia zobaczenie informacji bezpieczeństwa S/MIME dla wiadomości.
Jeś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.
Załączniki z rozszerzeniem *.pgp, *.asc i *.gpg są rozpoznawane jako załączniki, które mogą być obsługiwane przez Enigmail specjalnie. Kliknięcie takiego załącznika prawym przyciskiem myszy spowoduje wyświetlenie w menu kontekstowym dwóch specjalnych elementów: Deszyfruj i otwórz i Deszyfruj i zapisz jako… Użyj tych dwóch elementów, jeśli chcesz, by Enigmail deszyfrował załącznik przed otworzeniem lub jego zapisaniem. Jeśli załącznik jest rozpoznany jako plik klucza OpenPGP, zostanie zaoferowane zaimportowanie kluczy do twojej bazy kluczy.
Więcej pomocy można uzyskać na stronie pomocy Enigmail.
enigmail-2.0.8/lang/pl/help/rulesEditor.html 0000664 0000000 0000000 00000006741 13343027545 0020777 0 ustar 00root root 0000000 0000000
Pomoc dla Enigmail – Edytor reguł
Pomoc dla Enigmail
Użycie edytora reguł
W 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:
E-mail
Pola do dopasowywania wiadomości e-mail – Do:, Kopia: i Ukryta kopia:. Dopasowywanie działa w oparciu o substringi. Więcej szczegółów można znaleźć w oknie dialogowym edytora reguł.
Klucze OpenPGP
Wykaz ID kluczy OpenPGP używanych dla adresata
Podpis
Włącza lub wyłącza podpisywanie wiadomości. Ta funkcja używa lub nadpisuje, to co zostało określone w oknie tworzenia wiadomości. Dostępne ustawienia:
Nigdy – wyłącza podpisywanie wiadomości, nawet jeśli funkcja była włączona w oknie tworzenia wiadomości – unieważnia inne ustawienia.
Pozostaw – pozostawia podpis, taki jaki był ustawiony w oknie tworzenia wiadomości,
Zawsze – włącza podpisywanie wiadomości, nawet jeśli nie było włączone w oknie tworzenia wiadomości.
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.
Szyfrowanie
Włącza lub wyłącza szyfrowanie wiadomości. Dostępne ustawienia i znaczenie są takie same, jak dla podpisywania wiadomości.
PGP/MIME
Włącza lub wyłącza używanie kodowania PGP/MIME (RFC 3156) wiadomoÅ›ci. JeÅ›li PGP/MIME jest wyłączone, wiadomoÅ›ci sÄ… kodowane za pomocÄ… „inline PGPâ€. DostÄ™pne ustawienia i znaczenie sÄ… takie same, jak dla podpisywania wiadomoÅ›ci.
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-2.0.8/lang/pl/help/sendingPrefs.html 0000664 0000000 0000000 00000005076 13343027545 0021125 0 ustar 00root root 0000000 0000000
Pomoc dla Enigmail – Edytowanie reguł OpenPGP
Pomoc dla Enigmail
Defining Preferences to Send Encrypted
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Menu do Enigmail na janela de Composição de Mensagem
Assinar mensagem: Habilitar/Desabilitar o envio de mensagens assinadas. O usuário será notificado se a assinatura falhar.
Criptografar mensagem: Habilitar/Desabilitar criptografia para todos os destinatário(s) antes de enviar a mensagem. O usuário será notificado caso a criptografia falhe.
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.
Utilizar PGP/MIME para esta mensagem: Habilitar/Desabilitar o uso de
PGP/MIME
para esta mensagem.
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.
Opções padrão para composição: Submenu.
Opções de Assinatura/Criptografia...: atalho para Configurações de Conta -> Opções do OpenPGP.
Opções de Envio...: atalho para a aba Preferências -> Envio.
Opções de seleções de Chave...: atalho para a aba Preferências -> Seleção de Chaves.
Opções de PGP/MIME...: atalho para a aba Preferências -> PGP/MIME.
Desfazer criptografia: Casa haja uma falha ao enviar a mensagem,
tal como um servidor POP não aceitar o pedido, o Enigmail não saberá sobre o ocorrido,
e a mensagem criptografada continuará a ser mostrada na janela de Composição de Mensagem.
Escolhendo este item de menu fará com que a criptografia/assinatura seja desfeita,
revertendo a janela de Composição de Mensagem de volta ao seu texto original. Como uma solução temporária, esta opção também pode ser utilizada para descriptografar a
o texto de citação da mensagem anterior (quote) quando estiver respondendo mensagens criptografadas.
O Enigmail deve automaticamente descriptografar a citação, mas caso isto falhe por alguma razão, você pode
utilizar este item do menu para forçá-lo.
Inserir chave pública: inserir o bloco ASCII com a chave pública na posição
atual do cursor na janela de Composição. Você será perguntado sobre os endereços das chaves a serem inseridas.
Chaves inseridas desta maneira serão reconhecidas pelo Enigmail do destinatário. Após a inserção da chave, você
ainda pode escolher assinar/criptografar a mensagem como for necessário. Não insira mais de um bloco de chave por mensagem; apenas especifique
múltiplos endereços de email, separados por vírgulas ou espaços, quando for solicitado.
Remover senha: Remove a senha armazenada. Útil quando você possui múltiplas senhas.
enigmail-2.0.8/lang/pt-BR/help/editRcptRule.html 0000664 0000000 0000000 00000014556 13343027545 0021420 0 ustar 00root root 0000000 0000000
Ajuda do Enigmail: Edição de Regra do OpenPGP
Ajuda do Enigmail
Usando o Editor de Regras do Enigmail: Editando uma Regra OpenPGP
No 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.
Definir Regras OpenPGP para: Contém os endereços de email dos destinatários (sem nomes, por exemplo: apenas um endereço como
alguem@dominio). Você pode especificar diversos endereços, separados por espaços.
O endereço especificado aqui pode consistir apenas da parte com o domínio, de forma que qualquer mensagem que faça parte deste domínio será processada, por exemplo @email.domain permitirá processar mensagens como usuario@email.domain,
alguem@email.domain, qualquerumy@email.domain, etc.
Aplicar regra se o destinatário for ...:
Esta opção modifica a maneira como os endereços são processados.
Caso múltiplos endereços sejam colocados, esta configuração será aplicada a todos.
Os exemplos abaixo são baseados no endereço usuario@email.domain
mostrado no exemplo de Regras OpenPGP mostrado acima.
É exatamente: com esta configuração, esta regra será apenas utilizada em emails para usuario@email.domain (texto exato, sem levar em consideração maiúsculas ou minúsculas).
Contém: com esta configuração, qualquer endereço de email contendo a sub-palavra especificada é encontrada, por exemplo qualquerum@email.domain ou usuario@email.domain.net
Começa com: com esta configuração, qualquer endereço começando com esta palavra é processado, por exemplo usuario@email.domain.net, usuario@email.domain-name.com.
Termina com: com esta configuração, qualquer endereço terminando com esta palavra será processado, por exemplo qualquerum@email.domain,
alguem@email.domain.
Continua com a próxima regra para o endereço selecionado
Ligando esta funçã permitirá que se defina uma regra mas não seja necessário especificar um ID de Chave no campo Usar as seguintes chaves OpenPGP:, de formad que o endereço de email será utilizado para verificar por uma chave na hora do envio. Além disso, regras criadas para o mesmo endereço serão processadas també.
Não continuar verificando regras para o endereço selecionado
Ligando esta função, o processamento de quaisquer outras regras será abortado para o(s) endereço(s) selecionado(s) caso esta regra seja utilizada, ou seja, o processamento de regras continua com o próximo destinatário.
Utilizar as seguintes chaves OpenPGP:
Utilize o botão Selecionar Chave(s).. para selecionar as chaves de destinatário que serão utilizadas para criptografia.
Como na ação descrita anteriormente, nenhuma regra adicional para o(s) endereço(s) selecionado(s) serão processadas.
Padrão para Assinatura: habilitar ou desabilitar assinatura de mensagens.
Esta opção utiliza ou sobrepõe o que você especificou na janela de composição de mensagem.
Os valores são:
Nunca: desabilitar assinatura, mesmo quando tiver sido habilitada na janela de composição de mensagem. (sobrepõe os outros valores)
Sim, se selecionado na Composição da Mensagem: deixe a assinatura como especificada na janela de composição de mensagem
Sempre: habilitar assinatura, mesmo se não foi habilitada na janela de composição de mensagem
Estas configurações de assinatura são aplicadas para todas as regras que coincidirem.
Caso uma das regras desabilite assinatura, a mensagem não será assinada, mesmo que outras regras especifiquem Sempre assinar.
Criptografia: habilitar ou desabilitar criptografia de mensagem.
As configurações permitidas e seu significado é o mesmo que para assinatura de mensagens.
PGP/MIME: habilitar ou desabilitar o uso de codificação de mensagem PGP/MIME (RFC 3156).
Caso o PGP/MIME esteja desligado, as mensagens são codificadas utilizando o processo "PGP inline". Os valores permitidos e seus significados são os mesmos utilizados para assinatura de mensagens.
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.
enigmail-2.0.8/lang/pt-BR/help/initError.html 0000664 0000000 0000000 00000005452 13343027545 0020762 0 ustar 00root root 0000000 0000000
Ajuda do Enigmail: Como Resolver Problemas com a Inicialização do OpenPGP
Ajuda do Enigmail
Como Resolver Problemas Com a Inicialização do OpenPGP
Existem 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.
GnuPG não pode ser encontrado
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)
Falha ao inicializar o Enigmime
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.
enigmail-2.0.8/lang/pt-BR/help/messenger.html 0000664 0000000 0000000 00000011656 13343027545 0021000 0 ustar 00root root 0000000 0000000
Ajuda do Enigmail: Leitura de Mensagens
Ajuda do Enigmail
Utilizando o Enigmail durante a leitura de mensagens
Botão Descriptografar na janela principal de mensagens
Este botão pode ser utilizado para diversas funções: descriptografar, verificar ou importar chaves públicas. Normalmente a criptografia/verificação ocorre automaticamente, embora isto possa ser desabilitado através de uma opção. No entanto, se isto falhar, geralmente uma pequena mensagem de erro irá aparecer na barra de status do Enigmail. Se você clicar no no botão Descriptografar, você poderá ver uma mensagem de erro mais detalhada, incluindo a saída do comando GnuPG.
Ícones de Caneta e Chave no Cabeçalho da Mensagem
Os ícones de Caneta e Chave no cabeçalho da mensagem indicam s a mensagem que você está lendo foi assinada e/ou criptografada e se a assinatura é válida, ou seja, se a mensagem não foi alterada desde que foi assinada. Caso a mensagem tenha sido alterada, o ícone da Caneta irá mudar para um ícone de Caneta Quebrada para indicar que a assinatura não é válida. Clicando com o botão direito em qualquer um dos ícones de Caneta ou Chave trará um menu com as seguintes opçóes:
Informações de Segurança do OpenPGP: permite que você veja a saída do GnuPG para esta mensagem.
Copiar Informações de Segurança do OpenPGP: copia a saída do GnuPG para a área de transferência; para colar em uma mensagem, por exemplo.
Ver ID com Foto do OpenPGP: permite que você visualize o ID com Foto da pessoa que enviou a mensagem, caso possua uma foto contida em sua Chave Pública.
(Esta opção apenas será habilitada caso um ID com Foto exista na chave da pessoa.)
Informações de Segurança S/MIME: permite que você visualize as Informações de Segurança S/MIME para a mensagem.
Se 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.
Abrindo anexos criptografados / importando chaves OpenPGP anexadas
Anexos terminando em *.pgp, *.asc e *.gpg são reconhecidos como anexos que podem ser tratados de forma especial pelo Enigmail. Clicando com o botão direito em um destes anexos habilita dois itens especiais no menu de contexto: Descriptografar e Abrir e Descriptografar e Salvar. Utilize estes dois itens se você quer que o Enigmail descriptografe um anexo antes de abrí-lo ou salvá-lo. Caso um anexo seja reconhecido com um arquivo de chave OpenPGP, será oferecida a oportunidade de importar as chaves em seu chaveiro.
enigmail-2.0.8/lang/pt-BR/help/rulesEditor.html 0000664 0000000 0000000 00000007070 13343027545 0021304 0 ustar 00root root 0000000 0000000
Ajuda do Enigmail: Editor de Regras
Ajuda do Enigmail
Utilizando o Editor de Regras do Enigmail
No 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:
Email: o endereço de email que serão pesquisados nos campos De:, Cc: e Bcc:. A pesquisa funciona em sub-palavras (Maiores detalhes podem ser encontrados no diálogo do Editor de Regras)
Chave(s) OpenPGP: uma lista de Id's de Chaves OpenPGP
Key ID's para utilizar para este destinatário
Assinar: habilitar ou desabilitar a assinatura da mensagem. Esta opção utiliza ou sobrepõe o que você especificou na janela de composição de mensagem. Os valores são:
Nunca: desabilita a assinatura, mesmo se estiver habilitada na janela de composição de mensagem (sobrepõe os outros valores)
Possível: deixa a opção de assinatura como especificada na janela de composição de mensagem
Sempre: habilita assinatura, mesmo se não estiver habilitada na janela de composição de mensagem
Estas opções de assinatura se aplicam para todas as regras que forem selecionadas. Caso uma destas regras desabilite a assinatura, a mensagem não será assinada, não importando o que outras regras especificarem Sempre.
Criptografar: habilita ou desabilita criptografia de mensagem. As opções permitidas e seus significados são os mesmos definidos para assinatura de mensagem.
PGP/MIME: habilita ou desabilita o uso de codificação PGP/MIME (RFC 3156).
Caso a opção PGP/MIME esteja desabilitada, as mensagens são codificadas utilizando o "PGP inline". Os valores permitidos e seus significados são os mesmos da assinatura de mensagem.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Assinar mensagem: Activar/Desactivar o envio de correio assinado. O utilizador
será notificado se a assinatura falhar.
Cifrar mensagem: Activar/Desactivar a encriptação para todo(s) o(s) destinatário(s)
antes do envio. O utilizador será notificado se a encriptação falhar.
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.
Usar PGP/MIME para esta mensagem: Activar/Desactivar o uso de
PGP/MIME
para esta mensagem.
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.
Opções de composição por omissão: Submenu.
Opções de assinar/cifrar...: atalho para Opções de conta -> Opções OpenPGP.
Opções de envio...: atalho para o separador Preferências -> Ao Enviar.
Opções de Selecção de chaves...: atalho o separador Preferências ->
Selecção de chaves.
Opções PGP/MIME...: atalho para o separador Preferências -> PGP/MIME.
Desfazer encriptação: se acontecer um erro ao enviar o correio, por exemplo o servidor
POP não aceitar o pedido, o Enigmail não terá conhecimento disso e a mensagem cifrada continuará
a ser mostrada na janela de composição. Ao escolher este item de menu reverterá a operação de
encriptação, colocando o texto original novamente na janela. Como solução temporária, esta opção pode também ser usada para decifrar as citações
ao responder a mensagens cifradas. O Enigmail deve decifrar automaticamente as mensagens
cifradas, mas se isso falhar por alguma razão, pode usar este item de menu para o forçar.
Inserir chave pública: inserir bloco de chave pública em ASCII na posição corrente
do cursor na janela de Composição. Ser-lhe-á pedido o endereço de correio electrónico da(s)
chave(s) a inserir. As chaves inseridas desta forma serão automaticamente reconhecidas pelo
Enigmail na recepção. Após a inserção da chave, pode escolher assinar/cifrar a mensagem
consoante necessário. Não insira mais do que um bloco de chave por mensagem; em vez disso,
indique os vários endereços de email separados por vírgulas ou espaços quando tal lhe
for pedido.
Limpar senha memorizada: Limpa a senha guardada em memória. Útil se tem várias senhas
diferentes.
Editar regras por destinatário
Ajuda: Mostra a informação de ajuda do site web (esta página).
Usar o Editor de Regras do Enigmail: Editar Regras OpenPGP
No 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.
Configurar regras OpenPGP para: Contém os
endereços de email dos destinatários (sem nomes, isto é, apenas um endereço como
alguem@dominio.email). Pode indicar vários endereços de email, separados por espaços.
Os endereços indicados aqui podem conter apenas o domínio, de forma a que apenas os endereços
daquele domínio sejam mostrados, por exemplo, @dominio.email permitiria mostrar os
endereços pessoa@dominio.email, alguem@dominio.email,
qualquer@dominio.email, etc.
Aplicar regra se destinatário ...:
Altera a forma de correspondência de endereços de email. Se forem introduzidos vários endereços,
esta definição aplicar-se-á a todos. Os exemplos abaixo baseiam-se em introduzir
pessoa@dominio.email no campo Regras OpenPGP definido acima.
É exactamente: com esta configuração, a regra apenas se aplicará às mensagens para
pessoa@dominio.email (correspondência exacta, ignorando maiúsculas/minúsculas).
Contém: com esta configuração, a regra aplicar-se-á a todos os endereços que contenham
a cadeia de caracteres especificada, por exemplo qualquerpessoa@dominio.email ou
pessoa@dominio.email.net
Começa por: com esta configuração, a regra irá aplicar-se a qualquer endereço
iniciado pela cadeia de caracteres especificada, como pessoa@dominio.email.net ou
pessoa@dominio.email-nome.com.
Termina em: esta configuração aplica a regra a todos os endereços terminados com
a cadeia de caracteres especificada, tais como qualquerpessoa@dominio.email ou
umapessoa@dominio.email.
Continuar com a próxima regra para os endereços coindidentes
Activar esta função permitirá definir uma regra sem ter que especificar o Identificador da chave em
Usar as seguintes chaves OpenPGP:, de forma a que o endereço de email seja usado para
procurar a chave ao enviar. De igual modo, as regras seguintes para os mesmos endereços serão
processadas da mesma maneira.
Não verificar mais regras para os endereços coincidentes
Activar esta definição impede o processamento de quaisquer outras regras para os endereços
coincidentes, caso esta regra seja verificada; ou seja, o processamento de regras continua
com o próximo destinatário.
Definições por omissão para assinar: activar ou desactivar
a assinatura de mensagens. Esta definição usa ou sobrepõe-se ao que especificou na janela de composições
de mensagens. Os valores são:
Nunca: desactivar a assinatura, mesmo se estiver seleccionada na janela de composição de
mensagens (sobrepõe-se a outros valores)
Sim, se seleccionado na Composição de Mensagens: deixar a assinatura como especificado na
janela de composição de mensagens
Sempre: Activar a assinatura, mesmo se não estiver
seleccionada na janela de composição de mensagens
Estas configurações de assinatura são aplicadas a todas as regras
coincidentes. Se uma das regras desactivar a assinatura, a mensagem não será assinada, independentemente
do que outras regras especifiquem. Sempre.
Cifrar: Activar ou desactivar a encriptação de mensagens.
As configurações permitidas e o seu significado são os mesmos que para a assinatura de mensagens.
PGP/MIME: activar ou desactivar o uso de PGP/MIME (RFC 3156)
para a codificação de mensagens. Se não seleccionar PGP/MIME, as mensagens serão codificadas usando o
método "PGP embebido". Os valores permitidos e o seu significado são os mesmos que para a assinatura de
mensagens.
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.
enigmail-2.0.8/lang/pt-PT/help/initError.html 0000664 0000000 0000000 00000004657 13343027545 0021010 0 ustar 00root root 0000000 0000000
Ajuda Enigmail: Como Resolver Problemas na Inicialização do OpenPGP
Ajuda Enigmail
Como Resolver Problemas na Inicialização do OpenPGP
Há 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.
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.
Botão Decifrar na janela principal do Mail & Newsgroups / Thunderbird
Este botão pode ser usado para: decifrar, verificar ou importar chaves públicas.
Normalmente, as mensagens são decifradas e verificadas automaticamente, embora
este comportamento possa ser desactivado numa preferência. Contudo, se isto falhar,
será apresentada uma curta mensagem de erro na barra de estado do Enigmail. Se clicar
sobre o botão Decifrar, poderá ver uma mensagem mais detalhada, incluindo a saída
do comando GnuPG.
Ícones da Caneta e da Chave no Cabeçalho da Mensagem
Os ícones da Caneta e da Chave no Cabeçalho da Mensagem indicam se
a mensagem que está a ler foi assinada e/ou cifrada e se a assinatura é válida, ou
seja, se a mensagem não foi alterada desde que foi assinada. Se a mensagem foi
alterada o ícone da Caneta mudará para uma Caneta Quebrada para
indicar que a assinatura não é válida. Clicar com o botão alternativo do rato quer no
ícone da Caneta quer no ícone da Chave fará aparecer um menu com as seguintes
opções:
Informação de Segurança OpenPGP: permite ver a saída do GnuPG para a
mensagem.
Copiar Informação de Segurança OpenPGP: copia a saída do GnuPG para a
área de transferência; para colar numa mensagem de resposta, etc.
Ver Identificador Fotográfico OpenPGP: permite ver o Identificador
Fotográfico do remetente, se ele tiver uma fotografia embebida na sua Chave
Pública. (Esta opção estará activa apenas se existir um Identificador
Fotográfico na chave.)
Informação de Segurança S/MIME: permite ver a informação de segurança
S/MIME da mensagem.
Se 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.
Abrir anexos cifrados / importar chaves OpenPGP em anexo
Anexos de nome *.pgp, *.asc, e *.gpg são reconhecidos como podendo ter um tratamento
especial por parte do Enigmail. Clicar com o botão alternativo do rato num anexo
deste tipo, activa dois itens de menu especiais no menu de contexto: Decifrar e
Abrir e Decifrar e Gravar Como.... Use estes dois itens de menu se
deseja que o Enigmail decifre um anexo antes de o abrir ou gravar. Se um anexo for
reconhecido como um ficheiro contendo uma chave OpenPGP, é-lhe oferecida a
possibilidade de importar as chaves para o seu porta-chaves.
enigmail-2.0.8/lang/pt-PT/help/rulesEditor.html 0000664 0000000 0000000 00000007273 13343027545 0021331 0 ustar 00root root 0000000 0000000
Ajuda do Enigmail: Editor de Regras
Ajuda do Enigmail
Usar o Editor de Regras do Enigmail
No 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:
Email: o(s) endereço(s) de email dos campos
Para:, CC:, e BCC: a encontrar. Cada coincidência trabalha em
substrings (Mais detalhes na janela do Editor de
Regras)
Chave(s) OpenPGP: a lista de Identificadores
de chaves OpenPGP a usar para o destinatário
Assinar: activar ou desactivar o assinar
de mensagens. Esta configuração usa ou sobrepõe-se ao indicado na janela de Composição
de mensagens. Os valores são:
Nunca: a mensagem não será assinada, mesmo com uma configuração em contrário
na janela de composição de mensagens (sobrepõe-se a outros valores)
Possível: a mensagem será assinada ou não, consoante a configuração na
janela de composição de mensagens.
Sempre: a mensagem será assinada, mesmo que a assinatura esteja
desactivada na janela de composição de
mensagens
Estas configurações aplicam-se a todas as regras
coincidentes. Se uma das regras desactivar a assinatura, a mensagem não será assinada,
independentemente de outras regras especificadas. Sempre.
Cifrar: activar ou desactivar a encriptação
de mensagens. As configurações permitidas e o seu significado são os mesmos de que
para a assinatura de mensagens.
PGP/MIME: activar ou desactivar o uso da
codificação de mensagens PGP/MIME (RFC 3156). Se a PGP/MIME estiver desactivada, as
mensagens serão codificadas usando "PGP embebido". As configurações permitidas e o
seu significado são os mesmo de que para a assinatura de mensagens.
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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.
Set OpenPGP Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the OpenPGP Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
enigmail-2.0.8/lang/ru/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020463 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
OpenPGP Security info: allows you to view the output status from GnuPG for the message.
Copy OpenPGP Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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.
Set OpenPGP Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the OpenPGP Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
enigmail-2.0.8/lang/sk/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020452 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
OpenPGP Security info: allows you to view the output status from GnuPG for the message.
Copy OpenPGP Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/sl/ 0000775 0000000 0000000 00000000000 13343027545 0014653 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/sl/am-enigprefs.properties 0000664 0000000 0000000 00000000120 13343027545 0021337 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=Varnost OpenPGP
enigmail-2.0.8/lang/sl/enigmail.dtd 0000664 0000000 0000000 00000164147 13343027545 0017152 0 ustar 00root root 0000000 0000000
' pri navajanju e-naslovov">
' za doloÄanje e-naslovov za GnuPG. IzkljuÄite, Äe imajo prejemniki stare kljuÄe Hushmail.">
Varnost OpenPGP)">
POZOR: Ustvarjanje kljuÄa lahko traja veÄ minut. V tem Äasu ne zaprite brskalnika. Ker je generator nakljunÄnih Å¡tevil odvisen od dejavnosti raÄunalnika, je priporoÄljivo npr. aktivno brskati, da bi pospeÅ¡ili ustvarjanje kljuÄa. Ko bo kljuÄ ustvarjen, boste o tem takoj obveÅ¡Äeni.">
' je neveljavno">
OPOMBA: Tvorba kljuÄa lahko traja nekaj minut. Ne zaprite aplikacije, medtem ko je tvorba kljuÄa v teku. Ko bo kljuÄ izdelan, boste o tem obveÅ¡Äeni.">
Opomba: Enigmail bo vedno preverjal podpise
e-sporoÄil za vsak raÄun ali identiteto, ne glede na to, ali je omogoÄeno ali ne">
javni kljuÄ je za druge, da vam poÅ¡ljejo Å¡ifrirana gesla. Razdelite ga lahko komerkoli.">
zasebni kljuÄ je za vas, da deÅ¡ifrirate to e-poÅ¡to in poÅ¡ljete podpisano e-poÅ¡to.
Nikomur ga ne smete dati.">
zasebni kljuÄ je za vas, da deÅ¡ifrirate to e-poÅ¡to in poÅ¡ljete podpisano e-poÅ¡to.
Nikomur ga ne smete dati.
Da zavarujete svoj javni kljuÄ, boste pozvani za geslo v naslednjih dveh pogovornih oknih.">
Geslo zaÅ¡Äiti vaÅ¡ zasebni kljuÄ in prepreÄi njegovo zlorabo.">
izvozite podatke s starega raÄunalnika s Äarovnikom za varnostno kopiranje iz nastavitev Enigmailuvozite podatke v nov raÄunalnik s tem Äarovnikom.
">
Hvala, ker uporabljate Enigmail.">
izvozite podatke s starega raÄunalnika s tem Äarovnikomuvozite podatke v nov raÄunalnik s Äarovnikom za namestitev.
">
enigmail-2.0.8/lang/sl/enigmail.properties 0000664 0000000 0000000 00000151721 13343027545 0020565 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Enigmail – opozorilo
enigConfirm=Enigmail – potrditev
# enigInfo=Enigmail Information
enigError=Enigmail – napaka
enigPrompt=Enigmail – prompt
dlgYes=&Da
dlgNo=&Ne
dlgKeepSetting=Zapomni si odgovor in ne spraÅ¡uj veÄ
dlgNoPrompt=Tega pogovornega okna ne pokaži nikoli veÄ
dlg.button.delete=I&zbriši
dlg.button.cancel=Pre&kliÄi
dlg.button.close=&Zapri
dlg.button.continue=&Nadaljuj
dlg.button.skip=Pres&koÄi
dlg.button.overwrite=&Prepiši
dlg.button.view=&Pokaži
dlg.button.retry=Poskusi &znova
dlg.button.ignore=&Prezri
# dlg.button.install=&Install
# dlg.button.ok=&OK
repeatPrefix=\n\nTo sporoÄilo se bo ponovilo %S
repeatSuffixSingular=-krat.
repeatSuffixPlural=-krat.
noRepeat=\n\nTo sporoÄilo se ne bo ponovilo vse do nadgradnje Enigmaila.
pgpNotSupported=Kot kaže, uporabljate Enigmail skupaj s PGP 6.x.\n\nŽal povzroÄa PGP 6.x nekatere težave, ki onemogoÄajo, da bi Enigmail deloval pravilno. Zato Enigmail PGP 6.x ni veÄ podprt. V prihodnosti raje uporabite GnuPG (GPG).\n\nÄŒe za prehod na GPG potrebujete podporo, obiÅ¡Äite stran PomoÄ/Help na domaÄi strani Enigmail.
initErr.howToFixIt=Za uporabo Enigmaila je zahtevan GnuPG. ÄŒe ga Å¡e niste namestili, je najlažji naÄin za namestitev uporaba spodnjega gumba "ÄŒarovnik za namestitev".
initErr.setupWizard.button=&ÄŒarovnik za namestitev
passphraseCleared=Geslo je bilo izbrisano.
cannotClearPassphrase=Za ravnanje z gesli uporabljate neobiÄajno orodje (kot je gnome-keyring). V Enigmailu zatorej ne morete poÄistiti gesla.
noPhotoAvailable=Na voljo ni nobene fotografije
debugLog.title=Enigmail Debug Log
error.photoPathNotReadable=Pot slike '%S' ni berljiva
# generalError=Error: %S
# Strings in configure.jsm
enigmailCommon.versionSignificantlyChanged=Nova razliÄica Enigmaila ima pomembne spremembe ravnanja z nastavitvami in možnostmi. Stare nastavitve smo poskusili prenesti na novo razliÄico. Vendar pa ne moremo samodejno zadostiti vsem primerom. Ponovno preverite nastale nove nastavitve in možnosti.
enigmailCommon.checkPreferences=Preveri nastavitve ...
preferences.defaultToPgpMime=Privzeto kodiranje sporoÄil smo v Enigmailu spremenili iz vdelanega PGP-ja v PGP/MIME. PriporoÄamo, da ga ohranite kot privzetega.\n\nÄŒe Å¡e vedno želite privzeto uporabljati vdelan PGP, to lahko storite v nastavitvah raÄuna pod Varnost OpenPGP.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=Uporabljate Enigmail razliÄice %S
# enigmailPepVersion=Enigmail/p≡p version %S
usingAgent=Za šifriranje in dešifriranje uporabi %S izvršilno datoteko %S
agentError=NAPAKA: Dostop do storitve Enigmail ni uspel!
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Napaka pri dostopu do storitve Enigmail
onlyGPG=Ustvarjanje kljuÄa deluje le z GnuPG (ne pa tudi z PGP)!
keygenComplete=Ustvarjanje kljuÄa je konÄano! Za podpisovanje bo uporabljena identiteta <%S>
revokeCertRecommended=Nadvse priporoÄamo, da za svoj kljuÄ ustvarite certifikat za preklic. Ta certifikat lahko uporabite za preklic svojega kljuÄa, npr. Äe vaÅ¡ skrivni kljuÄ izgubite ali je v nevarnosti. Želite zdaj ustvariti tak certifikat za preklic?
keyMan.button.generateCert=&Ustvari certifikat
genCompleteNoSign=Ustvarjanje kljuÄa je konÄano!
genGoing=Ustvarjanje kljuÄa je v teku!
passNoMatch=Geslo ni ustrezno; prosimo, ponovite vnos.
passCheckBox=ÄŒe ne uporabljate gesla za kljuÄ, potem prosim oznaÄite ustrezno možnost.
passUserName=Prosimo, podajte imena uporabnikov za to identiteto.
keygen.missingUserName=Za izbrani raÄun/identiteto ni navedenega imena. V polje "vaÅ¡e ime" v nastavitvah raÄuna vnesite vrednost.
keygen.passCharProblem=V svojem geslu uporabljate posebne znake. Na žalost lahko to povzroÄi težave pri ostalih programih. PriporoÄamo, da izberete geslo s samo naslednjimi znaki:\n a-z A-Z 0-9 /.;:-,!?(){}[]%*
passSpaceProblem=VaÅ¡e geslo se iz tehniÄnih razlogov ne sme zaÄeti ali konÄati s presledkom.
changePassFailed=Sprememba gesla ni uspela.
keyConfirm=Ustvari javni in skriti kljuÄ za '%S'?
keyMan.button.generateKey=&Ustvari kljuÄ
keyAbort=Prekinem ustvarjanje kljuÄa?
keyMan.button.generateKeyAbort=&Ustavi tvorbo kljuÄa
keyMan.button.generateKeyContinue=&Nadaljuj s tvorbo kljuÄa
expiryTooLong=Ne morete ustvariti kljuÄa, ki postane neveljaven kasneje kot v 100 letih.
expiryTooLongShorter=KljuÄa, ki poteÄe Äez veÄ kot 90 let, ne morete ustvariti.
expiryTooShort=VaÅ¡ kljuÄ mora biti veljaven najmanj en dan.
keyGenFailed=Ustvarjanje kljuÄa ni uspelo. Prosimo, za podrobnosti preverite konzolo Enigmail (Meni Enigmail > RazhroÅ¡Äevanje Enigmail).
setKeyExpirationDateFailed=Datuma prenehanja veljavnosti ni mogoÄe spremeniti
# Strings in enigmailMessengerOverlay.js
securityInfo=Varnostne informacije Enigmail\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Priloge temu sporoÄilu niso podpisane ali Å¡ifrirane*\n\n
possiblyPgpMime=Najverjetneje Å¡ifrirano ali podpisano sporoÄilo PGP/MIME; za preverjanje kliknite gumb DeÅ¡ifriraj
saveAttachmentHeader=Enigmail: Shrani dešifrirano priponko
noTempDir=Ni mogoÄe najti nobene zaÄasne mape za pisanje.\nProsimo, doloÄite sistemsko spremenljivko TEMP.
attachmentPgpKey=Priloga '%S', ki jo odpirate, je najverjetneje kljuÄ OpenPGP.\n\nKliknite 'Uvozi' za uvoz vsebovanega kljuÄa ali 'Pokaži', Äe si želite vsebino datoteke ogledati v oknu brskalnika.
beginPgpPart=********* *ZACETEK SIFRIRANEGA ali PODPISANEGA DELA* *********
endPgpPart=********** *KONEC SIFRIRANEGA ali PODPISANEGA DELA* **********
notePartEncrypted=Enigmail: *Deli sporocila NISO bili podpisani ali sifrirani*
noteCutMessage=Enigmail: *Najdenih je veÄ blokov sporoÄila -- deÅ¡ifriranje/preverjanje prekinjeno*
decryptOkNoSig=Pozor\n\nDeÅ¡ifriranje je bilo uspeÅ¡no, a podpisa ni mogoÄe preveriti.
msgOvl.button.contAnyway=&Vseeno nadaljuj
signature.verifiedOK=Podpis za priponko %S je bil uspešno preverjen.
signature.verifyFailed=Podpisa za priponko %S ni bilo mogoÄe preveriti.
attachment.noMatchToSignature=Priponka '%S' se ne ujema z datoteko podpisa
attachment.noMatchFromSignature=Datoteka podpisa '%S' se ne ujema s priponko
fixBrokenExchangeMsg.failed=SporoÄila ni uspelo popraviti.
# enigmail.msgViewColumn.label=Enigmail
# enigmailPep.msgViewColumn.label=Enigmail/p≡p
# wksNoIdentity=This key is not linked to any of your email accounts. Please add an account for at least one of the following email addresse(s):\n\n%S
# wksConfirmSuccess=Confirmation email sent.
# wksConfirmFailure=Sending the confirmation email failed.
# autocrypt.importSetupKey.accountPreconfigured=Your account is already correctly configured for Autocrypt.\n\nDo you really want to overwrite your settings with this setup message?
# autocrypt.importSetupKey.selfCreated=This message was created by your currently running instance of Enigmail.\n\nPlease switch to the email client to which you want to transfer the settings, and click on the message on that email client to import the settings.
# autocrypt.importSetupKey.invalidMessage=Error - could not read setup message. The message seems to be corrupted. Please try to create a new setup message on your "other" device.
# autocrypt.importSetupKey.invalidKey=Error - the key could not be imported. The key is either not supported by your version of GnuPG, or it got corrupted.
# autocrypt.importSetupKey.wrongPasswd=The password you entered is wrong. Do you want to retry?
# autocrypt.importSetupKey.success=The Autocrypt setup message was processed successfully. Autocrypt is now available for your account '%S'.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Izberi kljuÄe OpenPGP za vstavljanje
keysToUse=Izberi kljuÄe OpenPGP za uporabnika %S
pubKey=Javni kljuÄ za %S\n
windowLocked=Urejevalno okno je zaklenjeno; pošiljanje je bilo prekinjeno
sendUnencrypted=Inicializacija Enigmaila ni uspela.\nPoÅ¡ljem sporoÄilo neÅ¡ifrirano?
composeSpecifyEmail=Vnesite prosim glavni e-poÅ¡tni naslov, ki je potreben za izbor podpisnega kljuÄa za odhodna sporoÄila.\nÄŒe ne podate nobenega naslova, bo e-poÅ¡tni naslov v polju OD sporoÄila prepuÅ¡Äen izbiri kljuÄa.
sendingHiddenRcpt=To sporoÄilo ima prejemnike v polju BCC (skrita kopija). ÄŒe to sporoÄilo Å¡ifrirate, je mogoÄe skriti prejemnike skrite kopije, vendar uporabniki nekaterih izdelkov (npr. PGP Corp.) ne bodo mogli deÅ¡ifrirati sporoÄila. Zaradi tega priporoÄamo, da se izogibate polju skrite kopije (BCC) v Å¡ifriranih sporoÄilih.
sendWithHiddenBcc=Skrij prejemnike skrite kopije
sendWithShownBcc=Å ifriraj obiÄajno
sendingNews=PoÅ¡iljanje Å¡ifriranega sporoÄila je bilo prekinjeno.\n\nTega sporoÄila ne morete poslati Å¡ifriranega, ker so med prejemniki naslovi noviÄarskih skupin. To sporoÄilo poÅ¡ljite neÅ¡ifrirano.
sendToNewsWarning=Opozorilo: poslali boste Å¡ifrirano sporoÄilo na dopisni seznam.\n\nTega ne priporoÄamo, ker je to smiselno le, Äe lahko vsi Älani skupine deÅ¡ifrirajo sporoÄilo, t.j. sporoÄilo je potrebno deÅ¡ifrirati s kljuÄi vseh Älanov seznama. To sporoÄilo poÅ¡ljite le, Äe dobro veste, kaj poÄnete.\n\nŽelite nadaljevati?
hasHTML=Opozorilo za sporoÄila HTML: \nTo sporoÄilo lahko vsebuje HTML. To lahko onemogoÄi pravilno podpisovanje oz. Å¡ifriranje tega sporoÄila. Da bi to v prihodnje prepreÄili pri poÅ¡iljanju podpisanih sporoÄil, kliknite prosim dvigalko hkrati z gumbom Sestavi oz. Odgovori. Ko sporoÄilo podpiÅ¡ete, odstranite potrditev pri nastavitvah 'Ustvari sporoÄilo kot HTML' s Äimer poÅ¡iljanje sporoÄil HTML trajno prepreÄite.
strippingHTML=SporoÄilo vsebuje kodo HTML, ki bo izgubljena, Äe bo sporoÄilo za podpisovanje oz. Å¡ifriranje pretvorjeno v zgolj tekstovni zapis. Želite nadaljevati?
msgCompose.button.sendAnyway=&Vseeno poÅ¡lji sporoÄilo
attachWarning=Priponke tega sporoÄila niso lokalne, zato jih ni mogoÄe Å¡ifrirati. Za Å¡ifriranje priponk jih najprej shranite lokalno in jih nato dodajte sporoÄilu. Želite kljub temu poslati sporoÄilo?
quotedPrintableWarn=Za kodiranje sporoÄil ste nastavili 'quoted-printable'. To lahko pripelje do nepravilnega Å¡ifriranja in/ali preverjanja vaÅ¡ih sporoÄil.\nŽelite izklopiti nastavitev 'quoted printable'?
minimalLineWrapping=Prelom besedila ste nastavili na %S znakov. Za pravilno šifriranje in podpisovanje mora biti ta vrednost najmanj 68.\nŽelite zdaj vrednost nastaviti na 68?
warning=Opozorilo
signIconClicked=Spremenili ste nastavitve za podpisovanje. Zato za to sporoÄilo niÄ veÄ ne velja (de-)aktivacija podpisovanja skupaj z (de-)aktivacijo Å¡ifriranja.
errorOwnKeyUnusable=ID kljuÄa '%S', ki je nastavljen za trenutno identiteto, ne dobavi uporabnega kljuÄa OpenPGP.\n\nZagotovite, da imate veljaven kljuÄ OpenPGP in da vaÅ¡e nastavitve raÄuna nanj kažejo.\nÄŒe vaÅ¡ kljuÄ ni potekel, preverite, ali ste zaupanje lastniku nastavili na polno ali skrajno.
msgCompose.cannotSaveDraft=Napaka med shranjevanjem osnutka
# msgCompose.partiallyEncrypted.short=Beware of leaking sensitive information - partially encrypted email.
# msgCompose.partiallyEncrypted.mimeMsg=The message you are replying to contained both unencrypted and encrypted parts. Some encrypted message parts are invisible to you.\n\nIf the sender was not able to decrypt the hidden message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nWe recommend that you don't reply to the message, but create a new message containing your answer.
# msgCompose.partiallyEncrypted.inlinePGP=The message you are replying to contained both unencrypted and encrypted parts. If the sender was not able to decrypt some message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nPlease consider removing all quoted text from your reply to this sender.
msgCompose.internalEncryptionError=Notranja napaka: obljubljeno Å¡ifriranje onemogoÄeno
msgCompose.internalError=Pojavila se je zaÄetna napaka.
msgCompose.toolbarTxt.signAndEncrypt=To sporoÄilo po podpisano in Å¡ifrirano
msgCompose.toolbarTxt.signOnly=To sporoÄilo bo podpisano
msgCompose.toolbarTxt.encryptOnly=To sporoÄilo bo Å¡ifrirano
msgCompose.toolbarTxt.noEncryption=To sporoÄilo bo nepodpisano in neÅ¡ifrirano
msgCompose.toolbarTxt.disabled=Za izbrano identiteto je Enigmail onemogoÄen
# msgCompose.protectSubject.tooltip=Protect the message subject
# msgCompose.noSubjectProtection.tooltip=Do not protect the message subject
msgCompose.encryptedSubjectStub=Å ifrirano sporoÄilo
# msgCompose.protectSubject.dialogTitle=Enable Protection of Subject?
# msgCompose.protectSubject.question=Regular encrypted emails contain the unredacted subject.\n\nWe have established a standard to hide the original subject in the encrypted message\nand replace it with a dummy text, such that the subject is only visible after the email is decrypted.\n\nDo you want to protect the subject in encrypted messages?
# msgCompose.protectSubject.yesButton=&Protect subject
# msgCompose.protectSubject.noButton=&Leave subject unprotected
msgCompose.detailsButton.label=Podrobnosti …
msgCompose.detailsButton.accessKey=P
# msgCompose.pepSendUnknown=Unknown
# msgCompose.pepSendUnsecure=Unsecure
# msgCompose.pepSendSecure=Secure
# msgCompose.pepSendTrusted=Secure & Trusted
# pep.alert.disabledForIdentity=p≡p is disabled for the current identity. Please enable p≡p via the Enigmail/p≡p preferences.
# pep.alert.weakReply=You’re about to forward or reply to a secure message as insecure. If you choose to proceed, confidential information might be leaked putting you and your communication partner at risk. Are you sure you want to continue?
# note: should end with double newline:
sendAborted=Pošiljanje je bilo prekinjeno.\n\n
# details:
keyNotTrusted=Premalo zaupanja za kljuÄ '%S'
keyNotFound=KljuÄa '%S' ni mogoÄe najti
keyRevoked=KljuÄ '%S' je preklican
keyExpired=KljuÄ '%S' je potekel
statPGPMIME=PGP/MIME
# statSMIME=S/MIME
statSigned=PODPISANO
statEncrypted=Å IFRIRANO
statPlain=NEPODPISANO in NEÅ IFRIRANO
offlineSave=Želite shraniti sporoÄilo %S, namenjeno %S, v mapo 'Neodposlana sporoÄila'?
onlineSend=Želite poslati sporoÄilo %S prejemniku %S?
encryptKeysNote=Napotek\\: SporoÄilo je Å¡ifrirano z naslednjimi kljuÄi identitete uporabnikov\\: %S
hiddenKey=
signFailed=Napaka v programu Enigmail; Å¡ifriranje oz. podpisovanje ni uspelo. Želite poslati sporoÄilo nezavarovano?
msgCompose.button.sendUnencrypted=&PoÅ¡lji neÅ¡ifrirano sporoÄilo
recipientsSelectionHdr=Izberite prejemnika šifriranja
configureNow=Varnosti Enigmail za izbrano identiteto še niste nastavili. Želite to zdaj storiti?
# encryption/signing status and associated reasons:
encryptMessageAuto=Å ifriraj sporoÄilo (samodejno)
encryptMessageNorm=Å ifriraj sporoÄilo
signMessageAuto=PodpiÅ¡i sporoÄilo (samodejno)
signMessageNorm=PodpiÅ¡i sporoÄilo
encryptOff=Å ifriranje: IZKLJUÄŒENO
encryptOnWithReason=Å ifriranje: VKLJUÄŒENO (%S)
encryptOffWithReason=Å ifriranje: IZKLJUÄŒENO (%S)
encryptOn=Å ifriranje: VKLJUÄŒENO
signOn=Podpisovanje: VKLJUÄŒENO
signOff=Podpisovanje: IZKLJUÄŒENO
signOnWithReason=Podpisovanje: VKLJUÄŒENO (%S)
signOffWithReason=Podpisovanje: IZKLJUÄŒENO (%S)
reasonEnabledByDefault=privzeto omogoÄeno
reasonManuallyForced=roÄno vsiljeno
reasonByRecipientRules=vsiljeno s pravili prejemnika
reasonByAutoEncryption=vsiljeno s samo-šifriranjem
reasonByConflict=zaradi spora v pravilih prejemnika
reasonByEncryptionMode=zaradi naÄina Å¡ifriranja
# should not be used anymore:
encryptYes=SporoÄilo bo Å¡ifrirano
encryptNo=SporoÄilo ne bo Å¡ifrirano
# should not be used anymore:
signYes=SporoÄilo bo podpisano
signNo=SporoÄilo ne bo podpisano
# PGP/MIME status:
pgpmimeNormal=Protokol: PGP/MIME
inlinePGPNormal=Protokol: vdelan PGP
# smimeNormal=Protocol: S/MIME
pgpmimeAuto=Protokol: PGP/MIME (samodejno)
inlinePGPAuto=Protokol: vdelan PGP (samodejno)
# smimeAuto=Protocol: S/MIME (auto)
# should not be used anymore
pgpmimeYes=Uporabljen bo PGP/MIME
pgpmimeNo=Uporabljen bo vrinjen PGP
# Attach own key status (tooltip strings):
attachOwnKeyNo=VaÅ¡ lasten kljuÄ ne bo pripet
attachOwnKeyYes=VaÅ¡ lasten kljuÄ bo pripet
attachOwnKeyDisabled=VaÅ¡ega lastnega kljuÄa ni mogoÄe pripeti. Izbrati morate doloÄen kljuÄ\nv odseku OpenPGP v nastavitvah raÄuna, da omogoÄite to znaÄilnost.
rulesConflict=Najdena so nasprotujoÄa si pravila za prejemnika\n%S\n\nŽelite poslati sporoÄilo s temi nastavitvami?
msgCompose.button.configure=Pri&lagodi
msgCompose.button.send=&PoÅ¡lji sporoÄilo
msgCompose.button.save=&Shrani sporoÄilo
# Strings in enigmailMsgHdrViewOverlay.js
keyNeeded=Za preverjanje podpisa potrebujete javni kljuÄ %S
keyUsed=Javni kljuÄ %S, ki se uporablja za preverjanje podpisa
clickDecrypt=; kliknite na gumb Dešifriraj
clickDecryptRetry=; za ponoven poskus kliknite na ikono šifriranja
clickDetailsButton=; za veÄ informacij kliknite na gumb 'Podrobnosti'
clickImportButton=; za prenos kljuÄa kliknite na gumb 'Uvozi kljuÄ'
keyTypeUnsupported=; vaÅ¡a razliÄica GnuPG ne podpira te vrste kljuÄa
msgPart=Del sporoÄila %S
msgSigned=podpisan
msgSignedUnkownKey=podpisano z neznanim kljuÄem
msgEncrypted=šifriran
msgSignedAndEnc=podpisan in šifriran
unverifiedSig=Podpis ni preverjen
incompleteDecrypt=Dešifriranje je bilo nepopolno
needKey=Napaka - Za deÅ¡ifriranje je potreben skrivni kljuÄ
failedDecrypt=Napaka - Dešifriranje ni uspelo
badPhrase=Napaka - NapaÄno geslo
failedDecryptVerify=Napaka - Dešifriranje/preverjanje ni uspelo
viewInfo=; Za podrobnosti izberite Pogled > Informacije o varnosti sporoÄila
decryptedMsg=DeÅ¡ifrirano sporoÄilo
decryptedMsgWithFormatError=DeÅ¡ifrirano sporoÄilo (obnovljena pokvarjena oblika e-poÅ¡te PGP, ki jo je povzroÄil star strežnik Exchange, tako da rezultat verjetno ne bo popoln za branje)
usedAlgorithms=Uporabljeni algoritmi: %S in %S
# pepStatusInfo.text=p≡p Message Status.
# pepStatusInfo.title.m3=Under Attack
# pepStatusInfo.info.m3=This message is not secure and has been tampered with.
# pepStatusInfo.title.m1=Mistrusted
# pepStatusInfo.info.m1=This message has a communication partner that has previously been marked as mistrusted
# pepStatusInfo.title.r0=Unknown
# pepStatusInfo.info.r0=This message does not contain enough information to determine if it is secure.
# pepStatusInfo.title.r1=Cannot Decrypt
# pepStatusInfo.info.r1=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r2=Cannot Decrypt
# pepStatusInfo.info.r2=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r3=Unsecure
# pepStatusInfo.info.r3=This message is unsecure.
# pepStatusInfo.title.r4=Unsecure for Some
# pepStatusInfo.info.r4=This message is unsecure for some communication partners.
# pepStatusInfo.title.r5=Unreliable Security
# pepStatusInfo.info.r5=This message has unreliable protection.
# pepStatusInfo.title.r6=Secure...
# pepStatusInfo.info.r6=This message is secure but you still need to verify the identity of your communication partner.
# pepStatusInfo.title.r7=Secure & Trusted
# pepStatusInfo.info.r7=This message is secure and trusted.
# pepStatusInfo.color.green=Green
# pepStatusInfo.color.yellow=Yellow
# pepStatusInfo.color.red=Red
# pepRevokeTrust.question=Do you really want to cancel the trust for %S?
# pepRevokeMistrust.question=Do you really want to re-trust the key for %S?
# pepRevokeTrust.doRevoke=Cancel &trust
# wksConfirmationReq=Web Key Directory Confirmation Request
# wksConfirmationReq.message=This message has been sent by your email provider to confirm deployment of your OpenPGP public key\nin their Web Key Directory.\nProviding your public key helps others to discover your key and thus being able to encrypt messages to you.\n\nIf you want to deploy your key in the Web Key Directory now, please click on the button "Confirm Request" in the status bar.\nOtherwise, simply ignore this message.
# wksConfirmationReq.button.label=Confirm Request
# autocryptSetupReq=Perform Autocrypt Setup
# autocryptSetupReq.button.label=Start Setup
# autocryptSetupReq.setupMsg.desc=This message contains all information to transfer your Autocrypt settings along with your secret key securely from your original device.
# autocryptSetupReq.setupMsg.backup=You can keep this message and use it as a backup for your secret key. If you want to do this, you should write down the password and store it securely.
# autocryptSetupReq.message.import=To import the settings and key(s) in Enigmail, please click on the "Start Setup" button in the status bar.
# autocryptSetupReq.message.sent=Please click on the message on your new device and follow the instuctions to import the settings.
# strings in pref-enigmail.js
# oldGpgVersion20=Enigmail initialization failed.\n\nYou are using GnuPG version %1$S, which is not supported anymore. Enigmail requires GnuPG version %2$S or newer. Please upgrade your GnuPG installation, or Enigmail will not work.
locateGpg=Najdi program GPG
invalidGpgPath=GnuPG ni mogoÄe izvrÅ¡iti s podano potjo. OpenGPG je zatorej deaktiviran, dokler znova ne spremenite poti do GnuPG ali ponovno ne zaženete aplikacije.
warningsAreReset=Vsa opozorila so bila ponastavljena.
prefs.gpgFound=GnuPG se nahaja v %S
prefs.gpgNotFound=Ni mogoÄe najti programa GnuPG
prefs.warnAskNever=Opozorilo: z aktivacijo te možnosti boste povzroÄili neÅ¡ifrirana e-sporoÄila brez dodatnih opozoril, Äe kljuÄ za enega od prejemnikov ne obstaja -- Enigmail vas o tem ne bo opozarjal!
prefs.warnIdleTimeForUnknownAgent=VaÅ¡ sistem uporablja specializirano orodje za ravnanje z gesli, kot sta gnome-keyring ali seahorse-agent. Žal OpenGPG ne more nadzorovati Äasovne prekoraÄitve gesla za orodje, ki ga uporabljate. Zato se ustrezne nastavitve Äasovne prekoraÄitve v Enigmail ne upoÅ¡tevajo.
prefEnigmail.oneKeyserverOnly=Napaka - navedete lahko le en strežnik kljuÄev za samodejno prenaÅ¡anje manjkajoÄih kljuÄev OpenPGP.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Prosimo, vtipkajte ADMIN PIN svoje pametne kartice
enterCardPin=Prosimo, vtipkajte PIN svoje pametne kartice
notInit=Napaka - Storitev Enigmail še ni nastavljena
badCommand=Napaka - Å ifriranje ni uspelo
cmdLine=ukazna vrstica in izpis\\:
notRequired=Napaka - Å ifriranje ni potrebno
notComplete=Napaka - Ustvarjanje kljuÄa Å¡e ni dokonÄano
invalidEmail=Napaka - Neveljaven(i) e-poštni naslov(i)
noPassphrase=Napaka – Niste vnesli gesla
noPGPblock=Napaka – Ni nobenega veljavnega bloka OpenPGP
unverifiedReply=Del sporoÄila (odgovor) je bil morda spremenjen
keyInMessageBody=Najdena kljuÄ in telo sporoÄila. Kliknite 'Uvozi kljuÄ', da ga uvozite
sigMismatch=Napaka – Podpis ni pravilen
cantImport=Napaka pri uvozu javnega kljuÄa\n\n
doImportOne=Uvozi %1$S (%2$S)?
doImportMultiple=Uvozi naslednje kljuÄe?\n\n%S
previewFailed=Javnega kljuÄa ni mogoÄe brati.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=Pametne kartice %S, ki je v bralniku, ni mogoÄe uporabiti za obdelavo sporoÄila.\nProsimo, vstavite pametno kartico %S in ponovite postopek.
sc.insertCard=Postopek zahteva vašo pametno kartico %S.\nProsimo, vstavite zahtevano pametno kartico in ponovite postopek.
sc.removeCard=Postopek ne potrebuje prisotnosti pametne kartice v bralniku.\nProsimo, odstranite svojo pametno kartico in ponovite postopek.
sc.noCardAvailable=V vašem bralniku ni nobene pametne kartice.\nProsimo, vstavite svojo pametno kartico in ponovite postopek.
sc.noReaderAvailable=Vaš bralnik pametnih kartic ni dosegljiv.\nProsimo, povežite svoj bralnik pametnih kartic, vstavite kartico in ponovite postopek.
keyError.keySpecNotFound=E-poÅ¡tnega naslova "%S" ni mogoÄe ujemati s kljuÄem na vaÅ¡i verigi.
keyError.keyIdNotFound=Nastavljenega ID kljuÄa "%S" ni mogoÄe najti na vaÅ¡i verigi.
keyError.resolutionAction=Izberte veljaven kljuÄ v odseku OpenPGP v nastavitvah raÄuna.
missingPassphrase=Manjka geslo
errorHandling.gpgAgentInvalid=VaÅ¡ sistem izvaja razliÄico gpg-agenta, ki ni primerna za vaÅ¡o razliÄico GnuPG-ja.
errorHandling.gpgAgentError=GnuPG je sporoÄil napako v komunikaciji z gpg-agentom (sestavni del GnuPG-ja).
errorHandling.dirmngrError=GnuPG je sporoÄil napako v komunikaciji z dirmngr-jem (sestavni del GnuPG-ja).
errorHandling.pinentryError=GnuPG ne more poizvedeti za vaše geslo preko vnosa PIN-a.
errorHandling.readFaq=To je napaka namestitve ali nastavitve sistema, ki prepreÄuje pravilno delovanje Enigmaila in se je ne da samodejno popraviti.\n\nZelo priporoÄamo, da se posvetujete z naÅ¡o spletno stranjo za podporo na https://enigmail.net/faq.
gpgNotFound=Ni mogoÄe najti programa GnuPG '%S'.\nPreverite, da je pot do programa GnuPG v nastavitvah Enigmail podana pravilno.
gpgNotInPath=Na podani poti PATH ni mogoÄe najti programa GnuPG.\nPreverite, da je pot do programa GnuPG v nastavitvah Enigmail podana pravilno.
enigmailNotAvailable=Glavna storitev Enigmaila ni na voljo
prefGood=Pravilen podpis %S
prefBad=NAPAÄŒEN podpis %S
failCancel=Napaka - Uporabnik je prekinil sprejem kljuÄa
failNoServer=Napaka - Strežnik kljuÄev ni podan
failNoID=Napaka - Ni bila podana identiteta kljuÄa
failKeyExtract=Napaka - Ekstrakcija kljuÄa ni uspela
notFirstBlock=Napaka - Prvi blok OpenPGP ni javni blok kljuÄa
importKeyConfirm=Želite uvoziti v sporoÄilu vsebovani javni kljuÄ?
failKeyImport=Napaka - KljuÄa ni mogoÄe uvoziti
fileWriteFailed=Pisanje v datoteko %S ni mogoÄe
importKey=Uvažam javni kljuÄ %S s strežnika kljuÄev\\:
uploadKey=PoÅ¡lji javni kljuÄ %S na strežnik kljuÄev:
keyId=ID kljuÄa
keyAndSigDate=ID kljuÄa: 0x%S / Podpisano: %S
keyFpr=Prstni odtis kljuÄa: %S
noEmailProvided=Niste vnesli e-poštnega naslova!
keyAlreadySigned=KljuÄ je že podpisan, ne morete ga podpisati dvakrat.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=veljavnost %S je potekla
createdHeader=Ustvarjen
atLeastOneKey=Niste izbrali nobenega kljuÄa\\! Izbrati morate vsaj en kljuÄ.
fewerKeysThanRecipients=Izbrali ste manjÅ¡e Å¡tevilo kljuÄev, kot je prejemnikov. Ste prepriÄani, da je seznam kljuÄev za Å¡ifriranje popoln?
userSel.button.goBack=Izberite veÄ kljuÄev
userSel.secretKeySel.title=Izberite skrivni kljuÄ OpenPGP, s katerim boste podpisovali svoja sporoÄila
userSel.problemNoKey=Ni veljavnega kljuÄa.
userSel.problemMultipleKeys=VeÄ kljuÄev
# should be same as thunderbird ENTITY sendLaterCmd.label:
sendLaterCmd.label=Pošlji kasneje
# Strings used in enigmailAttachmentDialog.js
# pgpMimeNote=NOTE: PGP/MIME is not supported by all email clients. If you are unsure, select the %S option.
first=prvi
second=drugi
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Izberite kljuÄ OpenPGP za Å¡ifriranje
identityName=Identiteta: %S
# switchPepMode=You are currently using the 'p≡p Junior' mode of Enigmail.\n\nBy enabling OpenPGP or S/MIME for an account, you are disabling p≡p and use the 'regular' mode of Enigmail without p≡p.
# enableEnigmail=&Disable p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=Vklopili ste Å¡ifriranje, niste pa izbrali nobenega kljuÄa. Da bi poÅ¡iljali %S Å¡ifrirana sporoÄila, morate izbrati enega ali veÄ veljavnih kljuÄev. Želite izklopiti Å¡ifriranje?
noKeyToUse=(brez - ne zaklepaj)
noEmptyRule=Pravila ne smejo biti prazna. Prosimo, vnesite vsaj en e-poštni naslov.
invalidAddress=Vneseni e-poÅ¡tni naslovi niso veljavni. Ne smete vnesti imen prejemnikov, temveÄ zgolj e-poÅ¡tne naslove. Primer:\nNeveljavno: Janez Kranjski \nPravilno: janez.kranjski@domena.si
# noCurlyBrackets=The curly brackets {} have a special meaning and should not be used in an email address. If you want to modify the matching behavior for this rule, use the 'Apply rule if recipient ...' option.\nMore information is available from the Help button.
# Strings used in enigmailRulesEditor.js
never=nikoli
always=vedno
possible=ko je mogoÄe
deleteRule=Želite izbrisati izbrana pravila?
nextRcpt=(naslednji prejemnik)
negateRule=ne
addKeyToRule=Dodaj kljuÄ %1$S (%2$S) pravilu za uporabnika
# Strings used in enigmailSearchKey.js
needOnline=Funkcija, ki ste jo izbrali, ni na voljo v naÄinu brez povezave. Prosimo, povežite se in poskusite znova.
protocolNotSupported=Protokol '%S://', ki ste ga izbrali, ni podprt za prenos kljuÄev OpenPGP.
gpgkeysDisabled=Pomagalo bo, Äe omogoÄite izbiro 'extensions.enigmail.useGpgKeysTool'.
noKeyserverConn=Ni se mogoÄe povezati s strežnikom kljuÄev na naslovu %S.
keyDownloadFailed=Prenos kljuÄa s strežnika kljuÄev ni uspel. SporoÄilo o stanju se glasi:\n%S
internalError=PriÅ¡lo je do notranje napake. KljuÄev ni bilo mogoÄe prenesti ali uvoziti.
noKeyFound=Oprostite, a ni mogoÄe najti nobenega kljuÄa, ki bi ustrezal navedenemu e-poÅ¡tnemu naslovu.
# keyDownload.keyUnavailable=We are sorry, but the key with ID %S is not available on the keyserver. Most likely, the owner of the key did not upload their key to the keyserver.\n\nPlease ask the sender of the message to send you their key by email.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Iskanje ali prenos kljuÄa s strežnika kljuÄev: gpgkeys_%S ni bilo mogoÄe izvesti.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Nastavljanje zaupanja kljuÄa ni uspelo
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Podpisovanje kljuÄa ni uspelo
alreadySigned.label=Opomnik: kljuÄ %S je že podpisan z izbranim skrivnim kljuÄem.
alreadySignedexportable.label=Opomba: kljuÄ %S je že podpisan za izvažanje z izbranim zasebnim kljuÄem. Lokalni podpis ni smiseln.
partlySigned.label=Opomba: nekateri uporabniÅ¡ki ID-ji kljuÄa %S so že podpisani z izbranim skrivnim kljuÄem.
noTrustedOwnKeys=Primernega kljuÄa za podpisovanje ni bilo najdenega! Potrebujete vsaj en popolnega zaupanja vreden kljuÄ za podpisovanje drugih kljuÄev.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=Poteka nalaganje kljuÄev, prosimo, poÄakajte ...
keyValid.unknown=neznan
keyValid.invalid=neveljaven
keyValid.disabled=onemogoÄen
keyValid.revoked=preklican
keyValid.expired=pretekel
keyValid.noSubkey=ni veljavnega podkljuÄa
keyTrust.untrusted=ni vreden zaupanja
keyTrust.marginal=delno zaupanje
keyTrust.full=zaupanje
keyTrust.ultimate=popolno zaupanje
keyTrust.group=(skupina)
keyType.public=jav
keyType.publicAndSec=jav/skr
keyMan.enableKey=OmogoÄi kljuÄ
keyMan.disableKey=OnemogoÄi kljuÄ
userAtt.photo=Uporabniški atribut (slika JPEG)
asciiArmorFile=Zavarovane datoteke ASCII (*.asc)
importKeyFile=Uvozi datoteko kljuÄa OpenPGP
gnupgFile=Datoteke GnuPG
# createKeyOK=Your Key has been generated
saveRevokeCertAs=Ustvari in shrani potrdilo o preklicu
# revokeCertOK=The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
revokeCertFailed=Potrdila o preklicu ni bilo mogoÄe ustvariti.
addUidOK=Uporabniška ID uspešno dodana
addUidFailed=Dodajanje uporabniške ID ni uspelo
noKeySelected=Za izvedbo izbrane operacije morate izbrati vsaj en kljuÄ
exportToFile=Izvozi javni kljuÄ v datoteko
exportKeypairToFile=Izvozi tajni in javni kljuÄ v datoteko
exportSecretKey=Želite vkljuÄiti skrivni kljuÄ v shranjeno datoteko kljuÄa OpenPGP?
saveKeysOK=KljuÄi so bili uspeÅ¡no shranjeni
saveKeysFailed=Shranjevanje kljuÄev ni uspelo
importKeysFailed=Uvoz kljuÄev ni uspel
enableKeyFailed=OmogoÄanje/onemogoÄanje kljuÄa ni uspelo
specificPubKeyFilename=%1$S (0x%2$S) jav
specificPubSecKeyFilename=%1$S (0x%2$S) jav-skr
defaultPubKeyFilename=Izvoženi-javni-kljuÄi
defaultPubSecKeyFilename=Izvoženi-javni-in-skrivni-kljuÄi
noSecretKeys=Najdenih ni bilo skrivnih kljuÄev.\n\nŽelite zdaj tvoriti svoj lastni kljuÄ?
sendKeysOk=KljuÄ(i) uspeÅ¡no poslani
sendKeysFailed=PoÅ¡iljanje kljuÄev ni uspelo
receiveKeysOk=KljuÄ(i) uspeÅ¡no posodobljeni
receiveKeysFailed=Prenos kljuÄev ni uspel
importFromClip=Želite uvoziti nekatere kljuÄe iz odložiÅ¡Äa?
importFromUrl=Prenesi javni kljuÄ iz tega URL-ja:
copyToClipbrdFailed=Kopiranje izbranega kljuÄa(-ev) v odložiÅ¡Äe ni uspelo.
copyToClipbrdOK=KljuÄ(i) kopirani v odložiÅ¡Äe
deleteSecretKey=OPOZORILO: Izbrisati želite skrivni kljuÄ!\nÄŒe izbriÅ¡ete svoj skrivni kljuÄ, ne boste veÄ mogli deÅ¡ifrirati sporoÄil, Å¡ifriranih za ta kljuÄ.\n\nResniÄno želite izbrisati OBA, skrivni kljuÄ in javni kljuÄ\n'%S'?
deleteMix=OPOZORILO: Izbrisati želite skrivne kljuÄe!\nÄŒe izbriÅ¡ete svoj skrivni kljuÄ, ne boste veÄ mogli deÅ¡ifrirati sporoÄil, Å¡ifriranih za ta kljuÄ.\n\nResniÄno želite izbrisati OBA, skrivni kljuÄ in javni kljuÄ?
deletePubKey=Želite izbrisati javni kljuÄ\n'%S'?
deleteSelectedPubKey=Želite izbrisati javne kljuÄe?
deleteKeyFailed=KljuÄa ni mogoÄe izbrisati.
revokeKeyQuestion=Ste pred preklicem kljuÄa '%S'.\n\nS tem kljuÄem ne boste mogli veÄ podpisovati in ga porazdelitvi ne boste veÄ mogli uporabljati za Å¡ifriranje. Å e vedno ga lahko uporabljate za deÅ¡ifriranje starih sporoÄil.\n\nAli želite nadaljevati?
revokeKeyOk=KljuÄ je bil preklican. ÄŒe je vaÅ¡ kljuÄ na voljo na strežniku kljuÄev, je priporoÄljivo, da ga ponovno naložite nanj, tako da drugi lahko opazijo preklic.
revokeKeyFailed=KljuÄa ni mogoÄe preklicati.
# revokeKeyNotPresent=You have no key (0x%S) which fits to this revocation certificate!\n\nIf you have lost your key, you must import it (e.g. from a keyserver) before the revocation certificate!
# revokeKeyAlreadyRevoked=The key 0x%S has already been revoked.
refreshAllQuestion=Nobenega kljuÄa niste izbrali. Bi radi osvežili VSE kljuÄe?
# refreshKeyServiceOn.warn=Warning: Your keys are currently being refreshed in the background as safely as possible.\nRefreshing all your keys at once will unnecessarily reveal information about you.\nDo you really want to do this?
refreshKey.warn=Opozorilo: glede na Å¡tevilo kljuÄev in hitrost povezave je lahko osveževanje vseh kljuÄev razmeroma dolg postopek!
downloadContactsKeys.warn=Opozorilo: glede na Å¡tevilo stikov in hitrost povezave je prenos vseh kljuÄev lahko zelo dolg postopek!
downloadContactsKeys.importFrom=Želite uvoziti stike iz adresarja '%S'?
keyMan.button.exportSecKey=&Izvozi skrivne kljuÄe
keyMan.button.exportPubKey=Izvozi le &javne kljuÄe
keyMan.button.import=&Uvozi
keyMan.button.refreshAll=&Osveži vse kljuÄe
keyMan.button.revokeKey=&PrekliÄi kljuÄ
keyMan.button.skip=Pre&skoÄi kljuÄ
keylist.noOtherUids=Nima drugih identitet
keylist.hasOtherUids=Znan(a) tudi kot
keylist.noPhotos=Fotografija ni na voljo
keylist.hasPhotos=Fotografije
keyMan.addphoto.filepicker.title=Izberite fotografijo za dodajanje
keyMan.addphoto.warnLargeFile=Datoteka, ki ste jo izbrali, je veÄja od 25kB.\nNe priporoÄamo, da dodajate velike datoteke, ker se s tem zelo poveÄujejo kljuÄi.
keyMan.addphoto.noJpegFile=Izbrana datoteka ni datoteka JPEG. Izberite drugo datoteko.
keyMan.addphoto.failed=Slike ni mogoÄe dodati.
# noWksIdentity=The key %S does not have a WKS identity.
# keyman.addBlacklistKey.msg=Do you really want p≡p to stop using the key "%1$S (%2$S)" for encrypting messages?
# keyman.removeBlacklistKey.msg=Do you want to allow p≡p to use key "%1$S (%2$S)" for future messages?
# keyman.addBlacklistKey.button=&Blacklist the key
# keyman.removeBlacklistKey.button=&Remove key from Blacklist
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Spreminjanje primarnega uporabniške ID ni uspelo
changePrimUidOK=Primarna uporabniška ID uspešno spremenjena
revokeUidFailed=Preklic uporabniške ID %S ni uspel
revokeUidOK=UporabniÅ¡ka ID %S je bila uspeÅ¡no preklicana. ÄŒe je vaÅ¡ kljuÄ na voljo na strežniku kljuÄev, je priporoÄljivo, da ga ponovno naložite nanj, tako da drugi lahko opazijo preklic.
revokeUidQuestion=ResniÄno želite preklicati uporabniÅ¡ko ID %S?
# Strings in enigmailKeyImportInfo.xul
importInfoTitle=USPEH! KljuÄi uvoženi
importInfoBits=Biti
importInfoCreated=Ustvarjeno
importInfoFpr=Prstni odtis
importInfoDetails=(podrobnosti)
importInfoNoKeys=Noben kljuÄ se ni uvozil.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=javni kljuÄ
keyTypePrimary=primarni kljuÄ
keyTypeSubkey=podkljuÄ
keyTypePair=par kljuÄev
keyExpiryNever=nikoli
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
keyAlgorithm_18=ECC
keyAlgorithm_19=ECC
keyAlgorithm_20=ELG
keyAlgorithm_22=EDDSA
keyUsageEncrypt=Å ifriraj
keyUsageSign=Podpiši
keyUsageCertify=Potrdi
keyUsageAuthentication=Overjanje
keyDoesNotExpire=KljuÄ ne poteÄe
# Strings in enigmailGenCardKey.xul
keygen.started=Prosimo, poÄakajte, da se ustvari kljuÄ ...
keygen.completed=KljuÄ je bil ustvarjen. ID novega kljuÄa je: 0x%S
keygen.keyBackup=KljuÄ je bil varnostno kopiran kot %S
keygen.passRequired=Prosimo, navedite geslo, Äe želite ustvariti varnostno kopijo svojega kljuÄa zunaj pametne kartice.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=Sprememba PIN ni uspela
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Osveževanje kljuÄev je v teku, prosimo, poÄakajte ...
keyserverProgress.uploading=PrenaÅ¡anje kljuÄev je v teku, prosimo, poÄakajte ...
# keyserverProgress.wksUploadFailed=Could not upload your key to the Web Key Service
# keyserverProgress.wksUploadCompleted=Your public key was successfully submitted to your provider. You will receive an email to confirm that you initiated the upload.
keyserverTitle.refreshing=Osveževanje kljuÄev
keyserverTitle.uploading=Prenos kljuÄev
# Strings in enigmailSetupWizard
passphrase.min8keys=Geslo mora vsebovati najmanj osem znakov!
setupWizard.reallyCancel=ResniÄno želite zapreti namestitvenega Äarovnika Enigmail?
setupWizard.invalidGpg=Datoteka, ki ste jo navedli, ni izvršljiv program GnuPG. Navedite drugo datoteko.
setupWizard.specifyFile=Za nadaljevanje morate navesti vsaj datoteko javnega kljuÄa.
setupWizard.installFailed=Zdi se, da namestitev ni bila uspeÅ¡na. Ponovno poskusite z namestitvijo ali namestite GnuPG roÄno in ga poiÅ¡Äite z gumbom Prebrskaj.
# setupWizard.downloadForbidden=For your own security, we will not download GnuPG. Please visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.downloadImpossible=We cannot download GnuPG currently. Please try later or visit https://gnupg.org/ in order to download GnuPG.
setupWizard.hashSumError=ÄŒarovnik integritete prenesen datoteke ni uspel preveriti. Datoteka je morda okvarjena ali Å¡kodljivo spremenjena. Želite kljub temu nadaljevati z nameÅ¡Äanjem?
setupWizard.importSettingsFile=Navedite datoteko varnostne kopije za nalaganje
setupWizard.invalidSettingsFile=Navedena datoteka ni pravilna datoteka varnostne kopije nastavitev Enigmaila.
setupWizard.gpgConfExists=Datoteka nastavitev GnuPG že obstaja. Ali jo želite prepisati z datoteko iz stare namestiteve?
# setupWizard.noGpgHomeDir=It appears that you configured %S to use for GnuPG. However, this is not a directory - you cannot use it.
# setupWizard.unmachtedIds=The following identities of your old setup could not be matched:\n%S\nThe settings for these identities were skipped.
# Strings in installGnuPG.jsm
installGnuPG.downloadFailed=Pri prenašanju GnuPG je prišlo do napake. Preverite zapisnik konzole za podrobnosti.
installGnuPG.installFailed=Pri nameÅ¡Äanju GnuPG je priÅ¡lo do napake. Preverite zapisnik konzole za podrobnosti.
# Strings in enigmailAddUidDlg.xul
addUidDlg.nameOrEmailError=Vnesti morate ime in e-poštni naslov
addUidDlg.nameMinLengthError=Ime mora obsegati najmanj pet znakov
addUidDlg.invalidEmailError=Navesti morate veljaven e-poštni naslov
# Strings in enigmailCardDetails.js
Carddetails.NoASCII=Pametne kartice OpenPGP v imenu podpirajo samo znake ASCII.
# network error types
errorType.SecurityCertificate=Varnostno potrdilo, ki ga izkazuje spletna storitev, ni veljavno.
errorType.SecurityProtocol=Varnostni protokol, ki ga uporablja spletna storitev, ni znan.
errorType.Network=Prišlo je do omrežne napake.
# filter stuff
filter.folderRequired=Izbrati morate ciljno mapo.
filter.decryptMove.label=Dešifriraj za vedno (Enigmail)
filter.decryptCopy.label=Ustvari dešifrirano kopijo (Enigmail)
filter.decryptMove.warnExperimental=Opozorilo - dejanje filtra "Trajno deÅ¡ifriraj" lahko privede do uniÄenih sporoÄil.\n\nZelo priporoÄamo, da najprej poskusite s filtrom "Ustvari deÅ¡ifrirano kopijo", skrbno preskusite rezultat in zaÄnite uporabljati ta filter samo, ko ste zadovoljni z rezultatom.
# filter.tempPepFilterDesc=Temporary filter to store sent message unencrypted
# filter.term.pgpencrypted.label=OpenPGP Encrypted
# filter.encrypt.label=Encrypt to key (Enigmail)
# filter.keyRequired=You must select a recipient key.
# filter.keyNotFound=Could not find an encryption key for "%S".
# filter.warn.keyNotSecret=Warning - the filter action "Encrypt to key" replaces the recipients.\n\nIf you do not have the secret key for "%S" you will no longer be able to read the emails.
# strings in enigmailConvert.jsm
converter.decryptBody.failed=SporoÄila z zadevo "%S" ni bilo mogoÄe Å¡ifrirati.\nAli želite ponovno poskusiti z drugim geslom ali želite sporoÄilo preskoÄiti?
converter.decryptAtt.failed=Priponke "%1$S" v sporoÄilu z zadevo\n"%2$S"\nni bilo mogoÄe deÅ¡ifrirati.\nAli želite ponovno poskusiti z drugim geslom ali želite sporoÄilo preskoÄiti?\n
saveLogFile.title=Shrani zapisniško datoteko
# strings in gpg.jsm
unknownSigningAlg=Neznan algoritem podpisovanja (ID: %S)
unknownHashAlg=Neznano šifrirno razpršilo (ID: %S)
# strings in keyRing.jsm
keyring.photo=Fotografija
keyRing.pubKeyRevoked=KljuÄ %1$S (ID kljuÄa %2$S) je bil preklican.
keyRing.pubKeyExpired=KljuÄ %1$S (ID kljuÄa %2$S) je potekel.
keyRing.pubKeyNotForSigning=KljuÄa %1$S (ID kljuÄa %2$S) ni mogoÄe uporabiti za podpisovanje.
keyRing.pubKeyNotForEncryption=KljuÄa %1$S (ID kljuÄa %2$S) ni mogoÄe uporabiti za Å¡ifriranje.
keyRing.keyDisabled=KljuÄ %1$S (ID kljuÄa %2$S) je onemogoÄen; ni ga mogoÄe uporabiti.
keyRing.keyNotTrusted=KljuÄ %1$S (ID kljuÄa %2$S) ni dovolj zaupanja vreden. Za podpisovanje nastavite raven zaupanja na "skrajno".
keyRing.keyInvalid=KljuÄ %1$S (ID kljuÄa %2$S) je neveljaven (ni samopodpisan).
keyRing.signSubKeysRevoked=Vsi podkljuÄi za podpisovanje kljuÄa %1$S (ID kljuÄa %2$S) so bili preklicani.
keyRing.signSubKeysExpired=Vsi podkljuÄi za podpisovanje kljuÄa %1$S (ID kljuÄa %2$S) so potekli.
keyRing.signSubKeysUnusable=Vsi podkljuÄi za podpisovanje kljuÄa %1$S (ID kljuÄa %2$S) so potekli, bili preklicani ali so drugaÄe neuporabni.
keyRing.encSubKeysRevoked=Vsi podkljuÄi za Å¡ifriranje kljuÄa %1$S (ID kljuÄa %2$S) so bili preklicani.
keyRing.encSubKeysExpired=Vsi podkljuÄi za Å¡ifriranje kljuÄa %1$S (ID kljuÄa %2$S) so potekli.
keyRing.noSecretKey=Videti je, da nimate skrivnostnega kljuÄa za %1$S (ID kljuÄa %2$S) na svoji verigi; kljuÄa ne morete uporabiti za podpisovanje.
keyRing.encSubKeysUnusable=Vsi podkljuÄi za Å¡ifriranje kljuÄa %1$S (ID kljuÄa %2$S) so potekli, bili preklicani ali so drugaÄe neuporabni.
#strings in exportSettingsWizard.js
cannotWriteToFile=Ni mogoÄe shraniti v datoteko '%S'. Izberite drugo datoteko.
dataExportError=Med izvažanjem podatkov se je pojavila napaka.
enigmailSettings=Nastavitve Enigmail
defaultBackupFileName=Izvoz Enigmail
specifyExportFile=Navedite ime datoteke za izvoz
homedirParamNotSUpported=Dodatni parametri, ki doloÄajo poti, kot je --homedir in --keyring, niso podprti za izvažanje/obnavljanje nastavitev. Uporabite nadomestne naÄine, kot je nastavitev spremenljivke okolja GNUPGHOME.
#strings in expiry.jsm
expiry.keyExpiresSoon=VaÅ¡ kljuÄ %1$S bo potekle Äez %2$S dni.\n\nPriporoÄamo, da ustvarite nov par kljuÄev in ustrezne raÄune nastavite za njihovo uporabo.
# expiry.keysExpireSoon=The following of your keys will expire in less than %1$S days:\n%2$S We recommend that you create new keys and configure your accounts to use the new keys.
# expiry.keyMissingOwnerTrust=Your secret key %S has missing trust.\n\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.keysMissingOwnerTrust=The following of your secret keys have missing trust.\n%S.\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.OpenKeyManager=Open Enigmail Key Management
# expiry.OpenKeyProperties=Open Key Properties
#strings in pEpDecrypt.jsm
# pEpDecrypt.cannotDecrypt=This is an encrypted message. Unfortunately you don't have the secret key to decrypt the message.
#strings in gpgAgent.jsm
# gpghomedir.notexists=The directory '%S' containing your OpenPGP keys does not exist and cannot be created.
# gpghomedir.notwritable=The directory '%S' containing your OpenPGP keys is not writable.
# gpghomedir.notdirectory=The directory '%S' containing your OpenPGP keys is a file instead of a directory.
# gpghomedir.notusable=Please fix the directory permissions or change the location of your GnuPG "home" directory. GnuPG cannot work correctly otherwise.
#strings in pepTrustWords.js
# pepTrustWords.cannotVerifyOwnId=Cannot verify p≡p Trustwords for own account.
# pepTrustWords.cannotFindKey=Cannot find key for %S.
# pepTrustWords.cannotStoreChange=Could not change trust for %S.
# pepTrustWords.generalFailure=Cannot obtain trustwords for %S.
# pepTrustWords.partnerFingerprint=Fingerprint for %S:
#strings in mimeWkdHandler.jsm
# wkdMessage.body.req=Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.\n\nPlease click the confirmation button in the Enigmail header to complete the publishing of your public key.
# wkdMessage.body.process=This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.\n\nYou do not need to take any manual action at this point.
#strings in pepHandshake.js
# pepPrivacyStatus.RatingBrokenSuggestion=Either you or the sender should resend the message.
# pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=If you composed this message, your key is not available.
# pepPrivacyStatus.RatingMistrustSuggestion=Re-establish the connection with your communication partner and try to complete another handshake.
# pepPrivacyStatus.RatingReliableSuggestion=Complete a handshake with your communication partner by exchanging trustwords in person or over the phone. A handshake is needed only once per partner and will ensure secure and trusted communication.
# pepPrivacyStatus.RatingTrustedSuggestion=No action needed!
# pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Be aware this message may not be secure.
# pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=Please add the necessary information.
# pepPrivacyStatus.RatingUnderAttackSuggestion=Separately verify the content of this message with your communication partner.
# pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Make sure the privacy status for each communication partner listed is at least secure.
# pepPrivacyStatus.RatingUnencryptedSuggestion=Please ask your communication partner to use an encryption solution or install p≡p.
# pepPrivacyStatus.RatingUnreliableSuggestion=This message has no reliable encryption or no signature. Ask your communication partner to upgrade their encryption solution or install p≡p.
# pepPrivacyStatus.RatingBrokenExplanation=This message has broken encryption or formatting.
# pepPrivacyStatus.RatingHaveNoKeyExplanation=This message cannot be decrypted because the key is not available.
# pepPrivacyStatus.RatingMistrustExplanation=This message has a communication partner that has previously been marked as mistrusted.
# pepPrivacyStatus.RatingReliableExplanation=This message is secure but you still need to verify the identity of your communication partner.
# pepPrivacyStatus.RatingTrustedExplanation=This message is secure and trusted.
# pepPrivacyStatus.RatingUndefinedExplanation=This message does not contain enough information to determine if it is secure.
# pepPrivacyStatus.RatingUnderAttackExplanation=This message is not secure and has been tampered with.
# pepPrivacyStatus.RatingUnencryptedExplanation=This message is unsecure.
# pepPrivacyStatus.RatingUnencryptedForSomeExplanation=This message is unsecure for some communication partners.
# pepPrivacyStatus.RatingUnreliableExplanation=This message has unreliable protection.
# pepPrivacyStatus.RatingBrokenText=Broken
# pepPrivacyStatus.RatingHaveNoKeyText=Cannot Decrypt
# pepPrivacyStatus.RatingMistrustText=Mistrusted
# pepPrivacyStatus.RatingReliableText=Secure
# pepPrivacyStatus.RatingTrustedText=Secure & Trusted
# pepPrivacyStatus.RatingUndefinedText=Unknown
# pepPrivacyStatus.RatingUnderAttackText=Under Attack
# pepPrivacyStatus.RatingUnencryptedForSomeText=Unsecure for Some
# pepPrivacyStatus.RatingUnencryptedText=Unsecure
# pepPrivacyStatus.RatingUnreliableText=Unreliable Security
# handshakeDlg.button.initHandshake=Handshake...
# handshakeDlg.button.stopTrust=Stop Trusting
# handshakeDlg.button.reTrust=Stop Mistrusting
# handshakeDlg.label.outgoingMessage=Outgoing message
# handshakeDlg.label.incomingMessage=Incoming message
# handshakeDlg.error.noPeers=Cannot handshake without any correspondents.
# handshakeDlg.error.noProtection=Please enable protection in order to use the Handshake function.
# enigmail.acSetupPasswd.descEnterPasswd=Please enter the setup code that is displayed on the other device
# enigmail.acSetupPasswd.descCopyPasswd=Please enter the setup code below on your other device to proceed with the setup
#strings in autocrypt.jsm
# autocrypt.setupMsg.subject=Autocrypt Setup Message
# autocrypt.setupMsg.msgBody=To set up your new device for Autocrypt, please follow the instuctions that should be presented by your new device.
# autocrypt.setupMsg.fileTxt=This is the Autocrypt setup file used to transfer settings and keys between clients. You can decrypt it using the setup code presented on your old device, and then import the contained key into your keyring.
#strings in upgradeInfo.html
# upgradeInfo.doctitle=What's New in Enigmail v2.0?
# upgradeInfo.welcome1=Welcome to the new Enigmail version 2.0!
# upgradeInfo.welcome2=The release contains a lot of new and changed features. Please take a minute to find out what's new:
# upgradeInfo.encSubject.title=Encrypting the Message Subject
# upgradeInfo.encSubject.desc=We developed a new method that moves the email subject into the encrypted message, and replaces the visible subject with "Encrypted Message". Once such a message is decrypted, the original subject is replaced automatically. Hiding the subject is on by default; there is a preference to turn it off if you don't like it. (Note: this feature requires the message to be sent with PGP/MIME.)
# upgradeInfo.buttons.title=Changed behavior of Encrypt and Sign Buttons
# upgradeInfo.buttons.desc=The Encrypt and Sign buttons in the message composer window now work for both the OpenPGP and S/MIME protocols. If both algorithms are possible, then Enigmail will try to prefer the one for which all keys are available.
# upgradeInfo.autocrypt.title=Support for Autocrypt
# upgradeInfo.autocrypt.desc=Enigmail now supports Autocrypt, a new standard to distribute keys as part of sent messages. Enigmail automatically imports keys from Autocrypt-compliant messages, such that over time more and more emails can be encrypted.
# upgradeInfo.pEp.title=New p≡p Junior Mode (Pretty Easy Privacy)
# upgradeInfo.pEp.desc=Enigmail now contains a p≡p Junior Mode. You currently need to manually install p≡p for this purpose; this will change in a future release. The p≡p Junior Mode allows you to use OpenPGP encryption as transparently as possible; you don't need to care for key management and synchronization of keys between devices anymore.
# upgradeInfo.bottom.desc=Please visit our documentation for help on using Enigmail.
# pep.missingGnuPG=In order to use Enigmail/p≡p, GnuPG is required. As we could not find it, we suggest to download and install it for you.
#strings in enigmailAbout.html
# aboutEnigmail.tabName=About Enigmail
# aboutEnigmail.title=OpenPGP support provided by Enigmail
# aboutEnigmail.team=Enigmail is developed by the Enigmail Team:
# aboutEnigmail.projectLeader=Lead Developer:
# aboutEnigmail.usability=Usability:
# aboutEnigmail.documentation=Documentation:
# aboutEnigmail.testing=Testing:
# aboutEnigmail.userSupport=User Support:
# aboutEnigmail.localization=Localization: See the Enigmail Language Packs page
# aboutEnigmail.Credits=Credits:
# aboutEnigmail.origAuthor=Original author of the Enigmail extension
# aboutEnigmail.icons=Icons:
# aboutEnigmail.formerMembers=Former team members:
# aboutEnigmail.projectHosting=Project hosting:
# aboutEnigmail.licenseSupportTitle=License & Support
# aboutEnigmail.license=Enigmail OpenPGP is open source and licensed under the %S
# aboutEnigmail.support=Support and download is available from www.enigmail.net.
enigmail-2.0.8/lang/sl/help/ 0000775 0000000 0000000 00000000000 13343027545 0015603 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/sl/help/compose.html 0000664 0000000 0000000 00000007437 13343027545 0020151 0 ustar 00root root 0000000 0000000
PomoÄ za Enigmail: Sestavljanje sporoÄil
PomoÄ za Enigmail
Uporaba Enigmaila pri sestavljanju sporoÄil
Meni Enigmail v oknu Pošta/Sestavi
PodpiÅ¡i sporoÄilo: omogoÄi/onemogoÄi poÅ¡iljanje podpisane poÅ¡te. Uporabnik je obveÅ¡Äen,
Äe podpisovanje ne uspe.
Å ifriraj sporoÄilo: omogoÄi/onemogoÄi Å¡ifriranje vsem prejemnikom pred
poÅ¡iljanjem. Uporabnik je obveÅ¡Äen, Äe Å¡ifriranje ne uspe.
Č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.
Za to sporoÄilo uporabi PGP/MIME: omogoÄi/onemogoÄi uporabo
PGP/MIME
za to sporoÄilo.
Č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.
Privzete možnosti sestavljanja: podmeni.
Možnosti podpisovanja/Å¡ifriranja ...: bližnjica prek Nastavitve raÄuna ->
Možnosti OpenPGP.
Možnosti pošiljanja ...: bližnjica prek Nastavitve ->
zavihek Pošiljanje.
Key selection options...: bližnjica prek Nastavitve ->
zavihek Izbira kljuÄa.
Možnosti PGP/MIME ...: bližnjica prek Nastavitve ->
zavihek PGP/MIME.
Razveljavi Å¡ifriranje: Äe pride do napake pri poÅ¡iljanju sporoÄila,
npr. Äe strežnik POP ne sprejme zahteve, Enigmail o tem ne bo obveÅ¡Äen
in Å¡ifrirano sporoÄilo bo Å¡e naprej prikazano v oknu
Sestavljanje. S to menijsko izbiro boste razveljavili šifriranje/podpisovanje,
s Äimer boste v oknu Sestavljanje besedilov povrnili v izvoren zapis. Kot zaÄasno reÅ¡itev lahko to možnost uporabite tudi za deÅ¡ifriranje citiranega
besedila, ko odgovarjate na Å¡ifrirana sporoÄila. Enigmail bi moral samodejno
deÅ¡ifrirati citirano sporoÄilo, vendar Äe to ne uspe, lahko uporabite to menijsko
izbiro, da ga v to prisilite.
Vstavi javni kljuÄ: vstavi blok javnega kljuÄa z ASCII oklepnikom na
trenutni položaj kazalke v oknu Sestavljanje. Vnesti boste morali e-poštne naslove
kljuÄa(ev), ki naj bodo vstavljeni. Na ta naÄin vstavljeni kljuÄi
bodo samodejno prepoznani na sprejemnem delu Enigmaila. Po vstavljanju
kljuÄa lahko Å¡e vedno izbirate med podpisovanjem/Å¡ifriranjem sporoÄila.
Prav tako v sporoÄilo ne smete vstaviti veÄ kot enega bloka kljuÄa; le
navedite veÄ e-poÅ¡tnih naslovov, loÄenih z vejicami ali presledki, ko
boste po tem povprašani.
Uporaba Urejevalnika pravil Enigmail: Uredi pravilo OpenPGP
V 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.
Nastavi pravila OpenPGP za: vsebuje e-poštne
naslove za prejemnike (brez imen, torej le naslove, kot je
nekdo@neka.domena). DoloÄite lahko veÄ e-poÅ¡tnih sporoÄil, loÄenih s presledkom.
Tukaj neveden naslov lahko sestavlja le
del domene, tako da se bo ujemalo vsako sporoÄilo na kateri koli naslov iz te domene,
npr. @neka.domena omogoÄa ujemanje francelj@neka.domena,
nekdodrug@neka.domena, vsakdo@neka.domena itn.
Uporabi pravilo, Äe prejemnik ...:
S tem spremenite ujemanje e-naslovov.
ÄŒe je vnesenih veÄ naslovov, bo nastavitev veljala za vse.
Spodnji primeri temeljijo na body@email.domain,
vnesenem v gornjem polju Pravila OpenPGP.
je enako: s to nastavitvijo se bo pravilo sprožilo le na
e-sporoÄilih za body@email.domain (natanÄno ujemanje, ne razlikuje velikih/malih Ärk).
vsebuje: s to nastavitvijo se ujema vsak e-naslov, ki vsebuje
tak niz,
npr. anybody@email.domain ali body@email.domain.net
se zaÄne z: s to nastavitvijo se ujemajo vsi e-naslovi, ki se zaÄenjajo
z ujemajoÄim nizom, npr. body@email.domain.net,
body@email.domain-name.com.
se konÄa z: s to nastavitvijo se ujemajo vsi e-naslovi, ki se konÄujejo
z ujemajoÄim nizom, npr. anybody@email.domain,
somebody@email.domain.
Nadaljuj z naslednjim pravilom za ujemajoÄi naslov
VkljuÄitev te funkcije vam omogoÄa doloÄanje pravila, ne da bi morali
navesti ID kljuÄa v polje Uporabi naslednje kljuÄe OpenPGP:,
tako da je e-naslov uporabljen za preverjanje kljuÄa ob Äasu
pošiljanja. Prav tako bodo procesirana tudi nadaljna pravila za iste naslove.
Ne preverjaj nadaljnjih pravil za ujemajoÄi naslov
Z vkljuÄitvijo te funkcije ustavite obdelavo vseh drugih pravil za
ujemajoÄ(i) naslov(e), Äe je temu pravilu ustreženo; t.j. obdelava pravil
nadaljuje z naslednjim prejemnikom.
Uporabi naslednje kljuÄe OpenPGP:
Uporabite gumb Izberi kljuÄ(e) ... za izbor kljuÄev prejemnika,
ki naj bodo uporabljeni za šifriranje. Tako kot pri gornjem dejanju ne bodo
obdelana nobena druga pravila za ujemajoÄe naslove.
Privzeto za podpisovanje: vkljuÄite ali izkljuÄite
podpisovanje sporoÄil. S tem uporabite ali prekliÄete, kar ste doloÄili v oknu
sestavljanja sporoÄil. Vrednosti so:
nikoli: onemogoÄite podpisovanje, Äeprav je morda omogoÄeno v oknu
sestavljanja sporoÄila (preglasi druge vrednosti);
da, Äe je izbrano v sestavljanju sporoÄila: podpisovanje
poteka v skladu z izbranim v oknu sestavljanja sporoÄila;
vedno: omogoÄite podpisovanje, Äetudi ni omogoÄeno v oknu
sestavljanja sporoÄila;
Te nastavitve podpisovanja se uporabljajo za
vsa pravila, ki se ujemajo. ÄŒe eno od pravil prepoveduje podpisovanje, sporoÄilo
ne bo podpisano, ne glede na druga pravila, ki morda doloÄajo vedno.
Å ifriranje: vkljuÄite ali
izkljuÄite Å¡ifriranje sporoÄil. Dovoljene nastavitve in njihov pomen so
enaki kot za podpisovanje sporoÄil.
PGP/MIME: vkljuÄite ali
izkljuÄite uporabo kodiranja sporoÄil PGP/MIME (RFC 3156).
ÄŒe je PGP/MIME izkljuÄen, so
sporoÄila kodirana z uporabo "medvrstiÄnega PGP". Dovoljene vrednosti in njihov
pomen so enaki kot za podpisovanje sporoÄil.
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.
Gumb Dešifriraj v glavnem oknu Pošta
Ta gumb lahko uporabite za veÄ dejanj: deÅ¡ifriranje, preverjanje ali uvoz
javnih kljuÄev. ObiÄajno se deÅ¡ifriranje/preverjanje izvede samodejno,
Äeprav lahko to izkljuÄite v nastavitvah. ÄŒe pa to ne uspe,
se ponavadi pokaže kratko sporoÄilo o napaki v vrstici stanja Enigmaila. ÄŒe
kliknete na gumb DeÅ¡ifriraj, boste videli bolj natanÄno sporoÄilo
o napaki, vkljuÄno z izhodom ukaza GnuPG.
Ikoni Pisalo in KljuÄ v prikazu glave sporoÄila
Ikoni Pisalo in KljuÄ v glavi sporoÄila nakazujeta,
da je bilo sporoÄilo, ki ga prebirate podpisano in/ali Å¡ifrirano in da ali je podpis
dober, t.j. da sporoÄilo od trenutka podpisa ni bilo spremenjeno. ÄŒe je bilo sporoÄilo
spremenjeno, se ikona Peresa spremeni v Polomlneno pero, kar
nakazuje nepravilen podpis. Z desnim klikom na ikono Pero ali KljuÄ se
pojavi meni z naslednjimi možnostmi:
Podatki o varnosti OpenPGP: omogoÄa ogled izhodnega stanja iz
GnuPG za to sporoÄilo.
Kopiraj varnostne podatke OpenPGP: skopira izhodno stanje iz GnuPG na
odložiÅ¡Äe; za lepljenje v sporoÄilo-odgovor itn.
Pokaži fotografski ID OpenPGP: omogoÄa ogled Fotografskega ID
osebe, ki je poslala sporoÄilo, Äe imajo fotografijo vdelano v svoj javni kljuÄ.
(Ta možnost je na voljo le, Äe fotografski ID obstaja v njihovem kljuÄu.)
Varnostni podatki S/MIME: omogoÄa ogled varnostnih podatkov S/MIME
za sporoÄilo.
ÄŒ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.
Odpiranje Å¡ifriranih priponk / uvažanje pripetih kljuÄev OpenPGP
Priponke s konÄnicami *.pgp, *.asc in *.gpg so prepoznane kot priponke, ki jih
Enigmail lahko posebej obdela. Z desnim klikom na takšno priponko
se v pojavnem meniju pojavita dve posebni izbiri: Dešifriraj in odpri
in DeÅ¡ifriraj in shrani. Ti izbiri uporabite, Äe želite, da Enigmail
priponko dešifrira, preden jo odprete ali shranite. Če je priponka
prepoznana kot datoteka kljuÄa OpenPGP, vam bo ponujen uvoz kljuÄev
v vaÅ¡o shrambo kljuÄev.
V 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:
Email: e-sporoÄilo(a) from
the To:, Cc: and Bcc: fields to match. Ujemanje deluje na podnizih (Podrobnosti najdete
v pogovornem oknu Urejanja pravil)
KljuÄ(i) OpenPGP: seznam ID kljuÄev OpenPGP,
ki naj se uporabi(jo) za naslovnika
Podpisovanje: omogoÄi ali onemogoÄi
podpisovanje sporoÄil. To ali uporabi ali pa prezre nastavitve
v oknu sestavljanja sporoÄila. Možne vrednosti so:
nikoli: onemogoÄi podpisovanje, Äeprav je omogoÄeno v oknu sestavljanja
sporoÄila (preglasi druge vrednosti)
dovoli: prepusti nastavitev podpisovanja doloÄitvi v oknu sestavljanja
sporoÄila
vedno: omogoÄi podpisovanje, Äetudi ni omogoÄeno v oknu
sestavljanja sporoÄila
Te nastavitve podpisovanja se upoštevajo pri
vseh ujemajoÄih pravilih. ÄŒe eno od pravil onemogoÄi podpisovanje, sporoÄilo
ne bo podpisoano, ne glede na doloÄila dugega pravila, ki doloÄa podpisovanje Vedno.
Å ifriraj: omogoÄi ali
onemogoÄi Å¡ifriranje sporoÄila. Dovoljene nastavitve in njihov pomen so
enaki kot pri podpisovanju sporoÄila.
PGP/MIME: omogoÄi ali
onemogoÄi uporabo Å¡ifriranja sporoÄil PGP/MIME (RFC 3156).
ÄŒe je PGP/MIME onemogoÄen, se
sporoÄila Å¡ifrirajo z uporabo "inline PGP". Dovoljene vrednosti in njihov
pomen so enaki kot pri podpisovanju sporoÄil.
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.
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit Per-Recipient Rule
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.
Set Enigmail Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the Enigmail Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
Decrypt button in main Mail window
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Opening encrypted attachments / importing attached OpenPGP keys
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
enigmail-2.0.8/lang/sq/help/initError.html 0000664 0000000 0000000 00000004552 13343027545 0020461 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing Enigmail
Enigmail Help
How to Resolve Problems with Initializing Enigmail
There 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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
Enigmail Security info: allows you to view the output status from GnuPG for the message.
Copy Enigmail Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of Enigmail to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
Aktivera/inaktivera skicka signerad e-post. Användaren meddelas, om signering misslyckas.
Kryptera meddelande
Aktivera/inaktivera kryptering till alla mottagare innan du skickar. Användaren meddelas, om kryptering misslyckas.
Använd PGP/MIME för detta meddelande
Aktivera/inaktivera användning av PGP/MIME för detta meddelande.
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.
Standard kompositionsalternativ
Signering/Kryptering alternativ...: genväg till Kontoinställningar -> OpenPGP alternativ.
Skicka alternativ...: genväg till Inställningar -> skicka fliken.
Nyckelval alternativ...: genväg till Inställningar -> Nyckelval fliken.
PGP/MIME alternativ...: genväg till Inställningar -> PGP/MIME fliken.
Ã…ngra kryptering
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.
Bifoga publik nyckel
Infoga ASCII-armerade publika nyckelblock vid nuvarande markörposition i skrivfönstret. Du kommer att bli tillfrågad om e-postadresser till nyckeln som ska infogas. Nycklar som infogats på detta sätt kommer automatiskt att redovisas vid den mottagande änden av Enigmail. Efter nyckelinsättning, kan du fortfarande välja att signera/kryptera mail efter behov. Också, infoga inte mer än ett nyckelblock i ett meddelande; ange flera e-postadresser, avgränsade med kommatecken eller mellanslag, när det efterfrågas.
Rensa sparad lösenfras
Rensar cachade lösenfraser. Användbart om du har flera lösenfraser.
Hjälp
Visar hjälpinformation från webbplatsen (denna sida).
Använda Enigmail's regelredigerare: Redigera OpenPGP regel
I 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.
Ange Enigmail-regler för
Innehåller e-postadresserna till mottagarna (utan namn, det vill säga endast en adress som somebody@email.domain). Du kan ange flera e-postadresser, separerade med mellanslag. Adressen som anges här kan endast bestå av domändelen så att e-post till en adress på den domänen kommer att matchas, t.ex. @email.domain tillåter matchning till body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Tillämpa regel om mottagare ...
Detta ändrar matchning av e-postadresser. Om flera adresser anges kommer inställningen gälla för alla. Exemplen nedan är baserade på body@email.domain som angetts i OpenPGP reglerfältet ovan.
Är exakt: med denna inställning, kommer regeln endast trigga på e-post till body@email.domain (exakt, fall okänsliga matchning).
Innehåller: med denna inställning, kommer en e-postadress som innehåller strängen matchas, t.ex. anybody@email.domain eller body@email.domain.net
Startar med: med denna inställning, kommer en e-postadress som börjar med strängen matchas, t.ex. body@email.domain.net, body@email.domain-name.com.
Slutar med: med denna inställning, kommer en e-postadress som slutar med strängen matchas, t.ex. anybody@email.domain, somebody@email.domain.
Fortsätt med nästa regel för matchande adress
Aktivera den här funktionen kan du definiera en regel, men inte ange en nyckel-ID i Använd följande OpenPGP nycklar: fältet, så att e-postadressen används för att kontrollera en nyckel när du skickar. Dessutom kommer ytterligare regler för samma adress behandlas också.
Kontrollera inte ytterligare regler för matchande adress
Aktivera den här funktionen stoppar bearbetning av andra regler för matchande adress, om denna regel matchas; dvs regelbearbetningen fortsätter med nästa mottagare.
Använd följande OpenPGP nycklar:
Använd Välj nyckel... knappen för att välja mottagarens nycklar som ska användas för kryptering. Som i åtgärden ovan, inga ytterligare regler för matchande adress behandlas.
Standardvärden för...
Aktivera eller inaktivera signering för meddelanden. Detta använder eller åsidosätter vad du har specificerat i meddelandefönstret. Värdena är:
Aldrig: avaktivera signering, även om den var aktiverad i meddelandefönstret(upphäver de andra värdena)
Ja, om det valts i meddelandekompositionen: lämna signering som anges i meddelandefönstret
Alltid: aktivera signering, även om det var inte aktiverad i meddelandefönstret
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.
Kryptering
Aktivera eller inaktivera meddelandekryptering. Tillåtna inställningar och deras betydelse är de samma som för meddelandesignering.
PGP/MIME
Aktivera eller inaktivera användning av PGP/MIME (RFC 3156) meddelandekodning. Om PGP/MIME är inaktiverad kodas meddelandena med "inline PGP". Tillåtna värden och deras betydelse är de samma som för meddelandesignering.
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.
enigmail-2.0.8/lang/sv-SE/help/initError.html 0000664 0000000 0000000 00000004600 13343027545 0020765 0 ustar 00root root 0000000 0000000
Enigmail Hjälp: Hur man ska lösa problem med initiera OpenPGP
Enigmail Hjälp
Hur man ska lösa problem med Initiera OpenPGP
Det finns flera skäl till varför initiering av OpenPGP inte lyckas. De vanligaste beskrivs nedan;
Mer information finns på Enigmail supportsida.
GnuPG kunde inte hittas
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)
Enigmime gick inte att initiera
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.
Denna knapp kan användas för flera ändamål: dekryptera, verifiera, eller importera allmänna nycklar. Normalt dekryptering/verifiering sker automatiskt, även om detta kan inaktiveras genom en inställning. Om detta misslyckas, kommer vanligtvis en kort felmeddelande i Enigmail's statusrad. Om du klickar på Dekryptera knappen, kommer du att kunna se ett mer detaljerat felmeddelande, inklusive utdata från kommandot GnuPG.
Penn- och nyckelikoner som visas i meddelandehuvudet
Penn- och Nyckelikoner i meddelandehuvudet visar om meddelandet som du läser signerats och/eller krypterats och om signaturen är bra, det vill säga meddelandet har inte förändrats sedan det signerades. Om meddelandet har ändrats, Pennikonen ändras till en bruten penna för att indikera att signaturen är dålig. Högerklicka på antingen penn- eller nyckelikonen visar en meny med följande alternativ:
OpenPGP säkerhetsinfo: låter dig se utdata från GnuPG för meddelandet.
Kopiera OpenPGP säkerhetsinfo: kopierar utdata från GnuPG till urklipp; för att klistra in ett svarsmeddelande, etc.
Visa OpenPGP foto-ID: låter dig se foto-ID för den person som skickade meddelandet, om de har ett foto inbäddad i sin publika nyckel. (Detta alternativ kommer endast att aktiveras om ett foto-ID finns i deras nyckel.)
S/MIME säkerhetsinfo: låter dig se på S/MIME säkerhetsinfo för meddelandet.
Om 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.
Bifogade filer som slutar på *.Pgp, *.Asc och *.Gpg känns igen som bilagor som kan hanteras speciellt av Enigmail. Genom att högerklicka på en sådan bilaga möjliggörs två speciella menyalternativ i snabbmenyn: Dekryptera och öppna och Dekryptera och spara. Använd dessa två menyalternativ om du vill att Enigmail ska dekryptera en bifogad fil innan du öppnar eller sparar den. Om en bilaga känns igen som en OpenPGP nyckelfil, erbjuds du att importera nycklarna till din nyckelring.
I 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:
E-post
E-post att matcha i fälten Till:, Kopia: och Hemlig kopia:. Matchningen fungerar på delsträngar (Ytterligare information finns i fönstret redigera regler.)
OpenPGP nyckel
en lista med OpenPGP nyckel-ID för att använda för mottagaren
Signera
aktivera eller inaktivera signering av meddelanden. Detta använder eller åsidosätter vad du har specificerat i meddelandefönstret. Värdena är:
Aldrig: inaktivera signering, även om den var aktiverad i meddelandefönstret (upphäver de andra värdena)
Möjlig: lämna signering som angetts i meddelandefönstret
Alltid: aktivera signering, även om den inte var aktiverad i meddelandefönstret
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.
Kryptera
aktivera eller inaktivera kryptering av meddelande. Tillåtna inställningar och deras betydelse är de samma som för signering av meddelande.
PGP/MIME
aktivera eller inaktivera användning av PGP/MIME (RFC 3156) meddelandekodning. Om PGP/MIME är inaktiverad kodas meddelandena med "inline PGP". Tillåtna värden och deras betydelse är de samma som för signering av meddelande.
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
Fastställa inställningar för att skicka krypterat
I inställningar för att skicka kan du välja en allmän modell och inställningar för kryptering.
Smidig kryptering
Med dessa inställningar, krypteras e-post utan bekräftelse när det är möjligt.
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.
Manuell kryptering
Med det här alternativet kan du ange olika inställningar för kryptering enligt dina behov. Du kan ange
om svar på krypterade/signerade e-postmeddelanden bör automatisk också vara krypterad/signerad-
om du vill använda förtroende modellen av OpenPGP för att acceptera nycklar (detta innebär att man använder en nyckel som du antingen måste signera nyckel eller har tillräckligt många andra människor du litar på som har signerat nyckeln).
om du vill skicka e-post krypterat om alla nycklar accepteras.
om och när du vill slutligen bekräfta sändning av ett mail.
Om det är viktigt för dig att innehåll som du skickar krypteras inte kan läsas av andra personer eller organisationer, bör du använda de manuella inställningarna. Välj åtminstone alternativet att ta emot nycklarna om du eller andra människor signerat dem. Även denna modell minskar risken för att använda förfalskade nycklar, det kräver att du aktivt signerar nycklar och förklarar ägare förtroende med hjälp av fönstret nyckelhanteraren.
enigmail-2.0.8/lang/tr/ 0000775 0000000 0000000 00000000000 13343027545 0014662 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/tr/am-enigprefs.properties 0000664 0000000 0000000 00000000124 13343027545 0021352 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=OpenPGP Güvenliği
enigmail-2.0.8/lang/tr/enigmail.dtd 0000664 0000000 0000000 00000136533 13343027545 0017157 0 ustar 00root root 0000000 0000000
' kullan">
' karakterlerini kullan. Alıcıların eski Hushmail anahtarları varsa etkisiz kıl.">
NOT: Anahtar üretiminin bitmesi biraz zaman alabilir. Anahtar üretimi sırasında uygulamayı kapatmayın. Aktif olarak internette gezinmek ya da diskle ilgili işler yapmak rasgele üretimi kolaylaştıracağından işlemin hızını artıracaktır. Anahtar üretimi bittiğinde uyarılacaksınız.">
' yanlış">
NOT: Anahtar üretimi biraz uzun sürebilir. Anahtar üretimi sırasında uygulamayı kapatmayın. Anahtar üretimi bittiğinde uyarılacaksınız.">
Not: Enigmail ayarlarda etkin olup olmamasına bakmadan herzaman her kimlikteki ya da hesaptaki imzaları doğrulayacaktır.">
Enigmail kullandığınız için teşekkürler.">
enigmail-2.0.8/lang/tr/enigmail.properties 0000664 0000000 0000000 00000151556 13343027545 0020602 0 ustar 00root root 0000000 0000000 Enigmail=Enigmail
#####################################################################
# Strings used within enigmailCommon.js and enigmailCommon.jsm
#####################################################################
enigAlert=Enigmail Uyarı
enigConfirm=Enigmail DoÄŸrula
# enigInfo=Enigmail Information
enigError=Enigmail Hata
enigPrompt=Enigmail Bilgi İstemi
dlgYes=Evet
dlgNo=Hayır
dlgKeepSetting=Cevabımı hatırla ve tekrar sorma
dlgNoPrompt=Bu diyaloğu tekrar gösterme
dlg.button.delete=&Sil
dlg.button.cancel=&Vazgeç
dlg.button.close=&Kapat
dlg.button.continue=&Devam
dlg.button.skip=&Atla
# dlg.button.overwrite=&Overwrite
dlg.button.view=&Göster
# dlg.button.retry=&Retry
# dlg.button.ignore=&Ignore
# dlg.button.install=&Install
# dlg.button.ok=&OK
repeatPrefix=\n\nBu uyarı tekrar edecek %S
repeatSuffixSingular=kere daha.
repeatSuffixPlural=kere daha.
noRepeat=\n\nBu uyarı Enigmail'i yükseltene kadar tekrar etmeyecek.
pgpNotSupported=Enigmail'yi PGP 6.x sürümüyle kullanıyor görünüyorsunuz\n\nPGP 6.x Enigmail'in düzgün çalışmasını bazı sebeplerden engellediğinden Enigmail 6.x desteklemiyor; lütfen GnuPG (GPG)'ye geçiş yapın.\n\nGnuPG'ye geçiş konusunda yardıma ihtiyacınız olursa, Enigmail ana sayfasından Yardım kısmına göz atın.
# initErr.howToFixIt=In order to use Enigmail, GnuPG is required. If you did not install GnuPG yet, the easiest way to do this is using the "Setup Wizard" button below.
# initErr.setupWizard.button=&Setup Wizard
passphraseCleared=Parola temizlendi.
# cannotClearPassphrase=You are using a non-standard tool (such as gnome-keyring) for passphrase handling. Clearing the passphrase is therefore not possible from within Enigmail.
noPhotoAvailable=Hiçbir fotoğraf uygun değil
debugLog.title=Enigmail Debug Log
# error.photoPathNotReadable=Photo path '%S' is not readable
# generalError=Error: %S
# Strings in configure.jsm
# enigmailCommon.versionSignificantlyChanged=This new version of Enigmail has significant changes in the handling of preferences and options. We tried to transfer the old settings to this new version. However, we cannot cover all cases automatically. Please double check the resulting new preferences and options.
# enigmailCommon.checkPreferences=Check Preferences ...
# preferences.defaultToPgpMime=We have changed the default message encoding in Enigmail from Inline-PGP to PGP/MIME. We recommend you keep this as default.\n\nIf you still wish to use Inline-PGP by default, you can do so in the Account Settings under OpenPGP Security.
#####################################################################
# Strings in enigmailAbout.js
#####################################################################
usingVersion=Enigmail %S sürümü kullanıyorsunuz
# enigmailPepVersion=Enigmail/p≡p version %S
usingAgent=Şifreleme ve deşifreleme için %S çalışıtırılabiliri %S kullanılıyor
agentError=HATA: Enigmime servisine ulaşılamadı!
#####################################################################
# Strings in enigmailKeygen.js
#####################################################################
accessError=Enigmail servisine eriÅŸimde hata
onlyGPG=Anahtar üretimi sadece GnuPG ile çalışır (PGP ile değil)!
keygenComplete=Anahtar üretimi tamamlandı! İmzalama için <%S> kimliği kullanılacak
revokeCertRecommended=Anahtarınız için bir iptal sertifikası oluşturmanızı öneririz. Bu sertifika örneğin özel anahtarınız kaybolur ya da çalınırsa, anahtarınızın iptali için gereklidir. Böyle bir iptal sertifikası oluşturmak istiyor musunuz ?
keyMan.button.generateCert=Sertifika &OluÅŸtur
genCompleteNoSign=Anahtar üretimi tamamlandı!
genGoing=Anahtar üretimi işlem halinde!
passNoMatch=Parolalar uyuşmuyor, lütfen tekrar girin
passCheckBox=Anahtar için bir parola girmeyecekseniz lütfen kutuyu işaretleyin
passUserName=Lütfen bu kimlik için bir kullanıcı adı belirleyin
# keygen.missingUserName=There is no name specified for the selected account/identity. Please enter a value in the field "Your name" in the account settings.
# keygen.passCharProblem=You are using special characters in your passphrase. Unfortunately, this can cause troubles for other applications. We recommend you choose a passphrase consisting only of any of these characters:\na-z A-Z 0-9 /.;:-,!?(){}[]%*
# passSpaceProblem=Due to technical reasons, your passphrase may not start or end with a space character.
changePassFailed=Parola değişimi başarısız.
keyConfirm='%S' için genel ve özel anahtarlar oluşturulsun mu?
keyMan.button.generateKey=Anahtar &Üret
keyAbort=Anahtar üretiminden çık?
keyMan.button.generateKeyAbort=Anahtar Üretimini &İptal Et
keyMan.button.generateKeyContinue=Anahtar Üretimine &Devam Et
expiryTooLong=100 yıldan uzun sürede kaybolan bir anahtar oluşturamazsınız.
expiryTooLongShorter=90 yıldan uzun sürede kaybolan bir anahtar oluşturamazsınız.
expiryTooShort=Anahtarınız en az bir günlük olmalı.
keyGenFailed=Anahtar üretimi başarısız. Daha fazla bilgi için Enigmail konsoluna göz atın ( Enigmail Menüsü > Hata ayıklama )
# setKeyExpirationDateFailed=The expiration date could not be changed
# Strings in enigmailMessengerOverlay.js
securityInfo=Enigmail Güvenlik Bilgisi\n\n
enigHeader=Enigmail:
enigContentNote=Enigmail: *Bu mesajın ekleri imzalanmadı ve şifrelenmedi*\n\n
possiblyPgpMime=Muhtemelen PGP/MIME mesajı şifreledi ya da imzaladı; doğrulamak için Deşifre düğmesine tıklayın
saveAttachmentHeader=Enigmail: DeÅŸifre edilmiÅŸ eki kaydet
noTempDir=Yazacak geçici bir dizin bulunamadı\nLütfen TEMP çevre değişkenini belirleyin
attachmentPgpKey=Açtığınız '%S' eki bir OpenPGP anahtar dosyasına benziyor.\n\nİçindeki anahtarları almak için Evet'e, dosya içeriğini ayrı bir pencerede görmek için Hayır'a tıklayın
beginPgpPart=********* *SIFRELI veya IMZALI KISIM BASLANGICI* *********
endPgpPart=********** *SIFRELI veya IMZALI KISIM BITISI* **********
notePartEncrypted=Enigmail: *Mesajın bazı kısımları şifrelenmedi veya imzalanmadı*
noteCutMessage=Enigmail: *Birden fazla mesaj bloÄŸu bulundu -- deÅŸifre/doÄŸrulama iÅŸlemi durduruldu*
decryptOkNoSig=Uyarı\n\nDeşifre işlemi başarılıydı, ama imza düzgün doğrulanamadı
msgOvl.button.contAnyway=Yine de &devam et
# signature.verifiedOK=The signature for attachment %S was successfully verified
# signature.verifyFailed=The signature for attachment %S could not be verified
# attachment.noMatchToSignature=Could not match attachment '%S' to a signature file
# attachment.noMatchFromSignature=Could not match signature file '%S' to an attachment
# fixBrokenExchangeMsg.failed=Did not succeed to repair message.
# enigmail.msgViewColumn.label=Enigmail
# enigmailPep.msgViewColumn.label=Enigmail/p≡p
# wksNoIdentity=This key is not linked to any of your email accounts. Please add an account for at least one of the following email addresse(s):\n\n%S
# wksConfirmSuccess=Confirmation email sent.
# wksConfirmFailure=Sending the confirmation email failed.
# autocrypt.importSetupKey.accountPreconfigured=Your account is already correctly configured for Autocrypt.\n\nDo you really want to overwrite your settings with this setup message?
# autocrypt.importSetupKey.selfCreated=This message was created by your currently running instance of Enigmail.\n\nPlease switch to the email client to which you want to transfer the settings, and click on the message on that email client to import the settings.
# autocrypt.importSetupKey.invalidMessage=Error - could not read setup message. The message seems to be corrupted. Please try to create a new setup message on your "other" device.
# autocrypt.importSetupKey.invalidKey=Error - the key could not be imported. The key is either not supported by your version of GnuPG, or it got corrupted.
# autocrypt.importSetupKey.wrongPasswd=The password you entered is wrong. Do you want to retry?
# autocrypt.importSetupKey.success=The Autocrypt setup message was processed successfully. Autocrypt is now available for your account '%S'.
#####################################################################
# Strings in enigmailMsgComposeOverlay.js
#####################################################################
keysToExport=Eklenecek OpenPGP anahtarlarını seçin
keysToUse=%S için kullanılacak OpenPGP Anahtarı(ları)nı seçin
pubKey=%S için Genel Anahtar\n
windowLocked=Yazım penceresi kilitli; gönderme iptal edildi
sendUnencrypted=Enigmail başlatılamadı.\nŞifrelenmemiş gönder?
composeSpecifyEmail=Lütfen gönderilen mesajları imzalamada kullanılacak birincil eposta adresinizi belirtin.\nBoş bırakırsanız mesajdan alınan KİMDEN adresi kullanılacak.
sendingHiddenRcpt=Bu mesajın BCC (kör karbon kopya) alıcıları var. Mesaj şifrelenmişse, BCC alıcıları saklamak mümkün olmasına rağmen bazı ürünlerin kullanıcıları (ör: PGP Corp.) mesajı deşifre edemeyecektir. Bu durum yüzünden şifrelenmiş mesajlar içeren ve BCC kullanılan postaları önermiyoruz.
sendWithHiddenBcc=BCC alıcıları gizle
sendWithShownBcc=Normal ÅŸifrele
sendingNews=Şifrelenmiş gönderim iptal edildi.\n\n Bu mesaj şifrelenemez çünkü haber grubuna dahil alıcıları var. Lütfen şifrelemeden tekrar gönderin.
sendToNewsWarning=Uyarı: şifrelenmiş bir postayı haber grubuna yollamak üzeresiniz.\n\nBu durum pek mantıklı değil çünkü üyelerin hepsi mesajı deşifre edemediği sürece bir anlamı olmayacak, mesajın tüm grup üyelerinin anahtarları ile şifrelenmesi gerekiyor. Lütfen bu mesajı ne yaptığınızı bildiğinizden eminseniz yollayın.\n\nDevam?
hasHTML=HTML posta uyarısı:\nBu mesaj imzalama/şifreleme işlemini engelleyebilecek HTML içerebilir. Bu durumu önlemek için bir dahaki sefere mesaj yazma/cevaplama düğmelerine SHIFT tuşuna basılı tutarak tıklayın ki imzalı gönderilebilsin.\nPostaları öntanımlı olarak imzalıyorsanız, bu posta hesabında kalıcı olarak HTML'yi kapatmak için 'HTML Mesajları Gönder' seçeneğini kapatmalısınız.
strippingHTML=Bu mesaj imzalama/şifreleme işlemleri için düz yazıya dönüştürüldüğünde kaybolacak HTML formatına sahip. Devam etmek istiyor musunuz ?
msgCompose.button.sendAnyway=Mesajı &Yine de Gönder
attachWarning=Bu mesajın ekleri yerelde değil. Şifrelenemezler. Ekleri şifrelemek için, önce bilgisayarınıza kaydedin ve sonra ekleyin. Yine de devam etmek istiyor musunuz?
quotedPrintableWarn=Mesajları gönderirken 'quoted-printable' kullanılmasını istediniz. Bu mesajınızın yanlış deşifre edilmesine veya doğrulanmasına yol açabilir.\n 'quoted-printable' mesajlar göndermeyi kapatmak istiyor musunuz ?
minimalLineWrapping=Satır bitimi %S karakter yapmışsınız. Düzgün şifreleme veya imzalama için bu değerin en az 68 olması gerek.\n 68'e değiştirmek istiyor musunuz?
warning=Uyarı
signIconClicked=İmzalamayı elle değiştirdiniz. Yani, bu mesajı yazarken, imzayı kapatmak artık şifrelemeyi kapatmaya bağımlı değil.
# errorOwnKeyUnusable=The key ID '%S' configured for the current identity does not yield a usable OpenPGP key.\n\nPlease ensure that you have a valid, not expired OpenPGP key and that your account settings point to that key.\nIf your key is not expired, then check if you did set Owner trust to full or ultimate.
# msgCompose.cannotSaveDraft=Error while saving draft
# msgCompose.partiallyEncrypted.short=Beware of leaking sensitive information - partially encrypted email.
# msgCompose.partiallyEncrypted.mimeMsg=The message you are replying to contained both unencrypted and encrypted parts. Some encrypted message parts are invisible to you.\n\nIf the sender was not able to decrypt the hidden message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nWe recommend that you don't reply to the message, but create a new message containing your answer.
# msgCompose.partiallyEncrypted.inlinePGP=The message you are replying to contained both unencrypted and encrypted parts. If the sender was not able to decrypt some message parts originally, you may be leaking confidential information that the sender was not able to originally decrypt themselves.\n\nPlease consider removing all quoted text from your reply to this sender.
# msgCompose.internalEncryptionError=Internal Error: promised encryption disabled
# msgCompose.internalError=An internal error has occurred.
# msgCompose.toolbarTxt.signAndEncrypt=This message will be signed and encrypted
# msgCompose.toolbarTxt.signOnly=This message will be signed
# msgCompose.toolbarTxt.encryptOnly=This message will be encrypted
# msgCompose.toolbarTxt.noEncryption=This message will be unsigned and unencrypted
# msgCompose.toolbarTxt.disabled=Enigmail is disabled for the selected identity
# msgCompose.protectSubject.tooltip=Protect the message subject
# msgCompose.noSubjectProtection.tooltip=Do not protect the message subject
# msgCompose.encryptedSubjectStub=Encrypted Message
# msgCompose.protectSubject.dialogTitle=Enable Protection of Subject?
# msgCompose.protectSubject.question=Regular encrypted emails contain the unredacted subject.\n\nWe have established a standard to hide the original subject in the encrypted message\nand replace it with a dummy text, such that the subject is only visible after the email is decrypted.\n\nDo you want to protect the subject in encrypted messages?
# msgCompose.protectSubject.yesButton=&Protect subject
# msgCompose.protectSubject.noButton=&Leave subject unprotected
# msgCompose.detailsButton.label=Details ...
# msgCompose.detailsButton.accessKey=D
# msgCompose.pepSendUnknown=Unknown
# msgCompose.pepSendUnsecure=Unsecure
# msgCompose.pepSendSecure=Secure
# msgCompose.pepSendTrusted=Secure & Trusted
# pep.alert.disabledForIdentity=p≡p is disabled for the current identity. Please enable p≡p via the Enigmail/p≡p preferences.
# pep.alert.weakReply=You’re about to forward or reply to a secure message as insecure. If you choose to proceed, confidential information might be leaked putting you and your communication partner at risk. Are you sure you want to continue?
# note: should end with double newline:
sendAborted=Gönderme işleminden çıkıldı.\n\n
# details:
# keyNotTrusted=Not enough trust for key '%S'
# keyNotFound=Key '%S' not found
# keyRevoked=Key '%S' revoked
# keyExpired=Key '%S' expired
statPGPMIME=PGP/MIME
# statSMIME=S/MIME
statSigned=İMZALI
statEncrypted=ŞİFRELENMİŞ
statPlain=DÜZMETİN
offlineSave=%S mesajı Gönderilmemiş Mesajlar klasöründe %S e kaydedelim mi?
onlineSend=%S mesajını %S e gönder?
encryptKeysNote=Not: mesaj şu Kullanıcı ID'si / Anahtarları ile şifreli: %S
# hiddenKey=
signFailed=Enigmail'de hata; Şifreleme/imzalama başarısız; şifrelenmemiş posta gönder?
msgCompose.button.sendUnencrypted=Şifrelenmemiş Me&sajı Gönder
recipientsSelectionHdr=Şifreleme için alıcıları seçin
configureNow=Seçili kimlik için Enigmail güvenliğini henüz ayarlamadınız. Şimdi yapmak istiyor musunuz?
# encryption/signing status and associated reasons:
# encryptMessageAuto=Encrypt Message (auto)
# encryptMessageNorm=Encrypt Message
# signMessageAuto=Sign Message (auto)
# signMessageNorm=Sign Message
# encryptOff=Encryption: OFF
# encryptOnWithReason=Encryption: ON (%S)
# encryptOffWithReason=Encryption: OFF (%S)
# encryptOn=Encryption: ON
# signOn=Signing: ON
# signOff=Signing: OFF
# signOnWithReason=Signing: ON (%S)
# signOffWithReason=Signing: OFF (%S)
# reasonEnabledByDefault=enabled by default
# reasonManuallyForced=manually forced
# reasonByRecipientRules=forced by recipient rules
# reasonByAutoEncryption=forced by auto encryption
# reasonByConflict=due to conflict in recipient rules
# reasonByEncryptionMode=due to encryption mode
# should not be used anymore:
encryptYes=Mesaj ÅŸifrelenecek
encryptNo=Mesaj ÅŸifrelenmeyecek
# should not be used anymore:
signYes=Mesaj imzalanacak
signNo=Mesaj imzalanmayacak
# PGP/MIME status:
# pgpmimeNormal=Protocol: PGP/MIME
# inlinePGPNormal=Protocol: Inline PGP
# smimeNormal=Protocol: S/MIME
# pgpmimeAuto=Protocol: PGP/MIME (auto)
# inlinePGPAuto=Protocol: Inline PGP (auto)
# smimeAuto=Protocol: S/MIME (auto)
# should not be used anymore
# pgpmimeYes=PGP/MIME will be used
# pgpmimeNo=Inline PGP will be used
# Attach own key status (tooltip strings):
# attachOwnKeyNo=Your own key will not be attached
# attachOwnKeyYes=Your own key will be attached
# attachOwnKeyDisabled=Your own key cannot be attached. You have to select a specific key\nin the OpenPGP section of the Account Settings to enable this feature.
rulesConflict=Çakışan alıcı bazlı kurallar bulundu\n%S\n\nMesajı bu ayarlarla göndermek ister misiniz?
msgCompose.button.configure=&Ayarla
msgCompose.button.send=Mesajı &Gönder
msgCompose.button.save=Mesajı &Kaydet
# Strings in enigmailMsgHdrViewOverlay.js
keyNeeded=İmzayı doğrulamak için %S genel anahtarı gerekli
# keyUsed=Public key %S used to verify signature
clickDecrypt=; Deşifre düğmesine tıklayın
clickDecryptRetry=; tekrar denemek için Deşifre düğmesine tıklayın
# clickDetailsButton=; click on 'Details' button for more information
# clickImportButton=; click on the 'Import Key' button to import the key
# keyTypeUnsupported=; the key type is not supported by your version of GnuPG
msgPart=%S mesajının bir bölümü
msgSigned=imzalı
# msgSignedUnkownKey=signed with unknown key
msgEncrypted=ÅŸifreli
msgSignedAndEnc=imzalı ve şifreli
unverifiedSig=Doğrulanmamış imza
incompleteDecrypt=Deşifreleme tamamlanmadı
needKey=Hata - mesajı deşifre etmek için gizli anahtar gerekli
failedDecrypt=Hata - deşifreleme başarısız
badPhrase=Hata - kötü parola
failedDecryptVerify=Hata - deşifreleme/doğrulama başarısız
mdcError=Hata - ileti bütünlük korumalı değildi
viewInfo=; detaylar için Görünüm > Mesaj güvenliği bilgisi
decryptedMsg=DeÅŸifrelenmiÅŸ mesaj
# decryptedMsgWithFormatError=Decrypted message (restored broken PGP email format probably caused by an old Exchange server, so that the result might not be perfect to read)
# usedAlgorithms=Used Algorithms: %1$S and %2$S
# pepStatusInfo.text=p≡p Message Status.
# pepStatusInfo.title.m3=Under Attack
# pepStatusInfo.info.m3=This message is not secure and has been tampered with.
# pepStatusInfo.title.m1=Mistrusted
# pepStatusInfo.info.m1=This message has a communication partner that has previously been marked as mistrusted
# pepStatusInfo.title.r0=Unknown
# pepStatusInfo.info.r0=This message does not contain enough information to determine if it is secure.
# pepStatusInfo.title.r1=Cannot Decrypt
# pepStatusInfo.info.r1=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r2=Cannot Decrypt
# pepStatusInfo.info.r2=This message cannot be decrypted because the key is not available.
# pepStatusInfo.title.r3=Unsecure
# pepStatusInfo.info.r3=This message is unsecure.
# pepStatusInfo.title.r4=Unsecure for Some
# pepStatusInfo.info.r4=This message is unsecure for some communication partners.
# pepStatusInfo.title.r5=Unreliable Security
# pepStatusInfo.info.r5=This message has unreliable protection.
# pepStatusInfo.title.r6=Secure...
# pepStatusInfo.info.r6=This message is secure but you still need to verify the identity of your communication partner.
# pepStatusInfo.title.r7=Secure & Trusted
# pepStatusInfo.info.r7=This message is secure and trusted.
# pepStatusInfo.color.green=Green
# pepStatusInfo.color.yellow=Yellow
# pepStatusInfo.color.red=Red
# pepRevokeTrust.question=Do you really want to cancel the trust for %S?
# pepRevokeMistrust.question=Do you really want to re-trust the key for %S?
# pepRevokeTrust.doRevoke=Cancel &trust
# wksConfirmationReq=Web Key Directory Confirmation Request
# wksConfirmationReq.message=This message has been sent by your email provider to confirm deployment of your OpenPGP public key\nin their Web Key Directory.\nProviding your public key helps others to discover your key and thus being able to encrypt messages to you.\n\nIf you want to deploy your key in the Web Key Directory now, please click on the button "Confirm Request" in the status bar.\nOtherwise, simply ignore this message.
# wksConfirmationReq.button.label=Confirm Request
# autocryptSetupReq=Perform Autocrypt Setup
# autocryptSetupReq.button.label=Start Setup
# autocryptSetupReq.setupMsg.desc=This message contains all information to transfer your Autocrypt settings along with your secret key securely from your original device.
# autocryptSetupReq.setupMsg.backup=You can keep this message and use it as a backup for your secret key. If you want to do this, you should write down the password and store it securely.
# autocryptSetupReq.message.import=To import the settings and key(s) in Enigmail, please click on the "Start Setup" button in the status bar.
# autocryptSetupReq.message.sent=Please click on the message on your new device and follow the instuctions to import the settings.
# strings in pref-enigmail.js
# oldGpgVersion20=Enigmail initialization failed.\n\nYou are using GnuPG version %1$S, which is not supported anymore. Enigmail requires GnuPG version %2$S or newer. Please upgrade your GnuPG installation, or Enigmail will not work.
locateGpg=GnuPGP programını bul
invalidGpgPath=GnuPGP verilen yolda çalıştırılamadı. Bu yüzden uygulamayı tekrar başlatana ya da doğru yolu girene kadar Enigmail kapatıldı.
warningsAreReset=Tüm uyarılar ilk haline getirildi.
prefs.gpgFound=GnuPG ÅŸurada bulundu: %S
prefs.gpgNotFound=GnuPG bulunamadı
prefs.warnAskNever=Uyarı: bu seçeneğin işaretlenmesi alıcılardan birinin anahtarı yoksa, daha fazla bilgi verilmeyen şifrelenmemiş mesajlara neden olacaktır -- Enigmail böyle bir durumda sizi uyarmayacaktır!
# prefs.warnIdleTimeForUnknownAgent=Cannot connect to gpg-agent. Maybe your system uses a specialized tool for passphrase handling (e.g. gnome-keyring, seahorse-agent, KDE wallet manager, ...). Unfortunately Enigmail cannot control the passphrase timeout for the tool you are using. Therefore the respective timeout settings in Enigmail are disregarded.
prefEnigmail.oneKeyserverOnly=Hata - kayıp OpePGP anahtarlarının otomatik indirilebilmesi için sadece bir anahtar sunucu belirtebilirsiniz.
# Strings used in core.jsm
# (said file also re-uses some strings from above)
enterAdminPin=Lütfen SmartCard'ınızın YÖNETİCİ (admin) PIN'ini girin
enterCardPin=Lütfen SmartCard PIN'inizi girin
notInit=Hata - Enigmail servisi henüz başlatılmadı
badCommand=Hata - şifreleme komutu başarısız
cmdLine=komut satırı ve çıktısı:
notRequired=Hata - ÅŸifreleme gerekmiyor
notComplete=Hata - anahtar üretimi henüz bitmedi
invalidEmail=Hata - geçersiz posta adres(ler)i
noPassphrase=Hata - parola sağlanmamış
noPGPblock=Hata - Düzgün zırhlı(armored) OpenPGP veri bloğu bulunamadı
unverifiedReply=İçerden başlatılmış mesaj kısmı (cevap) muhtemelen değiştirilmiş
# keyInMessageBody=Key in message body found. Click 'Import Key' to import the key
sigMismatch=Hata - İmza kayıp
cantImport=Genel anahtar aktarımında hata\n\n
# doImportOne=Import %1$S (%2$S)?
# doImportMultiple=Import the following keys?\n\n%S
# previewFailed=Can't read public key file.
# Strings used in errorHandling.jsm
sc.wrongCardAvailable=Okuyucunuzda bulunan %S akıllı kartı bu mesajı işlemek için kullanılamaz.\nLütfen %S akıllı kartını takıp işlemi tekrarlayın.
sc.insertCard=Bu işlem %S akıllı kartınızı gerektiriyor.\nLütfen gerekli akıllı kartı takıp işlemi tekrarlayın.
sc.removeCard=Bu işlem okuyucuda hiçbir akıllı kartın olmamasını gerektiriyor.\nLütfen akıllı kartı çıkarıp işlemi tekrarlayın.
sc.noCardAvailable=Okuyucunuzda SmartCard bulunamadı\nLütfen SmartCard'ınızı takıp işlemi tekrarlayın
sc.noReaderAvailable=SmartCard okuyucunuza ulaşılamadı\nLütfen SmartCard okuyucunuzu takın, kartınızı takın, ve işlemi tekrarlayın
# keyError.keySpecNotFound=The email address "%S" cannot be matched to a key on your keyring.
# keyError.keyIdNotFound=The configured key ID "%S" cannot be found on your keyring.
# keyError.resolutionAction=Please select a valid key in the OpenPGP section of your Account Settings.
# missingPassphrase=Missing passphrase
# errorHandling.gpgAgentInvalid=Your system is running a version of gpg-agent that is not suitable for your GnuPG version.
# errorHandling.gpgAgentError=GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
# errorHandling.dirmngrError=GnuPG reported an error in the communication with dirmngr (a component of GnuPG).
# errorHandling.pinentryError=GnuPG cannot query your passphrase via pinentry.
# errorHandling.readFaq=This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.\n\nWe strongly recommend that you consult our support web site at https://enigmail.net/faq.
gpgNotFound=GnuPG programı bulunamadı '%S'.\nGnuPG çalıştırılabilirinin yolunu düzgün girdiğinizi Enigmail Seçenekler menüsünden kontrol edin
gpgNotInPath=PATH değişkeninde GnuPG çalıştırılabiliri bulunamadı.\nEnigmail Seçeneklerinden GnuPG çalıştırılabilirinin yolunu kontrol edin
# enigmailNotAvailable=Enigmail core Service not available
prefGood=%S kiÅŸisinden iyi imza
prefBad=%S şahsından KÖTÜ İmza
failCancel=Hata - Anahtar alımı kullanıcı tarafından iptal edildi
failNoServer=Hata - Anahtar alınacak anahtar sunucu belirtilmedi
failNoID=Hata - Anahtar almak için ID belirtilmemiş
failKeyExtract=Hata - anahtar çıkartma komutu başarısız
notFirstBlock=Hata - İlk OpenPGP bloğu genel anahtar bloğu değil
importKeyConfirm=Mesajda gömülü olan genel anahtar(lar)ı ekleyelim mi?
failKeyImport=Hata - anahtar eklemesi başarısız
fileWriteFailed=%S dosyaya yazılamadı
importKey=%S genel anahtarını anahtar sunucudan ekle:
uploadKey=%S genel anahtarını anahtar sunucuya gönder:
keyId=Anahtar ID'si
keyAndSigDate=Anahtar ID'si: 0x%S / İmzalanma tarihi: %S
keyFpr=Anahtar parmakizi: %S
noEmailProvided=Posta adresi belirtmediniz!
keyAlreadySigned=Anahtar zaten imzalı.
#####################################################################
# Strings used in enigmailKeySelection.js
#####################################################################
selKeyExpired=tarihi geçmiş %S
createdHeader=OluÅŸturuldu
atLeastOneKey=Anahtar seçilmedi! Bu diyaloğu geçmek için en az bir anahtar seçmelisiniz
fewerKeysThanRecipients=Alıcı sayısından daha az anahtar seçtiniz. Şifrelemek için gerekli anahtar listesinin tam olduğundan emin misiniz?
userSel.button.goBack=Daha fazla anahtar seç
# userSel.secretKeySel.title=Select a Secret OpenPGP Key to Sign Your Messages
# userSel.problemNoKey=No valid key
# userSel.problemMultipleKeys=Multiple keys
# should be same as thunderbird ENTITY sendLaterCmd.label:
# sendLaterCmd.label=Send Later
# Strings used in enigmailAttachmentDialog.js
# pgpMimeNote=NOTE: PGP/MIME is not supported by all email clients. If you are unsure, select the %S option.
first=ilk
second=ikinci
# Strings used in am-enigprefs.js / enigmailEditIdentity.js
encryptKeyHeader=Şifreleme için OpenPGP Anahtarı seçin
identityName=Kimlik: %S
# switchPepMode=You are currently using the 'p≡p Junior' mode of Enigmail.\n\nBy enabling OpenPGP or S/MIME for an account, you are disabling p≡p and use the 'regular' mode of Enigmail without p≡p.
# enableEnigmail=&Disable p≡p
# Strings used in enigmailSingleRcptSettings.js
noEncryption=Şifrelemeyi aktif ettiniz, ama anahtar seçmediniz. %S e gönderilen postaları şifrelemek için, anahtar listenizden bir ya da daha fazla doğru anahtar seçmelisiniz. %S için şifrelemeyi kapatmak istiyor musunuz?
noKeyToUse=(yok - ÅŸifreleme yok)
noEmptyRule=Kural boş olamaz! Lütfen Kural alanına bir posta adresi belirtin.
invalidAddress=Girdiğiniz posta adres(ler)i düzgün değil. Alıcıların isimlerini girmemelisiniz, sadece posta adreslerini. Ör:\nYanlış: Yngwie Malmsteen \nDoğru: sirin.baba@adres.net
# noCurlyBrackets=The curly brackets {} have a special meaning and should not be used in an email address. If you want to modify the matching behavior for this rule, use the 'Apply rule if recipient ...' option.\nMore information is available from the Help button.
# Strings used in enigmailRulesEditor.js
never=Asla
always=Her zaman
possible=Mümkün
deleteRule=Seçili kuralı gerçekten silmek istiyor musunuz?
nextRcpt=(Sonraki alıcı)
negateRule=DeÄŸil
# addKeyToRule=Add key %1$S (%2$S) to per-recipient rule
# Strings used in enigmailSearchKey.js
needOnline=Seçtiğiniz fonksiyon çevrimdışı modda kullanılamaz. Çevrimiçi olup tekrar deneyin.
protocolNotSupported=Seçtiğiniz '%S://' protokolü OpenPGP anahtarları indirmek için uygun değil.
gpgkeysDisabled='extensions.enigmail.useGpgKeysTool' seçeneğini açmak yardımcı olabilir.
noKeyserverConn=%S konumundaki anahtar sunucuya bağlanılamadı.
keyDownloadFailed=Anahtar sunucudan anahtar indirilemedi. Durum mesajı:\n%S
internalError=Dahili hata. Anahtarlar indirilemedi veya aktarılamadı.
noKeyFound=Üzgünüm, belirtilen arama kriterlerine uygun anahtar bulunamadı.\nAnahtar ID'lerinin "0x" öneki ile kullanılmaları gerektiğini unutmayın(ör: 0xABCDEF12).
# keyDownload.keyUnavailable=We are sorry, but the key with ID %S is not available on the keyserver. Most likely, the owner of the key did not upload their key to the keyserver.\n\nPlease ask the sender of the message to send you their key by email.
# gpgkeys_%S is one of the gpg command line tools gpgkeys_hkp, gpgkeys_ldap, etc.
gpgKeysFailed=Anahtar getirmede ya da aramada hata: gpgkeys_%S çalıştırılamadı.
# Strings in enigmailEditKeyTrustDlg.xul
setKeyTrustFailed=Anahtar sahibi güvenilirliği başarısız
# Strings in enigmailSignKeyDlg.js
signKeyFailed=Anahtar imzalama başarısız
# alreadySigned.label=Note: the key %S is already signed with the selected secret key.
# alreadySignedexportable.label=Note: the key %S is already signed exportable with the selected secret key. A local signature does not make sense.
# partlySigned.label=Note: some user IDs of key %S are already signed with the selected secret key.
# noTrustedOwnKeys=No eligible key found for signing! You need at least one fully trusted secret key in order to sign keys.
# Strings in enigmailKeyManager.js
keyMan.loadingKeys=Anahtarlar yükleniyor, lütfen bekleyin ...
keyValid.unknown=bilinmeyen
keyValid.invalid=yanlış
keyValid.disabled=aktif deÄŸil
keyValid.revoked=iptal edilmiÅŸ
keyValid.expired=süresi dolmuş
keyValid.noSubkey=düzgün alt anahtar yok
keyTrust.untrusted=güvenilmeyen
keyTrust.marginal=marjinal
keyTrust.full=güvenilir
keyTrust.ultimate=ultra
# keyTrust.group=(group)
keyType.public=genel
keyType.publicAndSec=pub/sec
keyMan.enableKey=Anahtar Aktif Et
keyMan.disableKey=Anahtar Etkisiz Kıl
userAtt.photo=Kullanıcı özelliği (JPEG resim)
asciiArmorFile=ASCII Zırhlı Dosyalar (*.asc)
# importKeyFile=Import OpenPGP Key File
gnupgFile=GnuPG Dosyaları
# createKeyOK=Your Key has been generated
saveRevokeCertAs=İptal etme sertifikası Oluştur & Kaydet
# revokeCertOK=The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
revokeCertFailed=İptal sertifikası oluşturulamadı.
addUidOK=Kullanıcı ID'si eklendi
addUidFailed=Kullanıcı ID'si ekleme başarısız
noKeySelected=Bu işlemi yapmak için en az bir anahtar seçmelisiniz
exportToFile=Genel Anahtarı Dosyaya Aktar
# exportKeypairToFile=Export Secret and Public Key To File
exportSecretKey=Özel anahtarı kaydedilen OpenPGP anahtar dosyasına eklemek istiyor musunuz?
saveKeysOK=Anahtarlar kaydedildi
saveKeysFailed=Anahtarlar kaydedileMEdi
importKeysFailed=Anahtarlar aktarılamadı
enableKeyFailed=Anahtarları aktif/etkisiz yapılması başarısız
specificPubKeyFilename=%S (0x%S) pub
specificPubSecKeyFilename=%S (0x%S) pub-sec
defaultPubKeyFilename=Aktarilmis-genel-anahtarlar
defaultPubSecKeyFilename=Aktarilmis-genel-ve-ozel-anahtarlar
noSecretKeys=Özel anahtar bulunamadı.\n\nAnahtarınızı şimdi üretmek ister misiniz?
sendKeysOk=Anahtar(lar) gönderildi
sendKeysFailed=Anahtarlar gönderileMEdi
receiveKeysOk=Anahtar(lar) güncellendi
receiveKeysFailed=Anahtarlar indirilemedi
importFromClip=Panodan anahtar aktarmak ister misiniz?
# importFromUrl=Download public key from this URL:
copyToClipbrdFailed=Seçili anahtar(lar) panoya kopyalanamadı
copyToClipbrdOK=Anahtar(lar) panoya kopyalandı
deleteSecretKey=UYARI: Bir özel anahtar silmek üzeresiniz!\nözel anahtarınızı silerseniz bu anahtar için şifrelenmiş hiçbir mesajı açamazsınız, ve anahtarınızı artık iptal edemezsiniz.\n\nGerçekten hem özel hem genel anahtarınızı silmek istiyor musunuz\n'%S'?
deleteMix=UYARI: özel anahtarları silmek üzeresiniz!\nözel anahtarınızı silerseniz, bu anahtar için şifrelenmiş mesajları açamazsınız.İKİSİNİ de, seçili özel ve genel anahtarları silmek istediğinizden emin misiniz?
deletePubKey=Genel anahtarı silmek istiyor musunuz\n'%S'?
deleteSelectedPubKey=Genel anahtarları silmek istiyor musunuz?
deleteKeyFailed=Anahtar silinemedi
# revokeKeyQuestion=You are about to revoke the key '%S'.\n\nYou will no longer be able to sign with this key, and once distributed, others will no longer be able to encrypt with that key. You can still use the key to decrypt old messages.\n\nDo you want to proceed?
revokeKeyOk=Anahtar iptal edildi. Anahtarınız bir anahtar sunucudaysa, tekrar yüklemeniz önerilir, böylece diğerleri iptal edildiğini görebilir.
revokeKeyFailed=Anahtar iptal edilemedi.
# revokeKeyNotPresent=You have no key (0x%S) which fits to this revocation certificate!\n\nIf you have lost your key, you must import it (e.g. from a keyserver) before the revocation certificate!
# revokeKeyAlreadyRevoked=The key 0x%S has already been revoked.
refreshAllQuestion=Anahtar seçmediniz. TÜM anahtarları yenilemek ister misiniz?
# refreshKeyServiceOn.warn=Warning: Your keys are currently being refreshed in the background as safely as possible.\nRefreshing all your keys at once will unnecessarily reveal information about you.\nDo you really want to do this?
refreshKey.warn=Uyarı: anahtar sayısı ve bağlantı hızına bağlı olarak, tüm anahtarların yenilenmesi uzun sürebilir!\n\nDevam?
# downloadContactsKeys.warn=Warning: depending on the number of contacts and the connection speed, downloading all keys could be quite a lengthy process!
# downloadContactsKeys.importFrom=Import contacts from address book '%S'?
keyMan.button.exportSecKey=&Gizli Anahtarları Dışa Aktar
keyMan.button.exportPubKey=Sadece &Açık Anahtarları Dışa Aktar
keyMan.button.import=&İçe Aktar
keyMan.button.refreshAll=&Tüm Anahtarları Tazele
keyMan.button.revokeKey=&Anahtarı Hükümsüz Kıl
# keyMan.button.skip=&Skip Key
keylist.noOtherUids=BaÅŸka kimliÄŸi yoktur
keylist.hasOtherUids=Ayrıca şöyle bilinir
keylist.noPhotos=Uygun fotoÄŸraf yok
keylist.hasPhotos=FotoÄŸraflar
# keyMan.addphoto.filepicker.title=Select photo to add
# keyMan.addphoto.warnLargeFile=The file you have chosen is larger than 25 kB.\nIt is not recommended to add very large files because the keys get very large by this.
# keyMan.addphoto.noJpegFile=The selected file does not appear to be a JPEG file. Please choose a different file.
# keyMan.addphoto.failed=The photo could not be added.
# noWksIdentity=The key %S does not have a WKS identity.
# keyman.addBlacklistKey.msg=Do you really want p≡p to stop using the key "%1$S (%2$S)" for encrypting messages?
# keyman.removeBlacklistKey.msg=Do you want to allow p≡p to use key "%1$S (%2$S)" for future messages?
# keyman.addBlacklistKey.button=&Blacklist the key
# keyman.removeBlacklistKey.button=&Remove key from Blacklist
# Strings in enigmailManageUidDlg.xul
changePrimUidFailed=Birincil kullanıcı ID'si değişimi başarısız
changePrimUidOK=Birincil kullanıcı ID'Si değiştirildi
revokeUidFailed=%S kullanıcı ID'sinin iptali başarısız
revokeUidOK=%S kullanıcı ID'si iptal edildi. Anahtarınız bir anahtar sunucudaysa, diğerlerinin iptali görebilmesi için tekrar yüklemeniz tavsiye edilir.
revokeUidQuestion=Gerçekten kullanıcı ID'si %S'i iptal etmek istiyor musunuz?
# Strings in enigmailKeyImportInfo.xul
# importInfoTitle=SUCCESS! Keys imported
# importInfoBits=Bits
# importInfoCreated=Created
# importInfoFpr=Fingerprint
# importInfoDetails=(Details)
# importInfoNoKeys=No keys imported.
# Strings in enigmailKeyDetailsDlg.xul
keyTypePublic=genel anahtar
keyTypePrimary=özel anahtar
keyTypeSubkey=altanahtar
keyTypePair=anahtar çifti
keyExpiryNever=asla
keyAlgorithm_1=RSA
keyAlgorithm_2=RSA
keyAlgorithm_3=RSA
keyAlgorithm_16=ELG
keyAlgorithm_17=DSA
# keyAlgorithm_18=ECDH
# keyAlgorithm_19=ECDSA
keyAlgorithm_20=ELG
# keyAlgorithm_22=EDDSA
# keyUsageEncrypt=Encrypt
# keyUsageSign=Sign
# keyUsageCertify=Certify
# keyUsageAuthentication=Authentication
# keyDoesNotExpire=Key does not expire
# Strings in enigmailGenCardKey.xul
keygen.started=Lütfen anahtar üretilirken bekleyin ....
keygen.completed=Anahtar Üretildi. Yeni Anahtar ID'si: 0x%S
keygen.keyBackup=Anahtar %S olarak yedeklendi
keygen.passRequired=Eğer anahtarınız için SmartCard'ınız dışında bir yedek yaratmak istiyorsanız bir parola belirtin.
# Strings in enigmailSetCardPin.xul
cardPin.processFailed=PIN deÄŸiÅŸtirilemedi
# Strings in enigRetrieveProgres.xul
keyserverProgress.refreshing=Anahtarlar yenileniyor, lütfen bekleyin ...
keyserverProgress.uploading=Anahtarlar gönderiliyor, lütfen bekleyin ...
# keyserverProgress.wksUploadFailed=Could not upload your key to the Web Key Service
# keyserverProgress.wksUploadCompleted=Your public key was successfully submitted to your provider. You will receive an email to confirm that you initiated the upload.
keyserverTitle.refreshing=Anahtarları Yenile
keyserverTitle.uploading=Anahtarları Gönder
# Strings in enigmailSetupWizard
passphrase.min8keys=Parolanız en az 8 karakter olmalı!
setupWizard.reallyCancel=Enigmail Kurulum Sihirbazından gerçekten mi çıkmak istiyorsunuz?
# setupWizard.invalidGpg=The file you specified is not a GnuPG executable. Please specify a different file.
# setupWizard.specifyFile=You need to at least specify a public key file in order to proceed.
# setupWizard.installFailed=It seems that the installation was not successful. Please either retry the installation, or install GnuPG manually and locate it using the Browse button.
# setupWizard.downloadForbidden=For your own security, we will not download GnuPG. Please visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.downloadImpossible=We cannot download GnuPG currently. Please try later or visit https://gnupg.org/ in order to download GnuPG.
# setupWizard.hashSumError=The wizard could not verify the integrity of the downloaded file. The file may be broken or manipulated. Do you want to continue the installation anyway?
# setupWizard.importSettingsFile=Specify backup file to load from
# setupWizard.invalidSettingsFile=The specified file is not a correct Enigmail Settings backup file.
# setupWizard.gpgConfExists=The GnuPG config file already exists. Do you want to overwrite it with the one from your old installation?
# setupWizard.noGpgHomeDir=It appears that you configured %S to use for GnuPG. However, this is not a directory - you cannot use it.
# setupWizard.unmachtedIds=The following identities of your old setup could not be matched:\n%S\nThe settings for these identities were skipped.
# Strings in installGnuPG.jsm
# installGnuPG.downloadFailed=An error occurred while trying to download GnuPG. Please check the console log for further details.
# installGnuPG.installFailed=An error occurred while installing GnuPG. Please check the console log for further details.
# Strings in enigmailAddUidDlg.xul
addUidDlg.nameOrEmailError=İsim ve mail adresi girmeniz gerekiyor
addUidDlg.nameMinLengthError=İsmin en az 5 karakter olması gerekiyor
addUidDlg.invalidEmailError=DoÄŸru bir mail adresi belirtmelisiniz
# Strings in enigmailCardDetails.js
# Carddetails.NoASCII=OpenPGP Smartcards only support ASCII characters in Firstname/Name.
# network error types
# errorType.SecurityCertificate=The security certificate presented by the web service is not valid.
# errorType.SecurityProtocol=The security protocol used by the web service is unknown.
# errorType.Network=A network error has occurred.
# filter stuff
# filter.folderRequired=You must select a target folder.
# filter.decryptMove.label=Decrypt permanently (Enigmail)
# filter.decryptCopy.label=Create decrypted Copy (Enigmail)
# filter.decryptMove.warnExperimental=Warning - the filter action "Decrypt permanently" may lead to destroyed messages.\n\nWe strongly recommend that you first try the "Create decrypted Copy" filter, test the result carefully, and only start using this filter once you are satisified with the result.
# filter.tempPepFilterDesc=Temporary filter to store sent message unencrypted
# filter.term.pgpencrypted.label=OpenPGP Encrypted
# filter.encrypt.label=Encrypt to key (Enigmail)
# filter.keyRequired=You must select a recipient key.
# filter.keyNotFound=Could not find an encryption key for "%S".
# filter.warn.keyNotSecret=Warning - the filter action "Encrypt to key" replaces the recipients.\n\nIf you do not have the secret key for "%S" you will no longer be able to read the emails.
# strings in enigmailConvert.jsm
# converter.decryptBody.failed=Could not decrypt message with subject\n"%S".\nDo you want to retry with a different passphrase or do you want to skip the message?
# converter.decryptAtt.failed=Could not decrypt attachment "%1$S"\nof message with subject\n"%2$S".\nDo you want to retry with a different passphrase or do you want to skip the message?
# saveLogFile.title=Save Log File
# strings in gpg.jsm
# unknownSigningAlg=Unknown signing algorithm (ID: %S)
# unknownHashAlg=Unknown cryptographic hash (ID: %S)
# strings in keyRing.jsm
# keyring.photo=Photo
# keyRing.pubKeyRevoked=The key %1$S (key ID %2$S) is revoked.
# keyRing.pubKeyExpired=The key %1$S (key ID %2$S) has expired.
# keyRing.pubKeyNotForSigning=The key %1$S (key ID %2$S) cannot be used for signing.
# keyRing.pubKeyNotForEncryption=The key %1$S (key ID %2$S) cannot be used for encryption.
# keyRing.keyDisabled=The key %1$S (key ID %2$S) is disabled; it cannot be used.
# keyRing.keyNotTrusted=The key %1$S (key ID %2$S) is not trusted enough. Please set the trust level of your key to "ultimate" to use it for signing.
# keyRing.keyInvalid=The key %1$S (key ID %2$S) is not valid. Please consider verifying it correctly. Alternatively use the Default encryption settings in the Enigmail preferences dialog.
# keyRing.signSubKeysRevoked=All signing-subkeys of key %1$S (key ID %2$S) are revoked.
# keyRing.signSubKeysExpired=All signing-subkeys of key %1$S (key ID %2$S) have expired.
# keyRing.signSubKeysUnusable=All signing-subkeys of key %1$S (key ID %2$S) are revoked, expired or otherwise unusable.
# keyRing.encSubKeysRevoked=All encryption subkeys of key %1$S (key ID %2$S) are revoked.
# keyRing.encSubKeysExpired=All encryption subkeys of key %1$S (key ID %2$S) have expired.
# keyRing.noSecretKey=You do not seem to have the secret key for %1$S (key ID %2$S) on your keyring; you cannot use the key for signing.
# keyRing.encSubKeysUnusable=All encryption subkeys of key %1$S (key ID %2$S) are revoked, expired or otherwise unusable.
#strings in exportSettingsWizard.js
# cannotWriteToFile=Cannot save to file '%S'. Please select a different file.
# dataExportError=An error occurred during exporting your data.
# enigmailSettings=EnigmailSettings
# defaultBackupFileName=Enigmail-export
# specifyExportFile=Specify file name for exporting
# homedirParamNotSUpported=Additional params that configure paths such as --homedir and --keyring are not supported for exporting/restoring your settings. Please use alternative methods such as setting the environment variable GNUPGHOME.
#strings in expiry.jsm
# expiry.keyExpiresSoon=Your key %1$S will expire in less than %2$S days.\n\nWe recommend that you create a new key pair and configure the corresponding accounts to use the new key.
# expiry.keysExpireSoon=The following of your keys will expire in less than %1$S days:\n%2$S We recommend that you create new keys and configure your accounts to use the new keys.
# expiry.keyMissingOwnerTrust=Your secret key %S has missing trust.\n\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.keysMissingOwnerTrust=The following of your secret keys have missing trust.\n%S.\nWe recommend that you set "You rely on certifications" to ultimate in key properties.
# expiry.OpenKeyManager=Open Enigmail Key Management
# expiry.OpenKeyProperties=Open Key Properties
#strings in pEpDecrypt.jsm
# pEpDecrypt.cannotDecrypt=This is an encrypted message. Unfortunately you don't have the secret key to decrypt the message.
#strings in gpgAgent.jsm
# gpghomedir.notexists=The directory '%S' containing your OpenPGP keys does not exist and cannot be created.
# gpghomedir.notwritable=The directory '%S' containing your OpenPGP keys is not writable.
# gpghomedir.notdirectory=The directory '%S' containing your OpenPGP keys is a file instead of a directory.
# gpghomedir.notusable=Please fix the directory permissions or change the location of your GnuPG "home" directory. GnuPG cannot work correctly otherwise.
#strings in pepTrustWords.js
# pepTrustWords.cannotVerifyOwnId=Cannot verify p≡p Trustwords for own account.
# pepTrustWords.cannotFindKey=Cannot find key for %S.
# pepTrustWords.cannotStoreChange=Could not change trust for %S.
# pepTrustWords.generalFailure=Cannot obtain trustwords for %S.
# pepTrustWords.partnerFingerprint=Fingerprint for %S:
#strings in mimeWkdHandler.jsm
# wkdMessage.body.req=Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.\n\nPlease click the confirmation button in the Enigmail header to complete the publishing of your public key.
# wkdMessage.body.process=This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.\n\nYou do not need to take any manual action at this point.
#strings in pepHandshake.js
# pepPrivacyStatus.RatingBrokenSuggestion=Either you or the sender should resend the message.
# pepPrivacyStatus.RatingHaveNoKeySuggestionOutgoing=If you composed this message, your key is not available.
# pepPrivacyStatus.RatingMistrustSuggestion=Re-establish the connection with your communication partner and try to complete another handshake.
# pepPrivacyStatus.RatingReliableSuggestion=Complete a handshake with your communication partner by exchanging trustwords in person or over the phone. A handshake is needed only once per partner and will ensure secure and trusted communication.
# pepPrivacyStatus.RatingTrustedSuggestion=No action needed!
# pepPrivacyStatus.RatingUndefinedSuggestionIncoming=Be aware this message may not be secure.
# pepPrivacyStatus.RatingUndefinedSuggestionOutgoing=Please add the necessary information.
# pepPrivacyStatus.RatingUnderAttackSuggestion=Separately verify the content of this message with your communication partner.
# pepPrivacyStatus.RatingUnencryptedForSomeSuggestion=Make sure the privacy status for each communication partner listed is at least secure.
# pepPrivacyStatus.RatingUnencryptedSuggestion=Please ask your communication partner to use an encryption solution or install p≡p.
# pepPrivacyStatus.RatingUnreliableSuggestion=This message has no reliable encryption or no signature. Ask your communication partner to upgrade their encryption solution or install p≡p.
# pepPrivacyStatus.RatingBrokenExplanation=This message has broken encryption or formatting.
# pepPrivacyStatus.RatingHaveNoKeyExplanation=This message cannot be decrypted because the key is not available.
# pepPrivacyStatus.RatingMistrustExplanation=This message has a communication partner that has previously been marked as mistrusted.
# pepPrivacyStatus.RatingReliableExplanation=This message is secure but you still need to verify the identity of your communication partner.
# pepPrivacyStatus.RatingTrustedExplanation=This message is secure and trusted.
# pepPrivacyStatus.RatingUndefinedExplanation=This message does not contain enough information to determine if it is secure.
# pepPrivacyStatus.RatingUnderAttackExplanation=This message is not secure and has been tampered with.
# pepPrivacyStatus.RatingUnencryptedExplanation=This message is unsecure.
# pepPrivacyStatus.RatingUnencryptedForSomeExplanation=This message is unsecure for some communication partners.
# pepPrivacyStatus.RatingUnreliableExplanation=This message has unreliable protection.
# pepPrivacyStatus.RatingBrokenText=Broken
# pepPrivacyStatus.RatingHaveNoKeyText=Cannot Decrypt
# pepPrivacyStatus.RatingMistrustText=Mistrusted
# pepPrivacyStatus.RatingReliableText=Secure
# pepPrivacyStatus.RatingTrustedText=Secure & Trusted
# pepPrivacyStatus.RatingUndefinedText=Unknown
# pepPrivacyStatus.RatingUnderAttackText=Under Attack
# pepPrivacyStatus.RatingUnencryptedForSomeText=Unsecure for Some
# pepPrivacyStatus.RatingUnencryptedText=Unsecure
# pepPrivacyStatus.RatingUnreliableText=Unreliable Security
# handshakeDlg.button.initHandshake=Handshake...
# handshakeDlg.button.stopTrust=Stop Trusting
# handshakeDlg.button.reTrust=Stop Mistrusting
# handshakeDlg.label.outgoingMessage=Outgoing message
# handshakeDlg.label.incomingMessage=Incoming message
# handshakeDlg.error.noPeers=Cannot handshake without any correspondents.
# handshakeDlg.error.noProtection=Please enable protection in order to use the Handshake function.
# enigmail.acSetupPasswd.descEnterPasswd=Please enter the setup code that is displayed on the other device
# enigmail.acSetupPasswd.descCopyPasswd=Please enter the setup code below on your other device to proceed with the setup
#strings in autocrypt.jsm
# autocrypt.setupMsg.subject=Autocrypt Setup Message
# autocrypt.setupMsg.msgBody=To set up your new device for Autocrypt, please follow the instuctions that should be presented by your new device.
# autocrypt.setupMsg.fileTxt=This is the Autocrypt setup file used to transfer settings and keys between clients. You can decrypt it using the setup code presented on your old device, and then import the contained key into your keyring.
#strings in upgradeInfo.html
# upgradeInfo.doctitle=What's New in Enigmail v2.0?
# upgradeInfo.welcome1=Welcome to the new Enigmail version 2.0!
# upgradeInfo.welcome2=The release contains a lot of new and changed features. Please take a minute to find out what's new:
# upgradeInfo.encSubject.title=Encrypting the Message Subject
# upgradeInfo.encSubject.desc=We developed a new method that moves the email subject into the encrypted message, and replaces the visible subject with "Encrypted Message". Once such a message is decrypted, the original subject is replaced automatically. Hiding the subject is on by default; there is a preference to turn it off if you don't like it. (Note: this feature requires the message to be sent with PGP/MIME.)
# upgradeInfo.buttons.title=Changed behavior of Encrypt and Sign Buttons
# upgradeInfo.buttons.desc=The Encrypt and Sign buttons in the message composer window now work for both the OpenPGP and S/MIME protocols. If both algorithms are possible, then Enigmail will try to prefer the one for which all keys are available.
# upgradeInfo.autocrypt.title=Support for Autocrypt
# upgradeInfo.autocrypt.desc=Enigmail now supports Autocrypt, a new standard to distribute keys as part of sent messages. Enigmail automatically imports keys from Autocrypt-compliant messages, such that over time more and more emails can be encrypted.
# upgradeInfo.pEp.title=New p≡p Junior Mode (Pretty Easy Privacy)
# upgradeInfo.pEp.desc=Enigmail now contains a p≡p Junior Mode. You currently need to manually install p≡p for this purpose; this will change in a future release. The p≡p Junior Mode allows you to use OpenPGP encryption as transparently as possible; you don't need to care for key management and synchronization of keys between devices anymore.
# upgradeInfo.bottom.desc=Please visit our documentation for help on using Enigmail.
# pep.missingGnuPG=In order to use Enigmail/p≡p, GnuPG is required. As we could not find it, we suggest to download and install it for you.
#strings in enigmailAbout.html
# aboutEnigmail.tabName=About Enigmail
# aboutEnigmail.title=OpenPGP support provided by Enigmail
# aboutEnigmail.team=Enigmail is developed by the Enigmail Team:
# aboutEnigmail.projectLeader=Lead Developer:
# aboutEnigmail.usability=Usability:
# aboutEnigmail.documentation=Documentation:
# aboutEnigmail.testing=Testing:
# aboutEnigmail.userSupport=User Support:
# aboutEnigmail.localization=Localization: See the Enigmail Language Packs page
# aboutEnigmail.Credits=Credits:
# aboutEnigmail.origAuthor=Original author of the Enigmail extension
# aboutEnigmail.icons=Icons:
# aboutEnigmail.formerMembers=Former team members:
# aboutEnigmail.projectHosting=Project hosting:
# aboutEnigmail.licenseSupportTitle=License & Support
# aboutEnigmail.license=Enigmail OpenPGP is open source and licensed under the %S
# aboutEnigmail.support=Support and download is available from www.enigmail.net.
enigmail-2.0.8/lang/tr/help/ 0000775 0000000 0000000 00000000000 13343027545 0015612 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/tr/help/compose.html 0000664 0000000 0000000 00000010076 13343027545 0020151 0 ustar 00root root 0000000 0000000
Enigmail Help: Message Composition
Enigmail Help
Using Enigmail when composing messages
Enigmail menu in Mail/Compose window
Sign message
Enable/Disable sending signed mail. User is notified, if signing fails.
Encrypt message
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.
Use PGP/MIME for this message
Enable/Disable the use of PGP/MIME for this message.
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.
Default composition options
Signing/Encryption Options...: shortcut to Account Settings -> OpenPGP Options.
Send options...: shortcut to Preferences -> Send tab.
Key selection options...: shortcut to Preferences -> Key Selection tab.
PGP/MIME options...: shortcut to Preferences -> PGP/MIME tab.
Undo encryption
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.
Insert public key
insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.
Clear save passphrase
Clears cached passphrase. Useful if you have multiple passphrases.
Help
Displays Help information from the website (this page).
Using the Enigmail Rules Editor: Edit OpenPGP Rule
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.
Set OpenPGP Rules for
Contains the email addresses of the recipients (without names, i.e. just an address like somebody@email.domain). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. @email.domain will allow matching to body@email.domain, somebody@email.domain, anybody@email.domain, etc.
Apply rule if recipient ...
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the OpenPGP Rules field above.
Is exactly: with this setting, the rule will only trigger on emails to body@email.domain (exact, case insensitive matching).
Contains: with this setting, any email address containing the string is matched, e.g. anybody@email.domain or body@email.domain.net
Begins with: with this setting, any email address starting with the string is matched, e.g. body@email.domain.net, body@email.domain-name.com.
Ends with: with this setting, any email address ending with the string is matched, e.g. anybody@email.domain , somebody@email.domain.
Continue with the next rule for the matching address
Enabling this function will allow you to define a rule but not have to specify a KeyID in the Use the following OpenPGP keys: field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.
Do not check further rules for the matching address
Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.
Use the following OpenPGP keys:
Use the Select Key(s).. button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.
Default for Signing
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Yes, if selected from in Message Composition: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encryption
Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.
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.
enigmail-2.0.8/lang/tr/help/initError.html 0000664 0000000 0000000 00000004542 13343027545 0020462 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.
Pen and Key icons in Message Header display
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
OpenPGP Security info: allows you to view the output status from GnuPG for the message.
Copy OpenPGP Security info: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.
View OpenPGP Photo ID: allows you to view the Photo ID of the person who sent the message, if they have a photo embedded in their Public Key. (This option will only be enabled if a Photo ID exists in their key.)
S/MIME Security info: allows you to view the S/MIME Security Info for the message.
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.
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: Decrypt and Open and Decrypt and Save. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.
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:
Email
The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on substrings (Further details can be found in the Edit Rule dialog)
OpenPGP Key(s)
a list of OpenPGP Key ID's to use for the recipient
Sign
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
Never: disable signing, even if it was enabled in the message composition window (overrules the other values)
Possible: leave signing as specified in the message composition window
Always: enable signing, even if it was not enabled in the message composition window
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.
Encrypt
enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.
PGP/MIME
enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.
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
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on body@email.domain entered in the OpenPGP Rules field above.
ChÃnh xác là : vá»›i thiết láºp nà y, các quy tắc sẽ chỉ kÃch hoạt ở những thư Ä‘iện tỠđến body@email.domain (chÃnh xác, không so sánh chữ hoa/thưá»ng).
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-2.0.8/lang/vi/help/initError.html 0000664 0000000 0000000 00000004500 13343027545 0020445 0 ustar 00root root 0000000 0000000
Enigmail Help: How to Resolve Problems with Initializing OpenPGP
Enigmail Help
How to Resolve Problems with Initializing OpenPGP
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.
GnuPG could not be found
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)
Enigmime failed to initialize
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.
Nút nà y có thể được dùng cho nhiá»u mục Ä‘Ãch: giải mã, xác nháºn, hoặc nháºp các khóa công và o. Thông thưá»ng thì việc giải mã/xác nháºn xảy ra tá»± động, mặc dù Ä‘iá»u nà y có thể bị tắt qua má»™t tùy thÃch. Tuy nhiên, nếu Ä‘iá»u nà y không là m được thì má»™t thông báo lá»—i ngắn sẽ thưá»ng xuất hiện trong dòng trạng thái cá»§a Enigmail. Nếu bạn nhấn nút Giải mã, bạn sẽ có thể thấy má»™t thông báo lá»—i chi tiết hÆ¡n, kể luôn kết qá»§a cá»§a lệnh GnuPG.
Các biểu tượng cá»§a Bút và Khóa trong hiển thị Äầu đỠTin nhắn
The Pen and Key icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the Pen icon will change to a Broken Pen to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
In the Sending Preferences you can choose the general model and preferences for encryption.
Convenient Encryption
With these settings, emails are encrypted without confirmation whenever possible.
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.
Manual Encryption
This option allows you to specify the different preferences for encryption according to your needs. You can specify
whether replies to encrypted/signed emails should automatically also be encrypted/signed-
whether to use the trust model of OpenPGP to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).
whether you want to automatically send emails encrypted if all keys are accepted.
whether and when you want to finally confirm sending an email.
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
enigmail-2.0.8/lang/zh-CN/ 0000775 0000000 0000000 00000000000 13343027545 0015154 5 ustar 00root root 0000000 0000000 enigmail-2.0.8/lang/zh-CN/am-enigprefs.properties 0000664 0000000 0000000 00000000117 13343027545 0021646 0 ustar 00root root 0000000 0000000 # Strings used in the Mozill AccountManager
prefPanel-enigprefs=OpenPGP 安全
enigmail-2.0.8/lang/zh-CN/enigmail.dtd 0000664 0000000 0000000 00000155666 13343027545 0017461 0 ustar 00root root 0000000 0000000
Mozilla 公共许å¯è¯ 2.0