v1.9.0

What's Changed

This version contains support for the new static-ct logs. Since this new kind of CT log isn't supported by the certificate-transparency-go package (see this feature request), @mimi89999 created an implementation for this project. I couldn't test this as thoroughly as I wished, so I am releasing this feature as a pre-release. Please report any issues or change requests via the GitHub issue tracker.

Custom logs can be added via the config file like so:
https://github.com/d-Rickyy-b/certstream-server-go/blob/f17d7fd050e17339f92b3305477a1e3c3d29d8bf/config.sample.yaml#L35-L38

It also comes with new command line switches and config management through cobra and viper.

Warning

The config file that's being used for a docker deployment must now reside under /app/config/.

Known Issues

https://github.com/d-Rickyy-b/certstream-server-go/branches#issuecomment-3765475127

• The certLink (code reference) that is contained in the json for each entry will be an empty string for tiled log entries.

Full Changelog: v1.8.2...v1.9.0

v1.9.0-beta.4

What's Changed

This version contains support for the new static-ct logs. Since this new kind of CT log isn't supported by the certificate-transparency-go package (see this feature request), @mimi89999 created an implementation for this project. I couldn't test this as thoroughly as I wished, so I am releasing this feature as a pre-release. Please report any issues or change requests via the GitHub issue tracker.

Custom logs can be added via the config file like so:
https://github.com/d-Rickyy-b/certstream-server-go/blob/f17d7fd050e17339f92b3305477a1e3c3d29d8bf/config.sample.yaml#L35-L38

It also comes with new command line switches and config management through cobra and viper.

Warning

The config file that's being used for a docker deployment must now reside under /app/config/.

Known Bugs

https://github.com/d-Rickyy-b/certstream-server-go/branches#issuecomment-3765475127

• The certLink (code reference) that is contained in the json for each entry will be in the format of the old RFC 6962 format, which leads to 404 responses by the tiled logs, as that API is not supported. If you rely on that, you shouldn't use this version yet.
• There currently is no proper way to distinguish between certs published in RFC 6962 logs vs tiled logs. In future versions we might add a new "type" attribute that describes if we're dealing with a RFC 6962/tiled log.
• Log output is quite verbose as of now. Should be less verbose by beta.3
• Log entries are not validated and probably will not be in the future. This would cause a lot of computational and network overhead. The use case of certstream rather is monitoring for new domains.

Full Changelog: v1.8.2...v1.9.0-beta.4
Changes since last beta: v1.9.0-beta.3...v1.9.0-beta.4

v1.9.0-beta.3

What's Changed

This version contains support for the new static-ct logs. Since this new kind of CT log isn't supported by the certificate-transparency-go package (see this feature request), @mimi89999 created an implementation for this project. I couldn't test this as thoroughly as I wished, so I am releasing this feature as a pre-release. Please report any issues or change requests via the GitHub issue tracker.

Custom logs can be added via the config file like so:
https://github.com/d-Rickyy-b/certstream-server-go/blob/f17d7fd050e17339f92b3305477a1e3c3d29d8bf/config.sample.yaml#L35-L38

Known Bugs

https://github.com/d-Rickyy-b/certstream-server-go/branches#issuecomment-3765475127

• The certLink (code reference) that is contained in the json for each entry will be in the format of the old RFC 6962 format, which leads to 404 responses by the tiled logs, as that API is not supported. If you rely on that, you shouldn't use this version yet.
• There currently is no proper way to distinguish between certs published in RFC 6962 logs vs tiled logs. In future versions we might add a new "type" attribute that describes if we're dealing with a RFC 6962/tiled log.
• Log output is quite verbose as of now. Should be less verbose by beta.3
• Log entries are not validated and probably will not be in the future. This would cause a lot of computational and network overhead. The use case of certstream rather is monitoring for new domains.

Full Changelog: v1.8.2...v1.9.0-beta.3
Changes since last beta: v1.9.0-beta.2...v1.9.0-beta.3

v1.9.0-beta.2

What's Changed

This version contains support for the new static-ct logs. Since this new kind of CT log isn't supported by the certificate-transparency-go package (see this feature request), @mimi89999 created an implementation for this project. I couldn't test this as thoroughly as I wished, so I am releasing this feature as a pre-release. Please report any issues or change requests via the GitHub issue tracker.

Custom logs can be added via the config file like so:
https://github.com/d-Rickyy-b/certstream-server-go/blob/f17d7fd050e17339f92b3305477a1e3c3d29d8bf/config.sample.yaml#L35-L38

Known Bugs

https://github.com/d-Rickyy-b/certstream-server-go/branches#issuecomment-3765475127

• The certLink (code reference) that is contained in the json for each entry will be in the format of the old RFC 6962 format, which leads to 404 responses by the tiled logs, as that API is not supported. If you rely on that, you shouldn't use this version yet.
• There currently is no proper way to distinguish between certs published in RFC 6962 logs vs tiled logs. In future versions we might add a new "type" attribute that describes if we're dealing with a RFC 6962/tiled log.
• Log output is quite verbose as of now.
• Log entries are not validated and probably will not be in the future. This would cause a lot of computational and network overhead. The use case of certstream rather is monitoring for new domains.

Full Changelog: v1.8.2...v1.9.0-beta.2
Changes since last beta: v1.9.0-beta.1...v1.9.0-beta.2

v1.9.0-beta.1

What's Changed

• Ability to persist CT indexes and resume from the saved index file by @messede-degod in #49
• Skip retired CT logs by @mimi89999 in #77
• Use uint64 for cert index by @mimi89999 in #80
• Remove the Comodo Dodo log from sample config file by @mimi89999 in #78
• refactor: consolidate CT log reconciliation into single updateLogs method by @mimi89999 in #83

New Contributors

• @messede-degod made their first contribution in #49

Full Changelog: v1.8.2...v1.9.0-beta.1

v1.8.2

Added missing fields certificatePolicies and ctlPoisonByte (#85)

Full Changelog: v1.8.1...v1.8.2

v1.8.1

Fixed

• No longer reject URLs with trailing slashes defined in the additional_logs config (#62)
• When using drop_old_logs in the config, the server won't remove logs defined in additional_logs anymore (#64)

Full Changelog: v1.8.0...v1.8.1

v1.8.0

Security

• Close several CVEs in x/crypto and x/net dependencies (#59)

Added

• New CLI tool for fetching certificates from a CT log (#47)
• Ability to add custom CT logs to the config (#56)
• Remove old CT logs as soon as they are removed from the Google CT Loglist (#60)
• New configuration for buffer sizes (#58)

Fixed

• Properly handle IPv6 addresses in config (#61)

Full Changelog: v1.7.0...v1.8.0

v1.7.1

[1.7.1] - 2025-05-03

Fixed

• Properly handle IPv6 addresses in config (#61)

v1.7.0

What's Changed

• Start new ct-watchers as new ct logs become available in #42
• Add support for server heartbeats by @alberts-s in #39
• Add support for Websocket compression by @alberts-s in #40
• Ensure that Dockerfile_multistage builds and is runnable by @alberts-s in #38

New Contributors

• @alberts-s made their first contribution in #38

Full Changelog: v1.6.0...v1.7.0