mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2025-10-22 03:33:33 +00:00
Moved v3 code from NginxProxyManager/nginx-proxy-manager-3 to NginxProxyManager/nginx-proxy-manager
This commit is contained in:
26
frontend/src/locale/src/HelpDoc/en/CertificateAuthorities.md
Normal file
26
frontend/src/locale/src/HelpDoc/en/CertificateAuthorities.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# Certificate Authorities Help
|
||||
|
||||
## What is a Certificate Authority?
|
||||
|
||||
A **certificate authority (CA)**, also sometimes referred to as a
|
||||
**certification authority**, is a company or organization that acts to validate
|
||||
the identities of entities (such as websites, email addresses, companies, or
|
||||
individual persons) and bind them to cryptographic keys through the issuance of
|
||||
electronic documents known as digital certificates.
|
||||
|
||||
## Which CA should I use?
|
||||
|
||||
Not all CA's are created equal and you would be fine to use the default,
|
||||
ZeroSSL.
|
||||
|
||||
When using another CA it's worth considering the wildcard support and number of
|
||||
hosts-per-certificate that it supports.
|
||||
|
||||
## Can I use my own custom CA?
|
||||
|
||||
Yes, you can run your own CA software. You would only do this if you have a
|
||||
greater understanding of the SSL ecosystem.
|
||||
|
||||
When requesting SSL Certificates through your custom CA and while they will be
|
||||
successful, browsers will not automatically trust your CA and visiting hosts
|
||||
using certificates issued by that CA will show errors.
|
1
frontend/src/locale/src/HelpDoc/en/index.ts
Normal file
1
frontend/src/locale/src/HelpDoc/en/index.ts
Normal file
@@ -0,0 +1 @@
|
||||
export * as CertificateAuthorities from "./CertificateAuthorities.md";
|
Reference in New Issue
Block a user