RFC 5280, draft-nourse-scep-22
Certificate manager is used to collect all certificates inside router, to manage and create self-signed certificates and to control and set SCEP related configuration.
Starting from v6rc10, CRL will be automatically renewed every hour for certificates which have "trusted=yes" using http protocol (ldap and ftp is currently unsupported). Segmented CRL is also currently unsupported.
RouterOS allows to manage and create self-signed CAs. Implementation was made based on RFC 5280 and all certificates are X.509 v3.
All certificate fingerprints are SHA1. Starting from v6.18 sha256 is used for certificate fingerprints and hashes. All private keys and CA export passphrase are stored encrypted with hardware ID. CA CRL renewal happens at every certificate revocation and after 24hours.
General menu is used to manage certificates, add templates, issue certificates and manage SCEP Clients.
|common-name (string; Default: )|
|copy-from (string; Default: )|
|country (string; Default: )|
|days-valid (integer [0..4294967295]; Default: )|
|key-size (1024 | 1536 | 2048 | 4096 | 8192; Default: )|
|key-usage (list of [digital-signature | content-commitment | key-encipherment | data-encipherment | key-agreement | key-cert-sign | crl-sign | encipher-only | decipher-only]; Default: )||Detailed key usage descriptions can be found in RFC 5280|
|locality (string; Default: )|
|name (string; Default: )||Name of the certificate. Name can be edited.|
|organization (string; Default: )|
|state (string; Default: )|
|subject-alt-name (string; Default: )||contact email address|
|trusted (yes | no; Default: )||If set to yes certificate is included "in trusted certificate chain"|
|unit (string; Default: )|
|dsa (yes | no)|
|expired (yes | no)||Set to true if certificate is expired|
|invalid-after (date)||The date after which certificate wil be invalid.|
|invalid-before (date)||The date before which certificate is invalid.|
|private-key (yes | no)|
|status ()||Shows current status of scep client|
|add ()||Adds new certificate template.|
|add-scep (ca-identity name on-smart-card scep-url template)||Add scep client. Command takes four parameters:
|create-certificate-request ()||Create certificate request from specified template.|
|export ()||Export certificate to file. When export-passphrase is specified, certificate will be exported with encrypted key.|
|import (file-name)||File name of certificate or key to be imported.|
|issued-revoke ()||Revoke issued certificate|
|sign-certificate-request (ca, days-valid, file-name, key-bits)||Generates certificate and key, except that standard parameters are taken from certificate request. Command takes four parameters:
|sign (ca, ca-crl-host, ca-on-smart-card, name, template)||Sign certificates. Command takes 5 parameters:
Simple Certificate Enrollment protocol (SCEP) was developed based on draft-nourse-scep-22.
The protocol is designed so that any user can request certificate as simple as possible. The protocol allows to issue and revoke certificates.
How SCEP works
Topology: CL ---- RA ---- CA
- CL - client
- RA - registration authority (proxy)
- CA - certification authority (server)
SCEP is using HTTP protocol and base64 encoded GET requests. Most of requests are without authentication and cipher, however important ones can be protected if necessary (ciphered or signed using received public key).
SCEP client in RouterOS will:
- get CA certificate from CA server or RA (if used);
- user should compare fingerprint of the CA certificate or if it comes from the right server;
- generate self-signed certificate with temporary key;
- sends certificate request to the server;
- if server respond with status x, then client keeps requesting until server sends an error or approval.
SCEP server supports issue of one certificate only. RouterOS supports also renew and next-ca options:
- renew - possibility to renew old certificate automatically with the same CA.
- next-ca - possibility to change current CA certificate to the new one. Client polls the server for any changes, if server advertise that next-ca is available, then client may request next CA or wait until CA almost expires and then request next-ca.
RouterOS Server also supports POST' operation, 3DES cipher and SHA1 hashing. If client does not support these features then http GET, DES cipher and MD5 hashing is used.
RouterOS client by default will try to use POST, 3DES and SHA1 if server advertises that.
/certificate scep-server otp
/certificate scep-server ra
/certificate scep-server requests