ZeroLog
Private preview
EN DE

Security

10 November: Google connection check, audit log numbering, video export input

Three hardening fixes: a signed check when connecting Google, no lost entries in the key service audit log, and stricter input for the video export.

User impact: Background

Background hardening: connecting Google needs a signed check, the key service audit log no longer loses entries during releases, and the video export accepts only valid input. Nothing changes in daily use, and no action is needed.

Google connection. When an account connects to Google, the return step now requires a random, signed value that is tied to the account and valid for 15 minutes. Which Google services get connected, and whether ZeroLog may write, now comes only from that value. Write access is stored only if Google granted every write permission that was requested. Before, the value was predictable and not checked on return; the same-origin check of the app still kept other websites from using that. The website does not call this step today.

Key service audit log. During a release without downtime, two instances of the key service briefly write to the same audit log. Under heavy load both could pick the same line number, and one entry was lost. The number is now assigned under a write lock.

Video export. The step that streams rendered video out of a container now accepts only a plain container ID and a whole-number size limit. A malformed value can no longer switch the size limit off.

No action is needed.

Back to Newsroom