Fix TTL boundary in cache freshness check

[elhoim]

Finding 32 (Low) — bin/cli.py:656

Problem

The freshness test is 'now - cached_at > ttl_seconds', so an entry exactly at the TTL boundary is still served; --cache-ttl-seconds 0, the natural way to disable caching, still returns a hit within the same second.

Fix

Finding #32 (ttl-boundary, low severity): get_cached_response() in bin/cli.py used now - cached_at > ttl_seconds to decide whether a cache entry was still fresh, so an entry exactly at the TTL boundary was still served as a hit. Concretely, --cache-ttl-seconds 0 — the natural way to disable caching entirely — still returned a cached response when queried within the same second it was written. Fixed by changing the comparison to >=, so an entry is treated as expired the instant its age reaches the TTL, matching the documented "TTL seconds" semantics. Minimal one-character diff, no other behavior touched.

Verification

Reproduced against the unmodified code at 9b8c605, then re-checked after the change.

Before

python3 (via importlib) with cache={"entries": {}}; set_cached_response(cache, "k", {"data": 1}, now=100); get_cached_response(cache, "k", now=100, ttl_seconds=0) -> {'cached_at': 100, 'response': {'data': 1}} (a hit, even though ttl_seconds=0 should mean "never fresh")

After

Same setup after fix: get_cached_response(cache, "k", now=100, ttl_seconds=0) -> None. Also verified now=110, ttl_seconds=10 (exact boundary) -> None, while now=105, ttl_seconds=10 (still within window) -> hit as expected.

python bin/cli.py --help exits 0 and the module still imports cleanly. Verification was performed offline against the pure functions — no running misp-modules instance is required.

Branched from 9b8c605. This PR addresses only this finding; the other findings from the same review are in separate PRs, so they will need rebasing against each other as they merge.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DYX4TKA5inzByJ4qGWKjqh