Certificatetest

1. Hardening the Security

The ZNC acts as proxy for the irc connection, so the ZNC will manage 2 kind of connections: - IRC client <-> ZNC - ZNC <-> IRC Server

To increase our security we want that both of them use SSL layer; otherwise the information will be securized only on the side with the SSL in use and totally undecure on the other side, and this means: garbage in - garbage out.

Before to proceed we have to be sure that the ZNC has been compiled with SSL support.

To do this (ask..)

1. 1. ZNC Config

As reported in the Configuration we have a couple of security options.

(Ask if split pem or keep it single)

Another important configuration is the keyxchange. The defaults are perfectly fine but if you are security paranoid and your clients support latest EC (elliptic curve) algos, you can push them yo accept only XXXX

1. 1. Certificate

Copy the certificate instructions

1. 1. IRC Client connection

As first connection we are going to manage the IRC Client <-> ZNC one. First step is the enabling of the SSL port directly on first configuration. Otherwise we can proceed enabling via WebAdmin panel or via command line.

1. 1. 1. Web Admin Page

Screenshot

1. 1. 1. Command line

Run this command (Check command)

Now we have to configure our clients to use the SSL on connection. The second optional step is to use the Cert

1. SSL Certificates

The SSL layer relays on the SSL Certificates, and on the asymmetric encryption.

Based on current security levels we have 2 options: - RSA - EC

It is not possible to talk about "the most secure" because all depends on the size of the key used. EC uses only keys of 256 bit, while RSA keys uses keys multiple of 2. Today the minimum recommended is 2048, but to achieve the same level of security of an EC 256bit, a RSA 8192bit is required. Considering the overhead in the connection due to the size of the key, the EC is suggested (if supported by your in use clients).

COPY THE CERT KEYS CREATION

We have 2 options for the SSL certifis