Translations by Jakub Bogusz

WARNING: unsafe enclosing directory ownership on configuration file `%s'

WARNING: unsafe enclosing directory ownership on extension `%s'

WARNING: unsafe enclosing directory permissions on homedir `%s'

WARNING: unsafe enclosing directory permissions on configuration file `%s'

WARNING: unsafe enclosing directory permissions on extension `%s'

show IETF standard notations during signature listings

could not parse keyserver URL

symmetric encryption of `%s' failed: %s

you cannot use --symmetric --encrypt while in %s mode

you cannot use --symmetric --sign --encrypt with --s2k-mode 0

you cannot use --symmetric --sign --encrypt while in %s mode

--clearsign [filename]

invalid hash algorithm `%s'

be somewhat more quiet

Syntax: gpgv [options] [files] Check signatures against known trusted keys

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.

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.

Answer "yes" or "no"

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.

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".

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.

The signature is not valid. It does make sense to remove it from your keyring.

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.

Please repeat the last passphrase, so you are sure what you typed in.

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.

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.

algorithms on these user IDs:

"%s": preference for cipher algorithm %s

"%s": preference for digest algorithm %s

"%s": preference for compression algorithm %s

re-distribute this key to avoid potential algorithm mismatch problems

writing to `%s'

error writing keyring `%s': %s

key %s: secret key with invalid cipher %d - skipped

no default secret keyring: %s

key %s: unsupported public key algorithm on user ID "%s"

key %s: invalid self-signature on user ID "%s"

WARNING: key %s may be revoked: fetching revocation key %s

NOTE: a key's S/N does not match the card's one

Please enter the depth of this trust signature. A depth greater than 1 allows the key you are signing to make trust signatures on your behalf.

Your current signature on "%s" has expired.

Your current signature on "%s" is a local signature.

Do you want to sign it again anyway? (y/N)

This would make the key unusable in PGP 2.x.

Are you sure that you want to sign this key with your key "%s" (%s)

Key has only stub or on-card key items - no passphrase to change.

Secret parts of primary key are stored on-card.

Can't edit this key: %s

list key and user IDs

check signatures