cacert/goocsp
9
0
Fork 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity
OCSP responder written in Go
27 commits 1 branch 3 tags 171 KiB
Go 100%
Find a file
Jan Dittberner f6089bac79 Run service as separate user 
- create user cacert-goocsp in postinst script
- use CAP_NET_BIND_SERVICE in systemd unit to allow binding to
  priviledged ports
- change config file path to /etc/goocsp/config.yaml
2022-10-11 19:39:03 +02:00
cmd/cacertocsp Make loglevel configurable 2022-10-08 13:40:32 +02:00
debian Run service as separate user 2022-10-11 19:39:03 +02:00
docs Run service as separate user 2022-10-11 19:39:03 +02:00
pkg Fix concurrent map access 2022-10-11 17:55:16 +02:00
.gitignore Add goreleaser configuration 2022-03-21 18:46:24 +01:00
.golangci.yml Fix golangci-lint warnings 2022-03-29 18:26:13 +02:00
.goreleaser.yml Run service as separate user 2022-10-11 19:39:03 +02:00
changelog.md Run service as separate user 2022-10-11 19:39:03 +02:00
go.mod Change module name to code.cacert.org/cacert/goocsp 2022-07-26 19:02:03 +02:00
go.sum Add test, include extensions support 2022-03-28 21:16:14 +02:00
LICENSE.txt Add license and inline documentation 2022-03-06 16:51:09 +01:00
README.md Add license and inline documentation 2022-03-06 16:51:09 +01:00

README.md

OCSP responder for CAcert

This project aims to provide an OCSP responder implementation for CAcert.

License

The project is licensed under the terms of the Apache License Version 2.0. See LICENSE.txt for details.

Requirements

  • the sources for OCSP answers should be files in openssl ca's index.txt format as documented in https://pki-tutorial.readthedocs.io/en/latest/cadb.html
  • certificates that are not listed in those files will be answered as unknown
  • the responder must support multiple CA certificates
  • the responder must support multiple OCSP signing certificates
  • responses must be signed
  • responses must contain the signing certificate

Configuration format

The responder is configured using a YAML configuration file config.yaml in the working directory.

Example:

---
issuers:
  - caCertificate: ca1/rootCA.pem
    responderCertificate: ca1/resp.crt.pem
    responderKey: ca1/resp.key.pem
    certificateList: ca1/index.txt
  - caCertificate: ca2/rootCA.pem
    responderCertificate: ca2/resp.crt.pem
    responderKey: ca2/resp.key.pem
    certificateList: ca2/index.txt

Supported configuration keys are:

  • issuer: a list of supported issuer CAs with the following sub keys:

    • caCertificate: the PEM encoded X.509 CA certificate
    • responderCertificate: the PEM encoded OCSP responder certificate
    • responderKey: the PEM encoded OCSP responder private key. The key must be in PKCS#8 or PKCS#1 format
    • certificateList: an openssl ca formatted index.txt containing the certificate status of issued certificates

All file names may either be given as absolute paths or paths relative to the working directory. The file specified in certificateList is watched for changes. The certificate database is automatically reloaded when a change is detected.

Command line parameters

The responder supports a command line parameter -serverAddr that allows the specification of the listening port and address. The default for -serverAddr is :8080.