HEX
Server: Apache/2.4.52 (Ubuntu)
System: Linux spn-python 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64
User: arjun (1000)
PHP: 8.1.2-1ubuntu2.20
Disabled: NONE
Upload Files
File: //usr/share/locale-langpack/en_AU/LC_MESSAGES/gnupg2.mo
��5�Gl���2S�4����ENh%�F�E��6(�j�iL �@�I	Hb	0�	�	�

�
<�
-4b~)��%�%�6"0Y�.�$�4�#*
IN
%�
�
�
�
!32f/�?�����2��5�2;LEc��&�FFN��&k?j� @7IxH�0<=M<Y-���*�$%<%b7�1��/
$:4_$�J�%*G[s�4��0�@'h/5
2+!$&*	40.31'"-
,#%( )
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 addressesIDEA cipher unavailable, optimistically attempting to use %s instead
Key generation canceled.
Not a valid email address
Options enforcing a passphrase policyOwner 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.
Reset Code not or not anymore available
Syntax: gpg-check-pattern [options] patternfile
Check a passphrase given on stdin against the patternfile
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
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.
armor header: armor: %s
cannot avoid weak key for symmetric cipher; tried %d times!
cipher algorithm %d%s is unknown or disabled
create ascii armored outputdearmoring failed: %s
do not allow the reuse of old passphrasesenarmoring failed: %s
encryption only with symmetric cipherfailed to initialize the TrustDB: %s
honor the PKA record set on a key when retrieving keyshonor the preferred keyserver URL set on the keyinvalid 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
unexpected armor: unknown armor header: use strict OpenPGP behaviorusing 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 aliasesProject-Id-Version: gnupg2
Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>
PO-Revision-Date: 2016-11-02 16:33+0000
Last-Translator: Anthony Harrington <Unknown>
Language-Team: English (Australia) <en_AU@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: 2023-08-01 15:29+0000
X-Generator: Launchpad (build d80dbb5bdc9110f3a64cc968928033472d5e0509)

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 addressesIDEA cypher unavailable, optimistically attempting to use %s instead
Key generation cancelled.
Not a valid e-mail address
Options enforcing a pass-phrase policyOwner 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.
Reset Code is not available any more.
Syntax: gpg-check-pattern [options] patternfile
Check a pass-phrase given on stdin against the patternfile
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
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.
armour header: armour: %s
cannot avoid weak key for symmetric cypher; tried %d times!
cypher algorithm %d%s is unknown or disabled
create ASCII armoured outputdearmouring failed: %s
do not allow the reuse of old pass-phrasesenarmouring failed: %s
encryption only with symmetric cypherfailed to initialise the TrustDB: %s
honour the PKA record set on a key when retrieving keyshonour the preferred keyserver URL set on the keyinvalid 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
unexpected armour: unknown armour header: use strict OpenPGP behaviourusing 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