Current File : //usr/share/locale/id/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�;�4�K<�9(>b=�3�45H2~6�(�@DR>�@�D(\(�>��8�D�� � �7�����  u!'�!�!N>"{�"�	##�##�#�#$$)-$$W$A|$)�$}�$=f%'�%)�%Z�%bQ&a�&Y'Yp'T�'X(Zx(Y�([-)Y�)W�)V;*Y�*X�*XE+Y�++�+"$,G,Ed,<�,�,#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.7.4
Report-Msgid-Bugs-To: [email protected]
PO-Revision-Date: 2012-05-18 15:33+0700
Last-Translator: Andhika Padmawan <[email protected]>
Language-Team: Indonesian <[email protected]>
Language: id
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Bugs: Report translation errors to the Language-Team address.
Otentikasi gagal karena nama CB tls-unique tidak disediakan.Otentikasi gagal karena sembarang token tidak disediakan.Otentikasi gagal karena identitas otentikasi tidak disediakan.Otentikasi gagal karena identitas otorisasi tidak disediakan.Otentikasi gagal karena nama host tidak disediakan.Otentikasi gagal karena kode lewat tidak disediakan.Otentikasi gagal karena sandi lewat tidak disediakan.Otentikasi gagal karena kode pin tidak disediakan.Otentikasi gagal karena nama layanan tidak disediakan.Galat penyandian base 64 di pustaka SASLPanggil kembali gagal untuk menyediakan pengalihan URL OPENID20.Panggil kembali gagal untuk menyediakan pengidentifikasi SAML20 IdP.Panggil kembali gagal untuk menyediakan pengalihan URL SAML20.Tak bisa mendapatkan penanganan pustaka internal (galat pustaka)Fungsionalitas sisi-klien tidak tersedia di pustaka (galat aplikasi)Tak dapat menutup berkas di pustaka SASLTak dapat membuka berkas di pustaka SASLTak dapat menyiapkan benang (non-ASCII) terinternasionalisasi.Galat mengotentikasi penggunaGagal melakukan Normalisasi Sandi Universal pada benang.Galat GSSAPI mengambil kredensial di gss_acquire_cred() di pustaka SASL.  Ini kelihatannya karena tidak memiliki kunci Kerberos asli yang tersedia di /etc/krb5.keytab di server.Galat GSSAPI membuat tampilan nama mendenotasi klien di gss_display_name() dipustaka SASL. Ini mungkin karena klien menyuplai data buruk.Galat GSSAPI mengeluarkan token.Galat GSSAPI menyelubungi token.Galat GSSAPI mendapatkan OID untuk nama mekanisme SASL.Galat GSSAPI di klien ketika bernegosiasi konteks keamanan di gss_init_sec_context() di pustaka SASL. Ini kelihatannya karena kredensial yang tidak cukup atau interaksi yang mencurigakan.Galat GSSAPI di server ketika bernegosiasi konteks keamanan di gss_accpet_sec_context() di pustaka SASL. Ini kelihatannya karena kredensial yang tidak cukup atau interaksi yang mencurigakan.Galat GSSAPI melepaskan set OID.Galat GSSAPI menguji OID dalam set OID.Galat GSSAPI ketika memecahkan atau mengawasandi data di gss_unwrap() di pustaka SASL. Ini kelihatannya karena data yang rusak.Galat GSSAPI ketika enkripsi atau menyandi data di gss_wrap() di pustaka SASL.Pustaka GSSAPI tak dapat melepas alokasi memori di gss_release_buffer() di pustaka SASL.  Ini adalah galat internal serius.Pustaka GSSAPI tidak mengerti nama peer di gss_import_name() di pustaka SASL. Ini kelihatannya karena layanan dan/atau nama host yang tidak tepat.Galat integritas di pemuat aplikasiKegagalan inisialisasi Kerberos V5.Galat internal Kerberos V5.Libgsasl suksesGalat tak diketahui libgsaslGalat kripto level rendah di pustaka SASLGalat alokasi memori di pustaka SASLTak ada panggil balik ditentukan oleh pemanggil (galat aplikasi).Tak ada lagi kawasan tersedia (tak-fatal)Entitas lain meminta proteksi integritas atau konfidensialitas di mekanisme GSSAPI tapi ini saat ini belum diimplementasikan.Fungsi SASL memerlukan penyangga lebih besar (galat internal)Mekanisme SASL dipanggil terlalu seringMekanisme SASL tak dapat mengurai masukanMekanisme SASL memerlukan panggil balik gsasl_client_callback_anonymous() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_authentication_id() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_authorization_id() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_passcode() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_password() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_pin() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_service() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_anonymous() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_cram_md5() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_digest_md5() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_external() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_gssapi() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_realm() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_retrieve() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_securid() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_server_callback_service() (galat aplikasi)Mekanisme SASL memerlukan panggil balik gsasl_client_callback_validate() (galat aplikasi)Mekanisme SASL memerlukan lebih banyak dataSecurID memerlukan sandi tambahan.SecurID memerlukan pin baru.Fungsionalitas sisi-server tidak tersedia di pustaka (galat aplikasi)Penanganan pustaka yang diberikan tidak sah (galat aplikasi)Mekanisme SASL tak diketahui