Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
caucase
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
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
Kirill Smelkov
caucase
Commits
4b80fc56
Commit
4b80fc56
authored
Sep 20, 2018
by
Łukasz Nowak
Committed by
Vincent Pelletier
Sep 21, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
README: Fix links
parent
c77d0042
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
README.rst
README.rst
+5
-5
No files found.
README.rst
View file @
4b80fc56
...
...
@@ -30,7 +30,7 @@ prolonged at a simple request of the key holder while the to-renew
certificate is still valid (not expired, not revoked).
Bootstrapping the system (creating the first service certificate for
_`caucased`
to operate on HTTPS, and creating the first user certificate to
`caucased`_
to operate on HTTPS, and creating the first user certificate to
control further certificate issuance) works by caucase automatically signing a
set number of certificates upon submission.
...
...
@@ -135,7 +135,7 @@ This command is intended to be used for isolated actions:
It is also able to submit certificate signing requests, retrieve signed
certificates, requesting certificate renewals and updating both
CA certificates and revocation lists, but you may be interested in using
_`caucase-updater`
for this instead.
`caucase-updater`_
for this instead.
caucase-updater
+++++++++++++++
...
...
@@ -160,7 +160,7 @@ caucase-rerequest
Utility allowing to re-issue a CSR using a locally-generated private key.
Intended to be used in conjunction with
_`caucase-updater`
when user cannot
Intended to be used in conjunction with
`caucase-updater`_
when user cannot
generate the CSR on the system where the certificate is desired (ex: automated
HTTPS server deployment), where user is not the intended audience for
caucase-produced certificate:
...
...
@@ -182,7 +182,7 @@ Utility displaying the identifier of given key, or the identifier of keys
involved in given backup file.
Allows identifying users which hold a private key candidate for restoring a
caucased backup (see
_`Restoration procedure`
).
caucased backup (see
`Restoration procedure`_
).
caucased
++++++++
...
...
@@ -193,7 +193,7 @@ This daemon provides access to both CAU and CAS services over both HTTP and
HTTPS.
It handles its own certificate issuance and renewal, so there is no need to use
_`caucase-updater`
for this service.
`caucase-updater`_
for this service.
Backups
-------
...
...
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