⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.13
Server IP:
109.199.105.153
Server:
Linux connect.inboxifs.com 5.15.0-152-generic #162-Ubuntu SMP Wed Jul 23 09:48:42 UTC 2025 x86_64
Server Software:
Apache
PHP Version:
8.2.29
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
usr
/
share
/
locale-langpack
/
en_GB
/
LC_MESSAGES
/
View File Name :
gnupg2.mo
�� D < a \ � � � 2 � � 4 � 1 : J � ` E Q k = � % � F � E 1 � w � ( y 1 � j � d ? f � H i T � @ � I H j 0 � � � � > � � , < D - � � � ) � % # % I 3 o % � % � $ � 6 0 K | . � $ � 4 � # I @ % � � . � � & B 3 S � / � ? � � 2 � 2 � 5 " X a r � � E 7 } � ? � & � F F b � � � , & � 2 � k f s h � I C j � � @ I Z H � 0 � � �! > �" 8# H# , T# < �# - �# �# $ * !$ L$ % d$ % �$ 3 �$ % �$ % % $ 0% 7 U% 1 �% �% / �% $ & 4 ,& $ a& J �& % �& �& / ' D' X' p' �' 4 �' �' 0 �' @ $( e( ? $ 9 + : # % @ , " ) ; 5 ! ( 0 - 2 = 1 4 D < 8 & > * A ' B 3 / C 6 . 7 You need a user ID to identify your key; the software constructs the user ID from the Real Name, Comment and Email Address in this form: "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>" "%s": preference for cipher algorithm %s ASCII armored output forced. Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? Cipher: Email address: Enter email addresses Hint: If this message was created before the year 2003 it is likely that this message is legitimate. This is because back then integrity protection was not widely used. IDEA cipher unavailable, optimistically attempting to use %s instead Key generation canceled. Not a valid email address Note: Use "%s %s" for a full featured key generation dialog. Options enforcing a passphrase policy Owner trust may not be set while using a user provided trust database Please don't put the email address into the real name or the comment Please enter the passphrase to unlock the secret key for the X.509 certificate: "%s" S/N %s, ID 0x%08lX, created %s, expires %s. Please indicate whether this email address should be associated with key %s or whether you think someone is impersonating "%s". Reset Code not or not anymore available Statistics for keys with the email address "%s": Syntax: gpg-check-pattern [options] patternfile Check a passphrase given on stdin against the patternfile The email address "%s" is associated with %d key! The email address "%s" is associated with %d keys! The email address "%s" is associated with %d key: The email address "%s" is associated with %d keys: This is the first time the email address "%s" is being used with key %s. To complete this certificate request please enter the passphrase for the key you just created once more. User ID "%s": already minimized WARNING: cipher algorithm %s not found in recipient preferences WARNING: forcing symmetric cipher %s (%d) violates recipient preferences WARNING: message was encrypted with a weak key in the symmetric cipher. WARNING: using experimental cipher algorithm %s Warning: if you think you've seen more signatures by this key and user id, then this key might be a forgery! Carefully examine the email address for small variations. If the key is suspect, then use %s to mark it as being bad. Warning: if you think you've seen more signatures by this key and these user ids, then this key might be a forgery! Carefully examine the email addresses for small variations. If the key is suspect, then use %s to mark it as being bad. 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. a notation name must have only printable characters or spaces armor header: armor: %s can't initialize certificate cache lock: %s cannot avoid weak key for symmetric cipher; tried %d times! cipher algorithm %d%s is unknown or disabled create ascii armored output dearmoring failed: %s do not allow the reuse of old passphrases enarmoring failed: %s encryption only with symmetric cipher error initializing TOFU database: %s error initializing cache file '%s' for reading: %s error initializing reader object: %s failed to initialize the TrustDB: %s failed to initialize the server: %s honor the PKA record set on a key when retrieving keys honor the preferred keyserver URL set on the key invalid armor header: invalid armor: line longer than %d characters invalid personal cipher preferences key %s: secret key with invalid cipher %d - skipped line %d: not a valid email address quoted printable character in armor - probably a buggy MTA has been used selected cipher algorithm is invalid too many cipher preferences too many open cache files; can't open anymore unexpected armor: unknown armor header: use strict OpenPGP behavior using cipher %s |FILE|check new passphrases against pattern in FILE |NAME|use cipher algorithm NAME |NAME|use encoding NAME for PKCS#12 passphrases |N|require at least N non-alpha characters for a new passphrase |SPEC|set up email aliases Project-Id-Version: gnupg2 Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS> PO-Revision-Date: 2022-04-09 10:18+0000 Last-Translator: Anthony Harrington <Unknown> Language-Team: English (United Kingdom) <en_GB@li.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=n != 1; X-Launchpad-Export-Date: 2024-09-02 19:42+0000 X-Generator: Launchpad (build 1b1ed1ad2dbfc71ee62b5c5491c975135a771bf0) You need a user ID to identify your key; the software constructs the user ID from the Real Name, Comment and E-mail Address in this form: "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>" "%s": preference for cypher algorithm %s ASCII armoured output forced. Change (N)ame, (C)omment, (E)-mail or (O)kay/(Q)uit? Cypher: E-mail address: Enter e-mail addresses Hint: If this message was created before the year 2003, it is likely that this message is legitimate. This is because, back then, integrity protection was not widely used. IDEA cypher unavailable, optimistically attempting to use %s instead Key generation cancelled. Not a valid e-mail address Note: Use "%s %s" for a full featured key generation dialogue. Options enforcing a pass-phrase policy Owner trust may not be set while using a user-provided trust database Please don't put the e-mail address into the real name or the comment Please enter the pass-phrase to unlock the secret key for the X.509 certificate: "%s" S/N %s, ID 0x%08lX, created %s, expires %s. Please indicate whether this e-mail address should be associated with key %s or whether you think someone is impersonating "%s". Reset Code is not available any more. Statistics for keys with the e-mail address "%s": Syntax: gpg-check-pattern [options] patternfile Check a pass-phrase given on stdin against the patternfile The e-mail address "%s" is associated with %d key! The e-mail address "%s" is associated with %d keys! The e-mail address "%s" is associated with %d key: The e-mail address "%s" is associated with %d keys: This is the first time the e-mail address "%s" is being used with key %s. To complete this certificate request please enter the pass-phrase for the key you just created once more. User ID "%s": already minimised WARNING: cypher algorithm %s not found in recipient preferences WARNING: forcing symmetric cypher %s (%d) violates recipient preferences WARNING: message was encrypted with a weak key in the symmetric cypher. WARNING: using experimental cypher algorithm %s Warning: if you think you've seen more signatures by this key and user id, then this key might be a forgery! Carefully examine the e-mail address for small variations. If the key is suspect, then use %s to mark it as being bad. Warning: if you think you've seen more signatures by this key and these user ids, then this key might be a forgery! Carefully examine the email addresses for small variations. If the key is suspect, then use %s to mark it as being bad. 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, utilise the disks) during the prime generation; this gives the random number generator a better chance to gain enough entropy. a notation name must only have printable characters or spaces armour header: armour: %s can't initialise certificate cache lock: %s cannot avoid weak key for symmetric cypher; tried %d times! cypher algorithm %d%s is unknown or disabled create ASCII armoured output dearmouring failed: %s do not allow the reuse of old pass-phrases enarmouring failed: %s encryption only with symmetric cypher error initialising TOFU database: %s error initialising cache file '%s' for reading: %s error initialising reader object: %s failed to initialise the TrustDB: %s failed to initialise the server: %s honour the PKA record set on a key when retrieving keys honour the preferred keyserver URL set on the key invalid armour header: invalid armour: line longer than %d characters invalid personal cypher preferences key %s: secret key with invalid cypher %d - skipped line %d: not a valid e-mail address quoted printable character in armour - probably a buggy MTA has been used selected cypher algorithm is invalid too many cypher preferences too many open cache files; can't open any more unexpected armour: unknown armour header: use strict OpenPGP behaviour using cypher %s |FILE|check new pass-phrases against pattern in FILE |NAME|use cypher algorithm NAME |NAME|use encoding NAME for PKCS#12 pass-phrases |N|require at least N non-alpha characters for a new pass-phrase |SPEC|set up e-mail aliases