shell bypass 403

GrazzMean Shell

: /usr/share/locale/et/LC_MESSAGES/ [ drwxr-xr-x ]
Uname: Linux web3.us.cloudlogin.co 5.10.226-xeon-hst #2 SMP Fri Sep 13 12:28:44 UTC 2024 x86_64
Software: Apache
PHP version: 8.1.31 [ PHP INFO ] PHP os: Linux
Server Ip: 162.210.96.117
Your Ip: 3.144.115.207
User: edustar (269686) | Group: tty (888)
Safe Mode: OFF
Disable Function:
NONE

name : gnupg1.mo
��}U�'@5-A5�o5�5�6727O7l7�7�7D�7.8I78�8�8�8�8�89$9@9Y9$v9&�9,�9�9::<:N:h:]�:�:/�:(&;.O;3~;�;�;�;�;<!<4<M<i<"�<�<�<�<"�<%=&-=!T=%v="�=#�='�= >,>I>^>{>�>�>(�>$�>??#0?T?s?�?�?&�?%�?,@4C@x@�@�@�@�@'�@A/AMA_ArA�A"�A�A�A-�A(B0EBHvB	�B�C�C�CAD/CD0sD\�DE-E0DE.uE�E�E�E3�E4F-HF�vF.0G_G	hG
rG:�G�G�G#�G&H&@HgH~H�H�HG�H@�H>=I+|I=�I�I"�I:JTJgJyJ �J/�J��J�KH�K-L
?LJL8]L#�L�L"�L��LE}M��M;YN��NIOgO�O$�O�O�O��O�P�P�PQ)Q?QRQbQtQ%�Q�Q��Q MR!nR<�R�R"�R,S,8S2eS�S �S(�S �S
T**TUTgT�T�T�T�T"�TUU/UEOUo�U V &V8GV'�Vc�V/WE<W,�W#�W-�W)X�+XY'Z�=Z�Z�Z�Z[1[(I[r[�[�[�[ �[}�[q]/�]�]�]�]�]j^�z^9_OA_5�_.�_�_�a�a�a�a!b6b�RbGc-fc�c��cwd�d*�d+�d�d e2eKe%fe�e7�e�er^f>�f1g=BgI�g4�g�g#h=Bh�h?�hD�h1%i5WiH�i-�iHj�Mj�j<�jB/k)rkC�k.�k@lFPl2�l1�l �l2mPmhQn*�s&�s1t#>t2bt>�t��t=�u0�uM�u"Cv&fv3�v%�vD�v,,y5Yy�y�y_�y
zz(z9zEz%^z�z�z�z
�z�z
�z�z{*{2{:{J{R{a{p{
{�{�{�{�{�{�{ |-|.K|%z|2�|�|�|�|}-}B}5W}�}�};�}<�}/~E~&[~�~�~-�~(�~�~10by�������2�$O�=t�%��؀ ��1�H�`�|�&��&Á���K�%^�$������̂ނ���
��@-�
n�|�!��D��+��/'�W�`�~�%��%��$܄�
� �.7�f����2���� �8�+H�t���$��&��$�,�4�C�GZ�H��B�.�D�T�r�����Ȉ��	�'�B�[�u�����'����.�@�(R�,{�����
Ɋ
׊$��%� (�I�%h���&��ҋ��!�#�A�V�%u�%����
ی
�
�� �#&�&J�)q���<����
�(�,H�u�;��MΎ�7�O�"g�-����+ҏ*��!)�&K�$r���������IÐ
� �;�N�#f�#������ґ
����#0�T�3e�%��%���
����"%�H�\� e�5��$���4��%1�*W�0����Ӕ.ܔ*��6�+Ǖ/�%#�I�(\���-��/Ȗ,��"%�)H�r��� ��͗�#�-(�V�Iu���Ϙ�
��.�I�b�v�����ř#ՙ��	�#�7� K�l������ɚܚ6�#+� O�p���������-›�
�)�E�a�y���������D��F��EF�D��Aѝ7�K�$h�F�� Ԟ��$�#1�U�#n�j��/���-��������ˢ��"�?�5\�+��B����8�!W�y�'��%��'��'�1G�.y���ť"ޥ�� 2�eS���-̦+��0&�6W�������˧�
	��(�E�&d���!����"ɨ&�(�)<�)f�#��(��)ݩ$�,�J�$^�������.Ϊ.��,�C�&Y�������ݫ&�"�*>�7i�����Ϭ��$�A�^�}�������*ӭ���**�&U�6|�D��
���	�/�?I�1��+��d�L�1c�4��8ʱ �$$�I�*R�8}�3����&��ͳֳ�8�!(�J�*j�'��)������
/�>=�H|�>ŵ8�2=�p�)��<�����&�2A��t�4�BJ�*��
��ø-ٸ�%�),��V�;���5�JҺ�����!�$8�]�l����� '�$H�m�������Ƚڽ/�$��0�-��"�@�F�+a�5��.ÿ2� %�F�%b�)��
��1�����
�&�=�']�!����� �C��xA�#��!��/�+0�|\�/��=	�7G�&�!��-��������*��}��B�
]�k���1��1�����!�!3�#U��y�9�<V���������w���[�1�B4�,w�&��+�������������
��(��;"�^��j�f�	|�2��3����+
�6�V�+u���4�����}}�:��/6�Cf�M��3��),�"V�?y���A��B�*Z�5��?��,��?(��h���8�OK�1��J��/�@H�N��9��6�$I�8n������&����%��&�92�8l����:L�%��<��$��*�3:�)n�o��'�00�a�n�k{���
�����'5� ]�~�����������*���!�*�	;�E�Q�b�u���������,��	�##�1G�/y�-��>���-�0H�y���%��:���3�;O�U����
��+�2�L�0_�*������A��!-�O�#n���'�������#�A�%]�5��3����#�)�D�Y�r�*��8��9��/�?�]_�+��4���4�H�`�o�������F��� �!8�FZ�-��2����)�2>�%q�'����
����.��"�"B�e�5���������,�
D�
R�"`�&��$��,����=+�?i�J����("�(K�$t�(��&�&��
,�:�V�p�������/�#�+�'7�_�*r�$���"�
��!�"�@�!C�3e�!��#��/��$�A�'Z�����&��.�0�<�
Y�d�q�!��'��$�%��@5�v���!��*���D�EW�#��!��!�'�0-�^�%w�5��3�&-.\sv|K���''<)d����� �0 Q5d&�(���+I f
�*�3�*�A>%�1�/�!
*)5%_y�+�7+2c�;��,>-9l)�)�$�)?i�&�/�)�@"	c	t	%�	�	�	�	�	
"
;
[
s
$�
�
%�
�
�
8*T���;�!$:_s	�!�3��
",
#O
s
�
�
�
�
�
L�
I3L}F�:6L��4�-�!'5]{"�^��@�!�,%T�BVz ��!�@�����S1K0"���R4��`�Zl���(h;<�Fu�a�t|�WhxtQh5^�N�����=}\-]���<�A��Jk�8>���|'	la�w�]s�y��Q�_:B�����/��Hq���
���K���2pe���3�g$�CvH�Ek\�"g�S���W"l�+1)�F�Lm���`�F*w>���YyDV�Mw����s�
��S��fPP����*��B�{I�;�4y�o�X[+���A0��:�dX��g�z�x2�ia�r7�%.6�7�
�NU�{�;d���?�@���9}_�3?<��pb��m��R�cH�&�9GsC��j.��ZCr�z�����T&�K$^����_���f.Z�fi|��
x?�v��e�'
���n��1�m�L�uo+ ��(8��Y�~{%vO��Q�iUA/#>�-��~M*q��P�'�N�}���8�I�r)�k`M9�o��Vb�np��&OJG���Y�X6E:[W��6��t	��5���q�j������I��cbJG	���j�R�0��)7#���dn�=/$ �U��O]��\����L,!T���e2��45�
�,=#3D��Eu[c�D�-�(
Enter the user ID.  End with an empty line: 
Not enough random bytes available.  Please do some other work to give
the OS a chance to collect more entropy! (Need %d more bytes)

Pick an image to use for your photo ID.  The image must be a JPEG file.
Remember that the image is stored within your public key.  If you use a
very large picture, your key will become very large as well!
Keeping the image close to 240x288 is a good size to use.

Supported algorithms:
              imported: %lu             unchanged: %lu
           new subkeys: %lu
          new user IDs: %lu
          not imported: %lu
          w/o user IDs: %lu
         It is not certain that the signature belongs to the owner.
         The signature is probably a FORGERY.
         There is no indication that the signature belongs to the owner.
        new signatures: %lu
      Subkey fingerprint:      secret keys read: %lu
      skipped new keys: %lu
     Subkey fingerprint:   (%d) DSA (sign only)
   (%d) RSA (encrypt only)
   (%d) RSA (sign only)
   (0) I will not answer.%s
   (1) I have not checked at all.%s
   (2) I have done casual checking.%s
   (3) I have done very careful checking.%s
   new key revocations: %lu
  Unable to sign.
  secret keys imported: %lu
 (non-exportable) Primary key fingerprint: secret keys unchanged: %lu
# List of assigned trustvalues, created %s
# (Use "gpg --import-ownertrust" to restore them)
%d bad signatures
%d keys processed (%d validity counts cleared)
%d signatures not checked due to errors
%d signatures not checked due to missing keys
%d user IDs without valid self-signatures detected
%s ...
%s does not yet work with %s
%s encrypted data
%s encrypted session key
%s encryption will be used
%s is the new one
%s is the unchanged one
%s makes no sense with %s!
%s not allowed with %s!
%s signature, digest algorithm %s
%s.
%s/%s encrypted for: "%s"
%s: directory does not exist!
%s: error reading free record: %s
%s: error reading version record: %s
%s: error updating version record: %s
%s: error writing dir record: %s
%s: error writing version record: %s
%s: failed to append a record: %s
%s: failed to create hashtable: %s
%s: failed to create version record: %s%s: failed to zero a record: %s
%s: invalid file version %d
%s: invalid trustdb
%s: invalid trustdb created
%s: keyring created
%s: not a trustdb file
%s: skipped: %s
%s: skipped: public key already present
%s: skipped: public key is disabled
%s: trustdb created
%s: unknown suffix
%s: version record with recnum %lu
%s:%d: deprecated option "%s"
%s:%d: invalid export options
%s:%d: invalid import options
(No description given)
(Probably you want to select %d here)
(This is a sensitive revocation key)
(unless you specify the key by fingerprint)
(you may have used the wrong program for this task)
--clearsign [filename]--decrypt [filename]--edit-key user-id [commands]--encrypt [filename]--lsign-key user-id--output doesn't work for this command
--sign --encrypt [filename]--sign --symmetric [filename]--sign [filename]--sign-key user-id--store [filename]--symmetric [filename]-k[v][v][v][c] [user-id] [keyring]... this is a bug (%s:%d:%s)
1 bad signature
1 signature not checked due to a missing key
1 signature not checked due to an error
1 user ID without valid self-signature detected
@
(See the man page for a complete listing of all commands and options)
@
Examples:

 -se -r Bob [file]          sign and encrypt for user Bob
 --clearsign [file]         make a clear text signature
 --detach-sign [file]       make a detached signature
 --list-keys [names]        show keys
 --fingerprint [names]      show fingerprints
@
Options:
 @Commands:
 ASCII armored output forced.
Answer "yes" (or just "y") if it is okay to generate the sub key.Answer "yes" if it is okay to delete the subkeyAnswer "yes" if it is okay to overwrite the fileAnswer "yes" if you really want to delete this user ID.
All certificates are then also lost!Answer "yes" or "no"Are you sure you still want to add it? (y/N) Are you sure you still want to revoke it? (y/N) Are you sure you still want to sign it? (y/N) Can't check signature: %s
Can't edit this key: %s
CancelCertificates leading to an ultimately trusted key:
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? Change (N)ame, (C)omment, (E)mail or (Q)uit? 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.
Changing expiration time for the primary key.
Cipher: Comment: Compression: Create a revocation certificate for this signature? (y/N) Critical signature notation: Critical signature policy: Delete this good signature? (y/N/q)Delete this invalid signature? (y/N/q)Delete this unknown signature? (y/N/q)Deleted %d signature.
Deleted %d signatures.
Detached signature.
Digest: Do you want to issue a new signature to replace the expired one? (y/N) Do you want to promote it to a full exportable signature? (y/N) Do you want to promote it to an OpenPGP self-signature? (y/N) Do you want to sign it again anyway? (y/N) Do you want your signature to expire at the same time? (Y/n) Email address: Enter JPEG filename for photo ID: Enter an optional description; end it with an empty line:
Enter new filenameEnter passphrase
Enter passphrase: Enter the name of the key holderEnter the new passphrase for this secret key.

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.Enter the size of the keyEnter the user ID of the addressee to whom you want to send the message.Enter the user ID of the designated revoker: Features: File `%s' exists. Give the name of the file to which the signature appliesGo ahead and type your message ...
Hash: Hint: Select the user IDs to sign
How carefully have you verified the key you are about to sign actually belongs
to the person named above?  If you don't know what to answer, enter "0".
IDEA cipher unavailable, optimistically attempting to use %s instead
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.
If you want to use this untrusted key anyway, answer "yes".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.Invalid character in comment
Invalid character in name
Invalid command  (try "help")
Invalid passphrase; please try againInvalid selection.
Is this photo correct (y/N/q)? 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.Key available at: Key generation canceled.
Key generation failed: %s
Key has been compromisedKey is no longer usedKey is protected.
Key is revoked.Key is supersededKey is valid for? (0) Key not changed so no update needed.
KeyringN  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.NOTE: %s is not for normal use!
NOTE: This key is not protected!
NOTE: creating subkeys for v3 keys is not OpenPGP compliant
NOTE: key has been revokedNOTE: no default option file `%s'
NOTE: old default options file `%s' ignored
NOTE: sender requested "for-your-eyes-only"
NOTE: simple S2K mode (0) is strongly discouraged
NOTE: trustdb not writable
Name may not start with a digit
Name must be at least 5 characters long
Need the secret key to do this.
NnCcEeOoQqNo corresponding signature in secret ring
No help availableNo help available for `%s'No reason specifiedNo such user ID.
No user ID with index %d
Not a valid email address
Note: This key has been disabled.
Note: This key has expired!
Nothing deleted.
Please correct the error first
Please don't put the email address into the real name or the comment
Please enter a new filename. If you just hit RETURN the default
file (which is shown in brackets) will be used.Please enter an optional commentPlease enter name of data file: Please enter the passphrase; this is a secret sentence 
Please fix this possible security flaw
Please note that the shown key validity is not necessarily correct
unless you restart the program.
Please remove selections from the secret keys.
Please repeat the last passphrase, so you are sure what you typed in.Please report bugs to <gnupg-bugs@gnu.org>.
Please select exactly one user ID.
Please select the reason for the revocation:
Please select what kind of key you want:
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Please specify how long the signature should be valid.
         0 = signature does not expire
      <n>  = signature expires in n days
      <n>w = signature expires in n weeks
      <n>m = signature expires in n months
      <n>y = signature expires in n years
Please use the command "toggle" first.
Please wait, entropy is being gathered. Do some work if it would
keep you from getting bored, because it will improve the quality
of the entropy.
Primary key fingerprint:Pubkey: Public key is disabled.
Real name: Really create the revocation certificates? (y/N) Really delete this self-signature? (y/N)Reason for revocation: %s
Repeat passphrase
Repeat passphrase: Requested keysize is %u bits
Revocation certificate created.
Revocation certificate created.

Please move it to a medium which you can hide away; if Mallory gets
access to this certificate he can use it to make your key unusable.
It is smart to print this certificate and store it away, just in case
your media become unreadable.  But have some caution:  The print system of
your machine might store the data and make it available to others!
Secret key is available.
Secret parts of primary key are not available.
Signature expired %s
Signature expires %s
Signature notation: Signature policy: Syntax: gpg [options] [files]
Sign, check, encrypt or decrypt
Default operation depends on the input data
The random number generator is only a kludge to let
it run - it is in no way a strong RNG!

DON'T USE ANY DATA GENERATED BY THIS PROGRAM!!

The self-signature on "%s"
is a PGP 2.x-style signature.
The signature is not valid.  It does make sense to remove it from
your keyring.There are no preferences on a PGP 2.x-style user ID.
This command is not allowed while in %s mode.
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.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.This key belongs to us
This key has been disabledThis key has expired!This key is due to expire on %s.
This key is not protected.
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.This signature expired on %s.
This would make the key unusable in PGP 2.x.
To be revoked by:
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
Total number processed: %lu
UncompressedUsage: gpg [options] [files] (-h for help)Usage: gpgv [options] [files] (-h for help)User ID "%s" is expired.User ID "%s" is not self-signed.User ID "%s" is revoked.User ID is no longer validWARNING: "%s" is a deprecated option
WARNING: %s overrides %s
WARNING: 2 files with confidential information exists.
WARNING: This is a PGP 2.x-style key.  Adding a designated revoker may cause
         some versions of PGP to reject this key.
WARNING: This is a PGP2-style key.  Adding a photo ID may cause some versions
         of PGP to reject this key.
WARNING: This key has been revoked by its designated revoker!
WARNING: This key has been revoked by its owner!
WARNING: This key is not certified with a trusted signature!
WARNING: This key is not certified with sufficiently trusted signatures!
WARNING: This subkey has been revoked by its owner!
WARNING: Using untrusted key!
WARNING: We do NOT trust this key!
WARNING: Weak key detected - please change passphrase again.
WARNING: `%s' is an empty file
WARNING: a user ID signature is dated %d seconds in the future
WARNING: appointing a key as a designated revoker cannot be undone!
WARNING: encrypted message has been manipulated!
WARNING: invalid size of random_seed file - not used
WARNING: message was encrypted with a weak key in the symmetric cipher.
WARNING: message was not integrity protected
WARNING: multiple signatures detected.  Only the first will be checked.
WARNING: no user ID has been marked as primary.  This command may
              cause a different user ID to become the assumed primary.
WARNING: nothing exported
WARNING: options in `%s' are not yet active during this run
WARNING: potentially insecure symmetrically encrypted session key
WARNING: program may create a core file!
WARNING: recipients (-r) given without using public key encryption
WARNING: signature digest conflict in message
WARNING: this key might be revoked (revocation key not present)
WARNING: unable to %%-expand notation (too large).  Using unexpanded.
WARNING: unable to remove temp directory `%s': %s
WARNING: unable to remove tempfile (%s) `%s': %s
WARNING: using insecure memory!
WARNING: using insecure random number generator!!
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
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".You are about to revoke these signatures:
You are using the `%s' character set.
You can't change the expiration date of a v3 key
You can't delete the last user ID!
You did not specify a user ID. (you may use "-r")
You don't want a passphrase - this is probably a *bad* idea!

You don't want a passphrase - this is probably a *bad* idea!
I will do it anyway.  You can change your passphrase at any time,
using this program with the option "--edit-key".

You may not add a designated revoker to a PGP 2.x-style key.
You may not add a photo ID to a PGP2-style key.
You may not make an OpenPGP signature on a PGP 2.x key while in --pgp2 mode.
You must select at least one key.
You must select at least one user ID.
You need a Passphrase to protect your secret key.

You selected this USER-ID:
    "%s"

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.
Your current signature on "%s"
has expired.
Your current signature on "%s"
is a local signature.
Your decision? Your selection? Your system can't display dates beyond 2038.
However, it will be correctly handled up to 2106.
[filename][revocation][self-signature][uncertain]`%s' already compressed
`%s' is not a regular file - ignored
`%s' is not a valid long keyID
add a photo IDadd a revocation keyadd a user IDarmor header: armor: %s
assuming %s encrypted data
assuming signed data in `%s'
bad MPIbad URIbad certificatebad keybad passphrasebad public keybad secret keybad signaturebe somewhat more quietbinarybuild_packet failed: %s
can't close `%s': %s
can't connect to `%s': %s
can't create `%s': %s
can't create directory `%s': %s
can't disable core dumps: %s
can't generate a prime with less than %d bits
can't handle public key algorithm %d
can't handle text lines longer than %d characters
can't open `%s'
can't open `%s': %s
can't open signed data `%s'
can't open the keyringcan't read `%s': %s
can't stat `%s': %s
can't use a symmetric ESK packet due to the S2K mode
can't write `%s': %s
cancelled by user
cannot appoint a PGP 2.x style key as a designated revoker
cannot avoid weak key for symmetric cipher; tried %d times!
change the ownertrustchange the passphrasechecking created signature failed: %s
checking the trustdb
checksum errorcipher algorithm %d%s is unknown or disabled
completes-needed must be greater than 0
conflicting commands
create ascii armored outputdata not saved; use option "--output" to save it
dearmoring failed: %s
decrypt data (default)decryption failed: %s
decryption okay
deleting keyblock failed: %s
do not make any changesenarmoring failed: %s
encrypt dataencrypted with %lu passphrases
encrypted with 1 passphrase
encrypted with unknown algorithm %d
encrypting a message in --pgp2 mode requires the IDEA cipher
encryption only with symmetric ciphererror creating `%s': %s
error creating keyring `%s': %s
error creating passphrase: %s
error in trailer line
error reading `%s': %s
error reading keyblock: %s
error writing keyring `%s': %s
error writing public keyring `%s': %s
error writing secret keyring `%s': %s
export keysexport keys to a key serverexternal program calls are disabled due to unsafe options file permissions
failed to initialize the TrustDB: %s
failed to rebuild keyring cache: %s
file close errorfile create errorfile delete errorfile existsfile open errorfile read errorfile rename errorfile write errorforcing symmetric cipher %s (%d) violates recipient preferences
general errorgenerate a new key pairgenerate a revocation certificategenerating the deprecated 16-bit checksum for secret key protection
gpg-agent is not available in this session
gpg-agent protocol version %d is not supported
iImMqQsSimport keys from a key serverimport/merge keysinput line %u too long or missing LF
input line longer than %d characters
invalid S2K mode; must be 0, 1 or 3
invalid argumentinvalid armorinvalid armor header: invalid armor: line longer than %d characters
invalid clearsig header
invalid dash escaped line: invalid default preferences
invalid default-cert-level; must be 0, 1, 2, or 3
invalid export options
invalid hash algorithm `%s'
invalid import options
invalid keyringinvalid min-cert-level; must be 1, 2, or 3
invalid packetinvalid passphraseinvalid personal cipher preferences
invalid personal compress preferences
invalid personal digest preferences
invalid root packet detected in proc_tree()
invalid value
key export failed: %s
key has been created %lu second in future (time warp or clock problem)
key has been created %lu seconds in future (time warp or clock problem)
key is not flagged as insecure - can't use it with the faked RNG!
keyring `%s' created
keyserver errorkeyserver receive failed: %s
keyserver refresh failed: %s
keyserver search failed: %s
keyserver send failed: %s
keysize invalid; using %u bits
keysize rounded up to %u bits
list key and user IDslist keyslist keys and fingerprintslist keys and signatureslist preferences (expert)list preferences (verbose)list secret keysmake a detached signaturemake timestamp conflicts only a warningmake_keysig_packet failed: %s
malformed CRC
malformed GPG_AGENT_INFO environment variable
malformed user idmarginals-needed must be greater than 1
moving a key signature to the correct place
nNnested clear text signatures
network errornever     new configuration file `%s' created
next trustdb check due at %s
nono corresponding public key: %s
no default secret keyring: %s
no entropy gathering module detected
no need for a trustdb check
no remote program execution supported
no secret key
no signed data
no such user idno ultimately trusted keys found
no valid OpenPGP data found.
no valid addressees
no writable keyring found: %s
no writable public keyring found: %s
no writable secret keyring found: %s
not a detached signature
not encryptednot processednot supportednote: random_seed file is empty
note: random_seed file not updated
okay, we are the anonymous recipient.
old encoding of the DEK is not supported
old style (PGP 2.x) signature
operation is not possible without initialized secure memory
option file `%s': %s
original file name='%.*s'
ownertrust information cleared
passphrase not correctly repeated; try againplease do a --check-trustdb
please enter an optional but highly suggested email addressplease see http://www.gnupg.org/documentation/faqs.html for more information
please use "%s%s" instead
premature eof (in CRC)
premature eof (no CRC)
problem handling encrypted packet
problem with the agent - disabling agent use
prompt before overwritingprotection algorithm %d%s is not supported
public and secret key created and signed.
public key decryption failed: %s
public key does not match secret key!
public key encrypted data: good DEK
public key not foundqQquitquit this menuquoted printable character in armor - probably a buggy MTA has been used
reading from `%s'
reading options from `%s'
reading stdin ...
reason for revocation: remove keys from the public keyringremove keys from the secret keyringresource limitrevocation comment: rounded up to %u bits
save and quitsearch for keys on a key serversecret key not availablesecret key parts are not available
select user ID Nselected certification digest algorithm is invalid
selected cipher algorithm is invalid
selected digest algorithm is invalid
show this helpsign a keysign a key locallysign or edit a keysignature verification suppressed
signing failed: %s
signing:skipped: public key already set
skipped: public key already set as default recipient
skipped: secret key already present
skipping block of type %d
standalone revocation - use "gpg --import" to apply
standalone signature of class 0x%02x
subpacket of type %d has critical bit set
system error while calling external program: %s
take the keys from this keyringtextmodethe given certification policy URL is invalid
the given signature policy URL is invalid
the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
there is a secret key for public key "%s"!
this may be caused by a missing self-signature
this message may not be usable by %s
timestamp conflicttoo many entries in pk cache - disabled
trust database errortrust record %lu is not of requested type %d
trust record %lu, req type %d: read failed: %s
trust record %lu, type %d: write failed: %s
trustdb rec %lu: lseek failed: %s
trustdb rec %lu: write failed (n=%d): %s
trustdb transaction too large
trustdb: lseek failed: %s
trustdb: read failed (n=%d): %s
trustdb: sync failed: %s
unable to display photo ID!
unable to execute external program
unable to read external program response: %s
unable to set exec-path to %s
unable to use the IDEA cipher for all of the keys you are encrypting to.
unexpected dataunimplemented cipher algorithmunimplemented pubkey algorithmunknownunknown cipher algorithmunknown compress algorithmunknown digest algorithmunknown packet typeunknown protection algorithm
unknown pubkey algorithmunknown signature classunknown versionunnatural exit of external program
unsupported URIunusable pubkey algorithmunusable public keyunusable secret keyupdate all keys from a keyserverupdate failed: %s
update secret failed: %s
update the trust databaseusage: gpg [options] use as output fileuse canonical text modeuse option "--delete-secret-keys" to delete it first.
use this user-id to sign or decryptuser ID "%s" is already revoked
using cipher %s
verboseverify a signatureweak keyweak key created - retrying
weird size for an encrypted session key (%d)
writing direct signature
writing key binding signature
writing public key to `%s'
writing secret key to `%s'
writing self signature
writing to `%s'
writing to stdout
wrong secret key usedyYyesyou can only clearsign with PGP 2.x style keys while in --pgp2 mode
you can only detach-sign with PGP 2.x style keys while in --pgp2 mode
you can only encrypt to RSA keys of 2048 bits or less in --pgp2 mode
you can only make detached or clear signatures while in --pgp2 mode
you can't sign and encrypt at the same time while in --pgp2 mode
you cannot appoint a key as its own designated revoker
you found a bug ... (%s:%d)
you may not use %s while in %s mode
you must use files (and not a pipe) when working with --pgp2 enabled.
|FD|write status info to this FD|NAME|encrypt for NAME|N|set compress level N (0 disables)|[file]|make a clear text signature|[file]|make a signature|algo [files]|print message digestsProject-Id-Version: gnupg 1.2.2
Report-Msgid-Bugs-To: translations@gnupg.org
POT-Creation-Date: 2018-06-11 10:48+0200
PO-Revision-Date: 2012-08-24 17:22+0200
Last-Translator: Toomas Soome <Toomas.Soome@microlink.ee>
Language-Team: Estonian <et@li.org>
Language: et
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8-bit

Sisestage kasutaja ID.  L�petage t�hja reaga: 
Juhuslikke baite ei ole piisavalt. Palun tehke arvutiga muid t�id,
et anda masinal v�imalust koguda enam entroopiat! (Vajatakse %d baiti)

Valige foto ID'na kasutatav pilt. Pilt peab olema JPEG fail.
Pidage meeles, et pilt salvestatakse teie avalikus v�tmes. Kui kasutate
v�ga suurt pilti, on ka k�ti v�ha suur!
M�istlik pildi suurus v�iks olla umbes 240x288.

Toetatud algoritmid:
            imporditud: %lu              muutmata: %lu
      uusi alamv�tmeid: %lu
       uusi kasutajaid: %lu
       pole imporditud: %lu
    puudub kasutaja ID: %lu
         Ei ole kindel, et allkiri kuulub omanikule.
         Allkiri on t�en�oliselt V�LTSING.
         Ei ole midagi, mis n�itaks, et allkiri kuulub omanikule.
         uusi allkirju: %lu
     Alamv�tme s�rmej�lg: loetud salajasi v�tmeid: %lu
 vahele j�etud uusi v�tmeid: %lu
    Alamv�tme s�rmej�lg:   (%d) DSA (ainult allkirjastamiseks)
   (%d) RSA (ainult kr�pteerimiseks)
   (%d) RSA (ainult allkirjastamiseks)
   (0) Ma ei vasta.%s
   (1) Ma ei ole �ldse kontrollinud.%s
   (2) Ma olen teinud pealiskaudset kontrolli.%s
   (3) Ma olen kontrollinud v�ga hoolikalt.%s
      uusi t�histamisi: %lu
  Ei saa allkirjastada.
 salajasi v�tmeid imporditud: %lu
 (mitte-eksporditav) Primaarse v�tme s�rmej�lg: muutmata salajasi v�tmeid: %lu
# Omistatud usalduse v��rtuste loend, loodud: %s
# (Taastamiseks kasutage "gpg --import-ownertrust")
%d halba allkirja
%d v�tit t��deldud (%d kehtivust puhastatud)
%d allkirja j�i vigade t�ttu kontrollimata
%d allkirja j�i testimata, kuna v�tmed puuduvad
tuvastasin %d kehtiva iseenda allkirjata kasutaja IDd
%s ...
%s ei t��ta veel koos %s-ga
%s kr�pteeritud andmed
%s kr�pteeritud sessiooni v�ti
kasutatakse %s kr�pteerimist
%s on uus
%s ei ole muudetud
%s ja %s ei oma koos m�tet!
%s ja %s ei ole koos lubatud!
%s allkiri, s�numil�hendi algoritm %s
%s.
%s/%s kr�ptitud kasutajale: "%s"
%s: kataloogi ei ole!
%s: viga vaba kirje lugemisel: %s
%s: viga versioonikirje lugemisel: %s
%s: viga versioonikirje uuendamisel: %s
%s: viga kataloogikirje kirjutamisel: %s
%s: viga versioonikirje kirjutamisel: %s
%s: kirje lisamine eba�nnestus: %s
%s: paisktabeli loomine eba�nnestus: %s
%s: versioonikirje loomine ei �nnestu: %s%s: kirje nullimine eba�nnestus: %s
%s: vigane faili versioon %d
%s: vigane trustdb
%s: loodi vigane usalduse andmebaas
%s: v�tmehoidla on loodud
%s: ei ole trustdb fail
%s: j�tsin vahele: %s
%s: j�tsin vahele: avalik v�ti on juba olemas
%s: j�tsin vahele: avalik v�ti on blokeeritud
%s: trustdb on loodud
%s: tundmatu suffiks
%s: versioonikirje kirje numbriga %lu
%s:%d: ebasoovitav v�ti "%s"
%s:%d: vigased ekspordi v�tmed
%s:%d: vigased impordi v�tmed
(Kirjeldust ei antud)
(T�en�oliselt soovite siin valida %d)
(See on tundlik t�histamise v�ti)
(kui te just ei m��ra v�tit s�rmej�ljega)
(te kasutasite vahest selle t�� jaoks valet programmi)
--clearsign [failinimi]--decrypt [failinimi]--edit-key kasutaja-id [k�sud]--encrypt [failinimi]--lsign-key kasutaja-idv�ti --output ei t��ta selle k�suga
--sign --encrypt [failinimi]--sign --symmetric [failinimi]--sign [failinimi]--sign-key kasutaja-id--store [failinimi]--symmetric [failinimi]-k[v][v][v][c] [kasutaja-id] [v�tmehoidla]... see on viga (%s:%d:%s)
1 halb allkiri
1 allkiri j�i testimata, kuna v�ti puudub
1 allkiri j�i vea t�ttu kontrollimata
tuvastasin �he kehtiva iseenda allkirjata kasutaja ID
@
(K�ikide k�skude ja v�tmete t�ieliku kirjelduse leiate manualist)
@
N�ited:

 -se -r Bob [fail]          allkirjasta ja kr�pti kasutajale Bob
 --clearsign [fail]         loo avateksti allkiri
 --detach-sign [fail]       loo eraldiseisev allkiri
 --list-keys [nimed]        n�ita v�tmeid
 --fingerprint [nimed]      n�ita s�rmej�lgi
@
V�tmed:
 @K�sud:
 V�ljundis sunnitakse kasutama ASCII vormingut.
Vastake "jah" (v�i "j"), kui v�ib alustada alamv�tme loomisega.Kui selle alamv�tme v�ib kustutada, vastake "jah"Vastake "jah", kui faili v�ib �le kirjutadaKui te t�esti soovite seda kasutaja IDd kustutada, vastake "jah".
Sertifikaadid kustutatakse samuti!Vastake "jah" v�i "ei"Olete kindel, et soovite seda ikka lisada? (j/E) Olete kindel, et soovite seda ikka t�histada? (j/E) Olete kindel, et soovite seda ikka allkirjastada? (j/e) Allkirja ei saa kontrollida: %s
Seda v�tit ei �nnestu toimetada: %s
KatkestaSertifikaadid t�iesti usaldatava v�tmeni:
Muuda (N)ime, (K)ommentaari, (E)posti v�i (O)k/(V)�lju? Muuda (N)ime, (K)ommentaari, (E)posti v�i (V)�lju? Muuda k�ikide kasutaja ID-de seaded (v�i ainult valitud)
vastavaks hetkel m��ratud seadetele. K�ikide asjasse puutuvate
ise loodud allkirjade ajatempleid suurendatakse �he sekundi v�rra.
Muudan primaarse v�tme aegumise aega.
�iffer: Kommentaar: Pakkimine: Loon sellele allkirjale t�histamise sertifikaadi? (j/E) Kriitiline allkirja noteerimine: Kriitiline allkirja poliitika: Kustutan selle korrektse allkirja? (j/E/v)Kustutan selle vigase allkirja? (j/E/v)Kustutan selle tundmatu allkirja? (j/E/v)Kustutatud %d allkiri.
Kustutatud %d allkirja.
Eraldiseisev allkiri.
Teatel�hend: Kas soovite luua uut allkirja et asendada vana aegunud? (j/E) Kas te soovite seda edutada t�ielikuks eksporditavaks allkirjaks? (j/E) Kas te soovite seda edutada OpenPGP iseenda allkirjaks? (j/E) Olete kindel, et soovite seda ikka allkirjastada? (j/E) Soovite, et teie allkiri aeguks samal ajal? (J/e) E-posti aadress: Sisestage foto ID jaoks JPEG faili nimi: Sisestage mittekohustuslik kirjeldus. L�petage t�hja reaga:
Sisestage uus failinimiSisestage parool
Sisestage parool: Sisestage v�tmehoidja nimiSisestage sellele salajasele v�tmele uus parool.

Sisestage n�utav v��rtus, nagu viibal n�idati.
V�imalik on ka sisestada ISO kuup�ev (AAAA-KK-PP), aga te ei
saa korrektset veateadet, kuna s�steem �ritab antud v��rtust
t�lgendada vahemikuna.Sisestage v�tmepikkusSisestage kasutaja ID aadressile, kellele te soovite teadet saata.Sisestage m��ratud t�histaja kasutaja ID: Omadused: Fail `%s' on olemas. Sisestage palun failinimi, mida allkirjastadaKirjutage n��d oma teade ...
R�si: Vihje: Valige allkirjastamiseks kasutaja
Kui hoolikalt te olete kontrollinud et v�ti, mida te asute allkirjastama,
kuulub ka tegelikult �lal mainitud isikule? Kui te ei tea, mida vastata,
sisestage "0".
IDEA �iffer pole saadaval, loodan kasutada selle asemel %s
Kui te soovite, v�ite n��d sisestada p�hjenduse, miks te
soovite seda t�histamise sertifikaati esitada. Palun kirjutage
l�hidalt. T�hi rida l�petab teksti.
Kui te ikkagi soovite kasutada seda mitteusaldatavat v�tit, vastake "jah".�ldiselt ei ole hea m�te kasutada sama v�tit allkirjastamiseks ja
kr�pteerimiseks. Seda algoritmi tuleks kasutada ainult teatud piirides.
Enne kasutamist konsulteerige palun oma turva eksperdiga.Lubamatu s�mbol kommentaaris
Lubamatu s�mbol nimes
Vigane k�sklus (proovige "help")
Vigane parool; palun proovige uuestiVigane valik.
On see foto �ige (j/E/v)? Teie �lesanne on sisestada n��d v��rtus; seda v��rtust ei avalikustata
kolmandatele pooltele. Seda v��rtust on vaja et realiseerida usaldusv�rk.V�tme leiate: V�tme genereerimine katkestati.
V�tme genereerimine eba�nnestus: %s
V�ti on kompromiteeritudV�ti ei ole enam kasutuselV�ti on kaitstud.
V�ti on t�histatud.V�ti on asendatudV�ti on kehtiv kuni? (0) V�tit ei muudetud, seega pole uuendamist vaja.
V�tmehoidlaN  et muuta nime.
K  et muuta kommentaari.
E  et muuta e-posti aadressi.
O  et j�tkata v�tme loomist.
V  et l�petada v�tme loomine.M�RKUS: %s ei ole tavap�raseks kasutamiseks!
M�RKUS: See v�ti ei ole kaitstud!
M�RKUS: v3 v�tmetele alamv�tmete loomine ei ole OpenPGP �hilduv
M�RKUS: v�ti on t�histatudM�RKUS: vaikimisi v�tmete fail `%s' puudub
M�RKUS: ignoreerin vana vaikimisi v�tmete faili `%s'
M�RKUS: saatja n�udis "ainult-teie-silmadele"
M�RKUS: lihtne S2K mood (0) ei soovitata kasutada
M�RKUS: trustdb pole kirjutatav
Nimi ei v�i alata numbriga
Nimes peab olema v�hemalt 5 s�mbolit
Selle tegamiseks on vaja salajast v�tit.
NnKkEeOoVvVastavat allkirja salajaste v�tmete hoidlas pole
Abiinfo puudub`%s' kohta abiinfo puudubP�hjus puudubTundmatu kasutaja ID.
Kasutaja ID numbriga %d puudub
Selline e-posti aadress ei ole lubatud
M�rkus: See v�ti on blokeeritud.
M�rkus: See v�ti on aegunud!
Midagi ei kustutatud.
Palun parandage k�igepealt viga
�rge palun kirjutage e-posti aadressi p�risnimesse ega kommentaari
Palun sisestage uus failinimi. Kui te vajutate lihtsalt reavahetust,
kasutatakse vaikimisi faili (nimi on nurksulgudes).Te v�ite n��d sisestada kommentaariPalun sisestage andmefaili nimi: Palun sisestage parool; see on salajane tekst 
Palun parandage see v�imalik turvaprobleem
Tuleb t�hele panna et kuni te pole programmi uuesti k�ivitanud, ei pruugi
n�idatud v�tme kehtivus olla tingimata korrektne.
Palun eemaldage salajastelt v�tmetelt valikud.
Palun korrake parooli, siis saate oma kirjutatus kindel olla.Palun saatke veateated aadressil <gnupg-bugs@gnu.org>.
Palun valige t�pselt �ks kasutaja ID.
Palun valige t�histamise p�hjus:
Palun valige, millist v�tmet��pi te soovite:
Palun m��rake, kui kaua on v�ti kehtiv.
         0 = v�ti ei aegu
      <n>  = v�ti aegub n p�evaga
      <n>w = v�ti aegub n n�dalaga
      <n>m = v�ti aegub n kuuga
      <n>y = v�ti aegub n aastaga
Palun m��rake, kui kaua allkiri kehtib.
         0 = allkiri ei aegu
      <n>  = allkiri aegub n p�evaga
      <n>w = allkiri aegub n n�dalaga
      <n>m = allkiri aegub n kuuga
      <n>y = allkiri aegub n aastaga
Palun kasutage k�igepealt k�sku "toggle".
Palun oodake, kogutakse entroopiat. Igavuse v�ltimiseks v�ite teha arvutiga
mingit t��d, see t�stab ka entroopia kvaliteeti.
Primaarse v�tme s�rmej�lg:Avalik v�ti: Avalik v�ti on blokeeritud.
P�risnimi: Kas t�esti loon t�histamise sertifikaadid? (j/E) Kas t�esti kustutan selle iseenda allkirja? (j/E)T�histamise p�hjus: %s
Korrake parooli
Korrake parooli: Soovitud v�tmepikkus on %u bitti
T�histamise sertifikaat on loodud.
T�histamise sertifikaat on loodud.

Palun salvestage see andmekandjale, mida saate kindlasse kohta �ra panna.
Kui mallory saab sellele sertifikaadile juurdep��su, v�ib ta seda kasutades
muuta k�ik teie v�tmed kasutamisk�lbmatuks.
Samuti on m�istlik tr�kkida see sertifikaat paberile ja panna hoiule juhuks,
kui meedia muutub loetamatuks. Aga olge ettevaatlik: teie arvuti tr�kis�steem
v�ib salvestada need andmed ja teha teistele k�ttesaadavaks! 
Salajane v�ti on kasutatav.
Primaarse v�tme salajased komponendid ei ole k�ttesaadavad.
Allkiri aegus %s
Allkiri aegub %s
Allkirja noteerimine: Allkirja poliitika: S�ntaks: gpg [v�tmed] [failid]
allkirjasta, kontrolli, kr�pti ja dekr�pti
vaikimisi operatsioon s�ltub sisendandmetest
Juhuarvude generaator on ainult t�hi kest, et programmid
k�iks - see EI OLE tugev juhuarvude generaator!

�RGE KASUTAGE SELLE PROGRAMMI POOLT GENEREERITUD ANDMEID!!

Iseenda allkiri "%s"
on PGP 2.x stiilis allkiri.
Allkiri ei ole kehtiv. Oleks m�istlik see v�tmehoidlast kustutada.PGP 2.x stiilis kasutaja ID ei oma seadeid.
See k�sklus ei ole %s moodis lubatud.
See allkiri seob kasutaja ID v�tmega. Sellist allkirja ei ole
�ldiselt soovitatav eemaldada. Peale selle kustutamist ei pruugi
GnuPG enam olla v�imeline seda v�tit leidma. Kustutada v�iks
vaid siis, kui see allkiri ei ole miskip�rast kehtiv ja on
olemas ka teine allkiri, mis kasutajat v�tmega seob.See on v�tme kehtiv allkiri; tavaliselt seda ei soovita kustutada,
kuna see allkiri v�ib olla vajalik, et kirjeldada antud v�tme v�i
antud v�tmega sertifitseeritud teise v�tme usaldatavust.See v�ti kuulub meile
See v�ti on blokeeritudSee v�ti on aegunud!See v�ti aegub %s.
See v�ti ei ole kaitstud.
Seda allkirja ei saa kontrollida, kuna puudub allkirjale vastav v�ti.
Te peaksite peatama kustutamise, kuni on teada, millist v�tit see
kasutab, sest see v�ti v�ib moodustada usaldussuhte l�bi m�ne juba
sertifitseeritud v�tme.See allkiri aegub %s.
See muudab v�tme PGP 2.x programmidega mitte-kasutatavaks.
T�histaja:
Usalduse v�rgu loomiseks peab GnuPG teadma, millised v�tmed on
absoluutselt usaldatavad. Need on tavaliselt v�tmed, mille puhul
on teil juurdep��s ka nende salajastele v�tmetele. Kui soovite
m��rata seda v�tit absoluutselt usaldatavaks, vastake "jah"
T��deldud kokku: %lu
PakkimataKasuta: gpg [v�tmed] [failid] (-h n�itab abiinfot)Kasuta: gpgv [v�tmed] [failid] (-h n�itab abiinfot)Kasutaja ID "%s" on aegunud.Kasutaja ID "%s" ei ole ise allkirjastatud.Kasutaja ID "%s" on t�histatud.Kasutaja ID ei ole enam kehtivHOIATUS: v�tit "%s" ei soovitata kasutada.
HOIATUS: %s m��rab �le %s
HOIATUS: on olemas 2 faili konfidentsiaalse infoga.
HOIATUS: See on PGP2-stiilis v�ti. M��ratud t�histaja lisamine v�ib
         p�hjustada m�ningaid PGP versioone seda v�tit tagasi l�kkama.
HOIATUS: See on PGP2-stiilis v�ti. Foto ID lisamine v�ib sundida m�ningaid
         PGP versioone seda v�tit tagasi l�kkama.
HOIATUS: See v�ti on m��ratud t�histaja poolt t�histatud!
HOIATUS: See v�ti on omaniku poolt t�histatud!
HOIATUS: Seda v�tit ei ole sertifitseeritud usaldatava allkirjaga!
HOIATUS: Seda v�tit ei ole sertifitseeritud piisavalt usaldatava allkirjaga!
HOIATUS: See alamv�ti on omaniku poolt t�histatud!
HOIATUS: Kasutan mitteusaldatavat v�tit!
HOIATUS: Me EI usalda seda v�tit!
HOIATUS: Tuvastasin n�rga v�tme - palun muutke uuesti parooli.
HOIATUS: `%s' on t�hi fail
HOIATUS: kasutaja ID allkirja ajatempel on %d sekundit tulevikus
HOIATUS: v�tme seadmist m��ratud t�histajaks ei saa tagasi v�tta!
HOIATUS: kr�pteeritud teadet on muudetud!
HOIATUS: vigane random_seed faili suurus - ei kasuta
HOIATUS: teade on kr�ptitud s�mmeetrilise �ifri n�rga v�tmega.
HOIATUS: teate koosk�lalisus ei ole tagatud
HOIATUS: leidsin mitu allkirja. Kontrollitakse ainult esimest.
HOIATUS: �htegi kasutaja ID pole m�rgitud primaarseks.  See k�sklus v�ib
              p�hjustada muu kasutaja ID primaarseks m��ramist.
HOIATUS: midagi ei eksporditud
HOIATUS: seaded failis `%s' pole seekord veel aktiivsed
HOIATUS: t�en�oliselt ebaturvaline s�mmeetriliselt kr�pteeritud sessiooni v�ti
HOIATUS: programm v�ib salvestada oma m�lupildi!
HOIATUS: m��rati saajad (-r) aga ei kasutata avaliku v�tme kr�ptograafiat
HOIATUS: allkirja l�hend on teatega konfliktne
HOIATUS: see v�ti v�ib olla t�histatud (t�histamise v�tit pole)
HOIATUS: noteerimise %%-asendus eba�nnestus (liiga suur). Kasutan kompaktset.
HOIATUS: ei �nnestu eemaldada ajutist kataloogi `%s': %s
HOIATUS: ei saa kustutada ajutist faili (%s) `%s': %s
HOIATUS: kasutan ebaturvalist m�lu!
HOIATUS: kasutan ebaturvalist juhuarvude generaatorit!!
Me peame genereerima palju juhuslikke baite. Praegu oleks hea teostada
arvutil mingeid teisi tegevusi (kirjutada klaviatuuril, liigutada hiirt,
kasutada kettaid jne), see annaks juhuarvude generaatorile v�imaluse
koguda paremat entroopiat.
Kui te allkirjastate v�tme kasutaja ID, kontrollige k�igepealt, kas v�ti
ikka kuulub antud ID-ga n�idatud isikule. Teistel inimestel on hea teada,
kui hoolikalt te seda kontrolli olete teostanud.

"0" t�hendab, et te ei v�ida oma kontrollimise kohta midagi.

"1" t�hendab, et te usute, et v�tit omab isik, kes seda v�idab omavat, kuid
    te ei saanud v�i ei soovinud seda v�idet t�iendavalt kontrollida. See
    on kasulik "persooni" kontrolliks, kui te allkirjastate isiku pseudo-
    n��mi v�tit.

"2" t�hendab, et te teostasite v�tme pealiskaudset kontrolli. See v�ib
    n�iteks t�hendada, et te kontrollisite v�tme s�rmej�lge ja kontrollisite
    v�tme kasutaja ID foto ID vastu.

"3" t�hendab, et te teostasite v�tme p�hjalikku kontrolli. See v�ib n�iteks
    t�hendada, et v�rdlesite v�tme s�rmej�lge v�rme omanikuga otse suheldes
    ja et te kontrollisite raskesti v�ltsitavast allikast (nt. pass) et
    v�tme omaniku nimi vastab v�tmel n�idatud kasutaja IDle ja te kontrol-
    lisite, et v�tmel n�idatud e-posti aadress kuulub v�tme omanikule.

pange t�hele, et n�ited tasemete 2 ja 3 juures on *ainult* n�ited. S�ltub
ainult teist, milline on "pealiskaudse" ja "p�hjaliku" kontrolli t�hendus,
kui te allkirjastate teisi v�tmeid.

Kui te ei tea �iget vastust, vastake "0".Te asute t�histama j�rgmisi allkirju:
Te kasutate kooditabelit `%s'.
v3 v�tme aegumise aega ei saa muuta.
Viimast kasutaja ID ei saa kustutada!
Te ei m��ranud kasutaja IDd. (v�ite kasutada v�tit "-r")
Te ei soovi parooli - see on t�en�oliselt *halb* idee!

Te ei soovi parooli - see on t�en�oliselt *halb* idee!
Ma siiski t�idan teie soovi. Te saate oma parooli alati muuta,
kasutades seda programmi v�tmega "--edit-key".

PGP 2.x-stiili v�tmele ei saa m��ratud t�histajat lisada.
Foto IDd ei saa PGP2 v�tmele lisada.
--pgp2 moodis ei saa PGP 2.x v�tmele OpenPGP allkirja anda.
Te peata valima v�hemalt �he v�tme.
Te peate valima v�hemalt �he kasutaja ID.
Te vajate oma salajase v�tme kaitsmiseks parooli.

Te valisite selle KASUTAJA-ID:
    "%s"

Te peate m��rama sertifitseerimise p�hjuse. S�ltuvalt kontekstist on
teil v�imalus valida �ks j�rgnevaist:
  "V�ti on kompromiteeritud"
      Kasutage seda, kui teil on p�hjust uskuda, et autoriseerimata
      isikud on saanud juurdep��su teie salajasele v�tmele.
  "V�ti on asendatud"
      Kasutage seda, kui te olete selle v�tme asendanud uuemaga.
  "V�ti ei ole enam kasutusel"
      Kasutage seda, kui te ei kasuta enam seda v�tit.
  "Kasutaja ID ei ole enam kehtiv"
      Kasutage seda m�rkimaks, et konkreetset kasutaja ID ei peaks enam
      kasutama; seda kasutatakse tavaliselt m�rkimaks vigast e-posti aadressi.
Teie praegune allkiri "%s"
on aegunud.
Teie praegune allkiri "%s"
on lokaalne allkiri.
Teie otsus? Teie valik? Teie s�steem ei saa esitada kuup�evi peale aastat 2038.
Siiski k�sitletakse neid korrektselt aastani 2106.
[failinimi][t�histamine][iseenda allkiri][ebakindel]`%s' on juba pakitud
`%s' ei ole tavaline fail - ignoreerin
`%s' ei ole kehtiv pikk v�tmeID
lisa foto IDlisa t�histamise v�tilisa kasutaja IDpakendi p�is: pakend: %s
eeldan %s kr�pteeritud andmeid
eeldan allkirjastatud andmeid failis `%s'
halb MPIhalb URIhalb sertifikaathalb v�tihalb paroolhalb avalik v�tihalb salajane v�tihalb allkiriole m�nev�rra vaiksembinaarnebuild_packet eba�nnestus: %s
`%s' ei �nnestu sulgeda: %s
ei �nnestu luua �hendust serveriga `%s': %s
`%s' ei �nnestu luua: %s
kataloogi `%s' ei �nnestu luua: %s
ei �nnestu blokeerida m�lupildi salvestamist: %s
v�hem kui %d bitiga ei saa algarvu genereerida
ei oska k�sitleda avaliku v�tme algoritmi %d
ei suuda k�sitleda tekstiridu mis on pikemad, kui %d s�mbolit
`%s' ei �nnestu avada
`%s' ei �nnestu avada: %s
allkirjastatud andmete avamine eba�nnestus `%s'
v�tmehoidlat ei �nnestu avada`%s' ei �nnestu lugeda: %s
ei �nnestu lugeda `%s' atribuute: %s
S2K moodi t�ttu ei saa s�mmeetrilist ESK paketti kasutada
`%s' ei �nnestu kirjutada: %s
katkestatud kasutaja poolt
PGP 2.x stiilis v�tit ei saa nimetada m��ratud t�histajaks
s�mmeetrilises �ifris ei �nnestu v�ltida n�rga v�tme kasutamist; proovisin %d korda!
muuda omaniku usaldustmuuda parooliLoodud allkirja ei �nnestu kontrollida: %s
kontrollin trustdb faili
kontrollsumma viga�ifri algoritm %d%s on tundmatu v�i blokeeritud
completes-needed peab olema suurem, kui 0
vastuolulised k�sud
loo ascii pakendis v�ljundandmeid ei salvestatud; salvestamiseks kasutage v�tit "--output"
lahtipakendamine eba�nnestus: %s
dekr�pteeri andmed (vaikimisi)lahtikr�pteerimine eba�nnestus: %s
lahtikr�pteerimine �nnestus
v�tmebloki kustutamine eba�nnestus: %s
�ra tee mingeid muutusipakendamine eba�nnestus: %s
kr�pteeri andmedkr�pteeritud kasutades %lu parooli
kr�pteeritud �he parooliga
kr�pteeritud tundmatu algoritmiga %d
teate kr�pteerimine --pgp2 moodis n�uab IDEA �iffrit
kr�pteerimine kasutades ainult s�mmeetrilist �ifritviga `%s' loomisel: %s
viga v�tmehoidla `%s' loomisel: %s
viga parooli loomisel: %s
viga l�petaval real
viga `%s' lugemisel: %s
viga v�tmebloki lugemisel: %s
viga v�tmehoidlasse `%s' kirjutamisel: %s
viga avaliku v�tme v�tmehoidlasse `%s' kirjutamisel: %s
viga salajase v�tme v�tmehoidlasse `%s' kirjutamisel: %s
ekspordi v�tmedekspordi v�tmed v�tmeserverissev�liste programmide k�ivitamine on blokeeritud, kuna seadete failil on
ebaturvalised �igused
TrustDB initsialiseerimine eba�nnestus: %s
v�tmehoidla vahem�lu uuesti loomine eba�nnestus: %s
viga faili sulgemiselviga faili loomiselviga faili kustutamiselfail on olemasviga faili avamiselviga faili lugemiselviga faili �mber nimetamiselviga faili kirjutamisels�mmetrilise �ifri %s (%d) kasutamine on vastuolus saaja eelistustega
�ldine vigagenereeri uus v�tmepaargenereeri t�histamise sertifikaatloon salajase v�tme kaitseks mittesoovitavat 16 bitist kontrollsummat
gpg-agent ei ole sesses sessioonis kasutatav
gpg-agendi protokolli versioon %d ei ole toetatud
iItTvVjJimpordi v�tmed v�tmeserveristimpordi/mesti v�tmedsisendrida %u on liiga pikk v�i seavahetus puudub
sisendrida on pikem, kui %d s�mbolit
vigane S2K mood; peab olema 0, 1 v�i 3
vigane argumentvigane pakendvigane pakendi p�is: vigane pakend: rida on pikem, kui %d s�mbolit
vigane avateksti allkirja p�is
vigane kriipsudega m�rgitud rida: vigased vaikimisi eelistused
vigane vaikimisi-sert-tase; peab olema 0, 1, 2 v�i 3
vigased ekspordi v�tmed
vigane r�sialgoritm `%s'
vigased impordi v�tmed
vigane v�tmehoidlavigane min-sert-tase; peab olema 1, 2 v�i 3
vigane pakettvigane paroolvigased isikliku �ifri eelistused
vigased isikliku pakkimise eelistused
vigased isikliku l�hendi eelistused
proc_tree() tuvastas vigase juurmise paketi
vigane v��rtus
v�tme eksport eba�nnestus: %s
v�ti loodi %lu sekund tulevikus (ajah�pe v�i kella probleem)
v�ti loodi %lu sekundit tulevikus (ajah�pe v�i kella probleem)
v�ti ei ole m�rgitud ebaturvaliseks - sellega ei saa v�lts RNGd kasutada!
v�tmehoidla `%s' on loodud
v�tmeserveri vigav�tmeserverilt lugemine eba�nnestus: %s
v�tmeserveri uuendamine eba�nnestus: %s
v�tmeserveri otsing eba�nnestus: %s
v�tmeserverile saatmine eba�nnestus: %s
vigane v�tme suurus; kasutan %u bitti
v�tme suurus �mardatud �les %u bitini
n�ita v�tit ja kasutaja IDdn�ita v�tmeidn�ita v�tmeid ja s�rmej�lgin�ita v�tmeid ja allkirjun�ita eelistusi (ekspert)n�ita eelistusi (detailsena)n�ita salajasi v�tmeidloo eraldiseisev allkiriteata ajatemplite konfliktist ainult hoiatusegamake_keysig_packet eba�nnestus: %s
vigane CRC
vigane GPG_AGENT_INFO keskkonnamuutuja
vigane kasutaja idmarginals-needed peab olema suurem, kui 1
t�stan v�tme allkirja �igesse kohta
eEavateksti allkirjad �ksteise sees
v�rgu vigamitte kunagiuus omaduste fail `%s' on loodud
trustdb j�rgmine kontroll %s
eivastavat avalikku v�tit pole: %s
puudub salajaste v�tmete vaikimisi v�tmehoidla: %s
entroopia kogumise moodul puudub
trustdb kontrolliks puudub vajadus
mittelokaalse programmi k�ivitamist ei toetata
salajast v�tit pole
allkirjastatud andmeid pole
sellist kasutaja id poleabsoluutselt usaldatavaid v�tmeid pole
ei leia OpenPGP andmeid.
kehtivaid aadresse pole
ei leia kirjutatavat v�tmehoidlat: %s
kirjutatavat avalike v�tmete hoidlat pole: %s
kirjutatavat salajaste v�tmete hoidlat pole: %s
ei ole eraldiseisev allkiri
kr�ptimataei t��deldudei ole toetatudm�rkus: random_seed fail on t�hi
m�rkus: random_seed faili ei uuendatud
ok, me oleme anon��mne teate saaja.
vana DEK kodeerimine ei ole toetatud
vana stiili (PGP 2.x) allkiri
initsialiseerimata turvalise m�luta ei ole operatsioon v�imalik
v�tmete fail `%s': %s
algne failinimi on='%.*s'
omaniku usalduse info puhastatud
parooli ei korratud �ieti; proovige uuestipalun tehke --check-trustdb
palun e-posti aadress, aadress ei ole kohustuslik, aga v�ga soovitavLisainfot leiate lehelt http://www.gnupg.org/documentation/faqs.html
palun kasutage selle asemel "%s%s"
enneaegne failil�pp (poolik CRC)
enneaegne failil�pp (puudub CRC)
probleem kr�ptitud paketi k�sitlemisel
probleem agendiga - blokeerin agendi kasutamise
k�si enne �lekirjutamistkaitse algoritm %d%s ei ole toetatud
avalik ja salajane v�ti on loodud ja allkirjastatud.
avaliku v�tmega lahtikr�pteerimine eba�nnestus: %s
avalik v�ti ei sobi salajase v�tmega!
avaliku v�tmega kr�pteeritud andmed: hea DEK
ei leia avalikku v�titvVv�ljuv�lju sellest men��stkvooditud s�mbol pakendis - t�en�oliselt on kasutatud vigast MTA programmi
loen failist `%s'
loen v�tmeid failist `%s'
loen standardsisendit ...
t�histamise p�hjus: eemalda v�tmed avalike v�tmete hoidlasteemalda v�tmed salajaste v�tmete hoidlastressursi limiitt�histamise kommentaar: �mardatud �les %u bitini
salvesta ja v�ljuotsi v�tmeid v�tmeserveristsalajane v�ti ei ole k�ttesaadavsalajase v�tme komponendid ei ole k�ttesaadavad
vali kasutaja ID Nvalitud sertifikaadi l�hendi algoritm ei ole lubatud
valitud �ifri algoritm ei ole lubatud
valitud l�hendi algoritm ei ole lubatud
n�ita seda abiinfotallkirjasta v�tiallkirjasta v�ti lokaalseltallkirjasta v�i toimeta v�titallkirja kontroll j�eti �ra
allkirjastamine eba�nnestus: %s
allkirjastan:j�tsin vahele: avalik v�ti on juba olemas
j�tsin vahele: avalik v�ti on juba vaikimisi saaja
j�tsin vahele: avalik v�ti on juba olemas
j�tan bloki t��biga %d vahele
eraldiseisev t�histus - realiseerimiseks kasutage "gpg --import"
eraldiseisev allkiri klassiga 0x%02x
alampaketil t��biga %d on kriitiline bitt seatud
s�steemi viga v�lise programmi kasutamisel: %s
v�ta v�tmed sellest v�tmehoidlasttekstimoodantud sertifikaadi poliisi URL on vigane
antud allkirja poliisi URL on vigane
allkirja ei �nnestu kontrollida.
Palun pidage meeles, et allkirja fail (.sig v�i .asc)
peab olema k�sureal esimene fail.
avaliku v�tme "%s" jaoks on salajane v�ti!
see v�ib olla p�hjustatud puuduvast iseenda allkirjast
see teade ei pruugi olla programmiga %s kasutatav
ajatemplite konfliktavalike v�tmete puhvris on liiga palju v�tmeid - blokeerin
usalduse andmebaasi vigausalduse kirje %lu ei oma soovitud t��pi %d
usalduse kirje %lu, p�ringu t��p %d: lugemine eba�nnestus: %s
usalduse kirje %lu, t��p %d: kirjutamine eba�nnestus: %s
trustdb kirje %lu: lseek eba�nnestus: %s
trustdb rec %lu: write failed (n=%d): %s
trustdb transaktsioon on liiga suur
trustdb: lseek eba�nnestus: %s
trustdb: lugemine eba�nnestus (n=%d): %s
trustdb: sync eba�nnestus: %s
foto ID ei saa n�idata!
v�list programmi ei �nnestu k�ivitada
ei �nnestu lugeda v�lise programmi vastust: %s
exec-path v��rtuseks ei �nnestu seada %s
k�ikide kr�pteeritavate v�tmetega ei saa IDEA �iffrit kasutada.
ootamatud andmedrealiseerimata �ifri algoritmrealiseerimata avaliku v�tme algoritmtundmatutundmatu �ifri algoritmtundmatu pakkimisalgoritmtundmatu l�hendi algoritmtundmatu paketi t��ptundmatu kaitsealgoritm
tundmatu avaliku v�tme algoritmtundmatu allkirja klasstundmatu versioonv�line programm l�petas erandlikult
mittetoetatud URImittekasutatav avaliku v�tme algoritmmittekasutatav avalik v�timittekasutatav salajane v�tiuuenda v�tmeid v�tmeserveristuuendamine eba�nnestus: %s
salajase v�tme uuendamine eba�nnestus: %s
uuenda usalduse andmebaasikasuta: gpg [v�tmed] kasuta v�ljundfailinakasuta kanoonilist tekstimoodiselle kustutamiseks kasutage v�tit "--delete-secret-keys".
kasuta seda kasutaja IDdkasutaja ID "%s" on juba t�histatud
kasutan �iffrit %s
ole jutukaskontrolli allkirjan�rk v�tiloodi n�rk v�ti - proovin uuesti
veider suurus kr�ptitud sessiooni v�tme jaoks (%d)
kirjutan otsese allkirja
kirjutan v�tit siduva allkirja
kirjutan avaliku v�tme faili `%s'
kirjutan salajase v�tme faili `%s'
kirjutan iseenda allkirja
kirjutan faili `%s'
kirjutan standardv�ljundisse
kasutati valet salajast v�titjJjahPGP 2.x stiilis v�tmetega saab avateksti allkirjastada ainult --pgp2 moodis
PGP 2.x stiilis v�tmetega saab eraldi-allkirjastada ainult --pgp2 moodis
RSA v�tmeid pikkusega kuni 2048 bitti saab kr�pteerida ainult --pgp2 moodis
--pgp2 moodis saate luua ainult eraldiseisvaid v�i avateksti allkirju
--pgp2 moodis ei saa korraga allkirjastada ja kr�pteerida
te ei saa nimetada v�tit iseenda m��ratud t�histajaks
te leidsite vea ... (%s:%d)
%s ei ole moodis %s lubatud.
--pgp2 moodis peate kasutama faile (ja mitte toru).
|FP|kirjuta olekuinfo sellesse failipidemesse|NIMI|kr�pti NIMEle|N|m��ra pakkimise tase N (0 blokeerib)|[fail]|loo avateksti allkiri|[fail]|loo allkiri|algo [failid]|tr�ki teatel�hendid
© 2025 GrazzMean