Repository navigation
secsipidx 2.0.0
Version 2.0.0 is a major update focused on safer certificate retrieval,
configurable caching, concurrent library use, and stronger error handling.
Highlights
- Added instance-based Go APIs with
SJWTOptions,SJWTVerifier, and
SJWTSigner, avoiding reliance on process-wide mutable configuration. - Added Redis certificate caching with configurable URL, key prefix, timeout,
and expiration. - Added filesystem cache filename modes: legacy
plainand privacy-friendly
sha256. - Added optional certificate URL metadata storage for file and Redis caches.
- Preserved legacy global library APIs, now protected for safe concurrent
goroutine use.
Security and Reliability
- Certificate downloads are limited to 1 MiB by default, configurable with
MaxURLContentBytesor-max-url-content-bytes. - Added optional rejection of private and local X5U addresses through
DenyPrivateX5Uor-deny-private-x5u. Private X5U access remains allowed
by default for compatibility. - HTTP server request bodies are limited and server read, write, header, and
idle timeouts are enforced. - Invalid CRLs now return errors instead of causing panics.
- Invalid numeric library option values are rejected.
- Verification now treats every nonzero result as a failure.
- File-read errors and CLI operation return codes are handled correctly.
- Added certificate time-only verification mode.
- Identity verification uses the
infoparameter by default.
Configuration and CLI
The following CLI options were added:
-cache-backend-cache-file-mode-cache-store-url-redis-url-redis-key-prefix-redis-timeout-deny-private-x5u-max-url-content-bytes
The same settings are available through the Go library and the legacy
C-compatible option interface. The C API also adds SecSIPIDOptGetN() for
reading numeric options.
Compatibility and Build
- The minimum Go version increased from 1.16 to 1.26.
- The shared-library major version increased to 2.
- Redis support adds
github.com/redis/go-redis/v9. - Release archives now include
secsipidx.1. - Existing filesystem caching remains compatible when
-cache-diris used
without explicitly selecting a backend.