HOME

Mini Shell 1.0
DIR:/usr/share/locale/en@boldquot/LC_MESSAGES/
Current File : //usr/share/locale/en@boldquot/LC_MESSAGES/libgsasl.mo
��FLa|?CAK�J�=<Z<�<�@$R1w1�/�2	F>	$�	#�	7�	
2 
�S
�	!�!�1����}
(�
|�
MCv��&�#��&-'T4|$�y�2P$�$�S�[!Z}R�R+M~Q�SRrT�RPmO�RQaQ�RX"w�F�;�4LK?�C�KJh=�<�<.<k@�$�11@/r2�F�$#A7e�2�����!8!Z1|���` !(4!|]!M�!v("��"&5##\#�#�#�#&�#'�#4$$H$ym$2�$$%$?%Sd%[�%Z&Ro&R�&M'Qc'S�'R	(T\(R�(P)OU)R�)Q�)QJ*R�*�*"+1+FH+;�+�+#A<407)&F(1B>"'.D*+2
@!8% 3E6C,?;	/$
9=-5:Authentication failed because a tls-unique CB was not provided.Authentication failed because the anonymous token was not provided.Authentication failed because the authentication identity was not provided.Authentication failed because the authorization identity was not provided.Authentication failed because the host name was not provided.Authentication failed because the passcode was not provided.Authentication failed because the password was not provided.Authentication failed because the pin code was not provided.Authentication failed because the service name was not provided.Base 64 coding error in SASL libraryCallback failed to provide OPENID20 redirect URL.Callback failed to provide SAML20 IdP identifier.Callback failed to provide SAML20 redirect URL.Cannot get internal library handle (library error)Client-side functionality not available in library (application error)Could not close file in SASL libraryCould not open file in SASL libraryCould not prepare internationalized (non-ASCII) string.Error authenticating userFailed to perform Unicode Normalization on string.GSSAPI error acquiring credentials in gss_acquire_cred() in SASL library.  This is most likely due to not having the proper Kerberos key available in /etc/krb5.keytab on the server.GSSAPI error creating a display name denoting the client in gss_display_name() in SASL library.  This is probably because the client supplied bad data.GSSAPI error decapsulating token.GSSAPI error encapsulating token.GSSAPI error getting OID for SASL mechanism name.GSSAPI error in client while negotiating security context in gss_init_sec_context() in SASL library.  This is most likely due insufficient credentials or malicious interactions.GSSAPI error in server while negotiating security context in gss_accept_sec_context() in SASL library.  This is most likely due insufficient credentials or malicious interactions.GSSAPI error releasing OID set.GSSAPI error testing for OID in OID set.GSSAPI error while decrypting or decoding data in gss_unwrap() in SASL library.  This is most likely due to data corruption.GSSAPI error while encrypting or encoding data in gss_wrap() in SASL library.GSSAPI library could not deallocate memory in gss_release_buffer() in SASL library.  This is a serious internal error.GSSAPI library could not understand a peer name in gss_import_name() in SASL library.  This is most likely due to incorrect service and/or hostnames.Integrity error in application payloadKerberos V5 initialization failure.Kerberos V5 internal error.Libgsasl successLibgsasl unknown errorLow-level crypto error in SASL libraryMemory allocation error in SASL libraryNo callback specified by caller (application error).No more realms available (non-fatal)Other entity requested integrity or confidentiality protection in GSSAPI mechanism but this is currently not implemented.SASL function needs larger buffer (internal error)SASL mechanism called too many timesSASL mechanism could not parse inputSASL mechanism needs gsasl_client_callback_anonymous() callback (application error)SASL mechanism needs gsasl_client_callback_authentication_id() callback (application error)SASL mechanism needs gsasl_client_callback_authorization_id() callback (application error)SASL mechanism needs gsasl_client_callback_passcode() callback (application error)SASL mechanism needs gsasl_client_callback_password() callback (application error)SASL mechanism needs gsasl_client_callback_pin() callback (application error)SASL mechanism needs gsasl_client_callback_service() callback (application error)SASL mechanism needs gsasl_server_callback_anonymous() callback (application error)SASL mechanism needs gsasl_server_callback_cram_md5() callback (application error)SASL mechanism needs gsasl_server_callback_digest_md5() callback (application error)SASL mechanism needs gsasl_server_callback_external() callback (application error)SASL mechanism needs gsasl_server_callback_gssapi() callback (application error)SASL mechanism needs gsasl_server_callback_realm() callback (application error)SASL mechanism needs gsasl_server_callback_retrieve() callback (application error)SASL mechanism needs gsasl_server_callback_securid() callback (application error)SASL mechanism needs gsasl_server_callback_service() callback (application error)SASL mechanism needs gsasl_server_callback_validate() callback (application error)SASL mechanism needs more dataSecurID needs additional passcode.SecurID needs new pin.Server-side functionality not available in library (application error)The provided library handle was invalid (application error)Unknown SASL mechanismProject-Id-Version: libgsasl 1.10.0
Report-Msgid-Bugs-To: bug-gsasl@gnu.org
PO-Revision-Date: 2021-01-01 17:34+0100
Last-Translator: Automatically generated
Language-Team: none
Language: en@boldquot
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=(n != 1);
Authentication failed because a tls-unique CB was not provided.Authentication failed because the anonymous token was not provided.Authentication failed because the authentication identity was not provided.Authentication failed because the authorization identity was not provided.Authentication failed because the host name was not provided.Authentication failed because the passcode was not provided.Authentication failed because the password was not provided.Authentication failed because the pin code was not provided.Authentication failed because the service name was not provided.Base 64 coding error in SASL libraryCallback failed to provide OPENID20 redirect URL.Callback failed to provide SAML20 IdP identifier.Callback failed to provide SAML20 redirect URL.Cannot get internal library handle (library error)Client-side functionality not available in library (application error)Could not close file in SASL libraryCould not open file in SASL libraryCould not prepare internationalized (non-ASCII) string.Error authenticating userFailed to perform Unicode Normalization on string.GSSAPI error acquiring credentials in gss_acquire_cred() in SASL library.  This is most likely due to not having the proper Kerberos key available in /etc/krb5.keytab on the server.GSSAPI error creating a display name denoting the client in gss_display_name() in SASL library.  This is probably because the client supplied bad data.GSSAPI error decapsulating token.GSSAPI error encapsulating token.GSSAPI error getting OID for SASL mechanism name.GSSAPI error in client while negotiating security context in gss_init_sec_context() in SASL library.  This is most likely due insufficient credentials or malicious interactions.GSSAPI error in server while negotiating security context in gss_accept_sec_context() in SASL library.  This is most likely due insufficient credentials or malicious interactions.GSSAPI error releasing OID set.GSSAPI error testing for OID in OID set.GSSAPI error while decrypting or decoding data in gss_unwrap() in SASL library.  This is most likely due to data corruption.GSSAPI error while encrypting or encoding data in gss_wrap() in SASL library.GSSAPI library could not deallocate memory in gss_release_buffer() in SASL library.  This is a serious internal error.GSSAPI library could not understand a peer name in gss_import_name() in SASL library.  This is most likely due to incorrect service and/or hostnames.Integrity error in application payloadKerberos V5 initialization failure.Kerberos V5 internal error.Libgsasl successLibgsasl unknown errorLow-level crypto error in SASL libraryMemory allocation error in SASL libraryNo callback specified by caller (application error).No more realms available (non-fatal)Other entity requested integrity or confidentiality protection in GSSAPI mechanism but this is currently not implemented.SASL function needs larger buffer (internal error)SASL mechanism called too many timesSASL mechanism could not parse inputSASL mechanism needs gsasl_client_callback_anonymous() callback (application error)SASL mechanism needs gsasl_client_callback_authentication_id() callback (application error)SASL mechanism needs gsasl_client_callback_authorization_id() callback (application error)SASL mechanism needs gsasl_client_callback_passcode() callback (application error)SASL mechanism needs gsasl_client_callback_password() callback (application error)SASL mechanism needs gsasl_client_callback_pin() callback (application error)SASL mechanism needs gsasl_client_callback_service() callback (application error)SASL mechanism needs gsasl_server_callback_anonymous() callback (application error)SASL mechanism needs gsasl_server_callback_cram_md5() callback (application error)SASL mechanism needs gsasl_server_callback_digest_md5() callback (application error)SASL mechanism needs gsasl_server_callback_external() callback (application error)SASL mechanism needs gsasl_server_callback_gssapi() callback (application error)SASL mechanism needs gsasl_server_callback_realm() callback (application error)SASL mechanism needs gsasl_server_callback_retrieve() callback (application error)SASL mechanism needs gsasl_server_callback_securid() callback (application error)SASL mechanism needs gsasl_server_callback_service() callback (application error)SASL mechanism needs gsasl_server_callback_validate() callback (application error)SASL mechanism needs more dataSecurID needs additional passcode.SecurID needs new pin.Server-side functionality not available in library (application error)The provided library handle was invalid (application error)Unknown SASL mechanism