ZeroLog
Private preview
EN DE

Security

10 November: secrets stay out of key service logs, and ZeroLog Link reconnects

Several releases close gaps in how the key service removes secrets from its own log lines and checks requests on their way to a provider. ZeroLog Link reconnects again after a failed first attempt.

User impact: Targeted change

People who use the vault, database connections through it, or the ZeroLog Link tool. Secrets are removed from key service log lines more reliably, and Link reconnects after a failed first attempt. A request body with a very large whole number is now refused instead of being sent on with a changed number. Download the Link tool again on your own computer; nothing else is needed.

Secrets in log lines. The key service removes known secret formats from its log lines before it writes them. For eight formats, among them tokens of common code hosting and chat services, this step wrote the whole line back, secret included. It now removes the match. Vault values that contain emoji were never found in plain form; they are now. The log stays inside the key service.

Database connections through the vault. A malformed error message from a PostgreSQL server could make the key service stop answering for everyone. Such a message is now rejected.

Encrypted values. The key service accepts an encrypted value only with a full-length authentication tag. ZeroLog has always written full-length tags, so stored values are read as before.

Requests to providers. The path that is checked against your rules is now exactly the path that is sent. A request body with a whole number too large to pass through unchanged used to reach the provider with a different number. It is now refused with status 400.

Containers on worker nodes. The filter in front of the container engine checks where a container may mount files from. If the storage it needs for that check was missing entirely, it fell back to a weaker check. It now refuses the request.

ZeroLog Link. If the Link command-line tool started before the service was reachable, it could stay disconnected until it was restarted, depending on the installed Node.js version. It now retries. On your own computer, download the tool again to get the fix.

Groundwork. Several internal helper programs now also exist as compiled versions, each compared against the current one by tests. None of them is switched on, so nothing changes for you.

Back to Newsroom