Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
jetconf
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
9
Issues
9
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
labs
jetconf
Commits
fbdcee59
Commit
fbdcee59
authored
Oct 19, 2018
by
Pavel Spirek
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added HOWTO for server certificate generation
parent
76511d5b
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
29 additions
and
0 deletions
+29
-0
utils/cert_gen/HOWTO_SERVER.txt
utils/cert_gen/HOWTO_SERVER.txt
+29
-0
No files found.
utils/cert_gen/HOWTO_SERVER.txt
0 → 100644
View file @
fbdcee59
Generating a server SSL certificate for testing purposes
--------------------------------------------------------------------------------
To generate a new server certificate for Jetconf, which will be in the correct
form and accepted even by the more pedantic web browsers like Chrome, just run
the provided gen_server_cert.sh script in the following way:
./gen_server_cert.sh <out_file_suffix> <domain/ip>
or:
./gen_server_cert.sh <out_file_suffix> <domain/ip> <server_key>
The first form will generate a new server private key, while the second one
lets you to pass the private key file as an argument.
I.e.
./gen_server_cert.sh example example.com
will create a certificate "server_example.crt" for example.com domain with new
private key.
The script will autodetect if the certificate is being issued for a domain
name or an IP address, and sets the appropriate SAN value.
If you want this certificate to be recognized as valid by your web browser,
the issuing CA's certificate needs to be imported to your browser.
WARNING: It is strongly recommended not to import the provided CA's
certificate (ca.pem) to your production browser, as it's private key is
publicly known. If you do so, someone could perform a MITM attack to
any connection with an SSL-protected website.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment