文件操作 - libgsasl.mo
返回文件管理
返回主菜单
删除本文件
文件: /usr/share/locale/zh_CN/LC_MESSAGES/libgsasl.mo
编辑文件内容
�� B , Y < � ? � C � K % J q = � < � < 7 < t @ � $ � 1 1 I / { 2 � F � $ % # J 7 n � 2 � � � � � � A � � � | � M D v � � & � # � � & . ' U 4 } $ � y � 2 Q $ � $ � S � [ " Z ~ R � R , M Q � S R s T � R P n O � R Q b Q � R Y " x � F � ; � 5 � L / � - - 9 - g * � * � ' � * - > & l 5 � 0 � 3 � , . / [ � � 6 � � 3 � H � � � � v 4 � U Y � q 8 � � :! Y! x! �! �! # �! # �! 2 " , 5" ^ b" 1 �" �" # N 0# V # U �# M ,$ M z$ H �$ L % N ^% M �% O �% M K& K �& J �& M 0' L ~' L �' M ( f( �( �( 2 �( , �( ") , 2 & 3 # ; 7 ( - / : 0 B ' ) " + 1 ? 4 8 9 > . 6 % 5 @ * $ = A ! < 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 library Callback 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 library Could not open file in SASL library Could not prepare internationalized (non-ASCII) string. Error authenticating user Failed 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 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 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 payload Kerberos V5 initialization failure. Kerberos V5 internal error. Libgsasl success Libgsasl unknown error Low-level crypto error in SASL library Memory allocation error in SASL library No 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 times SASL mechanism could not parse input SASL 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 data SecurID 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 Project-Id-Version: libgsasl 1.7.4 Report-Msgid-Bugs-To: bug-gsasl@gnu.org PO-Revision-Date: 2013-03-08 12:59+0800 Last-Translator: Ji ZhengYu <zhengyuji@gmail.com> Language-Team: Chinese (simplified) <i18n-zh@googlegroups.com> Language: zh_CN 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. 验证失败，因为未提供 tls-unique CB。 验证失败，因为未提供匿名标记。 验证失败，因为未提供身份验证。 验证失败，因为未提供身份授权。 验证失败，因为未提供主机名。 验证失败，因为未提供 passcode。 验证失败，因为未提供密码。 验证失败，因为未提供 pin code。 验证失败，因为未提供服务名称。 SASL 库中出现 Base 64 编码错误 回调失败，无法提供 OPENID20 重定向 URL。 回调失败，无法提供 SAML20 IdP 编号。 回调失败，无法提供 SAML20 重定向 URL。 无法获取内存库处理函数(库错误) 客户端功能在库中不可用(程序错误) SASL 库无法关闭文件 SASL 库无法打开文件 无法生成国际化的(非 ACSII 码的)字符串。 验证用户时发生错误 无法对字符串进行 Unicode 标准化操作。 进行 SASL 库中 gss_acquire_cred() 函数中的请求证书操作时发生了 GSSAPI 错误。这极有可能是由于在服务器的 /etc/krb5.keytab 中没有合适的 Kerberos 密钥可用造成的。 进行 SASL 库中 gss_display_name() 函数中的创建表示客户端的显示名时发生了GSSAPI 错误。这可能是因为客户端提供了错误的数据。 当与 SASL 库中 gss_init_sec_context() 函数中的文本进行安全协商时客户端发生了GSSAPI 错误。这极有可能是由不受信任的证书或恶意会话造成的。 当与 SASL 库中 gss_accept_sec_context() 函数中的文本进行安全协商时服务器端发生了GSSAPI 错误。这极有可能是由不受信任的证书或恶意会话造成的。 GSSAPI 错误，释放 OID位。 当解密或解码 SASL 库中 gss_unwrap() 函数中的数据时发生了 GSSAPI 错误。这极有可能是由数据损坏造成的。 当加密或编码 SASL 库中 gss_wrap() 函数中的数据时发生了 GSSAPI 错误。 GSSAPI 库无法回收 SASL 库中 gss_release_buffer() 函数所占的内存。这是个严重的内部错误。 GSSAPI 库无法解析 SASL 库中 gss_import_name() 函数中的端点名称。这极有可能是由不正确的服务或主机名造成的。 程序中出现完整性错误 Kerberos V5 初始化失败。 Kerberos V5 内部错误。 Libgsasl 成功 Libgsasl 未知错误 SASL 库中出现低级加密错误 SASL 库中出现内存分配错误 调用函数未指定回调机制(程序错误)。 不可获得更多的领域(非严重错误) 其它信息要求在 GSSAP 中提供完整性或私密性保护机制，但目前未实现。 SASL 功能需要更大的缓冲区(内部错误) 调用 SASL 机制次数太多 SASL 机制无法解析输入 SASL 机制需要 gsasl_client_callback_anonymous() 函数回调(程序错误) SASL 机制需要 gsasl_client_callback_authentication_id() 函数回调(程序错误) SASL 机制需要 gsasl_client_callback_authorization_id() 函数回调(程序错误) SASL 机制需要 gsasl_client_callback_passcode() 函数回调(程序错误) SASL 机制需要 gsasl_client_callback_password() 函数回调(程序错误) SASL 机制需要 gsasl_client_callback_pin() 函数回调(程序错误) SASL 机制需要 gsasl_client_callback_service() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_anonymous() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_cram_md5() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_digest_md5() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_external() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_gssapi() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_realm() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_retrieve() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_securid() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_service() 函数回调(程序错误) SASL 机制需要 gsasl_server_callback_validate() 函数回调(程序错误) SASL 机制需要更多数据 SecurID 需要附加密码。 SecurID 需要新的 pin 值。 服务器端功能在库中不可用(程序错误) 提供的库操作函数无效(程序错误) 未知的 SASL 机制
修改文件时间
将文件时间修改为当前时间的前一年
删除文件