Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

[[ 🗃 ^yEzqv rel4tion-wiki ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Tags

master :: maint / admin / ca / tinyca /

Creating_a_Certificate.mdwn

Now it’s time to create a certificate for a web service you run. The examples below assume it’s a website certificate, but it could be anything else: A certificate for a mail server or for a Jabber server etc. The process involves two steps: First, the service operator generates a request and sends it to the CA. Then, the CA signs the request, “approving” the service as trusted as long as it holds the private key of the new certificate.

In TinyCA, select the Requests tab. Right-click inside the window and select “New request”. A request creation dialog will open:

[[!img 4.1-create-request-empty.png class=“center”]]

Here’s an example:

[[!img 4.2-create-request-filled.png class=“center”]]

The new certificate will be listed in the Requests tab. As the CA, you are going to sign it. Right-click on the request and select “Sign request”.

[[!img 5.1-sign-request-menu.png class=“center”]]

You will need to choose between server and client request. In this case, select server (I guess the client option is for client certificates). You should now see a small dialog.

Example:

[[!img 5.2-sign-request-filled.png class=“center”]]

Click OK. The certificate will be signed and upon success you’ll see something like this:

[[!img 5.3-sign-request-done.png class=“center”]]

[See repo JSON]