[jboss-cvs] JBossAS SVN: r90110 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jun 11 22:17:06 EDT 2009
Author: xhuang at jboss.com
Date: 2009-06-11 22:17:06 -0400 (Thu, 11 Jun 2009)
New Revision: 90110
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
Log:
update
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po 2009-06-11 21:53:05 UTC (rev 90109)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/zh-CN/J2EE_Security_On_JBOSS.po 2009-06-12 02:17:06 UTC (rev 90110)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Security_On_JBOSS\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-06-11 21:11+1000\n"
+"PO-Revision-Date: 2009-06-12 12:16+1000\n"
"Last-Translator: \n"
"Language-Team: en_US <kde-i18n-doc at kde.org>\n"
"MIME-Version: 1.0\n"
@@ -7144,10 +7144,9 @@
msgstr ""
#. Tag: title
-#: J2EE_Security_On_JBOSS.xml:1790
-#, fuzzy, no-c-format
+#: J2EE_Security_On_JBOSS.xml:1790, no-c-format
msgid "The security-ex3.sar jboss-service.xml descriptor for the SRP services"
-msgstr "第一个版本的jboss-service.xml描述符如下所示。"
+msgstr "用于 SRP 服务的 security-ex3.sar jboss-service.xml 描述符"
#. Tag: programlisting
#: J2EE_Security_On_JBOSS.xml:1791
@@ -7308,8 +7307,7 @@
"</application-policy>"
#. Tag: para
-#: J2EE_Security_On_JBOSS.xml:1796
-#, no-c-format
+#: J2EE_Security_On_JBOSS.xml:1796, no-c-format
msgid ""
"The example services are the <literal>ServiceConfig</literal> and the "
"<literal>PropertiesVerifierStore</literal> and <literal>SRPService</literal> "
@@ -7321,7 +7319,7 @@
"because the <literal>SRPService</literal> needs an implementation of the "
"<literal>SRPVerifierStore</literal> interface for accessing user password "
"verification information."
-msgstr ""
+msgstr "示例服务是 <literal>ServiceConfig</literal>、<literal>PropertiesVerifierStore</literal> 和 <literal>SRPService</literal> MBean。请注意，<literal>PropertiesVerifierStore</literal> 的 <literal>JndiName</literal> 属性和 <literal>SRPService</literal> 的 <literal>VerifierSourceJndiName</literal> 属性相等，且 <literal>SRPService</literal> 依赖于 <literal>PropertiesVerifierStore</literal>。这是必需的，因为 <literal>SRPService</literal> 需要一个 <literal>SRPVerifierStore</literal> 接口的实现来访问用户密码检验信息。"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1799
@@ -7337,6 +7335,13 @@
"authentication credentials generated by the <literal>SRPLoginModule</"
"literal> to the EJB invocation layer."
msgstr ""
+"客户端登录模块配置利用带有对应 JBoss 服务器组件 <literal>SRPService</literal> JndiName 属性值（<literal>srp-test/"
+"SRPServerInterface</literal>）的 <literal>srpServerJndiName</"
+"literal> 选项值的 <literal>SRPLoginModule</literal>。使用"
+" <literal>password-"
+"stacking=\"useFirstPass\"</literal> 配置来把 <literal>SRPLoginModule</"
+"literal> 生成的用户验证"
+" credential 传递给 EJB 调用层的 <literal>ClientLoginModule</literal> 也是必需的。"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1802
@@ -7362,6 +7367,13 @@
"user's roles are coming the <literal>roles.properties</literal> file "
"included in the EJB JAR."
msgstr ""
+"关于服务器端的登录模块，有两件事情需要注意。首先，请注意 <literal>cacheJndiName=srp-test/"
+"AuthenticationCache</literal> 配置选项，它把包含已经针对 <literal>SRPService</"
+"literal> 进行了验证的用户的 <literal>SRPServerSession</"
+"literal> 的 <literal>CachePolicy</literal> 的位置告诉 <literal>SRPCacheLoginModule</literal>。这个值对应 <literal>SRPService</"
+"literal> 的 <literal>AuthenticationCacheJndiName</literal> 属性值。其次，这个配置包括带有 <literal>password-stacking=useFirstPass</literal> 配置选项的 <literal>UsersRolesLoginModule</"
+"literal>。因为 SRP 只是一个验证技术，它被要求使用带有 <literal>SRPCacheLoginModule</literal> 的其他登录模块。这个登录模块需要进行配置以接受 <literal>SRPCacheLoginModule</"
+"literal> 检验的验证 credential，从而设置决定 principal 的权限的 principal 角色。带有基于属性文件的授权的 SRP 验证将以 <literal>UsersRolesLoginModule</literal> 为参数。用户的角色将出现在 EJB JAR 里包括的 <literal>roles.properties</literal> 文件里。"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1805
@@ -7369,7 +7381,7 @@
msgid ""
"Now, run the example 3 client by executing the following command from the "
"book examples directory:"
-msgstr ""
+msgstr "现在，通过 book 例程目录里的下列命令来运行 example 3 客户端："
#. Tag: programlisting
#: J2EE_Security_On_JBOSS.xml:1808
@@ -7384,6 +7396,14 @@
" [java] Echo.echo()#1 = This is call 1\n"
" [java] Echo.echo()#2 = This is call 2"
msgstr ""
+"[examples]$ ant -Dchap=security -Dex=3 run-example\n"
+"...\n"
+"run-example3:\n"
+" [echo] Waiting for 5 seconds for deploy...\n"
+" [java] Logging in using the 'srp' configuration\n"
+" [java] Created Echo\n"
+" [java] Echo.echo()#1 = This is call 1\n"
+" [java] Echo.echo()#2 = This is call 2"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1809
@@ -7393,7 +7413,7 @@
"called <literal>ex3-trace.log</literal>. This is a detailed trace of the "
"client side of the SRP algorithm. The traces show step-by-step the "
"construction of the public keys, challenges, session key and verification."
-msgstr ""
+msgstr "在 <literal>examples/logs</literal> 目录里，你将发现一个名为 <literal>ex3-trace.log</literal> 的文件。这是 SRP 算法的客户端的详细跟踪信息。这些信息逐步显示了公共密钥、challenge、会话密钥和验证的构造过程。"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1812
@@ -7412,6 +7432,8 @@
"this issue. As stated earlier, you need to make the cache timeout very long, "
"or handle re-authentication on failure."
msgstr ""
+"请注意，相对于其他简单例程，这个客户端已经运行了很长时间。其原因是构造客户的公共密钥。这涉及强加密随机数字的创建，尤其是第一次发生时会花费很长时间。如果你在相同的 VM 里登出并重新登录，这个过程将快得多。也请注意 <literal>Echo.echo()#2</literal> 失败并抛出验证异常。在第一次调用后客户端代码暂停 15 秒以演示<literal>SRPService</literal> 缓存过期的功能。<literal>SRPService</"
+"literal> 缓存超时策略已经设置为 10 秒来强制执行这一点。如前面所指出的，你需要设置很长的缓存超时时间，或者在失败识处理重验证的问题。"
#. Tag: title
#: J2EE_Security_On_JBOSS.xml:1822
@@ -7609,12 +7631,14 @@
"Access to the org.jboss.security.SecurityAssociation pushRunAsRole and "
"popRunAsRole methods."
msgstr ""
+"访问 org.jboss.security.SecurityAssociation 的 pushRunAsRole 和 "
+"popRunAsRole 方法。"
#. Tag: entry
#: J2EE_Security_On_JBOSS.xml:1906
#, no-c-format
msgid "The ability to change the current caller run-as role principal."
-msgstr ""
+msgstr "修改当前调用者的 run-as 角色的 principal 的能力。"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1912
@@ -7625,7 +7649,7 @@
"to determine how the security manager is using your security policy file as "
"well as what policy files are contributing permissions. Running the VM as "
"follows shows the possible debugging flag settings:"
-msgstr ""
+msgstr "总而言之，这是对调试安全策略设置的尝试。这里不同的调试标记决定了安全管理者如何使用策略文件以及哪些策略文件在控制权限。象下面这样运行 VM 可以显示可能的调试设置："
#. Tag: programlisting
#: J2EE_Security_On_JBOSS.xml:1915
@@ -7651,6 +7675,25 @@
"\n"
"Note: Separate multiple options with a comma"
msgstr ""
+"[bin]$ java -Djava.security.debug=help\n"
+" \n"
+"all turn on all debugging\n"
+"access print all checkPermission results\n"
+"combiner SubjectDomainCombiner debugging\n"
+"jar jar verification\n"
+"logincontext login context results\n"
+"policy loading and granting\n"
+"provider security provider debugging\n"
+"scl permissions SecureClassLoader assigns\n"
+"\n"
+"The following can be used with access:\n"
+"\n"
+"stack include stack trace\n"
+"domain dumps all domains in context\n"
+"failure before throwing exception, dump stack\n"
+" and domain that didn't have permission\n"
+"\n"
+"Note: Separate multiple options with a comma"
#. Tag: para
#: J2EE_Security_On_JBOSS.xml:1916
@@ -7664,6 +7707,8 @@
"verbose, but not nearly as bad as the all mode as the security domain "
"information is only displayed on access failures."
msgstr ""
+"<literal>-Djava.security.debug=all</literal> 参数提供了最多的输出信息，但也很冗余。如果你不理解某个安全设定为什么失败，这可能是一个开始研究的好地方。 使用 <literal>-"
+"Djava.security.debug=access,failure</literal> 可以提供更少的信息，也能帮助调试权限问题。相对而言，这仍然比较冗余，但情况至少没有 all 模式那么坏，因为只显示关于访问失败的安全域信息。"
#. Tag: title
#: J2EE_Security_On_JBOSS.xml:1922
More information about the jboss-cvs-commits
mailing list