Skip to content

log flood from TLS session key rotation

For some reason kresd log is full of these:

[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374131, scheduling rotation check in 0 ms
[tls] session ticket: epoch 374132, scheduling rotation check in 4096000 ms

This is post-2.4.0 code c222c545 running in single process.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information