Main Views
QA Views
About Transvision
BETA
Displaying 138 results for the string key in ja:
| Entity | ja | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-inadequate-key-size |
ja
The server presented a certificate with a key size that is too small to establish a secure connection.
|
en-US
The server presented a certificate with a key size that is too small to establish a secure connection.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-key-pinning-failure |
ja
The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden.
|
en-US
The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-bad-key |
ja
Peer’s public key is invalid.
|
en-US
Peer’s public key is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cannot-move-sensitive-key |
ja
A sensitive key cannot be moved to the slot where it is needed.
|
en-US
A sensitive key cannot be moved to the slot where it is needed.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-decryption-disallowed |
ja
Cannot decrypt: encrypted using a disallowed algorithm or key size.
|
en-US
Cannot decrypt: encrypted using a disallowed algorithm or key size.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-filing-key |
ja
Error refiling the key for this certificate.
|
en-US
Error refiling the key for this certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-inadequate-key-usage |
ja
Certificate key usage inadequate for attempted operation.
|
en-US
Certificate key usage inadequate for attempted operation.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-invalid-key |
ja
The key does not support the requested operation.
|
en-US
The key does not support the requested operation.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-key-nickname-collision |
ja
A key with the same nickname already exists.
|
en-US
A key with the same nickname already exists.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-keygen-fail |
ja
Unable to generate public/private key pair.
|
en-US
Unable to generate public/private key pair.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-krl-not-yet-valid |
ja
The key revocation list for this certificate is not yet valid.
|
en-US
The key revocation list for this certificate is not yet valid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-no-key |
ja
The private key for this certificate cannot be found in key database
|
en-US
The private key for this certificate cannot be found in key database
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-not-a-recipient |
ja
Cannot decrypt: you are not a recipient, or matching certificate and private key not found.
|
en-US
Cannot decrypt: you are not a recipient, or matching certificate and private key not found.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-key-database-not-initialized |
ja
Unable to export. Key database corrupt or deleted.
|
en-US
Unable to export. Key database corrupt or deleted.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-export-key |
ja
Unable to export. Private Key could not be located and exported.
|
en-US
Unable to export. Private Key could not be located and exported.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-import-key |
ja
Unable to import. Error attempting to import private key.
|
en-US
Unable to import. Error attempting to import private key.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-locate-object-by-name |
ja
Unable to export. Unable to locate certificate or key by nickname.
|
en-US
Unable to export. Unable to locate certificate or key by nickname.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs7-keyalg-mismatch |
ja
Cannot decrypt: key encryption algorithm does not match your certificate.
|
en-US
Cannot decrypt: key encryption algorithm does not match your certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-revoked-key |
ja
The key for this site’s certificate has been revoked.
|
en-US
The key for this site’s certificate has been revoked.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-unsupported-keyalg |
ja
Unsupported or unknown key algorithm.
|
en-US
Unsupported or unknown key algorithm.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-cert-kea-mismatch |
ja
The certificate provided cannot be used with the selected key exchange algorithm.
|
en-US
The certificate provided cannot be used with the selected key exchange algorithm.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-client-key-exchange-failure |
ja
Unspecified failure while processing SSL Client Key Exchange handshake.
|
en-US
Unspecified failure while processing SSL Client Key Exchange handshake.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-decrypt-error-alert |
ja
Peer reports failure of signature verification or key exchange.
|
en-US
Peer reports failure of signature verification or key exchange.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-extract-public-key-failure |
ja
SSL was unable to extract the public key from the peer’s certificate.
|
en-US
SSL was unable to extract the public key from the peer’s certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-no-certificate |
ja
Unable to find the certificate or key necessary for authentication.
|
en-US
Unable to find the certificate or key necessary for authentication.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-no-server-key-for-alg |
ja
Server has no key for the attempted key exchange algorithm.
|
en-US
Server has no key for the attempted key exchange algorithm.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-pub-key-size-limit-exceeded |
ja
SSL Server attempted to use domestic-grade public key with export cipher suite.
|
en-US
SSL Server attempted to use domestic-grade public key with export cipher suite.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-client-key-exch |
ja
SSL received a malformed Client Key Exchange handshake message.
|
en-US
SSL received a malformed Client Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-server-key-exch |
ja
SSL received a malformed Server Key Exchange handshake message.
|
en-US
SSL received a malformed Server Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-client-key-exch |
ja
SSL received an unexpected Client Key Exchange handshake message.
|
en-US
SSL received an unexpected Client Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-server-key-exch |
ja
SSL received an unexpected Server Key Exchange handshake message.
|
en-US
SSL received an unexpected Server Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-server-key-exchange-failure |
ja
Unspecified failure while processing SSL Server Key Exchange handshake.
|
en-US
Unspecified failure while processing SSL Server Key Exchange handshake.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-sym-key-context-failure |
ja
Failure to create Symmetric Key context.
|
en-US
Failure to create Symmetric Key context.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-sym-key-unwrap-failure |
ja
Failure to unwrap the Symmetric key in Client Key Exchange message.
|
en-US
Failure to unwrap the Symmetric key in Client Key Exchange message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-weak-server-cert-key |
ja
The server certificate included a public key that was too weak.
|
en-US
The server certificate included a public key that was too weak.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-weak-server-ephemeral-dh-key |
ja
SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.
|
en-US
SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-wrong-certificate |
ja
Client authentication failed: private key in key database does not match public key in certificate database.
|
en-US
Client authentication failed: private key in key database does not match public key in certificate database.
|
|
Entity
#
all locales
browser • browser • screenshots.ftl screenshots-notification-image-copied-details |
ja
ショットがクリップボードへコピーされました。{ screenshots-meta-key }+V キーで貼り付けできます。
|
en-US
Your shot has been copied to the clipboard. Press {screenshots-meta-key}-V to paste.
|
|
Entity
#
all locales
browser • browser • screenshots.ftl screenshots-notification-link-copied-details |
ja
ショットへのリンクがクリップボードへコピーされました。{ screenshots-meta-key }+V キーで貼り付けできます。
|
en-US
The link to your shot has been copied to the clipboard. Press {screenshots-meta-key}-V to paste.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties GTK2Conflict2 |
ja
GTK2 上のキーイベントは利用できません: key=“%S” modifiers=“%S” id=“%S”
|
en-US
Key event not available on GTK2: key=“%S” modifiers=“%S” id=“%S”
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadCryptoKeyHeader |
ja
スコープ ‘%1$S’ の ServiceWorker がプッシュメッセージの復号に失敗しました。‘Crypto-Key’ ヘッダーはアプリサーバーの公開鍵を含む ‘dh’ パラメーターを含まなければなりません。詳しい情報は https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 を参照してください。
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Crypto-Key‘ header must include a ‘dh‘ parameter containing the app server’s public key. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadEncryptionKeyHeader |
ja
スコープ ‘%1$S’ の ServiceWorker がプッシュメッセージの復号に失敗しました。‘Encryption-Key’ ヘッダーは ‘dh’ パラメーターを含まなければなりません。このヘッダーは推奨されず、間もなく削除されます。代わりに ‘Content-Encoding: aesgcm’ を指定した ‘Crypto-Key’ を使用してください。詳しい情報は https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 を参照してください。
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption-Key’ header must include a ‘dh‘ parameter. This header is deprecated and will soon be removed. Please use ‘Crypto-Key‘ with ‘Content-Encoding: aesgcm‘ instead. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadSenderKey |
ja
スコープ ‘%1$S’ の ServiceWorker がプッシュメッセージの復号に失敗しました。‘Crypto-Key’ ヘッダー内の ‘dh’ パラメーターはアプリサーバーの Diffie-Hellman 公開鍵であり、base64url でエンコード (https://tools.ietf.org/html/rfc7515#appendix-C) され、“uncompressed” または “raw” 形式 (エンコーディングの前に 65 バイトの長さ) でなければなりません。詳しい情報は https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 を参照してください。
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘dh‘ parameter in the ‘Crypto-Key‘ header must be the app server’s Diffie-Hellman public key, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) and in “uncompressed” or “raw” form (65 bytes before encoding). See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties WinConflict2 |
ja
一部のキーボードレイアウトではキーイベントが利用できません: key=“%S” modifiers=“%S” id=“%S”
|
en-US
Key event not available on some keyboard layouts: key=“%S” modifiers=“%S” id=“%S”
|
|
Entity
#
all locales
dom • chrome • xslt • xslt.properties 32 |
ja
key 関数の呼び出しは許可されていません。
|
en-US
Call to the key function not allowed.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.j.params |
ja
<channel-name> [<key>]
|
en-US
<channel-name> [<key>]
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join-charset.help |
ja
チャンネル <channel-name> に参加します。チャンネル名の最初が '#' の場合はグローバル、'&' の場合はローカル、'+' の場合はモードなしですが、記号がなければグローバルになります。メッセージは <charset> に指定された文字エンコーディングでエンコードおよびデコードされます。<charset> パラメーターは、/charset コマンドで選択される既定の文字エンコーディングとは無関係です。キー <key> が設定されていれば送信します。
|
en-US
Joins the global (name starts with #), local (name starts with &), or modeless (name starts with a +) channel named <channel-name>. Messages will be encoded and decoded according to the character encoding specified by <charset>. The <charset> parameter is independent of the default character encoding, which can be selected with the /charset command. If no prefix is given, # is assumed. Provides the key <key> if specified.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join-charset.params |
ja
[<channel-name> <charset> [<key>]]
|
en-US
[<channel-name> <charset> [<key>]]
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join.help |
ja
チャンネル <channel-name> に参加します。チャンネル名の最初が '#' の場合はグローバル、'&' の場合はローカル、'+' の場合はモードなしですが、記号がなければグローバルになります。キー <key> が設定されていれば送信します。
|
en-US
Joins the global (name starts with #), local (name starts with &), or modeless (name starts with a +) channel named <channel-name>. If no prefix is given, # is assumed. Provides the key <key> if specified.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join.params |
ja
[<channel-name> [<key>]]
|
en-US
[<channel-name> [<key>]]
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl collapse-attachment-pane-tooltip.tooltiptext |
ja
添付ペインを隠します ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
en-US
Hide the attachment pane ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl context-menuitem-attach-files.acceltext |
ja
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
en-US
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl expand-attachment-pane-tooltip.tooltiptext |
ja
添付ペインを表示します ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
en-US
Show the attachment pane ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl menuitem-attach-files.acceltext |
ja
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
en-US
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl menuitem-toggle-attachment-pane.acceltext |
ja
{ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key }
|
en-US
{ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key }
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl toolbar-button-add-attachment.tooltiptext |
ja
添付ファイルを追加します ({ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key })
|
en-US
Add an Attachment ({ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key })
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-error-revocation |
ja
OpenPGP 鍵の生成に成功しましたが、鍵 { $key } の失効証明書を生成できませんでした
|
en-US
OpenPGP Key created successfully, but failed to obtain revocation for key { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-passphrase-prompt |
ja
以下の鍵のロックを解除するためにパスフレーズを入力してください: { $key }
|
en-US
Please enter the passphrase to unlock the following key: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl message-security-button.title |
ja
{ PLATFORM() ->
[macos] メッセージのセキュリティ情報を見る (⌘ ⌥ { message-header-show-security-info-key })
*[other] メッセージのセキュリティ情報を表示 (Ctrl+Alt+{ message-header-show-security-info-key })
}
|
en-US
{ PLATFORM() ->
[macos] Show Message Security (⌃ ⌘ { message-header-show-security-info-key })
*[other] Show Message Security (Ctrl+Alt+{ message-header-show-security-info-key })
}
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-enc-key-id |
ja
あなたの復号鍵 ID: { $key }
|
en-US
Your decryption key ID: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-enc-key-with-subkey-id |
ja
あなたの復号鍵 ID: { $key } (副鍵 ID: { $subkey })
|
en-US
Your decryption key ID: { $key } (Sub key ID: { $subkey })
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-key-id |
ja
署名者の鍵 ID: { $key }
|
en-US
Signer key ID: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-key-id-with-subkey-id |
ja
署名者の鍵 ID: { $key } (副鍵 ID: { $subkey })
|
en-US
Signer key ID: { $key } (Sub key ID: { $subkey })
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-intro |
ja
鍵 { $key } が利用可能です
|
en-US
Available public keys for { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl cannot-send-enc-because-no-own-key |
ja
このメッセージを暗号化できませんでした。<{ $key }> のためのエンドツーエンド暗号化が設定されていません
|
en-US
Cannot send this message encrypted, because you haven't yet configured end-to-end encryption for <{ $key }>
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl cannot-send-sig-because-no-own-key |
ja
このメッセージにデジタル署名できませんでした。<{ $key }> のためのエンドツーエンド暗号化が設定されていません
|
en-US
Cannot digitally sign this message, because you haven't yet configured end-to-end encryption for <{ $key }>
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl do-import-multiple |
ja
以下の鍵をインポートしますか？
{ $key }
|
en-US
Import the following keys?
{ $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl key-expired |
ja
鍵 '{ $key }' は有効期限切れです
|
en-US
Key '{ $key }' expired
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl key-not-found |
ja
鍵 '{ $key }' が見つかりません
|
en-US
Key '{ $key }' not found
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl key-not-trusted |
ja
鍵 '{ $key }' の信用度が不足しています
|
en-US
Not enough trust for key '{ $key }'
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl key-revoked |
ja
鍵 '{ $key }' は失効しています
|
en-US
Key '{ $key }' revoked
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl openpgp-selection-status |
ja
{ $count ->
[0] 鍵を選択して OpenPGP プロトコルを有効にしてください。
*[other] 鍵 ID <b>{ $key }</b> を利用するよう設定されています。
}
|
en-US
{ $count ->
[0] Select a valid key to enable the OpenPGP protocol.
*[other] Your current configuration uses key ID <b>{ $key }</b>
}
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl openpgp-selection-status-error |
ja
鍵 ID <b>{ $key }</b> を利用するよう設定されていますが、この鍵は失効しています。
|
en-US
Your current configuration uses the key <b>{ $key }</b>, which has expired.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl passphrase-prompt |
ja
以下の鍵のロックを解除するため、パスフレーズを入力してください: { $key }
|
en-US
Please enter the passphrase that unlocks the following key: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl wkd-message-body-process |
ja
これは、OpenPGP Web Key Directory へのあなたの公開鍵のアップロードのための自動プロセスに関連したメールです。
現時点では、特に何も行う必要はありません。
|
en-US
This is an email related to the automatic processing to upload your public key to the OpenPGP Web Key Directory.
You do not need to take any manual action at this point.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl wkd-message-body-req |
ja
あなたのメールプロバイダーが、OpenPGP Web Key Directory へのあなたの公開鍵のアップロード要求を処理しました。
あなたの公開鍵が Directory 上で公開されていることを確認してください。
|
en-US
Your email provider processed your request to upload your public key to the OpenPGP Web Key Directory.
Please confirm to complete the publishing of your public key.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE |
ja
The server presented a certificate with a key size that is too small to establish a secure connection.
|
en-US
The server presented a certificate with a key size that is too small to establish a secure connection.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE |
ja
The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden.
|
en-US
The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_BAD_KEY |
ja
Peer’s public key is invalid.
|
en-US
Peer’s public key is invalid.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_CANNOT_MOVE_SENSITIVE_KEY |
ja
A sensitive key cannot be moved to the slot where it is needed.
|
en-US
A sensitive key cannot be moved to the slot where it is needed.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_DECRYPTION_DISALLOWED |
ja
Cannot decrypt: encrypted using a disallowed algorithm or key size.
|
en-US
Cannot decrypt: encrypted using a disallowed algorithm or key size.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_FILING_KEY |
ja
Error refiling the key for this certificate.
|
en-US
Error refiling the key for this certificate.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_INADEQUATE_KEY_USAGE |
ja
Certificate key usage inadequate for attempted operation.
|
en-US
Certificate key usage inadequate for attempted operation.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_INVALID_KEY |
ja
The key does not support the requested operation.
|
en-US
The key does not support the requested operation.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_KEYGEN_FAIL |
ja
Unable to generate public/private key pair.
|
en-US
Unable to generate public/private key pair.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_KEY_NICKNAME_COLLISION |
ja
A key with the same nickname already exists.
|
en-US
A key with the same nickname already exists.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_KRL_NOT_YET_VALID |
ja
The key revocation list for this certificate is not yet valid.
|
en-US
The key revocation list for this certificate is not yet valid.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_NOT_A_RECIPIENT |
ja
Cannot decrypt: you are not a recipient, or matching certificate and private key not found.
|
en-US
Cannot decrypt: you are not a recipient, or matching certificate and private key not found.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_NO_KEY |
ja
The private key for this certificate cannot be found in key database
|
en-US
The private key for this certificate cannot be found in key database
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_PKCS12_KEY_DATABASE_NOT_INITIALIZED |
ja
Unable to export. Key database corrupt or deleted.
|
en-US
Unable to export. Key database corrupt or deleted.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_PKCS12_UNABLE_TO_EXPORT_KEY |
ja
Unable to export. Private Key could not be located and exported.
|
en-US
Unable to export. Private Key could not be located and exported.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_PKCS12_UNABLE_TO_IMPORT_KEY |
ja
Unable to import. Error attempting to import private key.
|
en-US
Unable to import. Error attempting to import private key.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_PKCS12_UNABLE_TO_LOCATE_OBJECT_BY_NAME |
ja
Unable to export. Unable to locate certificate or key by nickname.
|
en-US
Unable to export. Unable to locate certificate or key by nickname.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_PKCS7_KEYALG_MISMATCH |
ja
Cannot decrypt: key encryption algorithm does not match your certificate.
|
en-US
Cannot decrypt: key encryption algorithm does not match your certificate.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_REVOKED_KEY |
ja
The key for this site’s certificate has been revoked.
|
en-US
The key for this site’s certificate has been revoked.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_UNSUPPORTED_KEYALG |
ja
Unsupported or unknown key algorithm.
|
en-US
Unsupported or unknown key algorithm.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_CERT_KEA_MISMATCH |
ja
The certificate provided cannot be used with the selected key exchange algorithm.
|
en-US
The certificate provided cannot be used with the selected key exchange algorithm.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_CLIENT_KEY_EXCHANGE_FAILURE |
ja
Unspecified failure while processing SSL Client Key Exchange handshake.
|
en-US
Unspecified failure while processing SSL Client Key Exchange handshake.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_DECRYPT_ERROR_ALERT |
ja
Peer reports failure of signature verification or key exchange.
|
en-US
Peer reports failure of signature verification or key exchange.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_EXTRACT_PUBLIC_KEY_FAILURE |
ja
SSL was unable to extract the public key from the peer’s certificate.
|
en-US
SSL was unable to extract the public key from the peer’s certificate.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_NO_CERTIFICATE |
ja
Unable to find the certificate or key necessary for authentication.
|
en-US
Unable to find the certificate or key necessary for authentication.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_NO_SERVER_KEY_FOR_ALG |
ja
Server has no key for the attempted key exchange algorithm.
|
en-US
Server has no key for the attempted key exchange algorithm.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_PUB_KEY_SIZE_LIMIT_EXCEEDED |
ja
SSL Server attempted to use domestic-grade public key with export cipher suite.
|
en-US
SSL Server attempted to use domestic-grade public key with export cipher suite.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_RX_MALFORMED_CLIENT_KEY_EXCH |
ja
SSL received a malformed Client Key Exchange handshake message.
|
en-US
SSL received a malformed Client Key Exchange handshake message.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_RX_MALFORMED_SERVER_KEY_EXCH |
ja
SSL received a malformed Server Key Exchange handshake message.
|
en-US
SSL received a malformed Server Key Exchange handshake message.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_RX_UNEXPECTED_CLIENT_KEY_EXCH |
ja
SSL received an unexpected Client Key Exchange handshake message.
|
en-US
SSL received an unexpected Client Key Exchange handshake message.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_RX_UNEXPECTED_SERVER_KEY_EXCH |
ja
SSL received an unexpected Server Key Exchange handshake message.
|
en-US
SSL received an unexpected Server Key Exchange handshake message.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_SERVER_KEY_EXCHANGE_FAILURE |
ja
Unspecified failure while processing SSL Server Key Exchange handshake.
|
en-US
Unspecified failure while processing SSL Server Key Exchange handshake.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_SYM_KEY_CONTEXT_FAILURE |
ja
Failure to create Symmetric Key context.
|
en-US
Failure to create Symmetric Key context.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_SYM_KEY_UNWRAP_FAILURE |
ja
Failure to unwrap the Symmetric key in Client Key Exchange message.
|
en-US
Failure to unwrap the Symmetric key in Client Key Exchange message.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_WEAK_SERVER_CERT_KEY |
ja
The server certificate included a public key that was too weak.
|
en-US
The server certificate included a public key that was too weak.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_WEAK_SERVER_EPHEMERAL_DH_KEY |
ja
SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.
|
en-US
SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SSL_ERROR_WRONG_CERTIFICATE |
ja
Client authentication failed: private key in key database does not match public key in certificate database.
|
en-US
Client authentication failed: private key in key database does not match public key in certificate database.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpAuthKeyID |
ja
Certificate Authority Key Identifier
|
en-US
Certificate Authority Key Identifier
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpECPublicKey |
ja
Elliptic Curve Public Key
|
en-US
Elliptic Curve Public Key
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpECTemplate |
ja
Key size: %S bits\nBase point order length: %S bits\nPublic value:\n%S
|
en-US
Key size: %S bits\nBase point order length: %S bits\nPublic value:\n%S
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpEKU_1_3_6_1_4_1_311_10_3_11 |
ja
Microsoft Key Recovery
|
en-US
Microsoft Key Recovery
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpEKU_1_3_6_1_4_1_311_21_6 |
ja
Microsoft Key Recovery Agent
|
en-US
Microsoft Key Recovery Agent
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpExtKeyUsage |
ja
Extended Key Usage
|
en-US
Extended Key Usage
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpKUEnc |
ja
Key Encipherment
|
en-US
Key Encipherment
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpKUKA |
ja
Key Agreement
|
en-US
Key Agreement
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpKeyCompromise |
ja
Key Compromise
|
en-US
Key Compromise
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpKeyID |
ja
Key ID
|
en-US
Key ID
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpKeyUsage |
ja
Certificate Key Usage
|
en-US
Certificate Key Usage
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpSPKI |
ja
Subject Public Key Info
|
en-US
Subject Public Key Info
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpSPKIAlg |
ja
Subject Public Key Algorithm
|
en-US
Subject Public Key Algorithm
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpSubjPubKey |
ja
Subject’s Public Key
|
en-US
Subject’s Public Key
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties CertDumpSubjectKeyID |
ja
Certificate Subject Key ID
|
en-US
Certificate Subject Key ID
|
|
Entity
#
all locales
security • manager • chrome • pipnss • pipnss.properties Fips140SlotDescription |
ja
FIPS 140 Cryptographic, Key and Certificate Services
|
en-US
FIPS 140 Cryptographic, Key and Certificate Services
|
|
Entity
#
all locales
suite • chrome • common • sync • syncSetup.properties save.recoverykey.defaultfilename |
ja
SeaMonkey Recovery Key.xhtml
|
en-US
SeaMonkey Recovery Key.xhtml
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-authority-key-id |
ja
Authority Key ID
|
en-US
Authority Key ID
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-extended-key-usages |
ja
Extended Key Usages
|
en-US
Extended Key Usages
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-key-exchange-group |
ja
Key Exchange Group
|
en-US
Key Exchange Group
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-key-id |
ja
Key ID
|
en-US
Key ID
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-key-size |
ja
Key Size
|
en-US
Key Size
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-key-usages |
ja
Key Usages
|
en-US
Key Usages
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-public-key-info |
ja
Public Key Info
|
en-US
Public Key Info
|
|
Entity
#
all locales
toolkit • toolkit • about • certviewer.ftl certificate-viewer-subject-key-id |
ja
Subject Key ID
|
en-US
Subject Key ID
|
Displaying 200 results for the string key in en-US:
| Entity | ja | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-details-key-pinning-label |
ja
HTTP 公開鍵ピンニング: { $hasHPKP }
|
en-US
HTTP Public Key Pinning: { $hasHPKP }
|
|
Entity
#
all locales
browser • browser • newtab • asrouter.ftl cfr-whatsnew-passwords-icon-alt |
ja
脆弱なパスワードの鍵アイコン
|
en-US
Vulnerable password key icon
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-inadequate-key-size |
ja
The server presented a certificate with a key size that is too small to establish a secure connection.
|
en-US
The server presented a certificate with a key size that is too small to establish a secure connection.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-key-pinning-failure |
ja
The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden.
|
en-US
The server uses key pinning (HPKP) but no trusted certificate chain could be constructed that matches the pinset. Key pinning violations cannot be overridden.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-bad-key |
ja
Peer’s public key is invalid.
|
en-US
Peer’s public key is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cannot-move-sensitive-key |
ja
A sensitive key cannot be moved to the slot where it is needed.
|
en-US
A sensitive key cannot be moved to the slot where it is needed.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-decryption-disallowed |
ja
Cannot decrypt: encrypted using a disallowed algorithm or key size.
|
en-US
Cannot decrypt: encrypted using a disallowed algorithm or key size.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-filing-key |
ja
Error refiling the key for this certificate.
|
en-US
Error refiling the key for this certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-inadequate-key-usage |
ja
Certificate key usage inadequate for attempted operation.
|
en-US
Certificate key usage inadequate for attempted operation.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-invalid-key |
ja
The key does not support the requested operation.
|
en-US
The key does not support the requested operation.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-key-nickname-collision |
ja
A key with the same nickname already exists.
|
en-US
A key with the same nickname already exists.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-keygen-fail |
ja
Unable to generate public/private key pair.
|
en-US
Unable to generate public/private key pair.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-krl-not-yet-valid |
ja
The key revocation list for this certificate is not yet valid.
|
en-US
The key revocation list for this certificate is not yet valid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-no-key |
ja
The private key for this certificate cannot be found in key database
|
en-US
The private key for this certificate cannot be found in key database
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-not-a-recipient |
ja
Cannot decrypt: you are not a recipient, or matching certificate and private key not found.
|
en-US
Cannot decrypt: you are not a recipient, or matching certificate and private key not found.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-key-database-not-initialized |
ja
Unable to export. Key database corrupt or deleted.
|
en-US
Unable to export. Key database corrupt or deleted.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-export-key |
ja
Unable to export. Private Key could not be located and exported.
|
en-US
Unable to export. Private Key could not be located and exported.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-import-key |
ja
Unable to import. Error attempting to import private key.
|
en-US
Unable to import. Error attempting to import private key.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-locate-object-by-name |
ja
Unable to export. Unable to locate certificate or key by nickname.
|
en-US
Unable to export. Unable to locate certificate or key by nickname.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs7-keyalg-mismatch |
ja
Cannot decrypt: key encryption algorithm does not match your certificate.
|
en-US
Cannot decrypt: key encryption algorithm does not match your certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-revoked-key |
ja
The key for this site’s certificate has been revoked.
|
en-US
The key for this site’s certificate has been revoked.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-unsupported-keyalg |
ja
Unsupported or unknown key algorithm.
|
en-US
Unsupported or unknown key algorithm.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-cert-kea-mismatch |
ja
The certificate provided cannot be used with the selected key exchange algorithm.
|
en-US
The certificate provided cannot be used with the selected key exchange algorithm.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-client-key-exchange-failure |
ja
Unspecified failure while processing SSL Client Key Exchange handshake.
|
en-US
Unspecified failure while processing SSL Client Key Exchange handshake.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-decrypt-error-alert |
ja
Peer reports failure of signature verification or key exchange.
|
en-US
Peer reports failure of signature verification or key exchange.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-extract-public-key-failure |
ja
SSL was unable to extract the public key from the peer’s certificate.
|
en-US
SSL was unable to extract the public key from the peer’s certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-no-certificate |
ja
Unable to find the certificate or key necessary for authentication.
|
en-US
Unable to find the certificate or key necessary for authentication.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-no-server-key-for-alg |
ja
Server has no key for the attempted key exchange algorithm.
|
en-US
Server has no key for the attempted key exchange algorithm.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-pub-key-size-limit-exceeded |
ja
SSL Server attempted to use domestic-grade public key with export cipher suite.
|
en-US
SSL Server attempted to use domestic-grade public key with export cipher suite.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-client-key-exch |
ja
SSL received a malformed Client Key Exchange handshake message.
|
en-US
SSL received a malformed Client Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-server-key-exch |
ja
SSL received a malformed Server Key Exchange handshake message.
|
en-US
SSL received a malformed Server Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-client-key-exch |
ja
SSL received an unexpected Client Key Exchange handshake message.
|
en-US
SSL received an unexpected Client Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-server-key-exch |
ja
SSL received an unexpected Server Key Exchange handshake message.
|
en-US
SSL received an unexpected Server Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-server-key-exchange-failure |
ja
Unspecified failure while processing SSL Server Key Exchange handshake.
|
en-US
Unspecified failure while processing SSL Server Key Exchange handshake.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-sym-key-context-failure |
ja
Failure to create Symmetric Key context.
|
en-US
Failure to create Symmetric Key context.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-sym-key-unwrap-failure |
ja
Failure to unwrap the Symmetric key in Client Key Exchange message.
|
en-US
Failure to unwrap the Symmetric key in Client Key Exchange message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-weak-server-cert-key |
ja
The server certificate included a public key that was too weak.
|
en-US
The server certificate included a public key that was too weak.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-weak-server-ephemeral-dh-key |
ja
SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.
|
en-US
SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-wrong-certificate |
ja
Client authentication failed: private key in key database does not match public key in certificate database.
|
en-US
Client authentication failed: private key in key database does not match public key in certificate database.
|
|
Entity
#
all locales
browser • browser • policies • policies-descriptions.ftl policy-DisableSafeMode |
ja
セーフモードで再起動する機能を無効にします。注意: Shift キーでセーフモードを起動する機能は、Windows でグループポリシーを利用する場合のみ無効にできます。
|
en-US
Disable the feature to restart in Safe Mode. Note: the Shift key to enter Safe Mode can only be disabled on Windows using Group Policy.
|
|
Entity
#
all locales
browser • browser • screenshots.ftl screenshots-notification-image-copied-details |
ja
ショットがクリップボードへコピーされました。{ screenshots-meta-key }+V キーで貼り付けできます。
|
en-US
Your shot has been copied to the clipboard. Press {screenshots-meta-key}-V to paste.
|
|
Entity
#
all locales
browser • browser • screenshots.ftl screenshots-notification-link-copied-details |
ja
ショットへのリンクがクリップボードへコピーされました。{ screenshots-meta-key }+V キーで貼り付けできます。
|
en-US
The link to your shot has been copied to the clipboard. Press {screenshots-meta-key}-V to paste.
|
|
Entity
#
all locales
browser • chrome • browser • browser.properties webauthn.registerDirectPrompt2 |
ja
%1$S はあなたのプライバシーに関わるより詳細なセキュリティキーを求めています。\n\n%2$S はキーを匿名化できますが、その場合はウェブサイトに拒否されることがあります。拒否されても再試行できます。
|
en-US
%1$S is requesting extended information about your security key, which may affect your privacy.\n\n%2$S can anonymize this for you, but the website might decline this key. If declined, you can try again.
|
|
Entity
#
all locales
browser • chrome • browser • browser.properties webauthn.signPrompt2 |
ja
%S は登録されたセキュリティキーでの認証を求めています。接続して認証するか、キャンセルしてください。
|
en-US
%S wants to authenticate you using a registered security key. You can connect and authorize one now, or cancel.
|
|
Entity
#
all locales
chat • irc.properties command.join |
ja
%S <チャンネル1>[ <キー1>][,<チャンネル2>[ <キー2>]]*: 指定した複数のチャンネルに参加します。必要な場合は各チャンネルのチャンネルキーを指定してください。
|
en-US
%S <room1>[ <key1>][,<room2>[ <key2>]]*: Enter one or more channels, optionally providing a channel key for each if needed.
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.security.hpkp |
ja
公開鍵のピン留め:
|
en-US
Public Key Pinning:
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.security.keaGroup |
ja
鍵共有グループ:
|
en-US
Key Exchange Group:
|
|
Entity
#
all locales
devtools • client • storage.properties table.headers.indexedDB.keyPath2 |
ja
キーパス
|
en-US
Key Path
|
|
Entity
#
all locales
devtools • client • storage.properties table.headers.indexedDB.name |
ja
名前
|
en-US
Key
|
|
Entity
#
all locales
devtools • client • storage.properties table.headers.indexedDB.uniqueKey |
ja
ユニークキー
|
en-US
Unique key
|
|
Entity
#
all locales
devtools • client • webconsole.properties table.key |
ja
名前
|
en-US
Key
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties GTK2Conflict2 |
ja
GTK2 上のキーイベントは利用できません: key=“%S” modifiers=“%S” id=“%S”
|
en-US
Key event not available on GTK2: key=“%S” modifiers=“%S” id=“%S”
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadCryptoKeyHeader |
ja
スコープ ‘%1$S’ の ServiceWorker がプッシュメッセージの復号に失敗しました。‘Crypto-Key’ ヘッダーはアプリサーバーの公開鍵を含む ‘dh’ パラメーターを含まなければなりません。詳しい情報は https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 を参照してください。
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Crypto-Key‘ header must include a ‘dh‘ parameter containing the app server’s public key. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadEncryptionKeyHeader |
ja
スコープ ‘%1$S’ の ServiceWorker がプッシュメッセージの復号に失敗しました。‘Encryption-Key’ ヘッダーは ‘dh’ パラメーターを含まなければなりません。このヘッダーは推奨されず、間もなく削除されます。代わりに ‘Content-Encoding: aesgcm’ を指定した ‘Crypto-Key’ を使用してください。詳しい情報は https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 を参照してください。
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption-Key’ header must include a ‘dh‘ parameter. This header is deprecated and will soon be removed. Please use ‘Crypto-Key‘ with ‘Content-Encoding: aesgcm‘ instead. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties PushMessageBadSenderKey |
ja
スコープ ‘%1$S’ の ServiceWorker がプッシュメッセージの復号に失敗しました。‘Crypto-Key’ ヘッダー内の ‘dh’ パラメーターはアプリサーバーの Diffie-Hellman 公開鍵であり、base64url でエンコード (https://tools.ietf.org/html/rfc7515#appendix-C) され、“uncompressed” または “raw” 形式 (エンコーディングの前に 65 バイトの長さ) でなければなりません。詳しい情報は https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 を参照してください。
|
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘dh‘ parameter in the ‘Crypto-Key‘ header must be the app server’s Diffie-Hellman public key, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) and in “uncompressed” or “raw” form (65 bytes before encoding). See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties WinConflict2 |
ja
一部のキーボードレイアウトではキーイベントが利用できません: key=“%S” modifiers=“%S” id=“%S”
|
en-US
Key event not available on some keyboard layouts: key=“%S” modifiers=“%S” id=“%S”
|
|
Entity
#
all locales
dom • chrome • xslt • xslt.properties 32 |
ja
key 関数の呼び出しは許可されていません。
|
en-US
Call to the key function not allowed.
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorButtonProperties.dtd AccessKey.label |
ja
アクセスキー:
|
en-US
Access Key:
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorInputProperties.dtd AccessKey.label |
ja
アクセスキー:
|
en-US
Access Key:
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorLabelProperties.dtd AccessKey.label |
ja
アクセスキー:
|
en-US
Access Key:
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorTextAreaProperties.dtd TextAreaAccessKey.label |
ja
アクセスキー:
|
en-US
Access Key:
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.j.params |
ja
<channel-name> [<key>]
|
en-US
<channel-name> [<key>]
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join-charset.help |
ja
チャンネル <channel-name> に参加します。チャンネル名の最初が '#' の場合はグローバル、'&' の場合はローカル、'+' の場合はモードなしですが、記号がなければグローバルになります。メッセージは <charset> に指定された文字エンコーディングでエンコードおよびデコードされます。<charset> パラメーターは、/charset コマンドで選択される既定の文字エンコーディングとは無関係です。キー <key> が設定されていれば送信します。
|
en-US
Joins the global (name starts with #), local (name starts with &), or modeless (name starts with a +) channel named <channel-name>. Messages will be encoded and decoded according to the character encoding specified by <charset>. The <charset> parameter is independent of the default character encoding, which can be selected with the /charset command. If no prefix is given, # is assumed. Provides the key <key> if specified.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join-charset.params |
ja
[<channel-name> <charset> [<key>]]
|
en-US
[<channel-name> <charset> [<key>]]
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join.help |
ja
チャンネル <channel-name> に参加します。チャンネル名の最初が '#' の場合はグローバル、'&' の場合はローカル、'+' の場合はモードなしですが、記号がなければグローバルになります。キー <key> が設定されていれば送信します。
|
en-US
Joins the global (name starts with #), local (name starts with &), or modeless (name starts with a +) channel named <channel-name>. If no prefix is given, # is assumed. Provides the key <key> if specified.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.join.params |
ja
[<channel-name> [<key>]]
|
en-US
[<channel-name> [<key>]]
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties msg.irc.475 |
ja
このチャンネルはキーが必要です。参加するには、現在のキーを提示する必要があります。キーを使用して参加する方法は "/help join" を参照してください。
|
en-US
This channel needs a key. You must provide the correct key to join the channel. See "/help join" for details on joining a channel with a key.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties msg.url.key |
ja
URL %S のキーを入力:
|
en-US
Enter key for url %S:
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.messages.ctrlClick.help |
ja
URL を Control キーを押しながらクリックしたときの動作です。
|
en-US
What to do when clicking a URL with the Control key held down.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.messages.metaClick.help |
ja
URL を Alt または Meta キーを押しながらクリックしたときの動作です。
|
en-US
What to do when clicking a URL with the Alt or Meta key held down.
|
|
Entity
#
all locales
mail • chrome • messenger-mapi • mapi.properties errorMessage |
ja
レジストリーキーを更新できなかったため %S を既定のメールクライアントに設定できませんでした。あなたがシステムのレジストリーに書き込む権限を持っているかどうかシステム管理者に確認してから、再度試してください。
|
en-US
%S could not be set as the default mail application because a registry key could not be updated. Verify with your system administrator that you have write access to your system registry, and then try again.
|
|
Entity
#
all locales
mail • chrome • messenger-mapi • mapi.properties errorMessageNews |
ja
レジストリーキーを更新できなかったため %S を既定のニュースリーダーに設定できませんでした。あなたがシステムのレジストリーに書き込む権限を持っているかどうかシステム管理者に確認してから、再度試してください。
|
en-US
%S could not be set as the default news application because a registry key could not be updated. Verify with your system administrator that you have write access to your system registry, and then try again.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgCompSMIMEOverlay.dtd menu_securityAttachMyKey.label |
ja
公開鍵を添付
|
en-US
Attach My Public Key
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgReadSMIMEOverlay.properties CantDecryptBody |
ja
このメッセージの送信者はあなたのデジタル証明書を使って暗号化していますが、その証明書と対応する秘密鍵が見つかりませんでした。<br/><ul><li>新しいコンピューターや %brand% の新しいプロファイルを使用している場合、以前のコンピューターやバックアップからあなたの証明書と秘密鍵を復元してください。証明書のバックアップファイルは通常 ".p12" で終わる名前のファイルです。</li><li>スマートカードを持っている場合、挿入してください。</li></ul>
|
en-US
The sender encrypted this message to you using one of your digital certificates, however %brand% was not able to find this certificate and corresponding private key. <br> Possible solutions: <br><ul><li>If you have a smartcard, please insert it now. <li>If you are using a new machine, or if you are using a new %brand% profile, you will need to restore your certificate and private key from a backup. Certificate backups usually end in ".p12".</ul>
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd e2eeReqWarning.description |
ja
送信メッセージを暗号化する必要がある場合は、あなたの公開鍵またはすべての受信者の証明書を用意しなければなりません。
|
en-US
If you require encryption, to send a message you must have the public key or certificate of every recipient.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd openpgpKey.button |
ja
秘密鍵を設定...
|
en-US
Set Personal Key…
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd openpgpKey.message |
ja
暗号化およびデジタル署名のための秘密鍵:
|
en-US
Personal key for encryption and digital signing:
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl address-input-type-aria-label |
ja
{ $count ->
[0] { $type }
[one] { $type } のアドレス 1 件、フォーカスするには左矢印キーを押してください。
*[other] { $type } のアドレス { $count } 件、フォーカスするには左矢印キーを押してください。
}
|
en-US
{ $count ->
[0] { $type }
[one] { $type } with one address, use left arrow key to focus on it.
*[other] { $type } with { $count } addresses, use left arrow key to focus on them.
}
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl collapse-attachment-pane-tooltip.tooltiptext |
ja
添付ペインを隠します ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
en-US
Hide the attachment pane ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl context-menuitem-attach-files.acceltext |
ja
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
en-US
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl expand-attachment-pane-tooltip.tooltiptext |
ja
添付ペインを表示します ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
en-US
Show the attachment pane ({ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key })
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl menuitem-attach-files.acceltext |
ja
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
en-US
{ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key }
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl menuitem-toggle-attachment-pane.acceltext |
ja
{ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key }
|
en-US
{ ctrl-cmd-shift-pretty-prefix }{ toggle-attachment-pane-key }
|
|
Entity
#
all locales
mail • messenger • messengercompose • messengercompose.ftl toolbar-button-add-attachment.tooltiptext |
ja
添付ファイルを追加します ({ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key })
|
en-US
Add an Attachment ({ ctrl-cmd-shift-pretty-prefix }{ trigger-attachment-picker-key })
|
|
Entity
#
all locales
mail • messenger • openpgp • backupKeyPassword.ftl set-password-backup-pw.value |
ja
秘密鍵のバックアップのためのパスワード:
|
en-US
Secret Key backup password:
|
|
Entity
#
all locales
mail • messenger • openpgp • backupKeyPassword.ftl set-password-message |
ja
これから作成される OpenPGP 秘密鍵のバックアップファイルは、ここで設定されたパスワードによって保護されます。バックアップの途中でこのパスワードを入力する必要があります。
|
en-US
The password you set here protects the OpenPGP secret key backup file that you are about to create. You must set this password to proceed with the backup.
|
|
Entity
#
all locales
mail • messenger • openpgp • backupKeyPassword.ftl set-password-reminder |
ja
<b>重要！</b> 秘密鍵のバックアップのためのパスワードを忘れると、このバックアップから復元することができなくなります。パスワードを安全な場所に保管してください。
|
en-US
<b>Important!</b> If you forget your secret key backup password, you will not be able to restore this backup later. Please record it in a safe location.
|
|
Entity
#
all locales
mail • messenger • openpgp • backupKeyPassword.ftl set-password-repeat-backup-pw.value |
ja
秘密鍵のバックアップのためのパスワード (もう一度):
|
en-US
Secret Key backup password (again):
|
|
Entity
#
all locales
mail • messenger • openpgp • backupKeyPassword.ftl set-password-window.title |
ja
OpenPGP 鍵のバックアップのためのパスワードを設定
|
en-US
Choose a password to backup your OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl expire-in-label.label |
ja
有効期限を次の期間までにする:
|
en-US
Key will expire in:
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl expire-never-label.label |
ja
有効期限を無期限にする
|
en-US
Key will never expire
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl info-already-expired |
ja
この鍵は既に有効期限切れです。
|
en-US
This key has already expired.
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl info-does-not-expire |
ja
現在この鍵は有効期限が無期限に設定されています。
|
en-US
This key is currently configured to never expire.
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl info-explanation-1 |
ja
<b>鍵の有効期限が切れると</b>、その鍵は暗号化やデジタル署名に使用できなくなります。
|
en-US
<b>After a key expires</b>, it's no longer possible to use it for encryption or digital signing.
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl info-explanation-2 |
ja
この鍵をより長い期間使用するのであれば、有効期限を変更し、公開鍵を通信相手と再度共有してください。
|
en-US
To use this key for a longer period of time, change its expiration date, and then share the public key with your conversation partners again.
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl info-will-expire |
ja
現在この鍵は { $date } に有効期限が切れるよう設定されています。
|
en-US
This key is currently configured to expire on { $date }.
|
|
Entity
#
all locales
mail • messenger • openpgp • changeExpiryDlg.ftl openpgp-change-key-expiry-title.title |
ja
鍵の有効期限を変更
|
en-US
Change Key Expiration
|
|
Entity
#
all locales
mail • messenger • openpgp • composeKeyStatus.ftl openpgp-compose-key-status-intro-need-keys |
ja
エンドツーエンド暗号化されたメッセージを送信するには、メッセージの受信者ごとの公開鍵を入手し、受け入れる必要があります。
|
en-US
To send an end-to-end encrypted message, you must obtain and accept a public key for each recipient.
|
|
Entity
#
all locales
mail • messenger • openpgp • composeKeyStatus.ftl openpgp-recip-missing |
ja
利用可能な鍵がありません
|
en-US
no key available
|
|
Entity
#
all locales
mail • messenger • openpgp • composeKeyStatus.ftl openpgp-recip-none-accepted |
ja
鍵は受け入れられませんでした
|
en-US
no accepted key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl import-key-file |
ja
OpenPGP 鍵ファイルをインポート
|
en-US
Import OpenPGP Key File
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl import-key-personal-checkbox.label |
ja
この鍵を個人鍵として利用する
|
en-US
Treat this key as a Personal Key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl key-wizard-dialog-window.title |
ja
{ $identity } のための OpenPGP 鍵を追加
|
en-US
Add a Personal OpenPGP Key for { $identity }
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl key-wizard-warning |
ja
このメールアドレスに紐づいた <b>個人鍵をすでに所有している場合には</b>、その鍵をインポートしてください。既存の鍵をインポートしないと、あなたの既存の鍵で暗号化されたメールは、保管しているものも今後受信するものも読めなくなります。
|
en-US
<b>If you have an existing personal key</b> for this email address, you should import it. Otherwise you will not have access to your archives of encrypted emails, nor be able to read incoming encrypted emails from people who are still using your existing key.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-external-key-description |
ja
鍵 ID を入力して、外部の GnuPG を設定してください。
|
en-US
Configure an external GnuPG key by entering the Key ID
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-external-key-info |
ja
また、対応する公開鍵を鍵マネージャーからインポートして受け入れる必要があります。
|
en-US
In addition, you must use Key Manager to import and accept the corresponding Public Key.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-external-key-label |
ja
秘密鍵 ID:
|
en-US
Secret Key ID:
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-external-key-title |
ja
外部の GnuPG 鍵
|
en-US
External GnuPG Key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-external-key-warning |
ja
<b>外部の GnuPG 鍵は 1 個しか設定できません</b>。以前に設定した鍵は置換されます。
|
en-US
<b>You may configure only one external GnuPG Key.</b> Your previous entry will be replaced.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-generate-key-info |
ja
<b>注意: 鍵の生成が完了するまで数分かかることがあります</b>。鍵の生成の途中でプログラムを終了させないでください。鍵の生成中に、ウェブブラウザーを使用する、もしくはディスクアクセスが激しい処理を行うと「乱数プール」が満たされ、処理が早く終わります。鍵の生成が終了したらお知らせします。
|
en-US
<b>Key generation may take up to several minutes to complete.</b> Do not exit the application while key generation is in progress. Actively browsing or performing disk-intensive operations during key generation will replenish the 'randomness pool' and speed-up the process. You will be alerted when key generation is completed.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-generate-key-title |
ja
OpenPGP 鍵を生成
|
en-US
Generate OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-key-info |
ja
他のソフトウェアでは、個人鍵のことをあなた自身の鍵、秘密鍵、プライベート鍵、鍵ペアなどと呼んでいるかもしれません。
|
en-US
Other software might describe a personal key using alternative terms such as your own key, secret key, private key or key pair.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-key-list-amount |
ja
{ $count ->
[one] インポート可能な鍵が 1 個あります。
*[other] インポート可能な鍵が { $count } 個あります。
}
|
en-US
{ $count ->
[one] Thunderbird found one key that can be imported.
*[other] Thunderbird found { $count } keys that can be imported.
}
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-key-list-caption |
ja
個人鍵として利用するとマークされた鍵は、エンドツーエンド暗号化セクションに表示されます。それ以外の鍵は、鍵マネージャーの中で利用可能です。
|
en-US
Keys marked to be treated as Personal Keys will be listed in the End-To-End Encryption section. The others will be available inside the Key Manager.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-key-list-description |
ja
どの鍵をあなたの個人鍵として利用するか確認してください。あなた自身が作成し、あなた自身の差出人情報が表示される鍵のみを個人鍵として利用可能です。後からこの設定を鍵のプロパティダイアログから変更することもできます。
|
en-US
Confirm which keys may be treated as your personal keys. Only keys that you created yourself and that show your own identity should be used as personal keys. You can change this option later in the Key Properties dialog.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-key-props.label |
ja
鍵のプロパティ
|
en-US
Key Properties
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-key-title |
ja
既存の OpenPGP 個人鍵をインポート
|
en-US
Import an existing personal OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-import-success-description |
ja
インポートしたあなたの既存の OpenPGP 鍵を利用するには、このダイアログを閉じ、アカウント設定から鍵を選択してください。
|
en-US
To start using your imported OpenPGP key for email encryption, close this dialog and access your Account Settings to select it.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-key-confirm |
ja
{ $identity } の公開鍵と秘密鍵を生成しますか？
|
en-US
Generate public and secret key for { $identity }?
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-abort |
ja
現在 OpenPGP 鍵の生成が進行中です。キャンセルしますか？
|
en-US
OpenPGP Key generation currently in progress, are you sure you want to cancel it?
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-abort-title |
ja
鍵の生成を中止しますか？
|
en-US
Abort key generation?
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-advanced-description |
ja
OpenPGP 鍵の高度な設定を行います。
|
en-US
Control the advanced settings of your OpenPGP Key.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-button |
ja
鍵を生成
|
en-US
Generate key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-error-failed |
ja
OpenPGP 鍵の生成に予期せず失敗しました
|
en-US
OpenPGP Key generation unexpectedly failed
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-error-revocation |
ja
OpenPGP 鍵の生成に成功しましたが、鍵 { $key } の失効証明書を生成できませんでした
|
en-US
OpenPGP Key created successfully, but failed to obtain revocation for key { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-expiry-description |
ja
新しく生成する鍵の有効期限を指定します。必要があれば、後から変更も可能です。
|
en-US
Define the expiration time of your newly generated key. You can later control the date to extend it if necessary.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-expiry-title |
ja
鍵の有効期限
|
en-US
Key expiry
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-keysize.value |
ja
鍵長:
|
en-US
Key size:
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-keytype.value |
ja
鍵のタイプ:
|
en-US
Key type:
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-long-expiry |
ja
有効期限を 100 年以上先に設定することはできません。
|
en-US
You cannot create a key that expires in more than 100 years.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-ongoing |
ja
既に鍵の生成は進行中です！
|
en-US
Key generation already in progress!
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-progress-title |
ja
あなたの新しい OpenPGP 鍵を生成中です...
|
en-US
Generating your new OpenPGP Key…
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-keygen-short-expiry |
ja
有効期限を 1 日以内に設定することはできません。
|
en-US
Your key must be valid for at least one day.
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-passphrase-prompt |
ja
以下の鍵のロックを解除するためにパスフレーズを入力してください: { $key }
|
en-US
Please enter the passphrase to unlock the following key: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl openpgp-save-external-button |
ja
鍵 ID を保存
|
en-US
Save key ID
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl radio-create-key.label |
ja
新しい OpenPGP 鍵を生成
|
en-US
Create a new OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl radio-gnupg-key.label |
ja
GnuPG 経由で外部の鍵を利用 (例: スマートカードに保存された鍵)
|
en-US
Use your external key through GnuPG (e.g. from a smartcard)
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl radio-import-key.label |
ja
既存の OpenPGP 鍵をインポート
|
en-US
Import an existing OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl radio-keygen-expiry.label |
ja
鍵の有効期限
|
en-US
Key expires in
|
|
Entity
#
all locales
mail • messenger • openpgp • keyWizard.ftl radio-keygen-no-expiry.label |
ja
無期限
|
en-US
Key does not expire
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl message-security-button.title |
ja
{ PLATFORM() ->
[macos] メッセージのセキュリティ情報を見る (⌘ ⌥ { message-header-show-security-info-key })
*[other] メッセージのセキュリティ情報を表示 (Ctrl+Alt+{ message-header-show-security-info-key })
}
|
en-US
{ PLATFORM() ->
[macos] Show Message Security (⌃ ⌘ { message-header-show-security-info-key })
*[other] Show Message Security (Ctrl+Alt+{ message-header-show-security-info-key })
}
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-enc-key-id |
ja
あなたの復号鍵 ID: { $key }
|
en-US
Your decryption key ID: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-enc-key-with-subkey-id |
ja
あなたの復号鍵 ID: { $key } (副鍵 ID: { $subkey })
|
en-US
Your decryption key ID: { $key } (Sub key ID: { $subkey })
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-invalid-rejected |
ja
このメッセージにはデジタル署名が含まれていますが、署名者の鍵は既に拒絶されています。
|
en-US
This message contains a digital signature, but you have previously decided to reject the signer key.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-key-id |
ja
署名者の鍵 ID: { $key }
|
en-US
Signer key ID: { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-key-id-with-subkey-id |
ja
署名者の鍵 ID: { $key } (副鍵 ID: { $subkey })
|
en-US
Signer key ID: { $key } (Sub key ID: { $subkey })
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-uncertain-no-key |
ja
このメッセージにはデジタル署名が含まれていますが、正当な署名か検証できません。署名を検証するには、送信者の公開鍵のコピーを入手する必要があります。
|
en-US
This message contains a digital signature, but it is uncertain if it is correct. To verify the signature, you need to obtain a copy of the sender's public key.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-uncertain-not-accepted |
ja
このメッセージにはデジタル署名が含まれていますが、署名者の鍵を受け入れるかまだ決定されていません。
|
en-US
This message contains a digital signature, but you haven't yet decided if the signer's key is acceptable to you.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-uncertain-uid-mismatch |
ja
このメッセージにはデジタル署名が含まれていますが、署名が一致しません。このメッセージは署名者の公開鍵とは一致しないメールアドレスから送信されています。
|
en-US
This message contains a digital signature, but a mismatch was detected. The message was sent from an email address that doesn't match the signer's public key.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-valid-own-key |
ja
このメッセージにはあなたの個人鍵による有効な署名が含まれています。
|
en-US
This message includes a valid digital signature from your personal key.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-valid-unverified |
ja
このメッセージにはあなたが受け入れた鍵による有効な署名が含まれていますが、その鍵が送信者のものであるか検証されていません。
|
en-US
This message includes a valid digital signature from a key that you have already accepted. However, you have not yet verified that the key is really owned by the sender.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-sig-valid-verified |
ja
このメッセージには検証済みの鍵による有効な署名が含まれています。
|
en-US
This message includes a valid digital signature from a verified key.
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-unknown-key-id |
ja
未知の鍵
|
en-US
Unknown key
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-view-signer-key.label |
ja
署名者の鍵を表示
|
en-US
View signer key
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl openpgp-view-your-encryption-key.label |
ja
あなたの復号鍵を表示
|
en-US
View your decryption key
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-intro |
ja
鍵 { $key } が利用可能です
|
en-US
Available public keys for { $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-key-own |
ja
受け入れる (個人鍵)
|
en-US
Accepted (personal key)
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-one-recipient-status-discover.label |
ja
新規、更新された鍵を検索
|
en-US
Discover new or updated key
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-one-recipient-status-instruction1 |
ja
エンドツーエンド暗号化されたメッセージを送信するには、メッセージの受取人の OpenPGP 公開鍵を入手し、受け入れる必要があります。
|
en-US
To send an end-to-end encrypted message to a recipient, you need to obtain their OpenPGP public key and mark it as accepted.
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-one-recipient-status-instruction2 |
ja
公開鍵を入手するには、公開鍵を添付されたあなた宛のメッセージからを公開鍵をインポートする必要があります。あるいは、鍵ディレクトリーから公開鍵を検索することができます。
|
en-US
To obtain their public key, import them from email they have sent to you and that includes it. Alternatively, you can try to discover their public key on a directory.
|
|
Entity
#
all locales
mail • messenger • openpgp • oneRecipientStatus.ftl openpgp-one-recipient-status-key-id.label |
ja
鍵 ID
|
en-US
Key ID
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-be-careful-new-key |
ja
警告: このメッセージに含まれる新しい OpenPGP 公開鍵は、{ $email } のものとしてあなたが以前に受け入れた公開鍵と異なります。
|
en-US
Warning: The new OpenPGP public key in this message differs from the public keys that you previously accepted for { $email }.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-cannot-decrypt-because-missing-key |
ja
このメッセージの復号のために必要な鍵は利用できません。
|
en-US
The secret key that is required to decrypt this message is not available.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-ctx-import-key.label |
ja
OpenPGP 鍵のインポート
|
en-US
Import OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-has-sender-key |
ja
このメッセージには送信者の OpenPGP 公開鍵が含まれています。
|
en-US
This message claims to contain the sender's OpenPGP public key.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-manage-keys-openpgp-cmd.label |
ja
OpenPGP 鍵マネージャー
|
en-US
OpenPGP Key Manager
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-missing-signature-key |
ja
このメッセージはあなたが所有していない鍵で署名されています。
|
en-US
This message was signed with a key that you don't yet have.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp-frontend.ftl openpgp-search-keys-openpgp.label |
ja
OpenPGP 鍵を検索
|
en-US
Discover OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl after-revoke-info |
ja
鍵は正常に失効されました。
メールで送信する、鍵サーバーへアップロードするなどして、この公開鍵を再度通信相手と共有してください。そうすることにより、あなたの鍵が失効していることが周知されます。
ソフトウェアが失効証明書を認識すると、あなたの古い鍵の利用を停止するでしょう。
同じメールアドレスに対する新しい鍵を利用しているのであれば、新しい公開鍵を添付してメッセージを送信することで、失効した古い鍵についての情報も周知されます。
|
en-US
The key has been revoked.
Share this public key again, by sending it by email, or by uploading it to keyservers, to let others know that you revoked your key.
As soon as the software used by other people learns about the revocation, it will stop using your old key.
If you are using a new key for the same email address, and you attach the new public key to emails you send, then information about your revoked old key will be automatically included.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl already-revoked |
ja
この鍵は既に失効しています。
|
en-US
This key has already been revoked.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl attachment-pgp-key |
ja
開こうとしている添付ファイル '{ $name }' は OpenPGP 鍵ファイルです。[インポート] をクリックして鍵をインポートするか、[表示] をクリックしてファイルの内容をウィンドウに表示してください
|
en-US
The attachment '{ $name }' you are opening appears to be an OpenPGP key file.
Click 'Import' to import the keys contained or 'View' to view the file contents in a browser window
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl cannot-send-enc-because-no-own-key |
ja
このメッセージを暗号化できませんでした。<{ $key }> のためのエンドツーエンド暗号化が設定されていません
|
en-US
Cannot send this message encrypted, because you haven't yet configured end-to-end encryption for <{ $key }>
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl cannot-send-sig-because-no-own-key |
ja
このメッセージにデジタル署名できませんでした。<{ $key }> のためのエンドツーエンド暗号化が設定されていません
|
en-US
Cannot digitally sign this message, because you haven't yet configured end-to-end encryption for <{ $key }>
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl cannot-use-own-key-because |
ja
あなたの個人鍵に問題があるためメッセージを送信できませんでした。{ $problem }
|
en-US
Unable to send the message, because there is a problem with your personal key. { $problem }
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl cant-import |
ja
公開鍵のインポート中にエラーが発生しました
|
en-US
Error importing public key
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl confirm-permissive-import |
ja
インポートに失敗しました。インポートを試みた鍵は破損しているか、未知の属性が使われています。正常な部分のみのインポートを試みますか？この場合、インポートが完了しない、あるいは利用できない鍵となる可能性があります。
|
en-US
Import failed. The key you are trying to import might be corrupt or use unknown attributes. Would you like to attempt to import the parts that are correct? This might result in the import of incomplete and unusable keys.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl copy-to-clipbrd-failed |
ja
選択した鍵をクリップボードにコピーできませんでした。
|
en-US
Could not copy the selected key(s) to the clipboard.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl copy-to-clipbrd-ok |
ja
鍵をクリップボードにコピーしました
|
en-US
Key(s) copied to clipboard
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-external-key-description |
ja
この外部 GnuPG 鍵 ID を除去しますか？
|
en-US
Do you want to remove this External GnuPG key ID?
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-external-key-title |
ja
外部 GnuPG 鍵を除去
|
en-US
Remove the External GnuPG Key
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-key-in-use-description |
ja
処理を進められません！削除のために選択した鍵はこの差出人で現在利用中です。違う鍵を選択するか、何も選択せずにもう一度試してください。
|
en-US
Unable to proceed! The Key you selected for deletion is currently being used by this identity. Select a different key, or select none, and try again.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-key-title |
ja
OpenPGP 鍵を削除
|
en-US
Delete OpenPGP Key
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-mix |
ja
警告: あなたは秘密鍵を削除しようとしています！
秘密鍵を削除するとあなた宛に暗号化されたメッセージを復号できなくなります。
本当に選択した秘密鍵と公開鍵の両方を削除しますか？
|
en-US
WARNING: You are about to delete secret keys!
If you delete your secret key, you will no longer be able to decrypt any messages encrypted for that key.
Do you really want to delete BOTH, the selected secret and public keys?
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-pub-key |
ja
公開鍵を削除しますか？
'{ $userId }'
|
en-US
Do you want to delete the public key
'{ $userId }'?
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl delete-secret-key |
ja
警告: あなたは秘密鍵を削除しようとしています！
秘密鍵を削除した場合、あなた宛に暗号化されたすべてのメッセージを復号できなくなり、鍵を失効することもできなくなります。
本当に以下の秘密鍵と公開鍵の両方を削除しますか？
'{ $userId }'
|
en-US
WARNING: You are about to delete a secret key!
If you delete your secret key, you will no longer be able to decrypt any messages encrypted for that key, nor will you be able to revoke it.
Do you really want to delete BOTH, the secret key and the public key
'{ $userId }'?
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl do-import-multiple |
ja
以下の鍵をインポートしますか？
{ $key }
|
en-US
Import the following keys?
{ $key }
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl e2e-intro-description-more |
ja
OpenPGP を有効化するためのあなたの個人鍵か、S/MIME を有効化するためのあなたの個人証明書を選択してください。どちらの場合にも、対応する秘密鍵を所有している必要があります。
|
en-US
Select your personal key to enable the use of OpenPGP, or your personal certificate to enable the use of S/MIME. For a personal key or certificate you own the corresponding secret key.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-key-expires-soon |
ja
あなたの鍵 { $desc } は { $days } 日以内に失効します。
新しい鍵ペアを生成し、その鍵を利用するようアカウント設定を変更することを推奨します。
|
en-US
Your key { $desc } will expire in less than { $days } days.
We recommend that you create a new key pair and configure the corresponding accounts to use it.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-key-missing-owner-trust |
ja
あなたの秘密鍵 { $desc } は信用度を失っています。
鍵の [所有者による信用度] の設定を [絶対的に信用] に変更することを推奨します。
|
en-US
Your secret key { $desc } has missing trust.
We recommend that you set "You rely on certifications" to "ultimate" in key properties.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-keys-missing-owner-trust |
ja
以下のあなたの秘密鍵は信用度を失っています。
{ $desc }
鍵の [所有者による信用度] の設定を [絶対的に信用] に変更することを推奨します。
|
en-US
The following of your secret keys have missing trust.
{ $desc }.
We recommend that you set "You rely on certifications" to "ultimate" in key properties.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-open-key-manager |
ja
OpenPGP 鍵マネージャーを開く
|
en-US
Open OpenPGP Key Manager
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-open-key-properties |
ja
{ PLATFORM() ->
[macos] 鍵の情報を見る
*[other] 鍵のプロパティを開く
}
|
en-US
Open Key Properties
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-too-long |
ja
有効期限を 100 年以上先に設定することはできません。
|
en-US
You cannot create a key that expires in more than 100 years.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl expiry-too-short |
ja
有効期限を 1 日以内に設定することはできません。
|
en-US
Your key must be valid for at least one day.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl export-keypair-to-file |
ja
ファイルとして秘密鍵と公開鍵をエクスポート
|
en-US
Export Secret and Public Key To File
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl export-secret-key |
ja
エクスポートする OpenPGP 鍵ファイルに秘密鍵を含めますか？
|
en-US
Do you want to include the secret key in the saved OpenPGP key file?
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl export-to-file |
ja
ファイルとして公開鍵をエクスポート
|
en-US
Export Public Key To File
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl fail-cancel |
ja
エラー - ユーザーによって鍵サーバーからの鍵のインポートが中止されました
|
en-US
Error - Key receive cancelled by user
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl fail-key-extract |
ja
エラー - 鍵の展開コマンドに失敗しました
|
en-US
Error - key extraction command failed
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl fail-key-import |
ja
エラー - 鍵のインポートに失敗しました
|
en-US
Error - key importing failed
|
APIThese results are also available as an API request to search in
ja or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.