Main Views
QA Views
About Transvision
BETA
Displaying 200 results out of 446 for the string certificate in en-US:
| Entity | en-US | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-details-cert-chain-label |
en-US
Certificate chain:
|
en-US
Certificate chain:
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-domain-mismatch |
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }.
|
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-domain-mismatch-multiple |
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }. The certificate is only valid for the following names: { $subject-alt-names }
|
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }. The certificate is only valid for the following names: { $subject-alt-names }
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-domain-mismatch-single |
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }. The certificate is only valid for <a data-l10n-name="domain-mismatch-link">{ $alt-name }</a>.
|
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }. The certificate is only valid for <a data-l10n-name="domain-mismatch-link">{ $alt-name }</a>.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-domain-mismatch-single-nolink |
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }. The certificate is only valid for { $alt-name }.
|
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust this site because it uses a certificate that is not valid for { $hostname }. The certificate is only valid for { $alt-name }.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-expired-now |
en-US
Websites prove their identity via certificates, which are valid for a set time period. The certificate for { $hostname } expired on { $not-after-local-time }.
|
en-US
Websites prove their identity via certificates, which are valid for a set time period. The certificate for { $hostname } expired on { $not-after-local-time }.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-intro |
en-US
{ $hostname } uses an invalid security certificate.
|
en-US
{ $hostname } uses an invalid security certificate.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-mitm-connection |
en-US
{ -brand-short-name } uses the Mozilla CA store to verify that a connection is secure, rather than certificates supplied by the user’s operating system. So, if an antivirus program or a network is intercepting a connection with a security certificate issued by a CA that is not in the Mozilla CA store, the connection is considered unsafe.
|
en-US
{ -brand-short-name } uses the Mozilla CA store to verify that a connection is secure, rather than certificates supplied by the user’s operating system. So, if an antivirus program or a network is intercepting a connection with a security certificate issued by a CA that is not in the Mozilla CA store, the connection is considered unsafe.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-mitm-intro |
en-US
Websites prove their identity via certificates, which are issued by certificate authorities.
|
en-US
Websites prove their identity via certificates, which are issued by certificate authorities.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-mitm-mozilla |
en-US
{ -brand-short-name } is backed by the non-profit Mozilla, which administers a completely open certificate authority (CA) store. The CA store helps ensure that certificate authorities are following best practices for user security.
|
en-US
{ -brand-short-name } is backed by the non-profit Mozilla, which administers a completely open certificate authority (CA) store. The CA store helps ensure that certificate authorities are following best practices for user security.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-not-yet-valid-now |
en-US
Websites prove their identity via certificates, which are valid for a set time period. The certificate for { $hostname } will not be valid until { $not-before-local-time }.
|
en-US
Websites prove their identity via certificates, which are valid for a set time period. The certificate for { $hostname } will not be valid until { $not-before-local-time }.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-symantec-distrust-description |
en-US
Websites prove their identity via certificates, which are issued by certificate authorities. Most browsers no longer trust certificates issued by GeoTrust, RapidSSL, Symantec, Thawte, and VeriSign. { $hostname } uses a certificate from one of these authorities and so the website’s identity cannot be proven.
|
en-US
Websites prove their identity via certificates, which are issued by certificate authorities. Most browsers no longer trust certificates issued by GeoTrust, RapidSSL, Symantec, Thawte, and VeriSign. { $hostname } uses a certificate from one of these authorities and so the website’s identity cannot be proven.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-cert-invalid |
en-US
The certificate is not trusted because it was issued by an invalid CA certificate.
|
en-US
The certificate is not trusted because it was issued by an invalid CA certificate.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-expired-issuer |
en-US
The certificate is not trusted because the issuer certificate has expired.
|
en-US
The certificate is not trusted because the issuer certificate has expired.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-self-signed |
en-US
The certificate is not trusted because it is self-signed.
|
en-US
The certificate is not trusted because it is self-signed.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-signature-algorithm-disabled |
en-US
The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.
|
en-US
The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-symantec |
en-US
Certificates issued by GeoTrust, RapidSSL, Symantec, Thawte, and VeriSign are no longer considered safe because these certificate authorities failed to follow security practices in the past.
|
en-US
Certificates issued by GeoTrust, RapidSSL, Symantec, Thawte, and VeriSign are no longer considered safe because these certificate authorities failed to follow security practices in the past.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-unknown-issuer |
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust { $hostname } because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.
|
en-US
Websites prove their identity via certificates. { -brand-short-name } does not trust { $hostname } because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-trust-untrusted-issuer |
en-US
The certificate is not trusted because the issuer certificate is not trusted.
|
en-US
The certificate is not trusted because the issuer certificate is not trusted.
|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl cert-error-untrusted-default |
en-US
The certificate does not come from a trusted source.
|
en-US
The certificate does not come from a trusted source.
|
|
Entity
#
all locales
browser • browser • browser.ftl identity-custom-root |
en-US
Connection verified by a certificate issuer that is not recognized by Mozilla.
|
en-US
Connection verified by a certificate issuer that is not recognized by Mozilla.
|
|
Entity
#
all locales
browser • browser • browser.ftl identity-description-custom-root |
en-US
Mozilla does not recognize this certificate issuer. It may have been added from your operating system or by an administrator. <label data-l10n-name="link">Learn More</label>
|
en-US
Mozilla does not recognize this certificate issuer. It may have been added from your operating system or by an administrator. <label data-l10n-name="link">Learn More</label>
|
|
Entity
#
all locales
browser • browser • browser.ftl identity-ev-owner-label |
en-US
Certificate issued to:
|
en-US
Certificate issued to:
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-additional-policy-constraint-failed |
en-US
An additional policy constraint failed when validating this certificate.
|
en-US
An additional policy constraint failed when validating this certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-ca-cert-used-as-end-entity |
en-US
The server uses a certificate with a basic constraints extension identifying it as a certificate authority. For a properly-issued certificate, this should not be the case.
|
en-US
The server uses a certificate with a basic constraints extension identifying it as a certificate authority. For a properly-issued certificate, this should not be the case.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-empty-issuer-name |
en-US
The server presented a certificate with an empty issuer distinguished name.
|
en-US
The server presented a certificate with an empty issuer distinguished name.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-inadequate-key-size |
en-US
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-invalid-integer-encoding |
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
|
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-key-pinning-failure |
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.
|
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 mozilla-pkix-error-not-yet-valid-certificate |
en-US
The server presented a certificate that is not yet valid.
|
en-US
The server presented a certificate that is not yet valid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-not-yet-valid-issuer-certificate |
en-US
A certificate that is not yet valid was used to issue the server’s certificate.
|
en-US
A certificate that is not yet valid was used to issue the server’s certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-ocsp-response-for-cert-missing |
en-US
The OCSP response does not include a status for the certificate being verified.
|
en-US
The OCSP response does not include a status for the certificate being verified.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-self-signed-cert |
en-US
The certificate is not trusted because it is self-signed.
|
en-US
The certificate is not trusted because it is self-signed.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-signature-algorithm-mismatch |
en-US
The signature algorithm in the signature field of the certificate does not match the algorithm in its signatureAlgorithm field.
|
en-US
The signature algorithm in the signature field of the certificate does not match the algorithm in its signatureAlgorithm field.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-v1-cert-used-as-ca |
en-US
An X.509 version 1 certificate that is not a trust anchor was used to issue the server’s certificate. X.509 version 1 certificates are deprecated and should not be used to sign other certificates.
|
en-US
An X.509 version 1 certificate that is not a trust anchor was used to issue the server’s certificate. X.509 version 1 certificates are deprecated and should not be used to sign other certificates.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-validity-too-long |
en-US
The server presented a certificate that is valid for too long.
|
en-US
The server presented a certificate that is valid for too long.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl psmerr-hostreusedissuerandserial |
en-US
You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information:
Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number.
|
en-US
You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information:
Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-adding-cert |
en-US
Error adding certificate to database.
|
en-US
Error adding certificate to database.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-bad-info-access-method |
en-US
Unknown information access method in certificate extension.
|
en-US
Unknown information access method in certificate extension.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-bad-nickname |
en-US
Certificate nickname already in use.
|
en-US
Certificate nickname already in use.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-bad-signature |
en-US
Peer’s certificate has an invalid signature.
|
en-US
Peer’s certificate has an invalid signature.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-ca-cert-invalid |
en-US
Issuer certificate is invalid.
|
en-US
Issuer certificate is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-addr-mismatch |
en-US
Address in signing certificate does not match address in message headers.
|
en-US
Address in signing certificate does not match address in message headers.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-bad-access-location |
en-US
The location for the certificate status server has invalid format.
|
en-US
The location for the certificate status server has invalid format.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-nickname-collision |
en-US
A certificate with the same nickname already exists.
|
en-US
A certificate with the same nickname already exists.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-not-in-name-space |
en-US
The Certifying Authority for this certificate is not permitted to issue a certificate with this name.
|
en-US
The Certifying Authority for this certificate is not permitted to issue a certificate with this name.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-not-valid |
en-US
This certificate is not valid.
|
en-US
This certificate is not valid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-signature-algorithm-disabled |
en-US
The certificate was signed using a signature algorithm that is disabled because it is not secure.
|
en-US
The certificate was signed using a signature algorithm that is disabled because it is not secure.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-usages-invalid |
en-US
Certificate usages field is invalid.
|
en-US
Certificate usages field is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-valid |
en-US
This certificate is valid.
|
en-US
This certificate is valid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-crl-bad-signature |
en-US
The CRL for the certificate’s issuer has an invalid signature.
|
en-US
The CRL for the certificate’s issuer has an invalid signature.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-crl-expired |
en-US
The CRL for the certificate’s issuer has expired. Update it or check your system date and time.
|
en-US
The CRL for the certificate’s issuer has expired. Update it or check your system date and time.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-crl-invalid-version |
en-US
Issuer’s Certificate Revocation List has an unknown version number.
|
en-US
Issuer’s Certificate Revocation List has an unknown version number.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-crl-not-yet-valid |
en-US
The certificate revocation list for this certificate is not yet valid.
|
en-US
The certificate revocation list for this certificate is not yet valid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-crl-unknown-critical-extension |
en-US
Issuer’s V2 Certificate Revocation List has an unknown critical extension.
|
en-US
Issuer’s V2 Certificate Revocation List has an unknown critical extension.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-crl-v1-critical-extension |
en-US
Issuer’s V1 Certificate Revocation List has a critical extension.
|
en-US
Issuer’s V1 Certificate Revocation List has a critical extension.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-duplicate-cert |
en-US
Certificate already exists in your database.
|
en-US
Certificate already exists in your database.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-duplicate-cert-name |
en-US
Downloaded certificate’s name duplicates one already in your database.
|
en-US
Downloaded certificate’s name duplicates one already in your database.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-expired-certificate |
en-US
Peer’s Certificate has expired.
|
en-US
Peer’s Certificate has expired.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-expired-issuer-certificate |
en-US
The certificate issuer’s certificate has expired. Check your system date and time.
|
en-US
The certificate issuer’s certificate has expired. Check your system date and time.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-extension-not-found |
en-US
Certificate extension not found.
|
en-US
Certificate extension not found.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-extension-value-invalid |
en-US
Certificate extension value is invalid.
|
en-US
Certificate extension value is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-filing-key |
en-US
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-cert-type |
en-US
Certificate type not approved for application.
|
en-US
Certificate type not approved for application.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-inadequate-key-usage |
en-US
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-krl-bad-signature |
en-US
The KRL for this site’s certificate has an invalid signature.
|
en-US
The KRL for this site’s certificate has an invalid signature.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-krl-expired |
en-US
The KRL for this site’s certificate has expired.
|
en-US
The KRL for this site’s certificate has expired.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-krl-not-yet-valid |
en-US
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-email-cert |
en-US
Not encrypted or signed: you do not yet have an email certificate.
|
en-US
Not encrypted or signed: you do not yet have an email certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-no-key |
en-US
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-no-krl |
en-US
No KRL for this site’s certificate has been found.
|
en-US
No KRL for this site’s certificate has been found.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-not-a-recipient |
en-US
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-not-fortezza-issuer |
en-US
Peer FORTEZZA chain has a non-FORTEZZA Certificate.
|
en-US
Peer FORTEZZA chain has a non-FORTEZZA Certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-ocsp-invalid-signing-cert |
en-US
Invalid OCSP signing certificate in OCSP response.
|
en-US
Invalid OCSP signing certificate in OCSP response.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-ocsp-responder-cert-invalid |
en-US
Configured OCSP responder’s certificate is invalid.
|
en-US
Configured OCSP responder’s certificate is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-ocsp-unauthorized-response |
en-US
The signer of the OCSP response is not authorized to give status for this certificate.
|
en-US
The signer of the OCSP response is not authorized to give status for this certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-ocsp-unknown-cert |
en-US
The OCSP server has no status for the certificate.
|
en-US
The OCSP server has no status for the certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-path-len-constraint-invalid |
en-US
Certificate path length constraint is invalid.
|
en-US
Certificate path length constraint is invalid.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-importing-cert-chain |
en-US
Unable to import. Error attempting to import certificate chain.
|
en-US
Unable to import. Error attempting to import certificate chain.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-pkcs12-unable-to-locate-object-by-name |
en-US
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 |
en-US
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-certificate |
en-US
Peer’s Certificate has been revoked.
|
en-US
Peer’s Certificate has been revoked.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-revoked-certificate-crl |
en-US
Certificate is revoked in issuer’s certificate revocation list.
|
en-US
Certificate is revoked in issuer’s certificate revocation list.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-revoked-certificate-ocsp |
en-US
Issuer’s OCSP responder reports certificate is revoked.
|
en-US
Issuer’s OCSP responder reports certificate is revoked.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-revoked-key |
en-US
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-unknown-cert |
en-US
The requested certificate could not be found.
|
en-US
The requested certificate could not be found.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-unknown-critical-extension |
en-US
Certificate contains unknown critical extension.
|
en-US
Certificate contains unknown critical extension.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-unknown-issuer |
en-US
Peer’s Certificate issuer is not recognized.
|
en-US
Peer’s Certificate issuer is not recognized.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-unknown-signer |
en-US
The signer’s certificate could not be found.
|
en-US
The signer’s certificate could not be found.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-untrusted-cert |
en-US
Peer’s certificate has been marked as not trusted by the user.
|
en-US
Peer’s certificate has been marked as not trusted by the user.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-untrusted-issuer |
en-US
Peer’s certificate issuer has been marked as not trusted by the user.
|
en-US
Peer’s certificate issuer has been marked as not trusted by the user.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-access-denied-alert |
en-US
Peer received a valid certificate, but access was denied.
|
en-US
Peer received a valid certificate, but access was denied.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-bad-cert-alert |
en-US
SSL peer cannot verify your certificate.
|
en-US
SSL peer cannot verify your certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-bad-cert-domain |
en-US
Unable to communicate securely with peer: requested domain name does not match the server’s certificate.
|
en-US
Unable to communicate securely with peer: requested domain name does not match the server’s certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-bad-cert-hash-value-alert |
en-US
SSL peer reported bad certificate hash value.
|
en-US
SSL peer reported bad certificate hash value.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-bad-cert-status-response-alert |
en-US
SSL peer was unable to get an OCSP response for its certificate.
|
en-US
SSL peer was unable to get an OCSP response for its certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-bad-certificate |
en-US
Unable to communicate securely with peer: peers’s certificate was rejected.
|
en-US
Unable to communicate securely with peer: peers’s certificate was rejected.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-cert-kea-mismatch |
en-US
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-certificate-unknown-alert |
en-US
SSL peer had some unspecified issue with the certificate it received.
|
en-US
SSL peer had some unspecified issue with the certificate it received.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-certificate-unobtainable-alert |
en-US
SSL peer could not obtain your certificate from the supplied URL.
|
en-US
SSL peer could not obtain your certificate from the supplied URL.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-expired-cert-alert |
en-US
SSL peer rejected your certificate as expired.
|
en-US
SSL peer rejected your certificate as expired.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-extract-public-key-failure |
en-US
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 |
en-US
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-trusted-ssl-client-ca |
en-US
No certificate authority is trusted for SSL client authentication.
|
en-US
No certificate authority is trusted for SSL client authentication.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-revoked-cert-alert |
en-US
SSL peer rejected your certificate as revoked.
|
en-US
SSL peer rejected your certificate as revoked.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-cert-request |
en-US
SSL received a malformed Certificate Request handshake message.
|
en-US
SSL received a malformed Certificate Request handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-cert-verify |
en-US
SSL received a malformed Certificate Verify handshake message.
|
en-US
SSL received a malformed Certificate Verify handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-malformed-certificate |
en-US
SSL received a malformed Certificate handshake message.
|
en-US
SSL received a malformed Certificate handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-cert-request |
en-US
SSL received an unexpected Certificate Request handshake message.
|
en-US
SSL received an unexpected Certificate Request handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-cert-status |
en-US
SSL received an unexpected Certificate Status handshake message.
|
en-US
SSL received an unexpected Certificate Status handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-cert-verify |
en-US
SSL received an unexpected Certificate Verify handshake message.
|
en-US
SSL received an unexpected Certificate Verify handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-rx-unexpected-certificate |
en-US
SSL received an unexpected Certificate handshake message.
|
en-US
SSL received an unexpected Certificate handshake message.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-sign-hashes-failure |
en-US
Unable to digitally sign data required to verify your certificate.
|
en-US
Unable to digitally sign data required to verify your certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-unknown-ca-alert |
en-US
Peer does not recognize and trust the CA that issued your certificate.
|
en-US
Peer does not recognize and trust the CA that issued your certificate.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-unrecognized-name-alert |
en-US
SSL peer has no certificate for the requested DNS name.
|
en-US
SSL peer has no certificate for the requested DNS name.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-unsupported-certificate-type |
en-US
Unsupported certificate type.
|
en-US
Unsupported certificate type.
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl ssl-error-weak-server-cert-key |
en-US
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-wrong-certificate |
en-US
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 • nsserrors.ftl xp-java-cert-not-exists-error |
en-US
This principal doesn’t have a certificate
|
en-US
This principal doesn’t have a certificate
|
|
Entity
#
all locales
browser • browser • pageInfo.ftl security-view.label |
en-US
View Certificate
|
en-US
View Certificate
|
|
Entity
#
all locales
browser • browser • preferences • preferences.ftl certs-personal-label |
en-US
When a server requests your personal certificate
|
en-US
When a server requests your personal certificate
|
|
Entity
#
all locales
browser • chrome • browser • browser.properties certImminentDistrust.message |
en-US
The security certificate in use on this website will no longer be trusted in a future release. For more information, visit https://wiki.mozilla.org/CA/Upcoming_Distrust_Actions
|
en-US
The security certificate in use on this website will no longer be trusted in a future release. For more information, visit https://wiki.mozilla.org/CA/Upcoming_Distrust_Actions
|
|
Entity
#
all locales
browser • chrome • browser • browser.properties identity.ev.contentOwner2 |
en-US
Certificate issued to: %S
|
en-US
Certificate issued to: %S
|
|
Entity
#
all locales
browser • chrome • overrides • netError.dtd certerror.expiredCert.secondPara2 |
en-US
It’s likely the website’s certificate is expired, which prevents &brandShortName; from connecting securely. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.
|
en-US
It’s likely the website’s certificate is expired, which prevents &brandShortName; from connecting securely. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.
|
|
Entity
#
all locales
browser • chrome • overrides • netError.dtd certerror.expiredCert.sts.secondPara |
en-US
It’s likely the website’s certificate is expired, which prevents &brandShortName; from connecting securely.
|
en-US
It’s likely the website’s certificate is expired, which prevents &brandShortName; from connecting securely.
|
|
Entity
#
all locales
browser • chrome • overrides • netError.dtd viewCertificate.label |
en-US
View Certificate
|
en-US
View Certificate
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.security.certificate |
en-US
Certificate:
|
en-US
Certificate:
|
|
Entity
#
all locales
dom • chrome • security • security.properties SHA1Sig |
en-US
This site makes use of a SHA-1 Certificate; it’s recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.
|
en-US
This site makes use of a SHA-1 Certificate; it’s recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.ssl-exception.help |
en-US
Opens the dialog to add an SSL certificate exception for <hostname>. If <connect> is true then a connection to <hostname> will be initiated after the exception is added.
|
en-US
Opens the dialog to add an SSL certificate exception for <hostname>. If <connect> is true then a connection to <hostname> will be initiated after the exception is added.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties msg.invalid.cert |
en-US
"%S has an invalid security certificate. If you trust this server, [[add an exception][Opens the dialog to add a security certificate exception][%S]].
|
en-US
"%S has an invalid security certificate. If you trust this server, [[add an exception][Opens the dialog to add a security certificate exception][%S]].
|
|
Entity
#
all locales
mail • chrome • messenger-newsblog • newsblog.properties newsblog-badCertError |
en-US
%S uses an invalid security certificate.
|
en-US
%S uses an invalid security certificate.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgReadSMIMEOverlay.properties CantDecryptBody |
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>
|
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-smime • msgReadSecurityInfo.dtd encryptionCert.label |
en-US
View Encryption Certificate
|
en-US
View Encryption Certificate
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgReadSecurityInfo.dtd issuer.name |
en-US
Certificate issued by:
|
en-US
Certificate issued by:
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgReadSecurityInfo.dtd signatureCert.label |
en-US
View Signature Certificate
|
en-US
View Signature Certificate
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SICertWithoutAddress |
en-US
The certificate used to sign the message does not contain an email address. Please look at the details of the signature certificate to learn who signed the message.
|
en-US
The certificate used to sign the message does not contain an email address. Please look at the details of the signature certificate to learn who signed the message.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIExpired |
en-US
The certificate used to sign the message appears to have expired. Make sure your computer's clock is set correctly.
|
en-US
The certificate used to sign the message appears to have expired. Make sure your computer's clock is set correctly.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIExpiredCA |
en-US
The certificate used to sign the message was issued by a certificate authority whose own certificate has expired. Make sure your computer's clock is set correctly.
|
en-US
The certificate used to sign the message was issued by a certificate authority whose own certificate has expired. Make sure your computer's clock is set correctly.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIHeaderMismatch |
en-US
The email address listed in the signer's certificate is different from the email address that was used to send this message. Please look at the details of the signature certificate to learn who signed the message.
|
en-US
The email address listed in the signer's certificate is different from the email address that was used to send this message. Please look at the details of the signature certificate to learn who signed the message.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SINotYetValid |
en-US
The certificate used to sign the message appears not to be valid yet. Make sure your computer's clock is set correctly.
|
en-US
The certificate used to sign the message appears not to be valid yet. Make sure your computer's clock is set correctly.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SINotYetValidCA |
en-US
The certificate used to sign the message was issued by a certificate authority whose own certificate is not yet valid. Make sure your computer's clock is set correctly.
|
en-US
The certificate used to sign the message was issued by a certificate authority whose own certificate is not yet valid. Make sure your computer's clock is set correctly.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIRevoked |
en-US
The certificate used to sign the message has been revoked. You should not trust the validity of this message until you verify its contents with the sender.
|
en-US
The certificate used to sign the message has been revoked. You should not trust the validity of this message until you verify its contents with the sender.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIRevokedCA |
en-US
The certificate used to sign the message was issued by a certificate authority whose own certificate has been revoked. You should not trust the validity of this message until you verify its contents with the sender.
|
en-US
The certificate used to sign the message was issued by a certificate authority whose own certificate has been revoked. You should not trust the validity of this message until you verify its contents with the sender.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIUnknownCA |
en-US
The certificate used to sign the message was issued by an unknown certificate authority.
|
en-US
The certificate used to sign the message was issued by an unknown certificate authority.
|
|
Entity
#
all locales
mail • chrome • messenger-smime • msgSecurityInfo.properties SIUntrustedCA |
en-US
The certificate used to sign the message was issued by a certificate authority that you do not trust for issuing this kind of certificate.
|
en-US
The certificate used to sign the message was issued by a certificate authority that you do not trust for issuing this kind of certificate.
|
|
Entity
#
all locales
mail • chrome • messenger • accountCreation.dtd insecureSelfSigned.description |
en-US
The server uses a certificate that we can't trust, so we can't be sure that someone isn't intercepting the traffic between &brandShortName; and your server. &brandShortName; will let you get to your mail, but you should really get your email provider to configure the server with a trusted certificate.
|
en-US
The server uses a certificate that we can't trust, so we can't be sure that someone isn't intercepting the traffic between &brandShortName; and your server. &brandShortName; will let you get to your mail, but you should really get your email provider to configure the server with a trusted certificate.
|
|
Entity
#
all locales
mail • chrome • messenger • accountCreation.properties selfsigned_details |
en-US
Normally, a secure mail server will present a trusted certificate to prove that it is really the server it claims to be. The connection to the mail server will be encrypted but cannot be validated as being the correct server.
|
en-US
Normally, a secure mail server will present a trusted certificate to prove that it is really the server it claims to be. The connection to the mail server will be encrypted but cannot be validated as being the correct server.
|
|
Entity
#
all locales
mail • chrome • messenger • accountCreation.properties selfsigned_warning |
en-US
%1$S does not use a trusted certificate.
|
en-US
%1$S does not use a trusted certificate.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd certPicker.detailsLabel |
en-US
Details of selected certificate:
|
en-US
Details of selected certificate:
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd certPicker.info |
en-US
Certificate:
|
en-US
Certificate:
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd certPicker.title |
en-US
Select Certificate
|
en-US
Select Certificate
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd e2eeReqWarning.description |
en-US
If you require encryption, to send a message you must have the public key or certificate of every recipient.
|
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 encryptionCert2.message |
en-US
Personal certificate for encryption:
|
en-US
Personal certificate for encryption:
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.dtd signingCert2.message |
en-US
Personal certificate for digital signing:
|
en-US
Personal certificate for digital signing:
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties ErrorEncryptMail |
en-US
Unable to encrypt message. Please check that you have a valid email certificate for each recipient. Please check that the certificates specified in Mail & Newsgroups Account Settings for this mail account are valid and trusted for mail.
|
en-US
Unable to encrypt message. Please check that you have a valid email certificate for each recipient. Please check that the certificates specified in Mail & Newsgroups Account Settings for this mail account are valid and trusted for mail.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties MissingRecipientEncryptionCert |
en-US
You specified encryption for this message, but the application failed to find an encryption certificate for %S.
|
en-US
You specified encryption for this message, but the application failed to find an encryption certificate for %S.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties NoEncryptionCert |
en-US
Certificate Manager can't locate a valid certificate that other people can use to send you encrypted email messages.
|
en-US
Certificate Manager can't locate a valid certificate that other people can use to send you encrypted email messages.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties NoEncryptionCertForThisAddress |
en-US
Certificate Manager can't locate a valid certificate that other people can use to send you encrypted email messages to the address <%S>.
|
en-US
Certificate Manager can't locate a valid certificate that other people can use to send you encrypted email messages to the address <%S>.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties NoSenderEncryptionCert |
en-US
You specified encryption for this message, but the application either failed to find the encryption certificate specified in your Mail & Newsgroup Account Settings, or the certificate has expired.
|
en-US
You specified encryption for this message, but the application either failed to find the encryption certificate specified in your Mail & Newsgroup Account Settings, or the certificate has expired.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties NoSenderSigningCert |
en-US
You specified that this message should be digitally signed, but the application either failed to find the signing certificate specified in your Mail & Newsgroup Account Settings, or the certificate has expired.
|
en-US
You specified that this message should be digitally signed, but the application either failed to find the signing certificate specified in your Mail & Newsgroup Account Settings, or the certificate has expired.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties NoSigningCert |
en-US
Certificate Manager can't locate a valid certificate that can be used to digitally sign your messages.
|
en-US
Certificate Manager can't locate a valid certificate that can be used to digitally sign your messages.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties NoSigningCertForThisAddress |
en-US
Certificate Manager can't locate a valid certificate that can be used to digitally sign your messages with an address of <%S>.
|
en-US
Certificate Manager can't locate a valid certificate that can be used to digitally sign your messages with an address of <%S>.
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties encryption_needCertWantSame |
en-US
You should also specify a certificate for other people to use when they send you encrypted messages. Do you want to use the same certificate to encrypt & decrypt messages sent to you?
|
en-US
You should also specify a certificate for other people to use when they send you encrypted messages. Do you want to use the same certificate to encrypt & decrypt messages sent to you?
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties encryption_needCertWantToSelect |
en-US
You should also specify a certificate for other people to use when they send you encrypted messages. Do you want to configure an encryption certificate now?
|
en-US
You should also specify a certificate for other people to use when they send you encrypted messages. Do you want to configure an encryption certificate now?
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties encryption_wantSame |
en-US
Do you want to use the same certificate to encrypt & decrypt messages sent to you?
|
en-US
Do you want to use the same certificate to encrypt & decrypt messages sent to you?
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties signing_needCertWantSame |
en-US
You should also specify a certificate to use for digitally signing your messages. Do you want to use the same certificate to digitally sign your messages?
|
en-US
You should also specify a certificate to use for digitally signing your messages. Do you want to use the same certificate to digitally sign your messages?
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties signing_needCertWantToSelect |
en-US
You should also specify a certificate to use for digitally signing your messages. Do you want to configure a certificate for digitally signing messages now?
|
en-US
You should also specify a certificate to use for digitally signing your messages. Do you want to configure a certificate for digitally signing messages now?
|
|
Entity
#
all locales
mail • chrome • messenger • am-smime.properties signing_wantSame |
en-US
Do you want to use the same certificate to digitally sign your messages?
|
en-US
Do you want to use the same certificate to digitally sign your messages?
|
|
Entity
#
all locales
mail • chrome • messenger • imapMsgs.properties imapTlsError |
en-US
Non-overridabe TLS error occurred. Handshake error or probably the TLS version or certificate used by server %S is incompatible.
|
en-US
Non-overridabe TLS error occurred. Handshake error or probably the TLS version or certificate used by server %S is incompatible.
|
|
Entity
#
all locales
mail • chrome • messenger • messenger.properties authExternal |
en-US
TLS Certificate
|
en-US
TLS Certificate
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl e2e-intro-description-more |
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.
|
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 keyserver-error-certificate-error |
en-US
The keyserver’s certificate is not valid.
|
en-US
The keyserver’s certificate is not valid.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl openpgp-key-man-ctx-gen-revoke-label.label |
en-US
Generate & Save Revocation Certificate
|
en-US
Generate & Save Revocation Certificate
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl openpgp-key-man-gen-revoke.label |
en-US
Revocation Certificate
|
en-US
Revocation Certificate
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl revoke-cert-failed |
en-US
The revocation certificate could not be created.
|
en-US
The revocation certificate could not be created.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl revoke-cert-ok |
en-US
The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
|
en-US
The revocation certificate has been successfully created. You can use it to invalidate your public key, e.g. in case you would lose your secret key.
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl revoke-key-not-present |
en-US
You have no key (0x{ $keyId }) which matches this revocation certificate!
If you have lost your key, you must import it (e.g. from a keyserver) before importing the revocation certificate!
|
en-US
You have no key (0x{ $keyId }) which matches this revocation certificate!
If you have lost your key, you must import it (e.g. from a keyserver) before importing the revocation certificate!
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl save-revoke-cert-as |
en-US
Create & Save Revocation Certificate
|
en-US
Create & Save Revocation Certificate
|
|
Entity
#
all locales
mail • messenger • preferences • preferences.ftl certificate-description |
en-US
When a server requests my personal certificate:
|
en-US
When a server requests my personal certificate:
|
|
Entity
#
all locales
mobile • android • chrome • browser.properties remoteIncomingPromptTCP |
en-US
Allow remote debugging connection from %1$S:%2$S? This connection requires a QR code to be scanned in order to authenticate the remote device's certificate. You can avoid future scans by remembering the device.
|
en-US
Allow remote debugging connection from %1$S:%2$S? This connection requires a QR code to be scanned in order to authenticate the remote device's certificate. You can avoid future scans by remembering the device.
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties certmgr.title |
en-US
Certificate Details
|
en-US
Certificate Details
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties clientAuthAsk.message1 |
en-US
This site has requested that you identify yourself with a certificate:
|
en-US
This site has requested that you identify yourself with a certificate:
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties clientAuthAsk.message2 |
en-US
Choose a certificate to present as identification:
|
en-US
Choose a certificate to present as identification:
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties clientAuthAsk.message3 |
en-US
Details of selected certificate:
|
en-US
Details of selected certificate:
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties downloadCert.message1 |
en-US
You have been asked to trust a new Certificate Authority (CA).
|
en-US
You have been asked to trust a new Certificate Authority (CA).
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties downloadCert.title |
en-US
Downloading Certificate
|
en-US
Downloading Certificate
|
|
Entity
#
all locales
mobile • android • chrome • pippki.properties pkcs12.getpassword.message |
en-US
Please enter the password that was used to encrypt this certificate backup.
|
en-US
Please enter the password that was used to encrypt this certificate backup.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_ADDITIONAL_POLICY_CONSTRAINT_FAILED |
en-US
An additional policy constraint failed when validating this certificate.
|
en-US
An additional policy constraint failed when validating this certificate.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_CA_CERT_USED_AS_END_ENTITY |
en-US
The server uses a certificate with a basic constraints extension identifying it as a certificate authority. For a properly-issued certificate, this should not be the case.
|
en-US
The server uses a certificate with a basic constraints extension identifying it as a certificate authority. For a properly-issued certificate, this should not be the case.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_EMPTY_ISSUER_NAME |
en-US
The server presented a certificate with an empty issuer distinguished name.
|
en-US
The server presented a certificate with an empty issuer distinguished name.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_INADEQUATE_KEY_SIZE |
en-US
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_INVALID_INTEGER_ENCODING |
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
|
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_KEY_PINNING_FAILURE |
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.
|
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 MOZILLA_PKIX_ERROR_NOT_YET_VALID_CERTIFICATE |
en-US
The server presented a certificate that is not yet valid.
|
en-US
The server presented a certificate that is not yet valid.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_NOT_YET_VALID_ISSUER_CERTIFICATE |
en-US
A certificate that is not yet valid was used to issue the server’s certificate.
|
en-US
A certificate that is not yet valid was used to issue the server’s certificate.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING |
en-US
The OCSP response does not include a status for the certificate being verified.
|
en-US
The OCSP response does not include a status for the certificate being verified.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT |
en-US
The certificate is not trusted because it is self-signed.
|
en-US
The certificate is not trusted because it is self-signed.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_SIGNATURE_ALGORITHM_MISMATCH |
en-US
The signature algorithm in the signature field of the certificate does not match the algorithm in its signatureAlgorithm field.
|
en-US
The signature algorithm in the signature field of the certificate does not match the algorithm in its signatureAlgorithm field.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_V1_CERT_USED_AS_CA |
en-US
An X.509 version 1 certificate that is not a trust anchor was used to issue the server’s certificate. X.509 version 1 certificates are deprecated and should not be used to sign other certificates.
|
en-US
An X.509 version 1 certificate that is not a trust anchor was used to issue the server’s certificate. X.509 version 1 certificates are deprecated and should not be used to sign other certificates.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_VALIDITY_TOO_LONG |
en-US
The server presented a certificate that is valid for too long.
|
en-US
The server presented a certificate that is valid for too long.
|
APIThese results are also available as an API request to search in
en-US or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.