openstack/security-doc
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
Change-Id: If2b5ae862e043cb4da1208e6c50af5cb5d79f6f2
This commit is contained in:
OpenStack Proposal Bot 2014-08-07 06:02:58 +00:00
parent 49acbadbca
commit 0becd2d601
2 changed files with 22 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
security-guide/locale/ja.po
View File

@ -12,8 +12,8 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: OpenStack Manuals\n" "Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-08-05 07:03+0000\n" "POT-Creation-Date: 2014-08-06 21:45+0000\n"
"PO-Revision-Date: 2014-08-05 06:58+0000\n" "PO-Revision-Date: 2014-08-06 22:12+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n" "Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n" "MIME-Version: 1.0\n"
@ -2186,26 +2186,28 @@ msgid ""
"messages on the queue. An attacker who is able to successfully place " "messages on the queue. An attacker who is able to successfully place "
"messages on the queue is able to create and delete VM instances, attach the " "messages on the queue is able to create and delete VM instances, attach the "
"block storage of any tenant and a myriad of other malicious actions. There " "block storage of any tenant and a myriad of other malicious actions. There "
"are a number of solutions on the horizon to fix this, with several proposals" "are a number of solutions anticipated in the near future, with several "
" for message signing and encryption making their way through the OpenStack " "proposals for message signing and encryption making their way through the "
"development process." "OpenStack development process."
msgstr "メッセージキューは、多数の OpenStack サービスを支える重要なインフラストラクチャであり、特にコンピュートサービスと強く結びついています。メッセージキューサービスの性質上、アリスとボブが抱えるセキュリティ上の懸念はよく似ています。特に大きな残課題は、数多くのシステムがキューにアクセスしているものの、キューメッセージのコンシューマーには、キューを発行したホストやサービスを確かめる手立てがないことです。攻撃者がキューの発行に成功すると、仮想マシンの作成や削除をしたり、あらゆるテナントのブロックストレージに接続するなど、他にも無数の悪意のある攻撃が可能になってしまいます。\nこれを防ぐためのソリューションが出始めており、いくつかはメッセージへの署名と暗号化を使ったものが OpenStack の開発プロセスで進んでいます。" msgstr ""
#: ./security-guide/section_case-studies-messaging.xml12(para) #: ./security-guide/section_case-studies-messaging.xml12(para)
msgid "" msgid ""
"In this case Alice's controls mimic those Bob has deployed for the public " "In this case, Alice's controls are the same as Bob's controls, which are "
"cloud." "described below."
msgstr "このケースでは、アリスの方法はボブがパブリッククラウドに展開した方法と同じものを使用します。" msgstr ""
#: ./security-guide/section_case-studies-messaging.xml16(para) #: ./security-guide/section_case-studies-messaging.xml16(para)
msgid "" msgid ""
"Bob assumes that at some point infrastructure or networks underpinning the " "Bob assumes the infrastructure or networks underpinning the Compute service "
"Compute service may become compromised. Due to this, he recognizes the " "could become compromised, therefore he recognizes the importance of "
"importance of locking down access to the message queue. To do this Bob " "hardening the system by restricting access to the message queue. In order to"
"deploys his RabbitMQ servers with SSL and X.509 client auth for access " " accomplish this task Bob deploys his RabbitMQ servers with SSL and X.509 "
"control. This in turn limits the capabilities of an attacker who has " "client auth for access control. Hardening activities assists in limiting the"
"compromised a system that does not have queue access." " capabilities of a malicious user that has compromised the system by "
msgstr "ボブは、コンピュートサービスを支えるインフラストラクチャとネットワークがある時点でセキュリティ侵害に会うと仮定します。そして、メッセージキューへのアクセス制限の重要性に気づきました。\nそこで、RabbitMQ サーバーに SSL と X.509 クライアントアクセス制御を適用することにします。これにより、キューアクセスを持たないシステムを乗っ取られても、攻撃者の能力を制限することができます。" "disallowing queue access, provided that this user does not have valid "
"credentials to override the controls."
msgstr ""
#: ./security-guide/section_case-studies-messaging.xml17(para) #: ./security-guide/section_case-studies-messaging.xml17(para)
msgid "" msgid ""

8
security-guide/locale/security-guide.pot
View File

@ -1,7 +1,7 @@
msgid "" msgid ""
msgstr "" msgstr ""
"Project-Id-Version: PACKAGE VERSION\n" "Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-08-06 06:04+0000\n" "POT-Creation-Date: 2014-08-07 06:02+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n" "Language-Team: LANGUAGE <LL@li.org>\n"
@ -1254,15 +1254,15 @@ msgid "To provide secure ephemeral instance storage, Bob implements qcow2 files
msgstr "" msgstr ""
#: ./security-guide/section_case-studies-messaging.xml:9(para) #: ./security-guide/section_case-studies-messaging.xml:9(para)
msgid "The message queue is a critical piece of infrastructure that supports a number of OpenStack services but is most strongly associated with the Compute service. Due to the nature of the message queue service, Alice and Bob have similar security concerns. One of the larger concerns that remains is that many systems have access to this queue and there is no way for a consumer of the queue messages to verify which host or service placed the messages on the queue. An attacker who is able to successfully place messages on the queue is able to create and delete VM instances, attach the block storage of any tenant and a myriad of other malicious actions. There are a number of solutions on the horizon to fix this, with several proposals for message signing and encryption making their way through the OpenStack development process." msgid "The message queue is a critical piece of infrastructure that supports a number of OpenStack services but is most strongly associated with the Compute service. Due to the nature of the message queue service, Alice and Bob have similar security concerns. One of the larger concerns that remains is that many systems have access to this queue and there is no way for a consumer of the queue messages to verify which host or service placed the messages on the queue. An attacker who is able to successfully place messages on the queue is able to create and delete VM instances, attach the block storage of any tenant and a myriad of other malicious actions. There are a number of solutions anticipated in the near future, with several proposals for message signing and encryption making their way through the OpenStack development process."
msgstr "" msgstr ""
#: ./security-guide/section_case-studies-messaging.xml:12(para) #: ./security-guide/section_case-studies-messaging.xml:12(para)
msgid "In this case Alice's controls mimic those Bob has deployed for the public cloud." msgid "In this case, Alice's controls are the same as Bob's controls, which are described below."
msgstr "" msgstr ""
#: ./security-guide/section_case-studies-messaging.xml:16(para) #: ./security-guide/section_case-studies-messaging.xml:16(para)
msgid "Bob assumes that at some point infrastructure or networks underpinning the Compute service may become compromised. Due to this, he recognizes the importance of locking down access to the message queue. To do this Bob deploys his RabbitMQ servers with SSL and X.509 client auth for access control. This in turn limits the capabilities of an attacker who has compromised a system that does not have queue access." msgid "Bob assumes the infrastructure or networks underpinning the Compute service could become compromised, therefore he recognizes the importance of hardening the system by restricting access to the message queue. In order to accomplish this task Bob deploys his RabbitMQ servers with SSL and X.509 client auth for access control. Hardening activities assists in limiting the capabilities of a malicious user that has compromised the system by disallowing queue access, provided that this user does not have valid credentials to override the controls."
msgstr "" msgstr ""
#: ./security-guide/section_case-studies-messaging.xml:17(para) #: ./security-guide/section_case-studies-messaging.xml:17(para)