Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified
📁 ..	-	2026-04-05 19:18
📄 distsigkey.gpg ��X˺��3��H��0�O�k��a�w��/CR�:��7��`�(��;L�[;ܗ��}�V��/��\�/iW�k�V��KAkq�Pfi�iG@�b��^��Gd�i��?Br��~��<_�[,jOŮ��9�/�-�6#��]��S��D��\|n�9�j��2MZkT��{�˻�ʜ&`�_��o? ��gM��hY��a�_��.W�"��hc)��1��H��:(��H�>�M��%h�A��^[��l��nx��2iU7i�"�M��Ijjuت��^�LF�x�ʡ�xD �h&��`��Cc�7�u~4�� a#�Ct\|��T�}�d�/�`Ñ1��/Fم�&C��8![��uB��U��j��~)K .(X��ɠ</��; ]��r<�b�� ~)K .(6 �O��1�.NL��8}�DsO�"t�L�o��X��y�ǥD��t�+\|��(%u4 L��L_� A;�g�� 2��3χ`ąR�6��(_>~��[Vk��Cjs�w�?n�k$a�;��v�I�SG��ep)#R'��L�KEC��cD��%��>�M=��JrB��>�Dw6C�CCށy+#O��@��'n>��Q�Y铀Y�c��A�F�VF�XX�w9%A��螐�/SN� �a� ��b�QR5�@�'d��y�<��35R�� O��DX8x��EY�j�1{��DIF��r��Zݩx�0�'ϲ�3�EM�@9�u+�F6B�!PN; �$Andre Heinecke (Release Signing Key)��>![��uB��U��j��~)K .(X˺� �� ~)K .(B�� HK��.�\|��l"�sdL�:��h'N��p��;�?�I[{��J��2Ɔ� %2HH �dY"�w��zD] W��(-�m�'=Kx0�+�I��I��C��l�ɓ�Q��-~�8��!H��Fν��~�%��?�eB�H8�݈��k2S>{�1�Ib��/�TF�a?�'��l(�m�2 �IgP��K>d\|�h ff�D��w�+x�rF�Y&^1�3�̨Zh�ߟE�:�R�\�5L��nȮ�yF�#ǤM��P>�c��c�؆��$`�\|"��m_Kմ�\�v�+S�RED��P%�0��d��&!�w2�\|~7�>�K�?��!��ɠ</��; ]��r<�b��X˿�� r<�b��p��\S7��ⰰ�\��bf`sK��ĥ�$%\��.��en�ȅ��d ��[U=I;o�B��j��{"��X�`Vv�x;Mw0�H� �>+`Gj�[��l6�j�"�� ]־��T��eY�w��qwy:`�]�� PW]��@��>j~gN7��fW�_2��V��X��L8g��ޮ�!y`_9�^VϏ\|�<Ы��u�x�̿�pKN�՞kf,r�z��^�W�<y7槖`��]��Z�q�V�Dv�6��%@"��x8eH��<,�v(4��? D(��w��)��f�J !��/�:�P�%o��2��@�Vz Xd�w��ѷ0�ʩ��+d�Qi .�"�3_C� +�G@ϾG��עa��40�DWݓ\0#�dn�0&6��Werner Koch (dist signing 2020)�� B!m�nd�m(@WIR��&@:�_C�5 �� " �� R��&@:�y��n/��t ��iQK��i��"O@F�4t`&��`!�� e��+N��G��֭Kz�B��m�!�aXp��֐36��򭅬B�g_C�� 򭅬B�g!��1�-�oW��<8��Ɇ�sH�s~:/b��2pyr)h�� O�M�s��u�!��N��lG�\c:�fX} _C�%� c:�fX} ��K��ܝ'�E�4�0UR�ʼ@ZԶS��jR�O�Ĭ"ٗGA��Z0S5�{��I��uj�m��3�!�i!#�]�^:�$�9�O%�_C�� $�9�O%� Z�J=��&�+��^��R�D�r�`�W��4�yY{�8�f�S��L��PO �-)^/��C�q�\|O��K��m3�8�{�׉�ɞp��#`A��x��z\�U�̺#��qz��rb��SS�I�֘��Y�0s>U(�+�$\|��y�VxfW�v��d~\|�+�1ek��"CA��"mr/��!BX��ܾ�F��a�YEϨ;0��y�"z��ӑ��d�L"CB��λ]mڈu �!��Ki!�J�!�!�E�+_C�� !�E�+�T�Ƭ�Yw�w�b6�ys��pry6L��N3#��y��SmU�VB2��_�3:6�@2��?�U<`�3`�� +�G@�� \|�Cy?w��"ZN�B/.��y��>� Niibe Yutaka (GnuPG Release Key)�� B!��[�>-�G��鎛-�Ƚ`�� " �� 鎛-�Ƚ��Z�J��S��8M0� ෂa�=�:�/UK��&��ؗ� l$��)FZ�c�>7㙏��ٛDl�3��u�!$��wPt]\�2<�g�R6O�a@C�� g�R6O�B��)4�QWPLa��f�B5<��7��9��]$�`���4L�.��nG��d ��/�'��m��3�!A$�;Hb�z B��^�L��a@C�� ^�L��$h��S��3VU-/\«�I4�c?� M��Q��uɾ$�;S�bHF��PDO)��;c�溿�(uRE�� E<9�r"�+,G��@��r �Nd\|�)7Y��o�,;x��B��Q�o�� 0)Xx��B�ޡL)�\|y�s�S.��㎢��#��ч ��=��Z�W�?�0%�sd[B#/<�s=��`�C��[n>�L��ᰑto��(~��j��cW��I�ٚ�#I;��L�>�	3.31 KB	2021-09-14 08:11
📄 help.be.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.ca.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.cs.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.da.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.de.txt # help.de.txt - German GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. # Die Datei help.txt beschreibt das verwendete Format. # Diese Datei muß UTF-8 kodiert sein. .#pinentry.qualitybar.tooltip # Dies ist lediglich eine kommentiertes Beispiel. Es ist am sinnvolssten # einen individuellen Text in /etc/gnupg/help.de.txt zu erstellen. Die Qualität der Passphrase, die Sie oben eingegeben haben. Bitte fragen sie Ihren Systembeauftragten nach den Kriterien für die Messung der Qualität. . .gpg.edit_ownertrust.value Sie müssen selbst entscheiden, welchen Wert Sie hier eintragen; dieser Wert wird niemals an eine dritte Seite weitergegeben. Wir brauchen diesen Wert, um das "Netz des Vertrauens" aufzubauen. Dieses hat nichts mit dem (implizit erzeugten) "Netz der Zertifikate" zu tun. . .gpg.edit_ownertrust.set_ultimate.okay Um das Web-of-Trust aufzubauen muß GnuPG wissen, welchen Schlüsseln ultimativ vertraut wird. Das sind üblicherweise die Schlüssel auf deren geheimen Schlüssel Sie Zugruff haben. Antworten Sie mit "yes" um diesen Schlüssel ultimativ zu vertrauen . .gpg.untrusted_key.override Wenn Sie diesen nicht vertrauenswürdigen Schlüssel trotzdem benutzen wollen, so antworten Sie mit "ja". . .gpg.pklist.user_id.enter Geben Sie die User-ID dessen ein, dem Sie die Botschaft senden wollen. . .gpg.keygen.algo Wählen Sie das zu verwendene Verfahren. DSA (alias DSS) ist der "Digital Signature Algorithm" und kann nur für Unterschriften genutzt werden. Elgamal ist ein Verfahren nur für Verschlüsselung. RSA kann sowohl für Unterschriften als auch für Verschlüsselung genutzt werden. Der erste Schlüssel (Hauptschlüssel) muß immer ein Schlüssel sein, mit dem unterschrieben werden kann. . .gpg.keygen.algo.rsa_se Normalerweise ist es nicht gut, denselben Schlüssel zum unterschreiben und verschlüsseln zu nutzen. Dieses Verfahren sollte in speziellen Anwendungsgebiten benutzt werden. Bitte lassen Sie sich zuerst von einem Sicherheistexperten beraten. . .gpg.keygen.size Wählen Sie die gewünschte Schlüssellänge . .gpg.keygen.size.huge.okay Geben Sie "ja" oder "nein" ein . .gpg.keygen.size.large.okay Geben Sie "ja" oder "nein" ein . .gpg.keygen.valid Geben Sie den benötigten Wert so an, wie er im Prompt erscheint. Es ist zwar möglich ein "ISO"-Datum (JJJJ-MM-DD) einzugeben, aber man erhält dann ggfs. keine brauchbaren Fehlermeldungen - stattdessen versucht der Rechner den Wert als Intervall (von-bis) zu deuten. . .gpg.keygen.valid.okay Geben Sie "ja" oder "nein" ein . .gpg.keygen.name Geben Sie den Namen des Schlüsselinhabers ein. Beispiel: Heinrich Heine. . .gpg.keygen.email Geben Sie eine Email-Adresse ein. Dies ist zwar nicht unbedingt notwendig, aber sehr empfehlenswert. Beispiel: heinrichh@duesseldorf.de . .gpg.keygen.comment Geben Sie - bei Bedarf - einen Kommentar ein. . .gpg.keygen.userid.cmd N um den Namen zu ändern. K um den Kommentar zu ändern. E um die Email-Adresse zu ändern. F um mit der Schlüsselerzeugung fortzusetzen. B um die Schlüsselerzeugung abbrechen. . .gpg.keygen.sub.okay Geben Sie "ja" (oder nur "j") ein, um den Unterschlüssel zu erzeugen. . .gpg.sign_uid.okay Geben Sie "ja" oder "nein" ein . .gpg.sign_uid.class Wenn Sie die User-ID eines Schlüssels beglaubigen wollen, sollten Sie zunächst sicherstellen, daß der Schlüssel demjenigen gehört, der in der User-ID genannt ist. Für Dritte ist es hilfreich zu wissen, wie gut diese Zuordnung überprüft wurde. "0" zeigt, daß Sie keine bestimmte Aussage über die Sorgfalt der Schlüsselzuordnung machen. "1" Sie glauben, daß der Schlüssel der benannten Person gehört, aber Sie konnten oder nahmen die Überpüfung überhaupt nicht vor. Dies ist hilfreich für eine "persona"-Überprüfung, wobei man den Schlüssel eines Pseudonym-Trägers beglaubigt "2" Sie nahmen eine flüchtige Überprüfung vor. Das heißt Sie haben z.B. den Schlüsselfingerabdruck kontrolliert und die User-ID des Schlüssels anhand des Fotos geprüft. "3" Sie haben eine ausführlich Kontrolle des Schlüssels vorgenommen. Das kann z.B. die Kontrolle des Schlüsselfingerabdrucks mit dem Schlüsselinhaber persönlich vorgenommen haben; daß Sie die User-ID des Schlüssel anhand einer schwer zu fälschenden Urkunde mit Foto (wie z.B. einem Paß) abgeglichen haben und schließlich per Email-Verkehr die Email-Adresse als zum Schlüsselbesitzer gehörig erkannt haben. Beachten Sie, daß diese Beispiele für die Antworten 2 und 3 nur Beispiele sind. Schlußendlich ist es Ihre Sache, was Sie unter "flüchtig" oder "ausführlich" verstehen, wenn Sie Schlüssel Dritter beglaubigen. Wenn Sie nicht wissen, wie Sie antworten sollen, wählen Sie "0". . .gpg.change_passwd.empty.okay Geben Sie "ja" oder "nein" ein . .gpg.keyedit.save.okay Geben Sie "ja" oder "nein" ein . .gpg.keyedit.cancel.okay Geben Sie "ja" oder "nein" ein . .gpg.keyedit.sign_all.okay Geben Sie "ja" (oder nur "j") ein, um alle User-IDs zu beglaubigen . .gpg.keyedit.remove.uid.okay Geben Sie "ja" (oder nur "j") ein, um diese User-ID zu LÖSCHEN. Alle Zertifikate werden dann auch weg sein! . .gpg.keyedit.remove.subkey.okay Geben Sie "ja" (oder nur "j") ein, um diesen Unterschlüssel zu löschen . .gpg.keyedit.delsig.valid Dies ist eine gültige Beglaubigung für den Schlüssel. Es ist normalerweise unnötig sie zu löschen. Sie ist möglicherweise sogar notwendig, um einen Trust-Weg zu diesem oder einem durch diesen Schlüssel beglaubigten Schlüssel herzustellen. . .gpg.keyedit.delsig.unknown Diese Beglaubigung kann nicht geprüft werden, da Sie den passenden Schlüssel nicht besitzen. Sie sollten die Löschung der Beglaubigung verschieben, bis sie wissen, welcher Schlüssel verwendet wurde. Denn vielleicht würde genau diese Beglaubigung den "Trust"-Weg komplettieren. . .gpg.keyedit.delsig.invalid Diese Beglaubigung ist ungültig. Es ist sinnvoll sie aus Ihrem Schlüsselbund zu entfernen. . .gpg.keyedit.delsig.selfsig Diese Beglaubigung bindet die User-ID an den Schlüssel. Normalerweise ist es nicht gut, solche Beglaubigungen zu entfernen. Um ehrlich zu sein: Es könnte dann sein, daß GnuPG diesen Schlüssel gar nicht mehr benutzen kann. Sie sollten diese Eigenbeglaubigung also nur dann entfernen, wenn sie aus irgendeinem Grund nicht gültig ist und eine zweite Beglaubigung verfügbar ist. . .gpg.keyedit.updpref.okay Ändern der Voreinstellung aller User-IDs (oder nur der ausgewählten) auf die aktuelle Liste der Voreinstellung. Die Zeitangaben aller betroffenen Eigenbeglaubigungen werden um eine Sekunde vorgestellt. . .gpg.passphrase.enter Bitte geben Sie die Passphrase ein. Dies ist ein geheimer Satz . .gpg.passphrase.repeat Um sicher zu gehen, daß Sie sich bei der Eingabe der Passphrase nicht vertippt haben, geben Sie diese bitte nochmal ein. Nur wenn beide Eingaben übereinstimmen, wird die Passphrase akzeptiert. . .gpg.detached_signature.filename Geben Sie den Namen der Datei an, zu dem die abgetrennte Unterschrift gehört . .gpg.openfile.overwrite.okay Geben Sie "ja" ein, wenn Sie die Datei überschreiben möchten . .gpg.openfile.askoutname Geben Sie bitte einen neuen Dateinamen ein. Falls Sie nur die Eingabetaste betätigen, wird der (in Klammern angezeigte) Standarddateiname verwendet. . .gpg.ask_revocation_reason.code Sie sollten einen Grund für die Zertifizierung angeben. Je nach Zusammenhang können Sie aus dieser Liste auswählen: "Schlüssel wurde kompromitiert" Falls Sie Grund zu der Annahme haben, daß nicht berechtigte Personen Zugriff zu Ihrem geheimen Schlüssel hatten "Schlüssel ist überholt" Falls Sie diesen Schlüssel durch einem neuen ersetzt haben. "Schlüssel wird nicht mehr benutzt" Falls Sie diesen Schlüssel zurückgezogen haben. "User-ID ist nicht mehr gültig" Um bekanntzugeben, daß die User-ID nicht mehr benutzt werden soll. So weist man normalerweise auf eine ungültige Emailadresse hin. . .gpg.ask_revocation_reason.text Wenn Sie möchten, können Sie hier einen Text eingeben, der darlegt, warum Sie diesen Widerruf herausgeben. Der Text sollte möglichst knapp sein. Eine Leerzeile beendet die Eingabe. . # Local variables: # mode: default-generic # coding: utf-8 # End:	8.8 KB	2017-03-17 08:34
📄 help.el.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.eo.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.es.txt # help.es.txt - es GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Está en su mano asignar un valor aquí. Dicho valor nunca será exportado a terceros. Es necesario para implementar la red de confianza, no tiene nada que ver con la red de certificados (implícitamente creada). . .gpg.edit_ownertrust.set_ultimate.okay Para construir la Red-de-Confianza, GnuPG necesita saber qué claves tienen confianza absoluta - normalmente son las claves para las que usted puede acceder a la clave secreta. Conteste "sí" para hacer que esta clave se considere como de total confianza . .gpg.untrusted_key.override Si quiere usar esta clave no fiable de todos modos, conteste "sí". . .gpg.pklist.user_id.enter Introduzca el ID de usuario al que quiere enviar el mensaje. . .gpg.keygen.algo Seleccione el algoritmo que usar. DSA (alias DSS) es el Algoritmo de Firma Digital y sólo se usa para firmas. Elgamal es un algoritmo sólo para cifrar. RSA sirve tanto para firmar como para cifrar. La primera clave (clave primaria) debe ser siempre de tipo capaz de firmar. . .gpg.keygen.algo.rsa_se En general no es una buena idea usar la misma clave para firmar y cifrar. Este algoritmo debéria usarse solo en ciertos contextos. Por favor consulte primero a un experto en seguridad. . .gpg.keygen.size Introduzca la longitud de la clave . .gpg.keygen.size.huge.okay Responda "sí" o "no" . .gpg.keygen.size.large.okay Responda "sí" o "no" . .gpg.keygen.valid Introduzca el valor requerido conforme se muestra. Es posible introducir una fecha ISO (AAAA-MM-DD), pero no se obtendrá una buena respuesta a los errores; el sistema intentará interpretar el valor introducido como un intervalo. . .gpg.keygen.valid.okay Responda "sí" o "no" . .gpg.keygen.name Introduzca el nombre del dueño de la clave . .gpg.keygen.email Introduzca una dirección de correo electrónico (opcional pero muy recomendable) . .gpg.keygen.comment Introduzca un comentario opcional . .gpg.keygen.userid.cmd N para cambiar el nombre. C para cambiar el comentario. E para cambiar la dirección. O para continuar con la generación de clave. S para interrumpir la generación de clave. . .gpg.keygen.sub.okay Responda "sí" (o sólo "s") para generar la subclave. . .gpg.sign_uid.okay Responda "sí" o "no" . .gpg.sign_uid.class Cuando firme un ID de usuario en una clave, debería verificar que la clave pertenece a la persona que se nombra en el ID de usuario. Es útil para otros saber cómo de cuidadosamente lo ha verificado. "0" significa que no hace ninguna declaración concreta sobre como ha comprobado la validez de la clave. "1" significa que cree que la clave pertenece a la persona que declara poseerla pero no pudo o no verificó la clave en absoluto. Esto es útil para una verificación en persona cuando firmas la clave de un usuario pseudoanónimo. "2" significa que hizo una comprobación informal de la clave. Por ejemplo podría querer decir que comprobó la huella dactilar de la clave y comprobó el ID de usuario en la clave con un ID fotográfico. "3" significa que hizo una comprobación exhaustiva de la clave. Por ejemplo verificando la huella dactilar de la clave con el propietario de la clave, y que comprobó, mediante un documento difícil de falsificar con ID fotográfico (como un pasaporte) que el nombre del poseedor de la clave coincide con el ID de usuario en la clave y finalmente que verificó (intercambiando email) que la dirección de email de la clave pertenece al poseedor de la clave. Observe que los ejemplos dados en los niveles 2 y 3 son solo ejemplos. En definitiva, usted decide lo que significa "informal" y "exhaustivo" para usted cuando firma las claves de otros. Si no sabe qué contestar, conteste "0". . .gpg.change_passwd.empty.okay Responda "sí" o "no" . .gpg.keyedit.save.okay Responda "sí" o "no" . .gpg.keyedit.cancel.okay Responda "sí" o "no" . .gpg.keyedit.sign_all.okay Responda "sí" si quiere firmar TODOS los IDs de usuario . .gpg.keyedit.remove.uid.okay Responda "sí" si realmente quiere borrar este ID de usuario. ¡También se perderán todos los certificados! . .gpg.keyedit.remove.subkey.okay Responda "sí" si quiere borrar esta subclave . .gpg.keyedit.delsig.valid Esta es una firma válida de esta clave. Normalmente no será deseable borrar esta firma ya que puede ser importante para establecer una conexión de confianza con la clave o con otra clave certificada por ésta. . .gpg.keyedit.delsig.unknown Esta firma no puede ser comprobada porque no tiene Vd. la clave correspondiente. Debería posponer su borrado hasta conocer qué clave se usó, ya que dicha clave podría establecer una conexión de confianza a través de otra clave certificada. . .gpg.keyedit.delsig.invalid Esta firma no es válida. Tiene sentido borrarla de su anillo. . .gpg.keyedit.delsig.selfsig Esta es una firma que une el ID de usuario a la clave. No suele ser una buena idea borrar dichas firmas. De hecho, GnuPG podría no ser capaz de volver a usar esta clave. Así que bórrela tan sólo si esta autofirma no es válida por alguna razón y hay otra disponible. . .gpg.keyedit.updpref.okay Cambiar las preferencias de todos los IDs de usuario (o sólo los seleccionados) a la lista actual de preferencias. El sello de tiempo de todas las autofirmas afectadas se avanzará en un segundo. . .gpg.passphrase.enter Por favor introduzca la contraseña: una frase secreta . .gpg.passphrase.repeat Repita la última frase contraseña para asegurarse de lo que tecleó. . .gpg.detached_signature.filename Introduzca el nombre del fichero al que corresponde la firma . .gpg.openfile.overwrite.okay Responda "sí" para sobreescribir el fichero . .gpg.openfile.askoutname Introduzca un nuevo nombre de fichero. Si pulsa INTRO se usará el fichero por omisión (mostrado entre corchetes). . .gpg.ask_revocation_reason.code Debería especificar un motivo para la certificación. Dependiendo del contexto puede elegir una opción de esta lista: "La clave ha sido comprometida" Use esto si tiene razones para pensar que personas no autorizadas tuvieron acceso a su clave secreta. "La clave ha sido sustituida" Use esto si ha reemplazado la clave por otra más nueva. "La clave ya no está en uso" Use esto si ha dejado de usar esta clave. "La identificación de usuario ya no es válida" Use esto para señalar que la identificación de usuario no debería seguir siendo usada; esto se utiliza normalmente para marcar una dirección de correo-e como inválida. . .gpg.ask_revocation_reason.text Si lo desea puede introducir un texto explicando por qué emite este certificado de revocación. Por favor, que el texto sea breve. Una línea vacía pone fin al texto. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.45 KB	2017-03-17 08:34
📄 help.et.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.fi.txt # help.fi.txt - fi GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Tämän arvon määrittäminen on sinun tehtäväsi, tätä arvoa ei koskaan kerrota kolmansille osapuolille. Tarvitsemme sitä toteuttamaan luottamusverkko eikä sillä ei ole mitään tekemistä (epäsuorasti luotujen) varmenneverkkojen kanssa. . .gpg.edit_ownertrust.set_ultimate.okay Rakentaakseen luottamusverkon, GnuPG:n täytyy tietää mihin avaimiin luotetaan ehdottomasti - nämä ovat tavallisesti ne avaimet, joiden salainen pari on sinulla. Vastaa "kyllä" luottaaksesi tähän avaimeen ehdoitta . .gpg.untrusted_key.override Vastaa "kyllä" jos haluat kaikesta huolimatta käyttää tätä epäluotettavaa avainta. . .gpg.pklist.user_id.enter Syötä vastaanottajan, jolle haluat lähettää viestin, käyttäjätunnus. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se Yleensä ei ole järkevää käyttää samaa avainta allekirjoitukseen ja salaamiseen. Tätä algorimiä tulisi käyttää vain määrätyissä ympäristöissä. Ole hyvä ja kysy tietoturva-asiantuntijaltasi ensin . .gpg.keygen.size Syötä avaimen koko . .gpg.keygen.size.huge.okay Vastaa "kyllä" tai " ei" . .gpg.keygen.size.large.okay Vastaa "kyllä" tai " ei" . .gpg.keygen.valid Syötä pyydetty arvo kuten näkyy kehotteessa. On mahdollista syöttää ISO-muotoinen päivä (VVVV-KK-PP), mutta sen seurauksena et saa kunnollista virheilmoitusta vaan järjestelmä yrittää tulkita arvon aikajaksona. . .gpg.keygen.valid.okay Vastaa "kyllä" tai " ei" . .gpg.keygen.name Anna avaimen haltijan nimi . .gpg.keygen.email anna vapaaehtoinen, mutta erittäin suositeltava sähköpostiosoite . .gpg.keygen.comment Kirjoita vapaaehtoinen huomautus . .gpg.keygen.userid.cmd N muuta nimeä C muuta kommenttia E muuta sähköpostiosoitetta O jatka avaimen luomista L lopeta . .gpg.keygen.sub.okay Vastaa "kyllä" (tai vain "k") jos haluat luoda aliavaimen. . .gpg.sign_uid.okay Vastaa "kyllä" tai " ei" . .gpg.sign_uid.class Allekirjoittaessasi avaimen käyttäjätunnuksen sinun tulisi varmista, että avain todella kuuluu henkilölle, joka mainitaan käyttäjätunnuksessa. Muiden on hyvä tietää kuinka huolellisesti olet varmistanut tämän. "0" tarkoittaa, että et väitä mitään siitä, kuinka huolellisesti olet varmistanut avaimen. "1" tarkoittaa, että uskot avaimen kuuluvan henkilölle, joka väittää hallitsevan sitä, mutta et voinut varmistaa tai et varmistanut avainta lainkaan. Tämä on hyödyllinen "persoonan" varmistamiseen, jossa allekirjoitat pseudonyymin käyttäjän avaimen. "2" tarkoittaa arkista varmistusta. Esimerkiksi olet varmistanut avaimen sormenjäljen ja tarkistanut käyttäjätunnuksen ja valokuvatunnisteen täsmäävän. "3" tarkoittaa syvällistä henkilöllisyyden varmistamista. Esimerkiksi tämä voi tarkoittaa avaimen sormenjäljen tarkistamista avaimen haltijan kanssa henkilökohtaisesti, ja että tarkistit nimen avaimessa täsmäävän vaikeasti väärennettävän kuvallisen henkilöllisyystodistuksen (kuten passi) kanssa, ja lopuksi varmistit (sähköpostin vaihtamisella), että sähköpostiosoite kuuluu avaimen haltijalle. Huomaa, että yllä annetut esimerkit tasoille 2 ja 3 ovat todellakin vain esimerkkejä. Lopullisesti se on sinun päätöksesi mitä "arkinen" ja "syvällinen" tarkoittaa allekirjoittaessasi muita avaimia. Jos et tiedä mikä olisi sopiva vastaus, vastaa "0". . .gpg.change_passwd.empty.okay Vastaa "kyllä" tai " ei" . .gpg.keyedit.save.okay Vastaa "kyllä" tai " ei" . .gpg.keyedit.cancel.okay Vastaa "kyllä" tai " ei" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Vastaa "kyllä", jos haluat poistaa tämän käyttäjätunnuksen. Menetät samalla kaikki siihen liittyvät varmenteet! . .gpg.keyedit.remove.subkey.okay Vastaa "kyllä", jos aliavaimen voi poistaa . .gpg.keyedit.delsig.valid Tämä on voimassa oleva allekirjoitus tälle avaimelle, tavallisesti ei kannata poistaa tätä allekirjoitusta koska se saattaa olla tarpeen luottamussuhteen luomiseksi avaimeen tai johonkin toiseen tämän avaimen varmentamaan avaimeen. . .gpg.keyedit.delsig.unknown Allekirjoitusta ei voida tarkistaa koska sinulla ei ole siihen liittyvää avainta. Lykkää sen poistamista kunnes tiedät mitä avainta on käytetty, koska allekirjoitus avain saattaa luoda luottamusketjun toisen, jo ennalta varmennetun avaimen kautta. . .gpg.keyedit.delsig.invalid Allekirjoitus ei ole pätevä. Järkevintä olisi poistaa se avainrenkaastasi. . .gpg.keyedit.delsig.selfsig Tämä allekirjoitus takaa avaimen haltijan henkilöllisyyden. Tällaisen allekirjoituksen poistaminen on tavallisesti huono ajatus. GnuPG ei kenties voi käyttää avainta enää. Poista allekirjoitus vain, jos se ei ole jostain syystä pätevä, ja avaimella on jo toinen allekirjoitus. . .gpg.keyedit.updpref.okay Muuta valinnat kaikille käyttäjätunnuksille (tai vain valituille) nykyiseen luetteloon valinnoista. Kaikkien muutettujen oma-allekirjoitusten aikaleima siirretään yhdellä sekunnilla eteenpäin. . .gpg.passphrase.enter Ole hyvä ja syötä salasana, tämän on salainen lause . .gpg.passphrase.repeat Toista edellinen salasanasi varmistuaksesi siitä, mitä kirjoitit. . .gpg.detached_signature.filename Anna allekirjoitetun tiedoston nimi . .gpg.openfile.overwrite.okay Vastaa "kyllä", jos tiedoston voi ylikirjoittaa . .gpg.openfile.askoutname Syötä uusi tiedostonimi. Jos painat vain RETURN, käytetään oletustiedostoa (joka näkyy sulkeissa). . .gpg.ask_revocation_reason.code Sinun tulisi määrittää syy varmenteelle. Riippuen asiayhteydestä voit valita tästä listasta: "Avain on paljastunut" Käytä tätä, jos sinulla on syytä uskoa, että luvattomat henkilöt ovat saaneet salaisen avaimesi käsiinsä. "Avain on korvattu" Käytä tätä, jos olet korvannut tämän uudemmalla avaimella. "Avain ei ole enää käytössä" Käytä tätä, jost ole lopettanut tämän avaimen käytön. "Käyttäjätunnus ei ole enää voimassa" Käytä tätä ilmoittamaan, että käyttäjätunnusta ei pitäisi käyttää; tätä normaalisti käytetään merkitsemään sähköpostiosoite vanhenneeksi. . .gpg.ask_revocation_reason.text Halutessasi voit kirjoittaa tähän kuvauksen miksi julkaiset tämän mitätöintivarmenteen. Kirjoita lyhyesti. Tyhjä rivi päättää tekstin. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.56 KB	2017-03-17 08:34
📄 help.fr.txt # help.fr.txt - fr GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value C'est à vous d'assigner une valeur ici; cette valeur ne sera jamais envoyée à une tierce personne. Nous en avons besoin pour créer le réseau de confiance (web-of-trust); cela n'a rien à voir avec le réseau des certificats (créé implicitement) . .gpg.edit_ownertrust.set_ultimate.okay Pour mettre en place le Réseau de confiance (Web of Trust), GnuPG a besoin de savoir en quelles clés votre confiance est ultime - ce sont en général les clés dont vous avez accès à la clé secrète. Répondez "oui" pour indiquer que votre confiance en cette clé est ultime . .gpg.untrusted_key.override Si vous voulez utiliser cette clé peu sûre quand-même, répondez «oui». . .gpg.pklist.user_id.enter Entrez le nom d'utilisateur de la personne à qui vous voulez envoyer le message. . .gpg.keygen.algo Sélectionnez l'algorithme à utiliser. DSA (connu également sous le nom de DSS) est un algorithme de signature digitale et ne peut être utilisé que pour des signatures. Elgamal est un algorithme pour le chiffrement seul. RSA peut être utilisé pour les signatures et le chiffrement. La première clé (clé principale) doit toujours être une clé capable de signer. . .gpg.keygen.algo.rsa_se En général ce n'est pas une bonne idée d'utiliser la même clé pour signer et pour chiffrer. Cet algorithme ne doit être utilisé que pour certains domaines. Consultez votre expert en sécurité d'abord. . .gpg.keygen.size Entrez la taille de la clé . .gpg.keygen.size.huge.okay Répondez «oui» ou «non» . .gpg.keygen.size.large.okay Répondez «oui» ou «non» . .gpg.keygen.valid Entrez la valeur demandée comme indiqué dans la ligne de commande. On peut entrer une date ISO (AAAA-MM-JJ) mais le résultat d'erreur sera mauvais - le système essaierait d'interpréter la valeur donnée comme un intervalle. . .gpg.keygen.valid.okay Répondez «oui» ou «non» . .gpg.keygen.name Entrez le nom du propriétaire de la clé . .gpg.keygen.email entrez une adresse e-mail optionnelle mais hautement recommandée . .gpg.keygen.comment Entrez un commentaire optionnel . .gpg.keygen.userid.cmd N pour changer le nom. C pour changer le commentaire. E pour changer l'adresse e-mail. O pour continuer à générer la clé. Q pour arrêter de générer de clé. . .gpg.keygen.sub.okay Répondez «oui» (ou simplement «o») pour générer la sous-clé . .gpg.sign_uid.okay Répondez «oui» ou «non» . .gpg.sign_uid.class Quand vous signez un nom d'utilisateur d'une clé, vous devriez d'abord vérifier que la clé appartient à la personne nommée. Il est utile que les autres personnes sachent avec quel soin vous l'avez vérifié. "0" signifie que vous n'avez pas d'opinon. "1" signifie que vous croyez que la clé appartient à la personne qui dit la posséder mais vous n'avez pas pu vérifier du tout la clé. C'est utile lorsque vous signez la clé d'un pseudonyme. "2" signifie que vous avez un peu vérifié la clé. Par exemple, cela pourrait être un vérification de l'empreinte et du nom de l'utilisateur avec la photo. "3" signifie que vous avez complètement vérifié la clé. Par exemple, cela pourrait être une vérification de l'empreinte, du nom de l'utilisateur avec un document difficile à contrefaire (comme un passeport) et de son adresse e-mail (vérifié par un échange de courrier électronique). Notez bien que les exemples donnés ci-dessus pour les niveaux 2 et 3 ne sont que des exemples. C'est à vous de décider quelle valeur mettre quand vous signez les clés des autres personnes. Si vous ne savez pas quelle réponse est la bonne, répondez "0". . .gpg.change_passwd.empty.okay Répondez «oui» ou «non» . .gpg.keyedit.save.okay Répondez «oui» ou «non» . .gpg.keyedit.cancel.okay Répondez «oui» ou «non» . .gpg.keyedit.sign_all.okay Répondez «oui» si vous voulez signer TOUS les noms d'utilisateurs . .gpg.keyedit.remove.uid.okay Répondez «oui» si vous voulez vraiment supprimer ce nom d'utilisateur. Tous les certificats seront alors perdus en même temps ! . .gpg.keyedit.remove.subkey.okay Répondez «oui» s'il faut vraiment supprimer la sous-clé . .gpg.keyedit.delsig.valid C'est une signature valide dans la clé; vous n'avez pas normalement intérêt à supprimer cette signature car elle peut être importante pour établir une connection de confiance vers la clé ou une autre clé certifiée par celle-là. . .gpg.keyedit.delsig.unknown Cette signature ne peut pas être vérifiée parce que vous n'avez pas la clé correspondante. Vous devriez remettre sa supression jusqu'à ce que vous soyez sûr de quelle clé a été utilisée car cette clé de signature peut établir une connection de confiance vers une autre clé déjà certifiée. . .gpg.keyedit.delsig.invalid Cette signature n'est pas valide. Vous devriez la supprimer de votre porte-clés. . .gpg.keyedit.delsig.selfsig Cette signature relie le nom d'utilisateur à la clé. Habituellement enlever une telle signature n'est pas une bonne idée. En fait GnuPG peut ne plus être capable d'utiliser cette clé. Donc faites ceci uniquement si cette auto-signature est invalide pour une certaine raison et si une autre est disponible. . .gpg.keyedit.updpref.okay Changer les préférences de tous les noms d'utilisateurs (ou juste ceux qui sont sélectionnés) vers la liste actuelle. La date de toutes les auto-signatures affectées seront avancées d'une seconde. . .gpg.passphrase.enter Entrez le mot de passe ; c'est une phrase secrète . .gpg.passphrase.repeat Répétez la dernière phrase de passe pour être sûr de ce que vous avez tapé. . .gpg.detached_signature.filename Donnez le nom du fichier auquel la signature se rapporte . .gpg.openfile.overwrite.okay Répondez «oui» s'il faut vraiment réécrire le fichier . .gpg.openfile.askoutname Entrez le nouveau nom de fichier. Si vous tapez simplement ENTRÉE le fichier par défaut (indiqué entre crochets) sera utilisé. . .gpg.ask_revocation_reason.code Vous devriez donner une raison pour la certification. Selon le contexte vous pouvez choisir dans cette liste: «La clé a été compromise» Utilisez cette option si vous avez une raison de croire que des personnes ont pu accéder à votre clé secrète sans autorisation. «La clé a été remplacée» Utilisez cette option si vous avez remplacé la clé par une nouvelle. «La clé n'est plus utilisée» Utilisez cette option si cette clé n'a plus d'utilité. «Le nom d'utilisateur n'est plus valide» Utilisez cette option si le nom d'utilisateur ne doit plus être utilisé. Cela sert généralement à indiquer qu'une adresse e-mail est invalide. . .gpg.ask_revocation_reason.text Si vous le désirez, vous pouvez entrer un texte qui explique pourquoi vous avez émis ce certificat de révocation. Essayez de garder ce texte concis. Une ligne vide délimite la fin du texte. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.61 KB	2017-03-17 08:34
📄 help.gl.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.hu.txt # help.hu.txt - hu GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Az Ön döntésén múlik, hogy milyen értéket ad meg itt. Ezt az értéket soha nem exportáljuk mások részére. Ez a bizalmak hálózatához (web-of-trust) szükséges, semmi köze az igazolások hálózatához (web-of-certificates). . .gpg.edit_ownertrust.set_ultimate.okay Hogy a bizalmak hálózatát felépítsük, a GnuPG-nek tudnia kell, hogy mely kulcsok alapvetően megbízhatóak - általában ezek azok a kulcsok, melyek titkos kulcsához hozzáfér. Válaszoljon "igen"-nel, ha kulcsot alapvetően megbízhatónak jelöli! . .gpg.untrusted_key.override Ha mégis használni akarja ezt a kulcsot, melyben nem bízunk, válaszoljon "igen"-nel! . .gpg.pklist.user_id.enter Adja meg a címzett felhasználói azonosítóját! . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se Általában nem jó ötlet ugyanazt a kulcsot használni aláíráshoz és titkosításhoz. Ezt az algoritmust csak bizonyos területeken ajánlatos használni. Kérem, először konzultáljon a biztonsági szakértőjével! . .gpg.keygen.size Adja meg a kulcs méretét! . .gpg.keygen.size.huge.okay Kérem, adjon "igen" vagy "nem" választ! . .gpg.keygen.size.large.okay Kérem, adjon "igen" vagy "nem" választ! . .gpg.keygen.valid Adja meg a szükséges értéket, ahogy a prompt mutatja! Lehetséges ISO dátumot is beírni (ÉÉÉÉ-HH-NN), de nem fog rendes hibaüzenetet kapni, hanem a rendszer megpróbálja az értéket intervallumként értelmezni. . .gpg.keygen.valid.okay Kérem, adjon "igen" vagy "nem" választ! . .gpg.keygen.name Adja meg a kulcs tulajdonosának a nevét! . .gpg.keygen.email Kérem, adjon meg egy opcionális, de nagyon ajánlott e-mail címet! . .gpg.keygen.comment Kérem, adjon meg egy opcionális megjegyzést! . .gpg.keygen.userid.cmd N név változtatása M megjegyzés változtatása E e-mail változtatása R kulcsgenerálás folytatása Q kilépés a kulcsgenerálásból . .gpg.keygen.sub.okay Válaszoljon "igen"-nel (vagy csak "i"-vel), ha kezdhetjük az alkulcs létrehozását! . .gpg.sign_uid.okay Kérem, adjon "igen" vagy "nem" választ! . .gpg.sign_uid.class Mielőtt aláír egy felhasználói azonosítót egy kulcson, ellenőriznie kell, hogy a kulcs a felhasználói azonosítóban megnevezett személyhez tartozik. Mások számára hasznos lehet, ha tudják, hogy milyen gondosan ellenőrizte Ön ezt. "0" azt jelenti, hogy nem tesz az ellenőrzés gondosságára vonatkozó kijelentést. "1" azt jelenti, hogy Ön hiszi, hogy a kulcs annak a személynek a tulajdona, aki azt állítja, hogy az övé, de Ön nem tudta ezt ellenőrizni, vagy egyszerűen nem ellenőrizte ezt. Ez hasznos egy "persona" típusú ellenőrzéshez, mikor Ön egy pszeudonim felhasználó kulcsát írja alá. "2" azt jelenti, hogy Ön a kulcsot hétköznapi alapossággal ellenőrizte. Például ez azt jelentheti, hogy ellenőrizte a kulcs ujjlenyomatát, és összevetette a kulcson szereplő felhasználóazonosítót egy fényképes igazolvánnyal. "3" azt jelenti, hogy alaposan ellenőrizte a kulcsot. Például ez azt jelentheti, hogy a kulcs ujjlenyomatát a tulajdonossal személyesen találkozva ellenőrizte, egy nehezen hamisítható, fényképes igazolvánnyal (mint az útlevél) meggyőződött arról, hogy a személy neve egyezik a kulcson levővel, és végül (e-mail váltással) ellenőrizte, hogy a kulcson szereplő e-mail cím a kulcs tulajdonosához tartozik. A 2-es és 3-as szintekhez adott példák csak példák. Végső soron Ön dönti el, hogy mit jelentenek Önnek a "hétköznapi" és "alapos" kifejezések, amikor mások kulcsát aláírja. Ha nem tudja, hogy mit válaszoljon, írjon "0"-t! . .gpg.change_passwd.empty.okay Kérem, adjon "igen" vagy "nem" választ! . .gpg.keyedit.save.okay Kérem, adjon "igen" vagy "nem" választ! . .gpg.keyedit.cancel.okay Kérem, adjon "igen" vagy "nem" választ! . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Válaszoljon "igen"-nel, ha valóban törölni akarja ezt a felhasználóazonosítót! Minden igazolás törlődik vele együtt! . .gpg.keyedit.remove.subkey.okay Válaszoljon "igen"-nel, ha az alkulcs törölhető. . .gpg.keyedit.delsig.valid Ez egy érvényes aláírás a kulcson. Normál esetben nincs értelme törölni, mert fontos lehet ahhoz, hogy érvényesítse ezt a kulcsot, vagy egy másikat, melyet ezzel a kulccsal igazolnak. . .gpg.keyedit.delsig.unknown Ezt az aláírást nem tudom ellenőrizni, mert nincs meg a hozzá tartozó kulcs. Ajánlatos lenne elhalasztani a törlést addig, amíg meg nem tudja, hogy melyik kulcsot használták, mert ez az aláíró kulcs bizalmi kapcsolatot hozhat létre egy már hitelesített kulcson keresztül. . .gpg.keyedit.delsig.invalid Ez az aláírás nem érvényes. Értelmetlen eltávolítani a kulcskarikáról. . .gpg.keyedit.delsig.selfsig Ez egy olyan aláírás, amely összeköti a felhasználóazonosítót a kulccsal. Általában nem jó ötlet egy ilyen aláírást eltávolítani. Az is lehetséges, hogy a GnuPG többé nem tudja használni ezt a kulcsot. Csak akkor tegye ezt, ha valami okból ez az önaláírás nem érvényes, és rendelkezésre áll egy másik! . .gpg.keyedit.updpref.okay Lecseréli az összes felhasználóazonosítóhoz (vagy csak a kijelöltekhez) tartozó preferenciákat az aktuális preferenciákra. Minden érintett önaláírás időpontját egy másodperccel növeli. . .gpg.passphrase.enter Kérem, adja meg a jelszót! Ezt egy titkos mondat. . .gpg.passphrase.repeat Kérem, ismételje meg az előző jelszót ellenőrzésképpen! . .gpg.detached_signature.filename Adja meg az állomány nevét, melyhez az aláírás tartozik! . .gpg.openfile.overwrite.okay Válaszoljon "igen"-nel, ha felülírható az állomány! . .gpg.openfile.askoutname Kérem, adjon meg egy új fájlnevet! Ha RETURN-t/ENTER-t nyom, akkor a szögletes zárójelben levő alapértelmezett nevet használom. . .gpg.ask_revocation_reason.code Ajánlatos megadni a visszavonás okát. A helyzettől függően válasszon a következő listából: "A kulcs kompromittálódott." Használja ezt akkor, ha oka van azt hinni, hogy titkos kulcsa illetéktelen kezekbe került! "A kulcsot lecserélték." Használja ezt akkor, ha a kulcsot lecserélte egy újabbra! "A kulcs már nem használatos." Használja ezt akkor, ha már nem használja a kulcsot! "A felhasználóazonosító már nem érvényes." Használja ezt akkor, ha azt állítja, hogy a felhasználóazonosító már nem használatos! Általában érvénytelen e-mail címet jelent. . .gpg.ask_revocation_reason.text Ha akarja, megadhat egy szöveget, melyben megindokolja, hogy miért adta ki ezt a visszavonó igazolást. Kérem, fogalmazzon tömören! Egy üres sor jelzi a szöveg végét. . # Local variables: # mode: fundamental # coding: utf-8 # End:	8.01 KB	2017-03-17 08:34
📄 help.id.txt # help.id.txt - id GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Terserah anda untuk memberi nilai baru di sini; nilai ini tidak akan diekspor ke pihak ketiga. Kami perlu untuk mengimplementasikan web-of-trust; tidak ada kaitan dengan (membuat secara implisit) web-of-certificates. . .gpg.edit_ownertrust.set_ultimate.okay Untuk membuat Web-of-Trust, GnuPG perlu tahu kunci mana yang sangat dipercaya - mereka biasanya adalah kunci yang anda punya akses ke kunci rahasia. Jawab "yes" untuk menset kunci ini ke sangat dipercaya . .gpg.untrusted_key.override Jika anda ingin menggunakan kunci tidak terpercaya ini, jawab "ya". . .gpg.pklist.user_id.enter Masukkan ID user penerima pesan. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se Secara umum bukan ide baik untuk menggunakan kunci yang sama untuk menandai dan mengenkripsi. Algoritma ini seharusnya digunakan dalam domain tertentu. Silakan berkonsultasi dulu dengan ahli keamanan anda. . .gpg.keygen.size Masukkan ukuran kunci . .gpg.keygen.size.huge.okay Jawab "ya" atau "tidak" . .gpg.keygen.size.large.okay Jawab "ya" atau "tidak" . .gpg.keygen.valid Masukkan nilai yang diperlukan seperti pada prompt. Dapat digunakan format (YYYY-MM-DD) untuk mengisi tanggal ISO tetapi anda tidak akan mendapat respon kesalahan yang baik - sebaiknya sistem akan berusaha menginterprestasi nilai yang diberikan sebagai sebuah interval. . .gpg.keygen.valid.okay Jawab "ya" atau "tidak" . .gpg.keygen.name Masukkan nama pemegang kunci . .gpg.keygen.email silakan masukkan alamat email (pilihan namun sangat dianjurkan) . .gpg.keygen.comment Silakan masukkan komentar tambahan . .gpg.keygen.userid.cmd N untuk merubah nama. K untuk merubah komentar. E untuk merubah alamat email. O untuk melanjutkan dengan pembuatan kunci. K untuk menghentikan pembuatan kunci. . .gpg.keygen.sub.okay Jawab "ya" (atau "y") jika telah siap membuat subkey. . .gpg.sign_uid.okay Jawab "ya" atau "tidak" . .gpg.sign_uid.class Ketika anda menandai user ID pada kunci, anda perlu memverifikasi bahwa kunci milik orang yang disebut dalam user ID. Ini penting bagi orang lain untuk tahu seberapa cermat anda memverifikasi ini. "0" berarti anda tidak melakukan klaim tentang betapa cermat anda memverifikasi kunci. "1" berarti anda percaya bahwa kunci dimiliki oleh orang yang mengklaim memilikinya namun anda tidak dapat, atau tidak memverifikasi kunci sama sekali. Hal ini bergunabagi verifikasi "persona", yaitu anda menandai kunci user pseudonymous "2" berarti anda melakukan verifikasi kasual atas kunci. Sebagai contoh, halini dapat berarti bahwa anda memverifikasi fingerprint kunci dan memeriksa user ID pada kunci dengan photo ID. "3" berarti anda melakukan verifikasi ekstensif atas kunci. Sebagai contoh, hal ini dapat berarti anda memverifikasi fingerprint kunci dengan pemilik kunci secara personal, dan anda memeriksa, dengan menggunakan dokumen yang sulit dipalsukan yang memiliki photo ID (seperti paspor) bahwa nama pemilik kunci cocok dengan nama user ID kunci, dan bahwa anda telah memverifikasi (dengan pertukaran email) bahwa alamat email pada kunci milik pemilik kunci. Contoh-contoh pada level 2 dan 3 hanyalah contoh. Pada akhirnya, terserah anda untuk memutuskan apa arti "kasual" dan "ekstensif" bagi anda ketika menandai kunci lain. Jika anda tidak tahu jawaban yang tepat, jawab "0". . .gpg.change_passwd.empty.okay Jawab "ya" atau "tidak" . .gpg.keyedit.save.okay Jawab "ya" atau "tidak" . .gpg.keyedit.cancel.okay Jawab "ya" atau "tidak" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Jawab "ya" jika anda benar-benar ingin menghapus ID user ini. Seluruh sertifikat juga akan hilang! . .gpg.keyedit.remove.subkey.okay Jawab "ya" jika ingin menghapus subkey . .gpg.keyedit.delsig.valid Ini adalah signature valid untuk kunci; anda normalnya tdk ingin menghapus signature ini karena mungkin penting membangun koneksi trust ke kunci atau ke kunci tersertifikasi lain dengan kunci ini. . .gpg.keyedit.delsig.unknown Signature ini tidak dapat diperiksa karena anda tidak memiliki kunci korespondennya. Anda perlu menunda penghapusannya hingga anda tahu kunci yang digunakan karena kunci penanda ini mungkin membangun suatu koneksi trust melalui kunci yang telah tersertifikasi lain. . .gpg.keyedit.delsig.invalid Signature tidak valid. Adalah hal yang masuk akal untuk menghapusnya dari keyring anda . .gpg.keyedit.delsig.selfsig Ini adalah signature yang menghubungkan ID pemakai ke kunci. Biasanya bukan ide yang baik untuk menghapus signature semacam itu. Umumnya GnuPG tidak akan dapat menggunakan kunci ini lagi. Sehingga lakukan hal ini bila self-signature untuk beberapa alasan tidak valid dan tersedia yang kedua. . .gpg.keyedit.updpref.okay Rubah preferensi seluruh user ID (atau hanya yang terpilih) ke daftar preferensi saat ini. Timestamp seluruh self-signature yang terpengaruh akan bertambah satu detik. . .gpg.passphrase.enter Silakan masukkan passphrase; ini kalimat rahasia . .gpg.passphrase.repeat Silakan ulangi passphrase terakhir, sehingga anda yakin yang anda ketikkan. . .gpg.detached_signature.filename Beri nama file tempat berlakunya signature . .gpg.openfile.overwrite.okay Jawab "ya" jika tidak apa-apa menimpa file . .gpg.openfile.askoutname Silakan masukan nama file baru. Jika anda hanya menekan RETURN nama file baku (yang diapit tanda kurung) akan dipakai. . .gpg.ask_revocation_reason.code Anda harus menspesifikasikan alasan pembatalan. Semua ini tergantung konteks, anda dapat memilih dari daftar berikut: "Key has been compromised" Gunakan ini jika anda punya alasan untuk percaya bahwa orang yang tidak berhak memiliki akses ke kunci pribadi anda. "Key is superseded" Gunakan ini bila anda mengganti kunci anda dengan yang baru. "Key is no longer used" Gunakan ini bila anda telah mempensiunkan kunci ini. "User ID is no longer valid" Gunakan ini untuk menyatakan user ID tidak boleh digunakan lagi; normalnya digunakan untuk menandai bahwa alamat email tidak valid lagi. . .gpg.ask_revocation_reason.text Jika anda suka, anda dapat memasukkan teks menjelaskan mengapa anda mengeluarkan sertifikat pembatalan ini. Buatlah ringkas. Baris kosong mengakhiri teks. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.36 KB	2017-03-17 08:34
📄 help.it.txt # help.it.txt - Italian GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value E compito tuo assegnare un valore; questo valore non sarà mai esportato a terzi. Ci serve per implementare il web-of-trust; non ha nulla a che fare con il web-of-certificates (creato implicitamente). . .gpg.edit_ownertrust.set_ultimate.okay Per costruire il Web-Of-Trust, GnuPG ha bisogno di sapere quali chiavi sono definitivamente affidabili - di solito quelle per cui hai accesso alla chiave segreta. Rispondi "sì" per impostare questa chiave come definitivamente affidabile . .gpg.untrusted_key.override Se vuoi usare comunque questa chiave non fidata, rispondi "si". . .gpg.pklist.user_id.enter Inserisci l'user ID del destinatario a cui vuoi mandare il messaggio. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se In generale non è una buona idea usare la stessa chiave per le firme e la cifratura. Questo algoritmo dovrebbe solo essere usato in determinati campi. Per favore consulta prima il tuo esperto di sicurezza. . .gpg.keygen.size Inserisci le dimensioni della chiave . .gpg.keygen.size.huge.okay Rispondi "si" o "no" . .gpg.keygen.size.large.okay Rispondi "si" o "no" . .gpg.keygen.valid Inserisci il valore richiesto come indicato dal prompt. È possibile inserire una data in formato ISO (YYYY-MM-DD) ma non avrai un messaggio di errore corretto: il sistema cerca di interpretare il valore dato come un intervallo. . .gpg.keygen.valid.okay Rispondi "si" o "no" . .gpg.keygen.name Inserisci il nome del proprietario della chiave . .gpg.keygen.email Inserisci un indirizzo di email opzionale (ma fortemente suggerito) . .gpg.keygen.comment Inserisci un commento opzionale . .gpg.keygen.userid.cmd N per cambiare il nome. C per cambiare il commento. E per cambiare l'indirizzo di email. O per continuare con la generazione della chiave. Q per abbandonare il processo di generazione della chiave. . .gpg.keygen.sub.okay Rispondi "si" (o "y") se va bene generare la subchiave. . .gpg.sign_uid.okay Rispondi "si" o "no" . .gpg.sign_uid.class Quando firmi l'user ID di una chiave dovresti prima verificare che questa appartiene alla persona indicata nell'user ID. È utile agli altri sapere con quanta attenzione lo hai verificato. "0" significa che non fai particolari affermazioni sull'attenzione con cui hai ferificato la chiave. "1" significa che credi che la chiave sia posseduta dalla persona che dice di possederla, ma non hai o non hai potuto verificare per niente la chiave. "2" significa che hai fatto una verifica superficiale della chiave. Per esempio potrebbe significare che hai verificato l'impronta digitale e confrontato l'user ID della chiave con un documento di identità con fotografia. "3" significa che hai fatto una verifica approfondita della chiave. Per esempio potrebbe significare che hai verificato di persona l'impronta digitale con il possessore della chiave e hai controllato, per esempio per mezzo di un documento di identità con fotografia difficile da falsificare (come un passaporto), che il nome del proprietario della chiave corrisponde a quello nell'user ID della chiave, e per finire che hai verificato (scambiando dei messaggi) che l'indirizzo di email sulla chiave appartiene al proprietario. Nota che gli esempi indicati per i livelli 2 e 3 sono solo esempi. Alla fine sta a te decidere cosa significano "superficiale" e "approfondita" quando firmi chiavi di altri. Se non sai cosa rispondere, rispondi "0". . .gpg.change_passwd.empty.okay Rispondi "si" o "no" . .gpg.keyedit.save.okay Rispondi "si" o "no" . .gpg.keyedit.cancel.okay Rispondi "si" o "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Rispondi "si" se vuoi davvero cancellare questo user ID. Tutti i certificati saranno persi! . .gpg.keyedit.remove.subkey.okay Rispondi "si" se va bene cancellare la subchiave . .gpg.keyedit.delsig.valid Questa è una firma valida per la chiave. Normalmente non vorresti cancellare questa firma perchè può essere importante per stabilire una connessione di fiducia alla chiave o a un'altra chiave certificata da questa chiave. . .gpg.keyedit.delsig.unknown Questa firma non può essere verificata perchè non hai la chiave corrispondente. Dovresti rimandare la sua cancellazione finchè non saprai quale chiave è stata usata perchè questa chiave potrebbe stabilire una connessione di fiducia attraverso una chiave già certificata. . .gpg.keyedit.delsig.invalid La firma non è valida. Ha senso rimuoverla dal tuo portachiavi. . .gpg.keyedit.delsig.selfsig Questa è una firma che collega l'user id alla chiave. Solitamente non è una buona idea rimuovere questo tipo di firma. In realtà GnuPG potrebbe non essere più in grado di usare questa chiave. Quindi fallo solo se questa autofirma non è valida per qualche ragione e ne è disponibile un'altra. . .gpg.keyedit.updpref.okay Cambia le preferenze di tutti gli user ID (o solo di quelli selezionati) con la lista di preferenze corrente. L'orario di tutte le autofirme coinvolte sarà aumentato di un secondo. . .gpg.passphrase.enter Inserisci la passphrase, cioè una frase segreta . .gpg.passphrase.repeat Ripeti l'ultima passphrase per essere sicuro di cosa hai scritto. . .gpg.detached_signature.filename Inserisci il nome del file a cui si riferisce la firma. . .gpg.openfile.overwrite.okay Rispondi "si" se va bene sovrascrivere il file. . .gpg.openfile.askoutname Inserisci il nuovo nome del file. Se premi INVIO sarà usato il nome predefinito (quello indicato tra parentesi). . .gpg.ask_revocation_reason.code Dovresti specificare un motivo per questa certificazione. A seconda del contesto hai la possibilità di scegliere tra questa lista: "Key has been compromised" Usa questo se hai un motivo per credere che una persona non autorizzata abbia avuto accesso alla tua chiave segreta. "Key is superseded" Usa questo se hai sostituito questa chiave con una più recente. "Key is no longer used" Usa questo se hai mandato in pensione questa chiave. "User ID is no longer valid" Usa questo per affermare che l'user ID non dovrebbe più essere usato; solitamente è usato per indicare un indirizzo di email non valido. . .gpg.ask_revocation_reason.text Se vuoi, puoi digitare un testo che descrive perché hai emesso questo certificato di revoca. Per favore sii conciso. Una riga vuota termina il testo. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.51 KB	2017-03-17 08:34
📄 help.ja.txt # help.ja.txt - Japanese GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#pinentry.qualitybar.tooltip # [ このエントリは有効にするには、上記のキーの # を削除してください。] # これは例です。このバーは、入力されたパスフレーズの品質を示しています。バーが赤い色となっている場合、GnuPGはパスフレーズが弱すぎると判断し、受け付けません。管理者にパスフレーズの制限の設定について詳細を問い合わせてください。 . .gnupg.agent-problem # There was a problem accessing or starting the agent. 動作中のGpg-Agentへの接続ができなかったか、通信の問題が発生しました。システムは、Gpg-Agentと呼ばれるバックグラウンド・プロセスを利用し、秘密鍵とパスフレーズの問い合わせを処理します。このエージェントは通常、ユーザがログインするときに開始され、ログインしている間、動いています。もし、エージェントが利用可能でない場合、システムは、その場でエージェントの起動を試しますが、この場合、機能がやや制限され、若干の問題がある場合があります。もしかしたら、管理者に問い合わせて、この問題をどのように解決したら良いか聞いた方が良いかもしれません。とりあえずの方策としては、一度ログアウトしてもう一度ログインし、改善が見られるか試してみることがあります。もし、これがうまくいくようであれば管理者に報告してください。それはおそらく、ソフトウェアのバグであることを示していますので。 . .gnupg.dirmngr-problem # There was a problen accessing the dirmngr. 動作中のDirmngrへの接続ができなかったか、通信の問題が発生しました。証明書失効リスト(CRL)を検索し、OCSPの検証とLDAPサーバを通じて鍵を検索するため、システムは、Dirmngrと呼ばれる外部サービス・プログラムを利用します。Dirmngrは通常、システムサービス(daemon)として実効されます、一般ユーザは気にする必要はありません。問題がある場合、システムは、要求に応じて、 Dirmngrを起動することがありますが、これは対応策であり、性能に制限が生じます。この問題がある場合、システム管理者に連絡し、どのように進めたら良いか問い合わせてください。とりあえずの解決策としては、gpgsmの設定でCRLの検証を停止させることが考えられます。 . .gpg.edit_ownertrust.value ここでの値の指定は、あなたに任されています。この値は、第三者に開示されることは決してありません。ウェブ・オブ・トラストを実装するためにこの値が必要となりますが、(暗黙的に作られる)証明書の網には何も関係しません。 . .gpg.edit_ownertrust.set_ultimate.okay ウェブ・オブ・トラストを構築するためにGnuPGは、どの鍵が究極的に信頼できるかを知る必要があります。その鍵は通常は、あなたが秘密鍵へアクセスできるものです。この鍵が究極的に信頼できる場合、"yes" と答えてください。 . .gpg.untrusted_key.override この信頼されてない鍵をどちらにせよ使いたい場合、"yes" と答えてください。 . .gpg.pklist.user_id.enter このメッセージを送りたい宛先のユーザIDを入力してください。 . .gpg.keygen.algo 使用するアルゴリズムを選択してください。 DSA (別名 DSS)は電子署名アルゴリズムであり、署名にのみ使えます。 Elgamal は暗号化のみのアルゴリズムです。 RSA は署名と暗号化のどちらにも使えます。主鍵は常に、署名が可能の鍵である必要があります。 . .gpg.keygen.algo.rsa_se 一般的に、署名と暗号化に同一の鍵を用いることは良いことではありません。このアルゴリズムはある特定の領域だけに使うべきです。まず、セキュリティの専門家に相談してください。 . .gpg.keygen.cardkey カードからどの鍵を使用するか選択する。リストには、選択の番号、keygrip (16進数の文字列)、カード固有の鍵参照、この鍵に使うアルゴリズム、そして、鍵の使用目的(cert, sign, auth, encr) が括弧内に示されます。鍵の標準的な使用がわかっている場合には、アスタリスクでマークされます。. .gpg.keygen.flags 鍵の機能をトグルする。選択されたアルゴリズムで可能な機能だけがトグルできます。すばやく一度ですべての機能を設定するには、'=' の文字を最初の文字として、続けて設定する機能の列を入力します: 's' は署名、'e' は暗号化、'a'は認証です。無効な文字と不可能な機能は無視されます。このサブメニューはこのショートカットを利用したのちにただちに閉じられます。 . .gpg.keygen.size 鍵の長さを入力してください。提案されたデフォルトが通常良い選択です。大きな鍵長を使いたい場合、たとえば4096ビットなど、本当に意味があるか再検討してください。こちらのウェブページを見るのも良いと思います: http://www.xkcd.com/538/ . .gpg.keygen.size.huge.okay "yes" か "no" で答えてください。 . .gpg.keygen.size.large.okay "yes" か "no" で答えてください。 . .gpg.keygen.valid プロンプトで示された必要な値を入力してください。 ISO形式の日付(YYYY-MM-DD)の入力が可能ですが、わかりやすいエラーの反応が得られないままにシステムが与えられた値を期間と解釈して扱うことがあります。 .gpg.keygen.valid.okay "yes" か "no" で答えてください。 . .gpg.keygen.name 鍵の持ち主の名前を入力してください。文字 "<" と ">" は許されていません。例: Heinrich Heine . .gpg.keygen.email オプションですが推奨される電子メールアドレスを入力してください。例: heinrichh@duesseldorf.de . .gpg.keygen.comment オプションのコメントを入力してください。文字 "(" と ")" は許されていません。一般的にコメントは必要ではありません。 . .gpg.keygen.userid.cmd # (Keep a leading empty line) N 名前の変更。 C コメントの変更。 E 電子メールアドレスの変更。 O 鍵生成に進む。 Q 鍵生成を止める。 . .gpg.keygen.sub.okay 副鍵を生成してよければ、"yes" (あるいは単に "y") と答えてください。 . .gpg.sign_uid.okay "yes" か "no" で答えてください。 . .gpg.sign_uid.class ある鍵のユーザIDに署名するとき、まず、その鍵がそのユーザIDの人に属するかどうかをあなたは確認しなければなりません。あなたがどれくらいこれを慎重に確認したかについて、ほかの人が知ることは有用です。 "0" は、どれくらい慎重に確認したかについて特になにも主張しないことを意味します。 "1" は、主張するその人が所有する鍵であるとあなたは信じるが、その鍵について、検証できなかった、あるいはしなかったことを意味します。これは、ペンネームのユーザの鍵に署名するような "persona" 確認に有用です。 "2" は、その鍵に対し、通常の検証を行ったことを意味します。たとえば、鍵のフィンガープリントを確認し、写真付きIDでユーザIDを確認したことを意味します。 "3" は、その鍵に対し、広範な検証を行ったことを意味します。たとえば、鍵のフィンガープリントを対面で確認し、パスポートなど偽造することが難しい写真付きIDでユーザIDを確認し、所有者の名前が鍵のユーザIDに適合し、メールの交換で、メールアドレスが所有者に属することを確認したことを意味します。上記のレベル2とレベル3で示した例は、単に例であることに注意してください。結局は、ほかの鍵に署名するとき、なにがあなたにとって「通常」で、なにが「広範」かをを決めるのは、あなた自身に任されています。正しい答えがなにかわからないときは "0" と答えてください。 . .gpg.change_passwd.empty.okay "yes" か "no" で答えてください。 . .gpg.keyedit.save.okay "yes" か "no" で答えてください。 . .gpg.keyedit.cancel.okay "yes" か "no" で答えてください。 . .gpg.keyedit.sign_all.okay すべてのユーザIDに対して署名したい場合、"yes"と答えてください。 . .gpg.keyedit.remove.uid.okay このユーザIDを本当に削除したい場合、"yes"と答えてください。そうすると全部の証明書が失われます! . .gpg.keyedit.remove.subkey.okay 副鍵を削除してよい場合、"yes"と答えてください。 . .gpg.keyedit.delsig.valid これは、この鍵の有効な署名です。通常、この署名を削除することは望まないでしょう。この鍵(または、この鍵で証明された別の鍵)への信頼のコネクションが成立することが重要となる場合があるからです。 . .gpg.keyedit.delsig.unknown この署名は検証できませんでした。対応する鍵を持っていないからです。どの鍵が使われたかわかるまでこの削除を延期すべきです。この署名の鍵は、別のすでに証明された鍵を通じて信頼のコネクションを成立することがあるからです。 . .gpg.keyedit.delsig.invalid この署名は有効ではありません。鍵リングから削除することに意味があります。 . .gpg.keyedit.delsig.selfsig これはこのユーザIDとこの鍵とを結ぶ署名です。通常、このような署名を削除することは良いことではありません。実際、GnuPGはこの鍵を使うことができなくなってしまうかもしれません。ですから、この自己署名がなんらかの理由によって無効であり、第二のものが利用可能である場合にだけ、実行してください。 . .gpg.keyedit.updpref.okay すべてのユーザID(もしくは単に選択された一つ)の優先指定を現行の優先指定に変更します。すべての関係する自己署名のタイムスタンプは、一秒進んだものとなります。 . .gpg.passphrase.enter # (keep a leading empty line) パスフレーズを入力してください。秘密の文です。 . .gpg.passphrase.repeat もう一度パスフレーズを入力し、間違いなく入力されたことを確認してください。 . .gpg.detached_signature.filename 署名が適用されるファイルの名前を与えてください。 . .gpg.openfile.overwrite.okay # openfile.c (overwrite_filep) ファイルを上書きしてよければ、"yes"と答えてください。 . .gpg.openfile.askoutname # openfile.c (ask_outfile_name) 新しいファイル名を入力してください。単にEnterを打つと、カッコで示されたデフォルトのファイルが使われます。 . .gpg.ask_revocation_reason.code # revoke.c (ask_revocation_reason) 証明書の理由を指定します。下記のリストから選択してください: "鍵が危うくなった" 承認していない人があなたの秘密鍵へのアクセスを得たと考える理由がある場合に、これを指定します。 "鍵を取り替えた" 新しい鍵でこの鍵を置き換えた場合に、これを指定します。 "鍵はもう使われない" この鍵を使わなくなった場合に、これを指定します。 "ユーザIDが無効となった" ユーザIDをもはや使うべきでない場合に、これを指定します。通常、これは、電子メールアドレスが無効となった場合です。 . .gpg.ask_revocation_reason.text # revoke.c (ask_revocation_reason) 必要であれば、この失効証明書を発行する理由を記述する文章を入力することができます。この文章は簡潔にしてください。空行は文章の終わりを意味します。 . .gpg.tofu.conflict # tofu.c TOFUが同一(もしくはとてもよく似ている)メールアドレスの別の鍵を検出しました。そのユーザが新しい鍵を作ったかもしれません。この場合には、あなたは新しい鍵を安全に信じることができます(が、その人に聞いて確かめましょう)。しかし、また、その鍵が偽造であるか、中間者(MitM)攻撃が行われているのかもしれません。この場合には、あなたはこの鍵を信じられないものとなるように不正としてマークすべきです。ある鍵を信じられないものとなるようにマークするとは、どんな署名も不正と考えられるようになる、その鍵への暗号化はフラグが立てられることを意味します。わからなくて今は確認できない場合、一度だけ認める、あるいは、一度だけ拒絶するを選択すべきです。 . .gpgsm.root-cert-not-trusted # This text gets displayed by the audit log if # a root certificates was not trusted. ルート証明書(信頼の拠り所)が信頼できるとされていません。設定にもよりますが、そのルート証明書を信頼できるものと指定するように既に問われたかもしれませんし、手動でGnuPGがその証明書を信頼できると扱うように設定する必要があります。信頼できる証明書は、GnuPGのホームディレクトリのファイル trustlist.txt に設定します。疑問のある場合、システム管理者にこの証明書を信頼してよいものかどうか問い合わせてください。 . .gpgsm.crl-problem # This tex is displayed by the audit log for problems with # the CRL or OCSP checking. 設定によりますが、CRLの取得か、OCSP検証の際に問題が起きました。これが動かない場合、実に様々な理由がありえます。解決策は、マニュアルを見てください。 . # Local variables: # mode: fundamental # coding: utf-8 # End:	15.17 KB	2020-12-23 13:46
📄 help.nb.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.pl.txt # help.pl.txt - pl GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Te wartości użytkownik przydziela wg swojego uznania; nie będą nigdy eksportowane poza ten system. Potrzebne są one do zbudowania sieci zaufania, i nie ma to nic wspólnego z tworzoną automatycznie siecią certyfikatów. . .gpg.edit_ownertrust.set_ultimate.okay Aby zbudować Sieć Zaufania, GnuPG potrzebuje znać klucze do których masz absolutne zaufanie. Zwykle są to klucze do których masz klucze tajne. Odpowiedz ,,tak'', jeśli chcesz określić ten klucz jako klucz do którego masz absolutne zaufanie. . .gpg.untrusted_key.override Jeśli mimo wszystko chcesz użyć tego klucza, klucza, co do którego nie ma żadnej pewności do kogo należy, odpowiedz ,,tak''. . .gpg.pklist.user_id.enter Podaj adresatów tej wiadomości. . .gpg.keygen.algo Proszę wybrać algorytm. DSA (znany także jako DSS) to algorytm podpisu cyfrowego (Digital Signature Algorithm) i może być używany tylko do podpisów. Elgamal to algorytm tylko do szyfrowania. RSA może być używany do podpisów lub szyfrowania. Pierwszy (główny) klucz zawsze musi być kluczem nadającym się do podpisywania. . .gpg.keygen.algo.rsa_se Używanie tego samego klucza do podpisywania i szyfrowania nie jest dobrym pomysłem. Można tak postępować tylko w niektórych zastosowaniach. Proszę się najpierw skonsultować z ekspertem od bezpieczeństwa. . .gpg.keygen.size Wprowadź rozmiar klucza . .gpg.keygen.size.huge.okay Odpowiedz "tak" lub "nie". . .gpg.keygen.size.large.okay Odpowiedz "tak" lub "nie". . .gpg.keygen.valid Wprowadź żądaną wartość (jak w znaku zachęty). Można tu podać datę w formacie ISO (RRRR-MM-DD) ale nie da to właściwej obsługi błędów - system próbuje interpretować podaną wartość jako okres. . .gpg.keygen.valid.okay Odpowiedz "tak" lub "nie". . .gpg.keygen.name Nazwa właściciela klucza. . .gpg.keygen.email proszę wprowadzić opcjonalny ale wysoce doradzany adres e-mail . .gpg.keygen.comment Proszę wprowadzić opcjonalny komentarz . .gpg.keygen.userid.cmd N aby zmienić nazwę (nazwisko). C aby zmienić komentarz.< E aby zmienić adres e-mail. O aby kontynuować tworzenie klucza. Q aby zrezygnować z tworzenia klucza. . .gpg.keygen.sub.okay Jeśli ma zostać wygenerowany podklucz, należy odpowiedzieć "tak". . .gpg.sign_uid.okay Odpowiedz "tak" lub "nie". . .gpg.sign_uid.class Przy podpisywaniu identyfikatora użytkownika na kluczu należy sprawdzić, czy tożsamość użytkownika odpowiada temu, co jest wpisane w identyfikatorze. Innym użytkownikom przyda się informacja, jak dogłębnie zostało to przez Ciebie sprawdzone. "0" oznacza, że nie podajesz żadnych informacji na temat tego jak dogłębnie tożsamość użytkownika została przez Ciebie potwierdzona. "1" oznacza, że masz przekonanie, że tożsamość użytkownika odpowiada identyfikatorowi klucza, ale nie było możliwości sprawdzenia tego. Taka sytuacja występuje też kiedy podpisujesz identyfikator będący pseudonimem. "2" oznacza, że tożsamość użytkownika została przez Ciebie potwierdzona pobieżnie - sprawdziliście odcisk klucza, sprawdziłaś/eś tożsamość na okazanym dokumencie ze zdjęciem. "3" to dogłębna weryfikacja tożsamości. Na przykład sprawdzenie odcisku klucza, sprawdzenie tożsamości z okazanego oficjalnego dokumentu ze zdjęciem (np paszportu) i weryfikacja poprawności adresu poczty elektronicznej przez wymianę poczty z tym adresem. Zauważ, że podane powyżej przykłady dla poziomów "2" i "3" to tylko przykłady. Do Ciebie należy decyzja co oznacza "pobieżny" i "dogłębny" w kontekście poświadczania i podpisywania kluczy. Jeśli nie wiesz co odpowiedzieć, podaj "0". . .gpg.change_passwd.empty.okay Odpowiedz "tak" lub "nie". . .gpg.keyedit.save.okay Odpowiedz "tak" lub "nie". . .gpg.keyedit.cancel.okay Odpowiedz "tak" lub "nie". . .gpg.keyedit.sign_all.okay Odpowiedz "tak", aby podpisać WSZYSTKIE identyfikatory użytkownika. . .gpg.keyedit.remove.uid.okay Aby skasować ten identyfikator użytkownika (co wiąże się ze utratą wszystkich jego poświadczeń!) należy odpowiedzieć ,,tak''. . .gpg.keyedit.remove.subkey.okay Aby skasować podklucz należy odpowiedzieć "tak". . .gpg.keyedit.delsig.valid To jest poprawny podpis na tym kluczu; normalnie nie należy go usuwać ponieważ może być ważny dla zestawienia połączenia zaufania do klucza którym go złożono lub do innego klucza nim poświadczonego. . .gpg.keyedit.delsig.unknown Ten podpis nie może zostać potwierdzony ponieważ nie ma odpowiadającego mu klucza publicznego. Należy odłożyć usunięcie tego podpisu do czasu, kiedy okaże się który klucz został użyty, ponieważ w momencie uzyskania tego klucza może pojawić się ścieżka zaufania pomiędzy tym a innym, już poświadczonym kluczem. . .gpg.keyedit.delsig.invalid Ten podpis jest niepoprawny. Można usunąć go ze zbioru kluczy. . .gpg.keyedit.delsig.selfsig To jest podpis wiążący identyfikator użytkownika z kluczem. Nie należy go usuwać - GnuPG może nie móc posługiwać się dalej kluczem bez takiego podpisu. Bezpiecznie można go usunąć tylko jeśli ten podpis klucza nim samym z jakichś przyczyn nie jest poprawny, i klucz jest drugi raz podpisany w ten sam sposób. . .gpg.keyedit.updpref.okay Przestawienie wszystkich (lub tylko wybranych) identyfikatorów na aktualne ustawienia. Data na odpowiednich podpisach zostane przesunięta do przodu o jedną sekundę. . .gpg.passphrase.enter Podaj długie, skomplikowane hasło, np. całe zdanie. . .gpg.passphrase.repeat Proszę powtórzyć hasło, aby upewnić się że nie było pomyłki. . .gpg.detached_signature.filename Podaj nazwę pliku którego dotyczy ten podpis . .gpg.openfile.overwrite.okay Jeśli można nadpisać ten plik, należy odpowiedzieć ,,tak'' . .gpg.openfile.askoutname Nazwa pliku. Naciśnięcie ENTER potwierdzi nazwę domyślną (w nawiasach). . .gpg.ask_revocation_reason.code Nalezy podać powód unieważnienia klucza. W zależności od kontekstu można go wybrać z listy: "Klucz został skompromitowany" Masz powody uważać że twój klucz tajny dostał się w niepowołane ręce. "Klucz został zastąpiony" Klucz został zastąpiony nowym. "Klucz nie jest już używany" Klucz został wycofany z użycia. "Identyfikator użytkownika przestał być poprawny" Identyfikator użytkownika (najczęściej adres e-mail przestał być poprawny. . .gpg.ask_revocation_reason.text Jeśli chcesz, możesz podać opis powodu wystawienia certyfikatu unieważnienia. Opis powinien byc zwięzły. Pusta linia kończy wprowadzanie tekstu. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.36 KB	2017-03-17 08:34
📄 help.pt.txt # help.pt.txt - pt GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Você decide que valor usar aqui; este valor nunca será exportado para terceiros. Precisamos dele implementar a rede de confiança, que não tem nada a ver com a rede de certificados (implicitamente criada). . .gpg.edit_ownertrust.set_ultimate.okay Para construir a Teia-de-Confiança ('Web-of-Trust'), o GnuPG precisa de saber quais são as chaves em que deposita confiança absoluta - normalmente estas são as chaves a que tem acesso à chave privada. Responda "sim" para que esta chave seja de confiança absoluta. . .gpg.untrusted_key.override Se você quiser usar esta chave, não de confiança, assim mesmo, responda "sim". . .gpg.pklist.user_id.enter Digite o ID de utilizador do destinatário para quem quer enviar a mensagem. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se Em geral não é uma boa ideia utilizar a mesma chave para assinar e para cifrar. Este algoritmo só deve ser utilizado em alguns domínios. Por favor consulte primeiro o seu perito em segurança. . .gpg.keygen.size Insira o tamanho da chave . .gpg.keygen.size.huge.okay Responda "sim" ou "não" . .gpg.keygen.size.large.okay Responda "sim" ou "não" . .gpg.keygen.valid Digite o valor necessário conforme pedido. É possível digitar uma data ISO (AAAA-MM-DD) mas você não terá uma boa reacção a erros - o sistema tentará interpretar o valor dado como um intervalo. . .gpg.keygen.valid.okay Responda "sim" ou "não" . .gpg.keygen.name Digite o nome do possuidor da chave . .gpg.keygen.email por favor digite um endereço de email (opcional mas recomendado) . .gpg.keygen.comment Por favor digite um comentário (opcional) . .gpg.keygen.userid.cmd N para mudar o nome. C para mudar o comentário. E para mudar o endereço de email O para continuar a geração da chave. S para interromper a geração da chave. . .gpg.keygen.sub.okay Responda "sim" (ou apenas "s") se quiser gerar a subchave. . .gpg.sign_uid.okay Responda "sim" ou "não" . .gpg.sign_uid.class Quando assina uma chave de identificação de um utilizador, deve primeiro verificar que a chave pertence realmente à pessoa em questão. É útil para terceiros saberem com que cuidado é que efectuou esta verificação. "0" significa que não deseja declarar a forma com verificou a chave "1" significa que acredita que a chave pertence à pessoa em questão, mas não conseguiu ou não tentou verificar. Este grau é útil para quando assina a chave de uma utilizador pseudo-anónimo. "2" significa que efectuou uma verificação normal da chave. Por exemplo, isto pode significar que verificou a impressão digital da chave e verificou o identificador de utilizador da chave contra uma identificação fotográfica. "3" significa que efectuou uma verificação exaustiva da chave. Por exemplo, isto pode significar que efectuou a verificação pessoalmente, e que utilizou um documento, com fotografia, difícil de falsificar (como por exemplo um passaporte) que o nome do dono da chave é o mesmo do que o identificador da chave, e que, finalmente, verificou (através de troca de e-mail) que o endereço de email da chave pertence ao done da chave. Atenção: os exemplos dados para os níveis 2 e 3 são apenas exemplos. Compete-lhe a si decidir o que considera, ao assinar chaves, uma verificação "normal" e uma verificação "exaustiva". Se não sabe qual é a resposta correcta, responda "0". . .gpg.change_passwd.empty.okay Responda "sim" ou "não" . .gpg.keyedit.save.okay Responda "sim" ou "não" . .gpg.keyedit.cancel.okay Responda "sim" ou "não" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Responda "sim" se quiser realmente remover este ID de utilizador. Todos os certificados também serão perdidos! . .gpg.keyedit.remove.subkey.okay Responda "sim" se quiser remover a subchave . .gpg.keyedit.delsig.valid Esta é uma assinatura válida na chave; normalmente não é desejável remover esta assinatura porque ela pode ser importante para estabelecer uma conexão de confiança à chave ou a outra chave certificada por esta. . .gpg.keyedit.delsig.unknown Esta assinatura não pode ser verificada porque você não tem a chave correspondente. Você deve adiar sua remoção até saber que chave foi usada porque a chave desta assinatura pode estabelecer uma conexão de confiança através de outra chave já certificada. . .gpg.keyedit.delsig.invalid A assinatura não é válida. Faz sentido removê-la do seu porta-chaves. . .gpg.keyedit.delsig.selfsig Esta é uma assinatura que liga o ID de utilizador à chave. Geralmente não é uma boa idéia remover tal assinatura. É possível que o GnuPG não consiga mais usar esta chave. Faça isto apenas se por alguma razão esta auto-assinatura não for válida e há uma segunda disponível. . .gpg.keyedit.updpref.okay Muda as preferências de todos os identificadores de utilizadores (ou apenas dos seleccionados) para a lista actual de preferências. O 'timestamp' de todas as auto-assinaturas afectuadas será avançado em um segundo. . .gpg.passphrase.enter Por favor digite a frase secreta . .gpg.passphrase.repeat Por favor repita a frase secreta, para ter certeza do que digitou. . .gpg.detached_signature.filename Dê o nome para o ficheiro ao qual a assinatura se aplica . .gpg.openfile.overwrite.okay Responda "sim" se quiser escrever por cima do ficheiro . .gpg.openfile.askoutname Por favor digite um novo nome de ficheiro. Se você apenas carregar em RETURN o ficheiro por omissão (que é mostrado entre parênteses) será utilizado. . .gpg.ask_revocation_reason.code Deve especificar uma razão para a emissão do certificado. Dependendo no contexto, pode escolher as seguintes opções desta lista: "A chave foi comprometida" Utilize esta opção se tem razões para acreditar que indivíduos não autorizados obtiveram acesso à sua chave secreta. "A chave foi substituida" Utilize esta opção se substituiu esta chave com uma mais recente. "A chave já não é utilizada" Utilize esta opção se já não utiliza a chave. "O identificador do utilizador já não é válido" Utilize esta opção para comunicar que o identificador do utilizador não deve ser mais utilizado; normalmente utilizada para indicar que um endereço de email é inválido. . .gpg.ask_revocation_reason.text Se desejar, pode inserir uma texto descrevendo a razão pela qual criou este certificado de revogação. Por favor mantenha este texto conciso. Uma linha vazia termina o texto. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.69 KB	2017-03-17 08:34
📄 help.pt_BR.txt # help.pt_BR.txt - Brazilian GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Você decide que valor usar aqui; este valor nunca será exportado para terceiros. Precisamos dele implementar a rede de confiança, que não tem nada a ver com a rede de certificados (implicitamente criada). . .gpg.edit_ownertrust.set_ultimate.okay Para construir a Teia-de-Confiança ('Web-of-Trust'), o GnuPG precisa de saber quais são as chaves em que deposita confiança absoluta - normalmente estas são as chaves a que tem acesso à chave privada. Responda "sim" para que esta chave seja de confiança absoluta. . .gpg.untrusted_key.override Se você quiser usar esta chave não confiável assim mesmo, responda "sim". . .gpg.pklist.user_id.enter Digite o ID de usuário do destinatário para o qual você quer enviar a mensagem. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se Em geral não é uma boa ideia utilizar a mesma chave para assinar e para cifrar. Este algoritmo só deve ser utilizado em alguns domínios. Por favor consulte primeiro o seu perito em segurança. . .gpg.keygen.size Digite o tamanho da chave . .gpg.keygen.size.huge.okay Responda "sim" ou "não" . .gpg.keygen.size.large.okay Responda "sim" ou "não" . .gpg.keygen.valid Digite o valor necessário conforme pedido. É possível digitar uma data ISO (AAAA-MM-DD) mas você não terá uma boa reação a erros - o sistema tentará interpretar o valor dado como um intervalo. . .gpg.keygen.valid.okay Responda "sim" ou "não" . .gpg.keygen.name Digite o nome do possuidor da chave . .gpg.keygen.email por favor digite um endereço de email (opcional mas recomendado) . .gpg.keygen.comment Por favor digite um comentário (opcional) . .gpg.keygen.userid.cmd N para mudar o nome. C para mudar o comentário. E para mudar o endereço de correio eletrônico. O para continuar a geração da chave. S para interromper a geração da chave. . .gpg.keygen.sub.okay Responda "sim" (ou apenas "s") se quiser gerar a subchave. . .gpg.sign_uid.okay Responda "sim" ou "não" . .gpg.sign_uid.class Quando assina uma chave de identificação de um utilizador, deve primeiro verificar que a chave pertence realmente à pessoa em questão. É útil para terceiros saberem com que cuidado é que efectuou esta verificação. "0" significa que não deseja declarar a forma com verificou a chave "1" significa que acredita que a chave pertence à pessoa em questão, mas não conseguiu ou não tentou verificar. Este grau é útil para quando assina a chave de uma utilizador pseudo-anónimo. "2" significa que efectuou uma verificação normal da chave. Por exemplo, isto pode significar que verificou a impressão digital da chave e verificou o identificador de utilizador da chave contra uma identificação fotográfica. "3" significa que efectuou uma verificação exaustiva da chave. Por exemplo, isto pode significar que efectuou a verificação pessoalmente, e que utilizou um documento, com fotografia, difícil de falsificar (como por exemplo um passaporte) que o nome do dono da chave é o mesmo do que o identificador da chave, e que, finalmente, verificou (através de troca de e-mail) que o endereço de email da chave pertence ao done da chave. Atenção: os exemplos dados para os níveis 2 e 3 são apenas exemplos. Compete-lhe a si decidir o que considera, ao assinar chaves, uma verificação "normal" e uma verificação "exaustiva". Se não sabe qual é a resposta correcta, responda "0". . .gpg.change_passwd.empty.okay Responda "sim" ou "não" . .gpg.keyedit.save.okay Responda "sim" ou "não" . .gpg.keyedit.cancel.okay Responda "sim" ou "não" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Responda "sim" se quiser realmente remover este ID de usuário. Todos os certificados também serão perdidos! . .gpg.keyedit.remove.subkey.okay Responda "sim" se quiser remover a subchave . .gpg.keyedit.delsig.valid Esta é uma assinatura válida na chave; normalmente não é desejável remover esta assinatura porque ela pode ser importante para estabelecer uma conexão de confiança à chave ou a outra chave certificada por esta. . .gpg.keyedit.delsig.unknown Esta assinatura não pode ser verificada porque você não tem a chave correspondente. Você deve adiar sua remoção até saber que chave foi usada porque a chave desta assinatura pode estabelecer uma conexão de confiança através de outra chave já certificada. . .gpg.keyedit.delsig.invalid A assinatura não é válida. Faz sentido removê-la de seu chaveiro. . .gpg.keyedit.delsig.selfsig Esta é uma assinatura que liga o ID de usuário à chave. Geralmente não é uma boa idéia remover tal assinatura. É possível que o GnuPG não consiga mais usar esta chave. Faça isto apenas se por alguma razão esta auto-assinatura não for válida e há uma segunda disponível. . .gpg.keyedit.updpref.okay Muda as preferências de todos os identificadores de utilizadores (ou apenas dos seleccionados) para a lista actual de preferências. O 'timestamp' de todas as auto-assinaturas afectuadas será avançado em um segundo. . .gpg.passphrase.enter Por favor digite a frase secreta . .gpg.passphrase.repeat Por favor repita a última frase secreta, para ter certeza do que você digitou. . .gpg.detached_signature.filename Dê o nome para o arquivo ao qual a assinatura se aplica . .gpg.openfile.overwrite.okay Responda "sim" se quiser sobrescrever o arquivo . .gpg.openfile.askoutname Por favor digite um novo nome de arquivo. Se você apenas apertar RETURN o arquivo padrão (que é mostrado em colchetes) será usado. . .gpg.ask_revocation_reason.code Deve especificar uma razão para a emissão do certificado. Dependendo no contexto, pode escolher as seguintes opções desta lista: "A chave foi comprometida" Utilize esta opção se tem razões para acreditar que indivíduos não autorizados obtiveram acesso à sua chave secreta. "A chave foi substituida" Utilize esta opção se substituiu esta chave com uma mais recente. "A chave já não é utilizada" Utilize esta opção se já não utiliza a chave. "O identificador do utilizador já não é válido" Utilize esta opção para comunicar que o identificador do utilizador não deve ser mais utilizado; normalmente utilizada para indicar que um endereço de email é inválido. . .gpg.ask_revocation_reason.text Se desejar, pode inserir uma texto descrevendo a razão pela qual criou este certificado de revogação. Por favor mantenha este texto conciso. Uma linha vazia termina o texto. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.69 KB	2017-03-17 08:34
📄 help.ro.txt # help.ro.txt - ro GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Este sarcina d-voastră să atribuiţi o valoare aici; această valoare nu va fi niciodată exportată pentru o terţă parte. Trebuie să implementăm reţeaua-de-încredere; aceasta nu are nimic în comun cu certificatele-de-reţea (create implicit). . .gpg.edit_ownertrust.set_ultimate.okay Pentru a construi Reţeaua-de-Încredere, GnuPG trebuie să ştie care chei au nivel de încredere suprem - acestea de obicei sunt cheile pentru care aveţi acces la cheia secretă. Răspundeţi "da" pentru a seta această cheie cu nivel de încredere suprem . .gpg.untrusted_key.override Dacă doriţi oricum să folosiţi această cheie fără încredere, răspundeţi "da". . .gpg.pklist.user_id.enter Introduceţi ID-ul utilizator al destinatarului mesajului. . .gpg.keygen.algo Selectaţi algoritmul de folosit. DSA (aka DSS) este Digital Signature Algorithm şi poate fi folosit numai pentru semnături. Elgamal este un algoritm numai pentru cifrare. RSA poate fi folosit pentru semnături sau cifrare. Prima cheie (primară) trebuie să fie întotdeauna o cheie cu care se poate semna. . .gpg.keygen.algo.rsa_se În general nu este o idee bună să folosiţi aceeaşi cheie şi pentru semnare şi pentru cifrare. Acest algoritm ar trebui folosit numai în anumite domenii. Vă rugăm consultaţi mai întâi un expert în domeniu. . .gpg.keygen.size Introduceţi lungimea cheii . .gpg.keygen.size.huge.okay Răspundeţi "da" sau "nu" . .gpg.keygen.size.large.okay Răspundeţi "da" sau "nu" . .gpg.keygen.valid Introduceţi valoarea cerută precum a arătat la prompt. Este posibil să introduceţi o dată ISO (AAAA-LL-ZZ) dar nu veţi obţine un răspuns de eroare bun - în loc sistemul încearcă să interpreteze valoare dată ca un interval. . .gpg.keygen.valid.okay Răspundeţi "da" sau "nu" . .gpg.keygen.name Introduceţi numele deţinătorului cheii . .gpg.keygen.email vă rugăm introduceţi o adresă de email (opţională dar recomandată) . .gpg.keygen.comment Vă rugăm introduceţi un comentriu opţional . .gpg.keygen.userid.cmd N pentru a schimba numele. C pentru a schimba comentariul. E pentru a schimba adresa de email. O pentru a continua cu generarea cheii. T pentru a termina generarea cheii. . .gpg.keygen.sub.okay Răspundeţi "da" (sau numai "d") dacă sunteţi OK să generaţi subcheia. . .gpg.sign_uid.okay Răspundeţi "da" sau "nu" . .gpg.sign_uid.class Când semnaţi un ID utilizator pe o cheie ar trebui să verificaţi mai întâi că cheia aparţine persoanei numite în ID-ul utilizator. Este util şi altora să ştie cât de atent aţi verificat acest lucru. "0" înseamnă că nu pretindeţi nimic despre cât de atent aţi verificat cheia "1" înseamnă că credeţi că cheia este a persoanei ce pretinde că este proprietarul ei, dar n-aţi putut, sau nu aţi verificat deloc cheia. Aceasta este utilă pentru verificare "persona", unde semnaţi cheia unui utilizator pseudonim. "2" înseamnă că aţi făcut o verificare supericială a cheii. De exemplu, aceasta ar putea însemna că aţi verificat amprenta cheii şi aţi verificat ID-ul utilizator de pe cheie cu un ID cu poză. "3" înseamnă că aţi făcut o verificare extensivă a cheii. De exemplu, aceasta ar putea însemna că aţi verificat amprenta cheii cu proprietarul cheii în persoană, că aţi verificat folosind un document dificil de falsificat cu poză (cum ar fi un paşaport) că numele proprietarului cheii este acelaşi cu numele ID-ului utilizator al cheii şi că aţi verificat (schimbând emailuri) că adresa de email de pe cheie aparţine proprietarului cheii. De notat că exemplele date pentru nivelele 2 şi 3 ceva mai sus sunt numai exemple. La urma urmei, d-voastră decideţi ce înseamnă "superficial" şi "extensiv" pentru d-voastră când semnaţi alte chei. Dacă nu ştiţi care este răspunsul, răspundeţi "0". . .gpg.change_passwd.empty.okay Răspundeţi "da" sau "nu" . .gpg.keyedit.save.okay Răspundeţi "da" sau "nu" . .gpg.keyedit.cancel.okay Răspundeţi "da" sau "nu" . .gpg.keyedit.sign_all.okay Răspundeţi "da" dacă doriţi să semnaţi TOATE ID-urile utilizator . .gpg.keyedit.remove.uid.okay Răspundeţi "da" dacă într-adevăr doriţi să ştergeţi acest ID utilizator. Toate certificatele sunt de asemenea pierdute! . .gpg.keyedit.remove.subkey.okay Răspundeţi "da" dacă este OK să ştergeţi subcheia . .gpg.keyedit.delsig.valid Aceasta este o semnătură validă pe cheie; în mod normal n-ar trebui să ştergeţi această semnătură pentru că aceasta ar putea fi importantăla stabilirea conexiunii de încredere la cheie sau altă cheie certificată de această cheie. . .gpg.keyedit.delsig.unknown Această semnătură nu poate fi verificată pentru că nu aveţi cheia corespunzătoare. Ar trebui să amânaţi ştergerea sa până ştiţi care cheie a fost folosită pentru că această cheie de semnare ar putea constitui o conexiune de încredere spre o altă cheie deja certificată. . .gpg.keyedit.delsig.invalid Semnătura nu este validă. Aceasta ar trebui ştearsă de pe inelul d-voastră de chei. . .gpg.keyedit.delsig.selfsig Aceasta este o semnătură care leagă ID-ul utilizator de cheie. De obicei nu este o idee bună să ştergeţi o asemenea semnătură. De fapt, GnuPG ar putea să nu mai poată folosi această cheie. Aşa că faceţi acest lucru numai dacă această auto-semnătură este dintr-o oarecare cauză invalidă şi o a doua este disponibilă. . .gpg.keyedit.updpref.okay Schimbaţi toate preferinţele ale tuturor ID-urilor utilizator (sau doar cele selectate) conform cu lista curentă de preferinţe. Timestamp-urile tuturor auto-semnăturilor afectate vor fi avansate cu o secundă. . .gpg.passphrase.enter Vă rugăm introduceţi fraza-parolă; aceasta este o propoziţie secretă . .gpg.passphrase.repeat Vă rugăm repetaţi ultima frază-parolă, pentru a fi sigur(ă) ce aţi tastat. . .gpg.detached_signature.filename Daţi numele fişierului la care se aplică semnătura . .gpg.openfile.overwrite.okay Răspundeţi "da" dacă este OK să suprascrieţi fişierul . .gpg.openfile.askoutname Vă rugăm introduceţi un nou nume-fişier. Dacă doar apăsaţi RETURN, va fi folosit fişierul implicit (arătat în paranteze). . .gpg.ask_revocation_reason.code Ar trebui să specificaţi un motiv pentru certificare. În funcţie de context aveţi posibilitatea să alegeţi din această listă: "Cheia a fost compromisă" Folosiţi această opţiune dacă aveţi un motiv să credeţi că persoane neautorizate au avut acces la cheia d-voastră secretă. "Cheia este înlocuită" Folosiţi această opţiune dacă înlocuiţi cheia cu una nouă. "Cheia nu mai este folosită" Folosiţi această opţiune dacă pensionaţi cheia. "ID-ul utilizator nu mai este valid" Folosiţi această opţiune dacă ID-ul utilizator nu mai trebuie folosit; de obicei folosită pentru a marca o adresă de email ca invalidă. . .gpg.ask_revocation_reason.text Dacă doriţi, puteţi introduce un text descriind de ce publicaţi acest certificat de revocare. Vă rugăm fiţi concis. O linie goală termină textul. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.92 KB	2017-03-17 08:34
📄 help.ru.txt # help.ru.txt - Russian GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # Copyright (C) 2016 Ineiev <ineiev@gnu.org> (translation) # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. # The translated revision was taken from HEAD b8bb16c6c08d3c2947f1ff67 # which is the same as the revision from STABLE-BRANCH-2-0 776bee6d370 .#pinentry.qualitybar.tooltip # [remove the hash mark from the key to enable this text] # This entry is just an example on how to customize the tooltip shown # when hovering over the quality bar of the pinentry. We don't # install this text so that the hardcoded translation takes # precedence. An administrator should write up a short help to tell # the users about the configured passphrase constraints and save that # to /etc/gnupg/help.txt. The help text should not be longer than # about 800 characters. Этот индикатор показывает качество введенной выше фразы-пароля. Пока индикатор красный, GnuPG считает фразу-пароль неприемлемо слабой. Уточните у своего администратора принятые требования к фразе-паролю. . .gnupg.agent-problem # There was a problem accessing or starting the agent. К запущенному Gpg-Agent было невозможно подключиться, либо возникла проблема соединения с ним. Система использует фоновый процесс под названием Gpg-Agent для обработки секретных ключей и запроса фраз-паролей. Обычно процесс запускается при входе пользователя в систему и работает, пока пользователь не выйдет. Если процесс недоступен, система пытается запустить его на ходу, но функции этой версий несколько ограничены, это может привести к небольшим проблемам. Вероятно, для решения проблемы нужно обратиться к администратору. В качестве временной меры можно выйти и снова войти в систему; может быть, это поможет. В любом случае сообщите об этом администратору, потому что это указывает на недочет в программе. . .gnupg.dirmngr-problem # There was a problen accessing the dirmngr. К запущенному Dirmngr было невозможно подключиться, либо возникла проблема соединения с ним. Для просмотра списков отзыва сертификатов во время проверки сертификатов и для поиска ключей на локальных серверах система пользуется внешней служебной программой Dirmngr. Обычно она работает как системная служба (демон) и не нуждается в каких-либо действиях со стороны пользователя. В случае проблем система может запускать новую копию Dirmngr по каждому запросу; это запасной вариант с ухудшенными характеристиками. Если Вы столкнулись с этой проблемой, обратитесь к системному администратору. В качестве временного решения можно попробовать отключить проверку списков отзыва сертификатов в настройках gpgsm. . .gpg.edit_ownertrust.value # The help identies prefixed with "gpg." used to be hard coded in gpg # but may now be overridden by help texts from this file. Если хотите, поставьте здесь значение; оно никогда не будет выводиться для третьих сторон. Нам оно нужно для реализации сети доверия; оно никак не связано с (неявно создаваемой) сетью сертификатов. . .gpg.edit_ownertrust.set_ultimate.okay Для построения Сети доверия GnuPG нужно знать, каким ключам доверять полностью - обычно это ключи, секретные части которых у Вас есть. Ответ "да" установит полное доверие этому ключу. .gpg.untrusted_key.override Если Вы хотите все равно пользоваться этим недоверенным ключом, ответьте "да". . .gpg.pklist.user_id.enter Введите ID пользователя - получателя Вашего сообщения. . .gpg.keygen.algo Выберите алгоритм. DSA (он же DSS) можно применять только для подписей. Elgamal - алгоритм только для шифрования. RSA можно применять для шифрования или подписей. Первый (первичный) ключ всегда должен быть пригоден для подписей. . .gpg.keygen.algo.rsa_se В целом неразумно пользоваться одним и тем же ключом и для подписи, и для шифрования. Это может быть полезно только в определенных случаях. Проконсультируйтесь со своим экспертом по безопасности. . .gpg.keygen.flags Поменять функции ключа. Переключать можно только функции, доступные для выбранного алгоритма. Для быстрой установки сразу всех возможностей введите сначала '=', а за ним список букв, задающих набор функций: '1' - подпись, '2' - шифрование, '3' - аутентификация. Неправильные буквы и функции не учитываются. Сразу после быстрого ввода это подменю закрывается. . .gpg.keygen.size Введите размер ключа. Предлагаемое значение обычно хорошо подходит. Если Вам нужен ключ большого размера, например, 4096 бит, подумайте, действительно ли это для Вас имеет смысл. См. комикс на странице http://www.xkcd.com/538/ . . .gpg.keygen.size.huge.okay Отвечайте "да" или "нет". . .gpg.keygen.size.large.okay Отвечайте "да" или "нет". . .gpg.keygen.valid Введите нужное значение, как показано в приглашении. Можно ввести дату ИСО (ГГГГ-ММ-ДД), но сообщения об ошибках будут неудобочитаемыми: система пытается интерпретировать данное значение как интервал. . .gpg.keygen.valid.okay Отвечайте "да" или "нет". . .gpg.keygen.name Введите имя владельца ключа. Символы "<" и ">" недопустимы. Пример: Вася Пушкин . .gpg.keygen.email Введите, пожалуйста, адрес электронной почты (необязательно, но очень рекомендуется). Пример: vp@test.ru . .gpg.keygen.comment Введите, пожалуйста, необязательное примечание. Символы "(" и ")" недопустимы. В общем и целом оно не нужно. . .gpg.keygen.userid.cmd # (Keep a leading empty line) N сменить имя. C сменить примечание. E сменить адрес. O продолжить создание ключа. Q прекратить создание ключа. . .gpg.keygen.sub.okay Введите "да" (или "y"), чтобы разрешить создание ключа. . .gpg.sign_uid.okay Отвечайте "да" или "нет". . .gpg.sign_uid.class Когда Вы подписываете идентификатор пользователя в ключе, нужно сначала удостовериться, что ключ принадлежит указанному в идентификаторе лицу. Другим полезно знать, насколько тщательно Вы это проверили. "0" значит, что Вы не указываете, насколько тщательно вы проверяли ключ. "1" значит, что Вы считаете, что ключ принадлежит заявленному лицу, но Вы не могли проверить или не проверяли ключ. Это полезно для проверки "инкогнито", когда вы подписываете ключ с псевдонимом. "2" значит, что Вы провели частичную проверку ключа. Например, проверили отпечаток ключа и идентификатор пользователя из ключа по фотоидентификатору. "3" значит, что Вы провели тщательную проверку ключа. Например, Вы проверили отпечаток ключа, а также проверили по удостоверению личности (такому как паспорт), что имя владельца ключа совпадает с именем человека, записанным в идентификаторе пользователя ключа; наконец, Вы удостоверились (обменявшись электронной почтой), что адрес электронной почты принадлежит владельцу ключа. Имейте в виду, что примеры, данные для уровней 2 и 3 - это только примеры. В конечном счете Вы сами решаете, что значит "частичная" и "тщательная" проверка, когда Вы подписываете другие ключи. Если затрудняетесь с ответом, поставьте "0". . .gpg.change_passwd.empty.okay Отвечайте "да" или "нет". . .gpg.keyedit.save.okay Отвечайте "да" или "нет". . .gpg.keyedit.cancel.okay Отвечайте "да" или "нет". . .gpg.keyedit.sign_all.okay Ответьте "да", если хотите подписать ВСЕ идентификаторы пользователя. . .gpg.keyedit.remove.uid.okay Ответьте "да", если действительно хотите удалить этот идентификатор пользователя. Все сертификаты будут также удалены! . .gpg.keyedit.remove.subkey.okay Ответьте "да", если подключ можно удалить. . .gpg.keyedit.delsig.valid Это верная подпись ключа; как правило, ее не нужно удалять, поскольку может быть важно установить отношение доверия между этим ключом и другими ключами. . .gpg.keyedit.delsig.unknown Эту подпись нельзя проверить, поскольку отсутствует соответствующий ключ. Удаление ее нужно отложить до тех пор, пока не станет известно, какой из ключей был использован, так как подпись этого ключа могло бы установить отношение доверия через другой, уже сертифицированный ключ. . .gpg.keyedit.delsig.invalid Подпись недействительна. Имеет смысл удалить ее из Вашей таблицы ключей. . .gpg.keyedit.delsig.selfsig Эта подпись связывает идентификатор пользователя с ключом. Обычно удалять такие подписи не следует. Это может сделать ключ непригодным для пользования с GnuPG. Так что делайте это только если эта самоподпись по какой-то причине недействительна и есть другая. . .gpg.keyedit.updpref.okay Изменить предпочтения для всех идентификаторов пользователя (или только для выбранных) на текущий список предпочтений. Дата всех самоподписей, которых это касается, будет сдвинута вперед на одну секунду. . .gpg.passphrase.enter # (keep a leading empty line) Введите, пожалуйста, фразу-пароль (секретное предложение). . .gpg.passphrase.repeat Повторите введенную фразу-пароль, чтобы проверить, что Вы не ошиблись. . .gpg.detached_signature.filename Задайте имя файла, который подписывается. . .gpg.openfile.overwrite.okay # openfile.c (overwrite_filep) Ответьте "да", если файл можно перезаписать. . .gpg.openfile.askoutname # openfile.c (ask_outfile_name) Введите новое имя файла. Если просто нажать "Enter", будет использован файл по умолчанию (указан в скобках). . .gpg.ask_revocation_reason.code # revoke.c (ask_revocation_reason) Нужно указать причину отзыва. Можно выбрать из списка: "Ключ был раскрыт" Есть основания полагать, что какие-то лица получили несанкционированный доступ к секретному ключу. "Ключ заменен другим" Вы заменили ключ на новый. "Ключ больше не используется" Вы дали ключу отставку. "ID пользователя больше не действителен" ID пользователя больше не должен употребляться; обычно это значит, что адрес электронной почты недействителен. . .gpg.ask_revocation_reason.text # revoke.c (ask_revocation_reason) Если хотите, можете ввести текст, поясняющий причину, по которой выпущен этот сертификат отзыва. Выражайтесь, пожалуйста, ясно. Текст заканчивается пустой строкой. . .gpgsm.root-cert-not-trusted # This text gets displayed by the audit log if # a root certificates was not trusted. Нет доверия к корневому сертификату. В зависимости от настроек Вам могли предложить пометить этот корневой сертификат как доверенный или вручную указать GnuPG, что этому сертификату нужно доверять. Доверенные сертификаты задаются в файле trustlist.txt в домашнем каталоге GnuPG. Если сомневаетесь, спросите своего системного администратора, следует ли Вам доверять этому сертификату. .gpgsm.crl-problem # This tex is displayed by the audit log for problems with # the CRL or OCSP checking. В зависимости от настроек возникла проблема в получении списка отозванных сертификатов или в выполнении проверки по протоколу OCSP. Это могло случиться по очень многим причинам. Обратитесь к документации за возможными решениями. # Local variables: # mode: default-generic # coding: utf-8 # End:	17.32 KB	2017-03-17 08:34
📄 help.sk.txt # help.sk.txt - sk GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Je na Vás, aby ste sem priradili hodnotu; táto hodnota nebude nikdy exportovaná tretej strane. Potrebujeme ju k implementácii "pavučiny dôvery"; nemá to nič spoločné s (implicitne vytvorenou) "pavučinou certifikátov". . .gpg.edit_ownertrust.set_ultimate.okay Aby bolo možné vybudovať pavučinu dôvery, musí GnuPG vedieť, ktorým kľúčom dôverujete absolútne - obyčajne sú to tie kľúče, pre ktoré máte prístup k tajným kľúčom. Odpovedzte "ano", aby ste nastavili tieto kľúče ako absolútne dôveryhodné . .gpg.untrusted_key.override Pokiaľ aj tak chcete použiť tento nedôveryhodný kľúč, odpovedzte "ano". . .gpg.pklist.user_id.enter Vložte identifikátor adresáta, ktorému chcete poslať správu. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se Všebecne nemožno odporúčať používať rovnaký kľúč na šifrovanie a podeisovanie Tento algoritmus je vhodné použiť len za určitých podmienok. Kontaktujte prosím najprv bezpečnostného špecialistu. . .gpg.keygen.size Vložte dĺžku kľúča . .gpg.keygen.size.huge.okay Odpovedzte "ano" alebo "nie" . .gpg.keygen.size.large.okay Odpovedzte "ano" alebo "nie" . .gpg.keygen.valid Vložte požadovanú hodnotu tak, ako je uvedené v príkazovom riadku. Je možné vložiť dátum vo formáte ISO (RRRR-MM-DD), ale nedostanete správnu chybovú hlášku - miesto toho systém skúsi interpretovať zadanú hodnotu ako interval. . .gpg.keygen.valid.okay Odpovedzte "ano" alebo "nie" . .gpg.keygen.name Vložte meno držiteľa kľúča . .gpg.keygen.email prosím, vložte e-mailovú adresu (nepovinné, ale veľmi odporúčané) . .gpg.keygen.comment Prosím, vložte nepovinný komentár . .gpg.keygen.userid.cmd N pre zmenu názvu. C pre zmenu komentára. E pre zmenu e-mailovej adresy. O pre pokračovanie generovania kľúča. Q pre ukončenie generovania kľúča. . .gpg.keygen.sub.okay Ak chcete generovať podkľúč, odpovedzte "ano" (alebo len "a"). . .gpg.sign_uid.okay Odpovedzte "ano" alebo "nie" . .gpg.sign_uid.class Skôr ako podpíšete id užívateľa, mali by ste najprv overiť, či kľúč patrí osobe, ktorej meno je uvedené v identifikátore užívateľa. Je veľmi užitočné, keď ostatní vedia, ako dôsledne ste previedli takéto overenie. "0" znamená, že neuvádzate, ako dôsledne ste pravosť kľúča overili "1" znamená, že veríte tomu, že kľúč patrí osobe, ktorá je uvedená, v užívateľskom ID, ale nemohli ste alebo jste nepreverili túto skutočnosť. To je užitočné pre "osobnú" verifikáciu, keď podpisujete kľúče, ktoré používajú pseudonym užívateľa. "2" znamená, že ste čiastočne overili pravosť kľúča. Napr. ste overili fingerprint kľúča a skontrolovali identifikátor užívateľa uvedený na kľúči s fotografickým id. "3" Znamená, že ste vykonali veľmi dôkladné overenie pravosti kľúča. To môže napríklad znamenať, že ste overili fingerprint kľúča jeho vlastníka osobne a ďalej ste pomocou tažko falšovateľného dokumentu s fotografiou (napríklad pasu) overili, že meno majiteľa kľúča sa zhoduje s menom uvedeným v užívateľskom ID a ďalej ste overili (výmenou elektronických dopisov), že elektronická adresa uvedená v ID užívateľa patrí majiteľovi kľúča. Prosím nezabúdajte, že príklady uvedené pre úroveň 2 a 3 sú len príklady. Je len na Vašom rozhodnutí, čo "čiastočné" a "dôkladné" overenie znamená keď budete podpisovať kľúče iným užívateľom. Pokiaľ neviete, aká je správna odpoveď, odpovedzte "0". . .gpg.change_passwd.empty.okay Odpovedzte "ano" alebo "nie" . .gpg.keyedit.save.okay Odpovedzte "ano" alebo "nie" . .gpg.keyedit.cancel.okay Odpovedzte "ano" alebo "nie" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .gpg.keyedit.remove.uid.okay Pokiaľ skutočne chcete zmazať tento identifikátor užívateľa, odpovedzte "ano". Všetky certifikáty budú tiež stratené! . .gpg.keyedit.remove.subkey.okay Odpovedzte "ano", pokiaľ chcete zmazať podkľúč . .gpg.keyedit.delsig.valid Toto je platný podpis kľúča; normálne nechcete tento podpis zmazať, pretože môže byť dôležitý pri vytváraní dôvery kľúča alebo iného kľúča ceritifikovaného týmto kľúčom. . .gpg.keyedit.delsig.unknown Tento podpis nemôže byť overený, pretože nemáte zodpovedajúci verejný kľúč. Jeho zmazanie by ste mali odložiť do času, keď budete vedieť, ktorý kľúč bol použitý, pretože tento podpisovací kľúč môže vytvoriť dôveru prostredníctvom iného už certifikovaného kľúča. . .gpg.keyedit.delsig.invalid Podpis je neplatný. Je rozumné ho odstrániť z Vášho súboru kľúčov. . .gpg.keyedit.delsig.selfsig Toto je podpis, ktorý viaže identifikátor užívateľa ku kľúču. Zvyčajne nie je dobré takýto podpis odstrániť. GnuPG nemôže tento kľúč naďalej používať. Urobte to len v prípade, keď je tento podpis kľúča ním samým z nejakého dôvodu neplatný a keď je k dispozícii iný kľúč. . .gpg.keyedit.updpref.okay Zmeniť predvoľby pre všetky užívateľské ID (alebo len pre označené) na aktuálny zoznam predvolieb. Časové razítka všetkých dotknutých podpisov kľúčov nimi samotnými budú posunuté o jednu sekundu dopredu. . .gpg.passphrase.enter Prosím, vložte heslo; toto je tajná veta . .gpg.passphrase.repeat Prosím, zopakujte posledné heslo, aby ste si boli istý, čo ste napísali. . .gpg.detached_signature.filename Zadajte názov súboru, ku ktorému sa podpis vzťahuje . .gpg.openfile.overwrite.okay Ak si prajete prepísanie súboru, odpovedzte "ano" . .gpg.openfile.askoutname Prosím, vložte nový názov súboru. Ak len stlačíte RETURN, bude použitý implicitný súbor (ktorý je zobrazený v zátvorkách). . .gpg.ask_revocation_reason.code Mali by ste špecifikovať dôvod certifikácie. V závislosti na kontexte máte možnosť si vybrať zo zoznamu: "kľúč bol kompromitovaný" Toto použite, pokiaľ si myslíte, že k Vášmu tajnému kľúču získali prístup neoprávnené osoby. "kľúč je nahradený" Toto použite, pokiaľ ste tento kľúč nahradili novším kľúčom. "kľúč sa už nepoužíva" Toto použite, pokiaľ tento kľúč už nepoužívate. "Identifikátor užívateľa už nie je platný" Toto použite, pokiaľ by sa identifikátor užívateľa už nemal používať; normálne sa používa na označenie neplatnej e-mailové adresy. . .gpg.ask_revocation_reason.text Ak chcete, môžete vložiť text popisujúcí pôvod vzniku tohto revokačného ceritifikátu. Prosím, stručne. Text končí prázdnym riadkom. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.9 KB	2017-03-17 08:34
📄 help.sv.txt # help..txt - GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .#gpg.edit_ownertrust.value # fixme: Please translate and remove the hash mark from the key line. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .#gpg.edit_ownertrust.set_ultimate.okay # fixme: Please translate and remove the hash mark from the key line. To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted . .#gpg.untrusted_key.override # fixme: Please translate and remove the hash mark from the key line. If you want to use this untrusted key anyway, answer "yes". . .#gpg.pklist.user_id.enter # fixme: Please translate and remove the hash mark from the key line. Enter the user ID of the addressee to whom you want to send the message. . .#gpg.keygen.algo # fixme: Please translate and remove the hash mark from the key line. Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .#gpg.keygen.algo.rsa_se # fixme: Please translate and remove the hash mark from the key line. In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .#gpg.keygen.size # fixme: Please translate and remove the hash mark from the key line. Enter the size of the key . .#gpg.keygen.size.huge.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.size.large.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.valid # fixme: Please translate and remove the hash mark from the key line. Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .#gpg.keygen.valid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keygen.name # fixme: Please translate and remove the hash mark from the key line. Enter the name of the key holder . .#gpg.keygen.email # fixme: Please translate and remove the hash mark from the key line. please enter an optional but highly suggested email address . .#gpg.keygen.comment # fixme: Please translate and remove the hash mark from the key line. Please enter an optional comment . .#gpg.keygen.userid.cmd # fixme: Please translate and remove the hash mark from the key line. N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to to quit the key generation. . .#gpg.keygen.sub.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" (or just "y") if it is okay to generate the sub key. . .#gpg.sign_uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.sign_uid.class # fixme: Please translate and remove the hash mark from the key line. When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .#gpg.change_passwd.empty.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.save.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.cancel.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" or "no" . .#gpg.keyedit.sign_all.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you want to sign ALL the user IDs . .#gpg.keyedit.remove.uid.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .#gpg.keyedit.remove.subkey.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to delete the subkey . .#gpg.keyedit.delsig.valid # fixme: Please translate and remove the hash mark from the key line. This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .#gpg.keyedit.delsig.unknown # fixme: Please translate and remove the hash mark from the key line. This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .#gpg.keyedit.delsig.invalid # fixme: Please translate and remove the hash mark from the key line. The signature is not valid. It does make sense to remove it from your keyring. . .#gpg.keyedit.delsig.selfsig # fixme: Please translate and remove the hash mark from the key line. This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .#gpg.keyedit.updpref.okay # fixme: Please translate and remove the hash mark from the key line. Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .#gpg.passphrase.enter # fixme: Please translate and remove the hash mark from the key line. Please enter the passphrase; this is a secret sentence . .#gpg.passphrase.repeat # fixme: Please translate and remove the hash mark from the key line. Please repeat the last passphrase, so you are sure what you typed in. . .#gpg.detached_signature.filename # fixme: Please translate and remove the hash mark from the key line. Give the name of the file to which the signature applies . .#gpg.openfile.overwrite.okay # fixme: Please translate and remove the hash mark from the key line. Answer "yes" if it is okay to overwrite the file . .#gpg.openfile.askoutname # fixme: Please translate and remove the hash mark from the key line. Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .#gpg.ask_revocation_reason.code # fixme: Please translate and remove the hash mark from the key line. You should specify a reason for the certification. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .#gpg.ask_revocation_reason.text # fixme: Please translate and remove the hash mark from the key line. If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . # Local variables: # mode: fundamental # coding: utf-8 # End:	9.51 KB	2017-03-17 08:34
📄 help.tr.txt # help.tr.txt - tr GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. .gpg.edit_ownertrust.value Bir değeri buraya işaretlemek size kalmış; bu değer herhangi bir 3. şahsa gönderilmeyecek. Bir güvence ağı sağlamak için bizim buna ihtiyacımız var; bunun (açıkça belirtilmeden oluşturulmuş) sertifikalar ağıyla hiçbir alakası yok. . .gpg.edit_ownertrust.set_ultimate.okay Web-of-Trust oluşturulabilmesi için GnuPG'ye hangi anahtarların son derece güvenli (bunlar gizli anahtarlarına erişiminiz olan anahtarlardır) olduğunun bildirilmesi gerekir. "evet" yanıtı bu anahtarın son derece güvenli olduğunun belirtilmesi için yeterlidir. . .gpg.untrusted_key.override Bu güvencesiz anahtarı yine de kullanmak istiyorsanız cevap olarak "evet" yazın. . .gpg.pklist.user_id.enter Bu iletiyi göndereceğiniz adresin kullanıcı kimliğini giriniz. . .gpg.keygen.algo Kullanılacak algoritmayı seçiniz. DSA (nam-ı diğer DSS) Sayısal İmza Algortimasıdır ve sadece imzalar için kullanılabilir. Elgamal sadece şifreleme amacıyla kullanılabilen bir algoritmadır. RSA hem imzalamak hem de şifrelemek amacıyla kullanılabilir. İlk (asıl) anahtar daima imzalama yeteneğine sahip bir anahtar olmalıdır. . .gpg.keygen.algo.rsa_se Genelde imzalama ve şifreleme için aynı anahtarı kullanmak iyi bir fikir değildir. Bu algoritma sadece belli alanlarda kullanılabilir. Lütfen güvenlik uzmanınıza danışın. . .gpg.keygen.size Anahtar uzunluğunu giriniz . .gpg.keygen.size.huge.okay Cevap "evet" ya da "hayır" . .gpg.keygen.size.large.okay Cevap "evet" ya da "hayır" . .gpg.keygen.valid İstenen değeri girin. ISO tarihi (YYYY-AA-GG) girmeniz mümkündür fakat iyi bir hata cevabı alamazsınız -- onun yerine sistem verilen değeri bir zaman aralığı olarak çözümlemeyi dener. . .gpg.keygen.valid.okay Cevap "evet" ya da "hayır" . .gpg.keygen.name Anahtar tutucunun ismini giriniz . .gpg.keygen.email lütfen bir E-posta adresi girin (isteğe bağlı ancak kuvvetle tavsiye edilir) . .gpg.keygen.comment Lütfen önbilgi girin (isteğe bağlı) . .gpg.keygen.userid.cmd S iSim değiştirmek için. B önBilgiyi değiştirmek için. P e-Posta adresini değiştirmek için. D anahtar üretimine Devam etmek için. K anahtar üretiminden çıKmak için. . .gpg.keygen.sub.okay Yardımcı anahtarı üretmek istiyorsanız "evet" ya da "e" girin. . .gpg.sign_uid.okay Cevap "evet" ya da "hayır" . .gpg.sign_uid.class Bir anahtarı bir kullanıcı kimlikle imzalamadan önce kullanıcı kimliğin içindeki ismin, anahtarın sahibine ait olup olmadığını kontrol etmelisiniz. "0" bu kontrolu yapmadığınız ve yapmayı da bilmediğiniz anlamındadır. "1" anahtar size sahibi tarafından gönderildi ama siz bu anahtarı başka kaynaklardan doğrulamadınız anlamındadır. Bu kişisel doğrulama için yeterlidir. En azında yarı anonim bir anahtar imzalaması yapmış olursunuz. "2" ayrıntılı bir inceleme yapıldığı anlamındadır. Örneğin parmakizi ve bir anahtarın foto kimliğiyle kullanıcı kimliğini karşılaştırmak gibi denetimleri yapmışsınızdır. "3" inceden inceye bir doğrulama anlatır. Örneğin, şahıstaki anahtarın sahibi ile anahtar parmak izini karşılaştırmışsınızdır ve anahtardaki kullanıcı kimlikte belirtilen isme ait bir basılı kimlik belgesindeki bir fotoğrafla şahsı karşılaştırmışsınızdır ve son olarak anahtar sahibinin e-posta adresini kendisinin kullanmakta olduğunu da denetlemişsinizdir. Burada 2 ve 3 için verilen örnekler sadece örnektir. Eninde sonunda bir anahtarı imzalarken "ayrıntılı" ve "inceden inceye" kontroller arasındaki ayrıma siz karar vereceksiniz. Bu kararı verebilecek durumda değilseniz "0" cevabını verin. . .gpg.change_passwd.empty.okay Cevap "evet" ya da "hayır" . .gpg.keyedit.save.okay Cevap "evet" ya da "hayır" . .gpg.keyedit.cancel.okay Cevap "evet" ya da "hayır" . .gpg.keyedit.sign_all.okay Kullanıcı kimliklerinin TÜMünü imzalamak istiyorsanız "evet" ya da "yes" yazın . .gpg.keyedit.remove.uid.okay Bu kullanıcı kimliğini gerçekten silmek istiyorsanız "evet" girin. Böylece bütün sertifikaları kaybedeceksiniz! . .gpg.keyedit.remove.subkey.okay Bu yardımcı anahtarı silme izni vermek istiyorsanız "evet" girin . .gpg.keyedit.delsig.valid Bu, anahtar üzerinde geçerli bir imzadır; anahtara ya da bu anahtarla sertifikalanmış bir diğer anahtara bir güvence bağlantısı sağlamakta önemli olabileceğinden normalde bu imzayı silmek istemezsiniz. . .gpg.keyedit.delsig.unknown Bu imza, anahtarına sahip olmadığınızdan, kontrol edilemez. Bu imzanın silinmesini hangi anahtarın kullanıldığını bilene kadar ertelemelisiniz çünkü bu imzalama anahtarı başka bir sertifikalı anahtar vasıtası ile bir güvence bağlantısı sağlayabilir. . .gpg.keyedit.delsig.invalid İmza geçersiz. Anahtarlıktan kaldırmak uygun olacak. . .gpg.keyedit.delsig.selfsig Bu imza kullanıcı kimliğini anahtara bağlar. Öz-imzayı silmek hiç iyi bir fikir değil. GnuPG bu anahtarı bir daha hiç kullanamayabilir. Bunu sadece, eğer bu öz-imza bazı durumlarda geçerli değilse ya da kullanılabilir bir ikincisi var ise yapın. . .gpg.keyedit.updpref.okay Tüm kullanıcı kimlik tercihlerini (ya da seçilen birini) mevcut tercihler listesine çevirir. Tüm etkilenen öz-imzaların zaman damgaları bir sonraki tarafından öne alınacaktır. . .gpg.passphrase.enter Lütfen bir anahtar parolası giriniz; yazdıklarınız görünmeyecek . .gpg.passphrase.repeat Lütfen son parolayı tekrarlayarak ne yazdığınızdan emin olun. . .gpg.detached_signature.filename İmzanın uygulanacağı dosyanın ismini verin . .gpg.openfile.overwrite.okay Dosyanın üzerine yazılacaksa lütfen "evet" yazın . .gpg.openfile.askoutname Lütfen yeni dosya ismini girin. Dosya ismini yazmadan RETURN tuşlarsanız parantez içinde gösterilen öntanımlı dosya kullanılacak. . .gpg.ask_revocation_reason.code Sertifikalama için bir sebep belirtmelisiniz. İçeriğine bağlı olarak bu listeden seçebilirsiniz: "Anahtar tehlikede" Yetkisiz kişilerin gizli anahtarınıza erişebildiğine inanıyorsanız bunu seçin. "Anahtar geçici" Mevcut anahtarı daha yeni bir anahtar ile değiştirmişseniz bunu seçin. "Anahtar artık kullanılmayacak" Anahtarı emekliye ayıracaksanız bunu seçin. "Kullanıcı kimliği artık geçersiz" Kullanıcı kimliği artık kullanılamayacak durumdaysa bunu seçin; genelde Eposta adresi geçersiz olduğunda kullanılır. . .gpg.ask_revocation_reason.text İsterseniz, neden bu yürürlükten kaldırma sertifikasını verdiğinizi açıklayan bir metin girebilirsiniz. Lütfen bu metin kısa olsun. Bir boş satır metni bitirir. . # Local variables: # mode: fundamental # coding: utf-8 # End:	7.47 KB	2017-03-17 08:34
📄 help.txt # help.txt - English GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. # Note that this help file needs to be UTF-8 encoded. When looking # for a help item, GnuPG scans the help files in the following order # (assuming a GNU or Unix system): # # /etc/gnupg/help.LL_TT.txt # /etc/gnupg/help.LL.txt # /etc/gnupg/help.txt # /usr/share/gnupg/help.LL_TT.txt # /usr/share/gnupg/help.LL.txt # /usr/share/gnupg/help.txt # # Here LL_TT denotes the full name of the current locale with the # territory (.e.g. "de_DE"), LL denotes just the locale name # (e.g. "de"). The first matching item is returned. To put a dot or # a hash mark at the beginning of a help text line, it needs to be # prefixed with ". ". A single dot may be used to terminated a help # entry. .#pinentry.qualitybar.tooltip # [remove the hash mark from the key to enable this text] # This entry is just an example on how to customize the tooltip shown # when hovering over the quality bar of the pinentry. We don't # install this text so that the hardcoded translation takes # precedence. An administrator should write up a short help to tell # the users about the configured passphrase constraints and save that # to /etc/gnupg/help.txt. The help text should not be longer than # about 800 characters. This bar indicates the quality of the passphrase entered above. As long as the bar is shown in red, GnuPG considers the passphrase too weak to accept. Please ask your administrator for details about the configured passphrase constraints. . .#pinentry.constraints.hint.short # [remove the hash mark from the key to enable this hint] # This entry is used by some pinentries to display a hint about # enabled passphrase constraints. These constraints are configurable # and the admin may give a hint about them by using this help entry. Please use letters and digits. . .#pinentry.constraints.hint.long # [remove the hash mark from the key to enable this hint] # This entry is used by some pinentries to show a tooltip with more # information about the configured passphrase constraints. Please use letters and digits. Extra constraints are enforced, for example the use of common car number plates. . .#pinentry.formatted_passphrase.hint", # [remove the hash mark from the key to enable this hint] # If this entry is not set a standard text is shown Note: The blanks are not part of the passphrase. . .gnupg.agent-problem # There was a problem accessing or starting the agent. It was either not possible to connect to a running Gpg-Agent or a communication problem with a running agent occurred. The system uses a background process, called Gpg-Agent, for processing private keys and to ask for passphrases. The agent is usually started when the user logs in and runs as long the user is logged in. In case that no agent is available, the system tries to start one on the fly but that version of the agent is somewhat limited in functionality and thus may lead to little problems. You probably need to ask your administrator on how to solve the problem. As a workaround you might try to log out and in to your session and see whether this helps. If this helps please tell the administrator anyway because this indicates a bug in the software. . .gnupg.dirmngr-problem # There was a problen accessing the dirmngr. It was either not possible to connect to a running Dirmngr or a communication problem with a running Dirmngr occurred. To lookup certificate revocation lists (CRLs), performing OCSP validation and to lookup keys through LDAP servers, the system uses an external service program named Dirmngr. The Dirmngr is usually running as a system service (daemon) and does not need any attention by the user. In case of problems the system might start its own copy of the Dirmngr on a per request base; this is a workaround and yields limited performance. If you encounter this problem, you should ask your system administrator how to proceed. As an interim solution you may try to disable CRL checking in gpgsm's configuration. . .gpg.edit_ownertrust.value # The help identies prefixed with "gpg." used to be hard coded in gpg # but may now be overridden by help texts from this file. It's up to you to assign a value here; this value will never be exported to any 3rd party. We need it to implement the web-of-trust; it has nothing to do with the (implicitly created) web-of-certificates. . .gpg.edit_ownertrust.set_ultimate.okay To build the Web-of-Trust, GnuPG needs to know which keys are ultimately trusted - those are usually the keys for which you have access to the secret key. Answer "yes" to set this key to ultimately trusted. .gpg.untrusted_key.override If you want to use this untrusted key anyway, answer "yes". . .gpg.pklist.user_id.enter Enter the user ID of the addressee to whom you want to send the message. . .gpg.keygen.algo Select the algorithm to use. DSA (aka DSS) is the Digital Signature Algorithm and can only be used for signatures. Elgamal is an encrypt-only algorithm. RSA may be used for signatures or encryption. The first (primary) key must always be a key which is capable of signing. . .gpg.keygen.algo.rsa_se In general it is not a good idea to use the same key for signing and encryption. This algorithm should only be used in certain domains. Please consult your security expert first. . .gpg.keygen.cardkey Select which key from the card shall be used. The listing shows the selection index, the keygrip (a string of hex digits), the card specific key reference, the algorithm used for this key, and in parentheses the usage of the key (cert, sign, auth, encr). If known the standard usage for a key is marked with an asterisk. . .gpg.keygen.flags Toggle the capabilities of the key. It is only possible to toggle those capabilities which are possible for the selected algorithm. To quickly set the capabilities all at once it is possible to enter a '=' as first character followed by a list of letters indicating the capability to set: 's' for signing, 'e' for encryption, and 'a' for authentication. Invalid letters and impossible capabilities are ignored. This submenu is immediately closed after using this shortcut. . .gpg.keygen.size Enter the size of the key. The suggested default is usually a good choice. If you want to use a large key size, for example 4096 bit, please think again whether it really makes sense for you. You may want to view the web page http://www.xkcd.com/538/ . . .gpg.keygen.size.huge.okay Answer "yes" or "no". . .gpg.keygen.size.large.okay Answer "yes" or "no". . .gpg.keygen.valid Enter the required value as shown in the prompt. It is possible to enter a ISO date (YYYY-MM-DD) but you won't get a good error response - instead the system tries to interpret the given value as an interval. . .gpg.keygen.valid.okay Answer "yes" or "no". . .gpg.keygen.name Enter the name of the key holder. The characters "<" and ">" are not allowed. Example: Heinrich Heine . .gpg.keygen.email Please enter an optional but highly suggested email address. Example: heinrichh@duesseldorf.de . .gpg.keygen.comment Please enter an optional comment. The characters "(" and ")" are not allowed. In general there is no need for a comment. . .gpg.keygen.userid.cmd # (Keep a leading empty line) N to change the name. C to change the comment. E to change the email address. O to continue with key generation. Q to quit the key generation. . .gpg.keygen.sub.okay Answer "yes" (or just "y") if it is okay to generate the sub key. . .gpg.sign_uid.okay Answer "yes" or "no". . .gpg.sign_uid.class When you sign a user ID on a key, you should first verify that the key belongs to the person named in the user ID. It is useful for others to know how carefully you verified this. "0" means you make no particular claim as to how carefully you verified the key. "1" means you believe the key is owned by the person who claims to own it but you could not, or did not verify the key at all. This is useful for a "persona" verification, where you sign the key of a pseudonymous user. "2" means you did casual verification of the key. For example, this could mean that you verified the key fingerprint and checked the user ID on the key against a photo ID. "3" means you did extensive verification of the key. For example, this could mean that you verified the key fingerprint with the owner of the key in person, and that you checked, by means of a hard to forge document with a photo ID (such as a passport) that the name of the key owner matches the name in the user ID on the key, and finally that you verified (by exchange of email) that the email address on the key belongs to the key owner. Note that the examples given above for levels 2 and 3 are only examples. In the end, it is up to you to decide just what "casual" and "extensive" mean to you when you sign other keys. If you don't know what the right answer is, answer "0". . .gpg.change_passwd.empty.okay Answer "yes" or "no". . .gpg.keyedit.save.okay Answer "yes" or "no". . .gpg.keyedit.cancel.okay Answer "yes" or "no". . .gpg.keyedit.sign_all.okay Answer "yes" if you want to sign ALL the user IDs. . .gpg.keyedit.remove.uid.okay Answer "yes" if you really want to delete this user ID. All certificates are then also lost! . .gpg.keyedit.remove.subkey.okay Answer "yes" if it is okay to delete the subkey. . .gpg.keyedit.delsig.valid This is a valid signature on the key; you normally don't want to delete this signature because it may be important to establish a trust connection to the key or another key certified by this key. . .gpg.keyedit.delsig.unknown This signature can't be checked because you don't have the corresponding key. You should postpone its deletion until you know which key was used because this signing key might establish a trust connection through another already certified key. . .gpg.keyedit.delsig.invalid The signature is not valid. It does make sense to remove it from your keyring. . .gpg.keyedit.delsig.selfsig This is a signature which binds the user ID to the key. It is usually not a good idea to remove such a signature. Actually GnuPG might not be able to use this key anymore. So do this only if this self-signature is for some reason not valid and a second one is available. . .gpg.keyedit.updpref.okay Change the preferences of all user IDs (or just of the selected ones) to the current list of preferences. The timestamp of all affected self-signatures will be advanced by one second. . .gpg.passphrase.enter # (keep a leading empty line) Please enter the passphrase; this is a secret sentence. . .gpg.passphrase.repeat Please repeat the last passphrase, so you are sure what you typed in. . .gpg.detached_signature.filename Give the name of the file to which the signature applies. . .gpg.openfile.overwrite.okay # openfile.c (overwrite_filep) Answer "yes" if it is okay to overwrite the file. . .gpg.openfile.askoutname # openfile.c (ask_outfile_name) Please enter a new filename. If you just hit RETURN the default file (which is shown in brackets) will be used. . .gpg.ask_revocation_reason.code # revoke.c (ask_revocation_reason) You should specify a reason for the revocation. Depending on the context you have the ability to choose from this list: "Key has been compromised" Use this if you have a reason to believe that unauthorized persons got access to your secret key. "Key is superseded" Use this if you have replaced this key with a newer one. "Key is no longer used" Use this if you have retired this key. "User ID is no longer valid" Use this to state that the user ID should not longer be used; this is normally used to mark an email address invalid. . .gpg.ask_revocation_reason.text # revoke.c (ask_revocation_reason) If you like, you can enter a text describing why you issue this revocation certificate. Please keep this text concise. An empty line ends the text. . .gpg.tofu.conflict # tofu.c TOFU has detected another key with the same (or a very similar) email address. It might be that the user created a new key. In this case, you can safely trust the new key (but, confirm this by asking the person). However, it could also be that the key is a forgery or there is an active Man-in-the-Middle (MitM) attack. In this case, you should mark the key as being bad, so that it is untrusted. Marking a key as being untrusted means that any signatures will be considered bad and attempts to encrypt to the key will be flagged. If you are unsure and can't currently check, you should select either accept once or reject once. . .gpgsm.root-cert-not-trusted # This text gets displayed by the audit log if # a root certificates was not trusted. The root certificate (the trust-anchor) is not trusted. Depending on the configuration you may have been prompted to mark that root certificate as trusted or you need to manually tell GnuPG to trust that certificate. Trusted certificates are configured in the file trustlist.txt in GnuPG's home directory. If you are in doubt, ask your system administrator whether you should trust this certificate. .gpgsm.crl-problem # This text is displayed by the audit log for problems with # the CRL or OCSP checking. Depending on your configuration a problem retrieving the CRL or performing an OCSP check occurred. There are a great variety of reasons why this did not work. Check the manual for possible solutions. # Local variables: # mode: default-generic # coding: utf-8 # End:	13.93 KB	2021-08-18 08:32
📄 help.zh_CN.txt # help.zh_CN.txt - zh_CN GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. # Update by bobwxc<bobwxc@yeah.net> 2020 # Note that this help file needs to be UTF-8 encoded. When looking # for a help item, GnuPG scans the help files in the following order # (assuming a GNU or Unix system): # # /etc/gnupg/help.LL_TT.txt # /etc/gnupg/help.LL.txt # /etc/gnupg/help.txt # /usr/share/gnupg/help.LL_TT.txt # /usr/share/gnupg/help.LL.txt # /usr/share/gnupg/help.txt # # Here LL_TT denotes the full name of the current locale with the # territory (.e.g. "de_DE"), LL denotes just the locale name # (e.g. "de"). The first matching item is returned. To put a dot or # a hash mark at the beginning of a help text line, it needs to be # prefixed with ". ". A single dot may be used to terminated ahelp # entry. .#pinentry.qualitybar.tooltip # [remove the hash mark from the key to enable this text] # This entry is just an example on how to customize the tooltip shown # when hovering over the quality bar of the pinentry. We don't # install this text so that the hardcoded translation takes # precedence. An administrator should write up a short help to tell # the users about the configured passphrase constraints and save that # to /etc/gnupg/help.txt. The help text should not be longer than # about 800 characters. This bar indicates the quality of the passphrase entered above. As long as the bar is shown in red, GnuPG considers the passphrase too weak to accept. Please ask your administrator for details about the configured passphrase constraints. . .gnupg.agent-problem # 无法连接或启动 Gpg-Agent 。无法连接到运行的 Gpg-Agent 或与正在运行的 Gpg-Agent 发生通信问题。本系统使用一个称为 Gpg-Agent (Gpg-代理)的后台进程来处理私钥和请求密码。代理通常在用户登录时启动，并在用户在线时运行。如果没有可用的代理，系统会尝试动态启动一个代理，但该状态的代理在功能上有一定的限制，可能会导致一些小问题。您可能需要询问管理员以解决该问题。您也可以尝试注销并重新登录来尝试解决此问题。无论如何，请通知管理员此错误，因为这表明软件中存在错误。 . .gnupg.dirmngr-problem # 无法连接到 dirmngr 无法连接到一个运行的 Dirmngr 或与正在运行的 Dirmngr 发生通信问题。若要查找证书吊销列表（CRL），请执行OCSP验证并通过LDAP服务器查找公钥，本系统依赖于名为 Dirmngr 的外部服务程序。Dirmngr 通常作为系统服务（守护进程）运行，无需用户管理。当守护进程出现问题时，系统可能会为每个请求启动自己的Dirmngr副本，这是一种性能有限的解决方法。如果遇到此问题，应询问系统管理员如何解决。作为一个临时解决方案，您可以尝试在 gpgsm 的配置中禁用 CRL 检查。 . .gpg.edit_ownertrust.value #标识前缀为“gpg”的帮助曾经为gpg的硬编码 #现在可能被此文件中的帮助文本覆盖。在这里指定的数值完全由您自己决定；这些数值永远不会被导出给任何第三方。我们需要它来实现“信任网络”；这与被隐式创建的“证书验证网络”无关。 . .gpg.edit_ownertrust.set_ultimate.okay 要建立起信任网络，GnuPG 需要知道哪些密钥是可绝对信任的――通常就是您拥有私钥的那些密钥。回答“yes”将此密钥设成可绝对信任的。 . .gpg.untrusted_key.override 如果您坚持要求使用这把未被信任的公钥，请回答“yes”。 . .gpg.pklist.user_id.enter 输入您要所发送报文的接收者的用户标识。 . .gpg.keygen.algo 选择使用的算法。 DSA 即“数字签名算法”(曾用于美国国家标准DSS)，只能够用作签名。 Elgamal 是一种只能用作加密的算法。 RSA 可以用作签名或加密。第一把密钥(主钥)必须具有签名的能力。 . .gpg.keygen.algo.rsa_se 通常来说用同一把密钥签名和加密并不是个好主意。这个算法只在特定的情况下使用。请事先咨询您的安全指导专家。 . .gpg.keygen.cardkey 从卡中选择要使用的密钥。列表显示了密钥索引，钥柄（keygrip，一个十六进制数字串），卡特别的密钥引用，密钥算法。括注为密钥允许的用法（cert 验证, sign 签名, auth 授权, encr 加密），有星号标记的为密钥的标准用法。 . .gpg.keygen.flags 选择密钥的功能。密钥功能受限于所选算法。要快速完成功能设置，可以输入“=”作为第一个字符，后跟字母列表；指示设置的功能：“s”用于签名，“e”用于加密，而“a”用于身份验证；无效字母和不可选的功能将被忽略。使用快速设置后，此子菜单将立即结束。 . .gpg.keygen.size 请输入密钥长度。默认选项通常是个不错的选择。如果您想使用一个较大的密钥长度，例如4096位，请认真考虑它是否真的对你有意义，长密钥可能会降低性能。您可以参考该网页 http://www.xkcd.com/538/ . .gpg.keygen.size.huge.okay 请回答“yes”或“no” . .gpg.keygen.size.large.okay 请回答“yes”或“no” . .gpg.keygen.valid 请按提示输入所要求的数值。您可以输入 ISO 日期格式(YYYY-MM-DD)，但出错时您可能不会得到友好的提示――系统可能会尝试将其解释为时间间隔。 . .gpg.keygen.valid.okay 请回答“yes”或“no” . .gpg.keygen.name 请输入密钥持有人的名字 “<”与“>”字符是不允许的。例如：ZhangSan . .gpg.keygen.email 请输入电子邮件地址(可选项，但强烈推荐使用) 例如：zhangsan@example.com . .gpg.keygen.comment 请输入注释(可选项) “(”与“)”字符是不允许的。通常无需输入注释。 . .gpg.keygen.userid.cmd # （开头来一个空行）—— help.txt要求的 N 修改姓名。 C 修改注释。 E 修改电子邮件地址。 O 继续生成密钥。 Q 中止生成密钥。 . .gpg.keygen.sub.okay 如果您允许生成子钥，请回答“yes”(或者“y”)。 . .gpg.sign_uid.okay 请回答“yes”或“no” . .gpg.sign_uid.class 当您对某把密钥上某个用户标识进行签名认证时，您必须首先验证这把密钥是否确实属于在用户标识上署名的那个人。而让他人了解您对此进行了多么仔细的验证是非常必要的。 “0” 表示您对验证这把密钥所属者真实性问题不表态。 “1” 表示您相信这把密钥属于那个声称是主人的人，但是您不能或根本没有验证过。如果您为一把属于类似虚拟人物的密钥签名，这个选项很有用。 “2” 表示您随意地验证了那把密钥。例如，您验证了这把密钥的指纹，或比对了照片以验证用户标识。 “3” 表示您做了大量而详尽的验证密钥工作。例如，您同密钥持有人直接联系验证了密钥指纹，而且通过查验附带照片且难以伪造的证件（如身份证)确认了密钥持有人的姓名与密钥上的用户标识一致，最后您还（通过电子邮件往来）验证了密钥上的电子邮件地址确实属于密钥持有人。请注意上述关于验证级别 2 和 3 的说明仅是例子而已，最终还是由您自己决定当您为其他密钥签名时，什么是“随意”，而什么是“大量而详尽”。如果您不知道应该选什么，请选“0”。 . .gpg.change_passwd.empty.okay 请回答“yes”或“no” . .gpg.keyedit.save.okay 请回答“yes”或“no” . .gpg.keyedit.cancel.okay 请回答“yes”或“no” . .gpg.keyedit.sign_all.okay 如果您想要为所有用户标识签名的话就选“yes” . .gpg.keyedit.remove.uid.okay 如果您真的想要删除这个用户标识的话就回答“yes”。所有相关认证在此之后也会丢失！ . .gpg.keyedit.remove.subkey.okay 如果要删除这把子钥，请回答“yes” . .gpg.keyedit.delsig.valid 这是一份在这把密钥上有效的签名；通常您不会想要删除这份签名，因为要与“这把密钥”或“拥有这把密钥的签名的密钥”建立认证关系可能相当重要。 . .gpg.keyedit.delsig.unknown 这份签名无法被检验，因为您没有相应的公钥。您应该暂缓删除它，直到您知道此签名使用了哪一把密钥；因为用来签名的密钥可能与其他已经验证的密钥存在信任关系。 . .gpg.keyedit.delsig.invalid 这份签名无效。应当把它从您的钥匙环里删除。 . .gpg.keyedit.delsig.selfsig 这是一份将密钥与用户标识相联系的签名，通常不应删除这样的签名。一旦删除，GnuPG 将可能无法再使用这把密钥。因此，只有在这把密钥的第一个自签名因某些原因失效，而拥有另一个可用自签名的情况下才这么做。 . .gpg.keyedit.updpref.okay 用现有的首选项更新所有（或选定的）用户标识的首选项。所有受影响的自签名的时间戳都会增加一秒钟。 . .gpg.passphrase.enter # （开头来一个空行）—— help.txt要求的请输入密码： . .gpg.passphrase.repeat 请再次输入密码，以确认输入了正确的密码。 . .gpg.detached_signature.filename 请给定要添加签名的文件名 . .gpg.openfile.overwrite.okay 如果要覆盖这个文件，请回答“yes” . .gpg.openfile.askoutname 请输入一个新的文件名。直接按下回车以使用默认文件名（括号中）。 . .gpg.ask_revocation_reason.code 您需要为这份吊销证书指定一个原因。根据情况的不同，您可以从下列清单中选出一项： “密钥已泄漏” 如果您相信有某个未经许可的人已取得了您的私钥，请选此项。 “密钥已替换” 如果您已用一把新密钥代替旧的，请选此项。 “密钥不再被使用” 如果您已决定让这把密钥退休，请选此项 “用户标识不再有效” 如果这个用户标识不再被使用了，请选此项；这通常用表明某个电子邮件地址已不再有效。 . .gpg.ask_revocation_reason.text # revoke.c (ask_revocation_reason) 您也可以输入一串文字，描述发布这份吊销证书的理由，请尽量简明扼要。输入一个空行以结束输入。 . .gpg.tofu.conflict # tofu.c TOFU 检测到了另一个电子邮件地址相同（或非常相似）的密钥。可能是用户创建了一个新的密钥；在这种情况下，您可以放心地信任新密钥（请通过询问此人来确认这一点）。但此密钥也可能是伪造的，或者有一个活跃的中间人（MitM）攻击；在这种情况下，应该将密钥标记为不受信的，这样它就不可信了。将密钥标记为不受信任意味着其任何签名都将被认为是无效的，并将标记所有使用该密钥进行的加密。如果您不确定且当前无法检查，则应选择接受一次或拒绝一次。 . .gpgsm.root-cert-not-trusted # This text gets displayed by the audit log if # a root certificates was not trusted. #如果根证书不受信任，审核日志将显示此文本。根证书（信任基础）不受信任。根据配置，可能会提示您将根证书标记为受信任的，或者您需要手动告诉 GnuPG 信任该证书。记载了受信任证书的 trustlist.txt 在GnuPG的主目录中。如有疑问，请询问系统管理员是否应信任此证书。 . .gpgsm.crl-problem #当CRL或OCSP检查出现问题，审核日志将显示此文本。您的配置在检索CRL或执行OCSP检查时出现问题。有很多不同的原因，查看手册以了解可能的解决方案。 . # Local variables: # mode: fundamental # coding: utf-8 # End:	12.33 KB	2020-12-23 13:46
📄 help.zh_TW.txt # help.zh_TW.txt - zh_TW GnuPG online help # Copyright (C) 2007 Free Software Foundation, Inc. # # This file is part of GnuPG. # # GnuPG 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. # # GnuPG 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 <https://www.gnu.org/licenses/>. # Note that this help file needs to be UTF-8 encoded. When looking # for a help item, GnuPG scans the help files in the following order # (assuming a GNU or Unix system): # # /etc/gnupg/help.LL_TT.txt # /etc/gnupg/help.LL.txt # /etc/gnupg/help.txt # /usr/share/gnupg/help.LL_TT.txt # /usr/share/gnupg/help.LL.txt # /usr/share/gnupg/help.txt # # Here LL_TT denotes the full name of the current locale with the # territory (.e.g. "de_DE"), LL denotes just the locale name # (e.g. "de"). The first matching item is returned. To put a dot or # a hash mark at the beginning of a help text line, it needs to be # prefixed with ". ". A single dot may be used to terminated ahelp # entry. .#pinentry.qualitybar.tooltip # [remove the hash mark from the key to enable this text] # This entry is just an example on how to customize the tooltip shown # when hovering over the quality bar of the pinentry. We don't # install this text so that the hardcoded translation takes # precedence. An administrator should write up a short help to tell # the users about the configured passphrase constraints and save that # to /etc/gnupg/help.txt. The help text should not be longer than # about 800 characters. 本指示條顯示上方輸入的密語的強度。本處若顯示為紅色，代表該密語強度不足，不能被 GnuPG 接受。請與管理者詢問關於密語強度的細節。 . .gnupg.agent-problem # There was a problem accessing or starting the agent. 無法連接執行中的 Gpg-Agent，或與執行中的 Gpg-Agent 通訊時出現異常。本系統使用稱為 Gpg-Agent 的背景程式，以代理處理私鑰或詢問密文。該代理程式會在使用者登入時執行，並持續執行直到使用者登出為止。若沒有代理程式，系統會在執行時嘗試使用一個功能受限的代理程式，該版本的代理程式可能會導致一些問題。您可能需要詢問管理者如何解決這個問題，作為臨時方案，您可以嘗試登出後重新登入，並檢查問題是否能改善。即使以上方法有用，也請告知系統管理者，因為這代表軟體可能存在瑕疵。 . .gnupg.dirmngr-problem # There was a problen accessing the dirmngr. 無法連接到執行中的 Dirmngr，或與執行中的 Dirmngr 通訊時出現異常。為了查詢憑證吊銷列表 (CRL)、執行 OCSP 金鑰驗證、與 LDAP 伺服器查詢金鑰，本系統會使用一個外部工具稱為 Dirmngr。Dirmngr 通常會以系統服務（常駐程式）的形式執行，使用者無須注意。若此處出現問題，作為臨時方案，系統每次在接到請求時會執行內建版本的 Dirmngr，因而導致效能上的限制。若您遇上這個問題，您可以與系統管理者詢問如何處理。作為暫代方案，您可以關閉在 gpgsm 的設定中關閉 CRL 的檢查。 . .gpg.edit_ownertrust.value # The help identies prefixed with "gpg." used to be hard coded in gpg # but may now be overridden by help texts from this file. 您可以自由決定是否要設定本值，該值不會輸出到任何第三方。本值只是為了實作信任網路而設，與（隱式建立的）憑證網路沒有關係。 . .gpg.edit_ownertrust.set_ultimate.okay 要建構信任網絡, GnuPG 需要知道哪些是徹底信任的金鑰——通常是指您可以存取到私鑰的金鑰。若要設定為徹底信任的金鑰，請回答 "yes"。 .gpg.untrusted_key.override 如果您仍要使用這把不受信任的金鑰, 請回答 "yes"。 . .gpg.pklist.user_id.enter 請輸入本訊息接收者的使用者 ID。 . .gpg.keygen.algo 請選擇要使用的金鑰演算法。 DSA（又稱 DSS）是數位簽章演算法 (Digital Signature Algorithm)，只能用於簽署。 Elgamal 是只能用於加密的演算法。 RSA 可以作為簽署及加密使用。第一把（主要的）金鑰必須要是能用於簽署的金鑰。 . .gpg.keygen.algo.rsa_se 通常來說用同一把金鑰簽署及加密並不是個好主意。這個演算法應該只能用於特定的領域。請先聯絡您的安全專家。 . .gpg.keygen.cardkey 請從本卡片選擇要使用的金鑰。本清單依序顯示選擇索引、鑰柄（十六進位字串）、卡片特定的金鑰參照、該金鑰的演算法，括號內會顯示金鑰的用途（cert 證書、sign 簽名、auth 認證、encr 加密）。若能得知預設的金鑰用途，會以星號標示。 . .gpg.keygen.flags 切換金鑰的功能。金鑰可以擁有哪些功能，受限於使用的金鑰演算法。若要快速設定金鑰的功能，您可以輸入 '=' 後接以下字元組合的字串： 's' 簽名、'e' 加密、'a' 認證。無效的字元跟無法設定的功能會被忽略。本子選單會在使用此快速設定的方法後立即關閉。 . .gpg.keygen.size 請輸入金鑰的大小。建議的金鑰大小通常是良好的選擇。若您要使用較大的金鑰大小，例如 4096 位元，請再三考慮是否合理。您可以參考以下網址：https://www.xkcd.com/538/。 . .gpg.keygen.size.huge.okay 請回答 "yes" 或 "no"。 . .gpg.keygen.size.large.okay 請回答 "yes" 或 "no"。 . .gpg.keygen.valid 請輸入提示裡要求的值。輸入 ISO 日期格式 (YYYY-MM-DD) 雖然會被接受，但是因為系統會解析成區間，因此不會得到正常的錯誤回應。 . .gpg.keygen.valid.okay 請回答 "yes" 或 "no"。 . .gpg.keygen.name 請輸入金鑰持有人的名字。字元 "<" 跟 ">" 不會被接受。例：Heinrich Heine . .gpg.keygen.email 請輸入 Email 地址（非必要，但強烈建議使用）。例：heinrichh@duesseldorf.de . .gpg.keygen.comment 請輸入註釋（非必要）。字元 "(" 跟 ")" 不會被接受。通常不需要寫入註釋。 . .gpg.keygen.userid.cmd # (Keep a leading empty line) N 修改姓名。 C 修改註釋。 E 修改 Email 地址。 O 繼續產生金鑰。 Q 中止產生金鑰。 . .gpg.keygen.sub.okay 如果要產生子鑰的話, 請回答 "yes" (或 "y")。 . .gpg.sign_uid.okay 請回答 "yes" 或 "no"。 . .gpg.sign_uid.class 當您在某把金鑰上簽署某個使用者 ID，您首先必須先驗證那把金鑰確實屬於該使用者 ID 上所代表的人。可以讓其他人知道您驗證該金鑰的詳細程度。 "0" 表示您不特別聲明您驗證那把金鑰的詳細程度。 "1" 表示您相信這把金鑰屬於那個主張是主人的人，但是您不能，或是完全沒有驗證那把金鑰。這對「人格上」的驗證，亦即簽署化名使用者的金鑰來說是有用的。 "2" 表示您做了快速的金鑰驗證。例如，這能表示您驗證了這把金鑰的指紋並將使用者 ID 與相片證件對照。 "3" 表示您做了仔細的金鑰驗證。例如，這能表示您當面向金鑰持有人驗證了金鑰指紋，並透過附帶照片而難以偽造的文件（像是護照）確認了金鑰持有人的姓名與金鑰上的使用者 ID 一致，最後您（透過 Email 往來）驗證了金鑰上的 Email 位址確實屬於金鑰持有人。請注意上述關於等級 2 和 3 的範例只是範例而已。到頭來還是得由您來決定當您簽署其他的金鑰時，「快速」與「仔細」的意義。若您不知道正確回答為何，請回答 "0"。 . .gpg.change_passwd.empty.okay 請回答 "yes" 或 "no"。 . .gpg.keyedit.save.okay 請回答 "yes" 或 "no"。 . .gpg.keyedit.cancel.okay 請回答 "yes" 或 "no"。 . .gpg.keyedit.sign_all.okay 如果您想要簽署所有使用者 ID 的話請回答 "yes"。 . .gpg.keyedit.remove.uid.okay 如果您真的想要刪除這個使用者 ID 的話請回答 "yes"。所有的憑證也會因此刪除！ . .gpg.keyedit.remove.subkey.okay 如果要刪除這把子鑰的話請回答 "yes"。 . .gpg.keyedit.delsig.valid 這是一份在這把金鑰上有效的簽章；通常您不會想要刪除這份簽章，因為建立與該金鑰（或與由該金鑰信任的其他金鑰）的信任連結，會是一件重要的事情。 . .gpg.keyedit.delsig.unknown 因為您沒有持有對應的金鑰，這份簽章無法被檢驗。您應該在知道哪一把金鑰被用來簽署前，暫緩刪除簽章的動作；因為這把來簽署的金鑰可能透過其他已經驗證的金鑰建立了信任連結。 . .gpg.keyedit.delsig.invalid 這份簽章無效。把它從您的鑰匙圈裡移除是合理的。 . .gpg.keyedit.delsig.selfsig 這是一份和這個金鑰使用者 ID 相繫的簽章。通常把這樣的簽章移除不會是個好主意。實際上 GnuPG 可能從此就不能再使用這把金鑰了。所以只有在這把金鑰的第一個自我簽章因某些原因無效，而第二個還可用的情況下才這麼做。 . .gpg.keyedit.updpref.okay 變更所有 (或只有被選取的那幾個) 使用者 ID 的偏好成現用的偏好清單。所有受到影響的自我簽章的時間戳記都會增加一秒鐘。 . .gpg.passphrase.enter # (keep a leading empty line) 請輸入密語; 密語代表為一個秘密的句子。 . .gpg.passphrase.repeat 請重新輸入先前的密語, 以確定您到底輸入了什麼。 . .gpg.detached_signature.filename 請給定簽章所要套用的檔案名稱。 . .gpg.openfile.overwrite.okay # openfile.c (overwrite_filep) 若要覆寫這個檔案的話，請回答 "yes"。 . .gpg.openfile.askoutname # openfile.c (ask_outfile_name) 請輸入一個新的檔名。若直接按下 Enter 則會使用預設的檔案 (顯示在括號中)。 . .gpg.ask_revocation_reason.code # revoke.c (ask_revocation_reason) 您應該為這份憑證指定一個原因。根據情境不同，您能夠從這個清單中選擇一個：「金鑰已經被洩漏了」使用此選項，若您相信有某個未經許可的人取得了您的私鑰。「金鑰被代換了」使用此選項，如果您把您的金鑰換成新的了。「金鑰不再被使用了」使用此選項，如果您已經撤回了這把金鑰。「使用者 ID 不再有效了」使用此選項，如果這個使用者 ID 已不再使用；這通常用來表示某個 Email 地址已經無效。 . .gpg.ask_revocation_reason.text # revoke.c (ask_revocation_reason) 您也可以輸入文字來描述為甚麼發佈這份撤銷憑證的理由。請讓這段文字保持簡明扼要。請輸入一個空行以結束文字。 . .gpg.tofu.conflict # tofu.c TOFU 偵測到其他的金鑰持有一樣（或是非常類似）的 Email 地址。可能是該使用者建立了新的金鑰，若為如此，您可以安全地信任該金鑰（但請與該使用者確認）。但也有可能是偽造的金鑰，或是有中間人攻擊 (MitM) 正在進行中，若為如此，您應該要標記該不良金鑰，該金鑰將會不受信任。標記一個金鑰為「不受信任」代表該金鑰的簽名也會被當成不良簽章，且使用該金鑰加密也會出現警告。若您無法確定，並且不能檢查該金鑰，您應選擇「接受一次」或「拒絕一次」。 . .gpgsm.root-cert-not-trusted # This text gets displayed by the audit log if # a root certificates was not trusted. 根憑證（信任的基點）不受信任。根據設定，您可能已被要求需要設定根憑證為信任憑證，或是您需要手動告知 GnuPG 信任該憑證。信任憑證的設定在 GnuPG 的家目錄下的 trustlist.txt。若有疑慮，請詢問系統管理者是否該信任此憑證。 .gpgsm.crl-problem # This text is displayed by the audit log for problems with # the CRL or OCSP checking. 根據您的設定，在取得憑證吊銷列表 (CRL) 或是透過 OCSP 檢查憑證狀態時出現問題。該問題的產生有很多因素，請詳閱說明文件以找出可能解法。 # Local variables: # mode: default-generic # coding: utf-8 # End:	12.39 KB	2020-12-30 14:03
📄 sks-keyservers.netCA.pem -----BEGIN CERTIFICATE----- MIIFizCCA3OgAwIBAgIJAK9zyLTPn4CPMA0GCSqGSIb3DQEBBQUAMFwxCzAJBgNV BAYTAk5PMQ0wCwYDVQQIDARPc2xvMR4wHAYDVQQKDBVza3Mta2V5c2VydmVycy5u ZXQgQ0ExHjAcBgNVBAMMFXNrcy1rZXlzZXJ2ZXJzLm5ldCBDQTAeFw0xMjEwMDkw MDMzMzdaFw0yMjEwMDcwMDMzMzdaMFwxCzAJBgNVBAYTAk5PMQ0wCwYDVQQIDARP c2xvMR4wHAYDVQQKDBVza3Mta2V5c2VydmVycy5uZXQgQ0ExHjAcBgNVBAMMFXNr cy1rZXlzZXJ2ZXJzLm5ldCBDQTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoC ggIBANdsWy4PXWNUCkS3L//nrd0GqN3dVwoBGZ6w94Tw2jPDPifegwxQozFXkG6I 6A4TK1CJLXPvfz0UP0aBYyPmTNadDinaB9T4jIwd4rnxl+59GiEmqkN3IfPsv5Jj MkKUmJnvOT0DEVlEaO1UZIwx5WpfprB3mR81/qm4XkAgmYrmgnLXd/pJDAMk7y1F 45b5zWofiD5l677lplcIPRbFhpJ6kDTODXh/XEdtF71EAeaOdEGOvyGDmCO0GWqS FDkMMPTlieLA/0rgFTcz4xwUYj/cD5e0ZBuSkYsYFAU3hd1cGfBue0cPZaQH2HYx Qk4zXD8S3F4690fRhr+tki5gyG6JDR67aKp3BIGLqm7f45WkX1hYp+YXywmEziM4 aSbGYhx8hoFGfq9UcfPEvp2aoc8u5sdqjDslhyUzM1v3m3ZGbhwEOnVjljY6JJLx MxagxnZZSAY424ZZ3t71E/Mn27dm2w+xFRuoy8JEjv1d+BT3eChM5KaNwrj0IO/y u8kFIgWYA1vZ/15qMT+tyJTfyrNVV/7Df7TNeWyNqjJ5rBmt0M6NpHG7CrUSkBy9 p8JhimgjP5r0FlEkgg+lyD+V79H98gQfVgP3pbJICz0SpBQf2F/2tyS4rLm+49rP fcOajiXEuyhpcmzgusAj/1FjrtlynH1r9mnNaX4e+rLWzvU5AgMBAAGjUDBOMB0G A1UdDgQWBBTkwyoJFGfYTVISTpM8E+igjdq28zAfBgNVHSMEGDAWgBTkwyoJFGfY TVISTpM8E+igjdq28zAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBQUAA4ICAQAR OXnYwu3g1ZjHyley3fZI5aLPsaE17cOImVTehC8DcIphm2HOMR/hYTTL+V0G4P+u gH+6xeRLKSHMHZTtSBIa6GDL03434y9CBuwGvAFCMU2GV8w92/Z7apkAhdLToZA/ X/iWP2jeaVJhxgEcH8uPrnSlqoPBcKC9PrgUzQYfSZJkLmB+3jEa3HKruy1abJP5 gAdQvwvcPpvYRnIzUc9fZODsVmlHVFBCl2dlu/iHh2h4GmL4Da2rRkUMlbVTdioB UYIvMycdOkpH5wJftzw7cpjsudGas0PARDXCFfGyKhwBRFY7Xp7lbjtU5Rz0Gc04 lPrhDf0pFE98Aw4jJRpFeWMjpXUEaG1cq7D641RpgcMfPFvOHY47rvDTS7XJOaUT BwRjmDt896s6vMDcaG/uXJbQjuzmmx3W2Idyh3s5SI0GTHb0IwMKYb4eBUIpQOnB cE77VnCYqKvN1NVYAqhWjXbY7XasZvszCRcOG+W3FqNaHOK/n/0ueb0uijdLan+U f4p1bjbAox8eAOQS/8a3bzkJzdyBNUKGx1BIK2IBL9bn/HravSDOiNRSnZ/R3l9G ZauX0tu7IIDlRCILXSyeazu0aj/vdT3YFQXPcvt5Fkf5wiNTo53f72/jYEJd6qph WrpoKqrwGwTpRUCMhYIUt65hsTxCiJJ5nKe39h46sg== -----END CERTIFICATE-----	1.94 KB	2016-02-02 06:05

Edit File:

Terminal