Skip to content

v0.0.1-beta.3

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Sep 11:56
· 40 commits to main since this release

Everything a review of the shared Telegram client turned up, including two
ways the bot token could have escaped.

Security

  • Through tg v0.0.1-alpha.6: the bot token can no longer reach a log line
    through an error body echoed by something in front of the Bot API server, nor
    through the file path wrapped inside a local-file error. A symlink in the
    server's media directory can no longer read a file out of another bot's
    directory.

Fixed

  • Through the client: an ok=false answer carried on a 2xx is an API error
    again, so rate limits and edit-not-modified are classified rather than
    slipping through as untyped failures; a startup preflight waits through a
    Bot API server that is still booting instead of exiting on its first 502;
    and TELEGRAM_READY_WAIT now bounds the whole startup check rather than only
    the pauses inside it.

Container image

ghcr.io/freshlabdev/voicy@sha256:339358301cf50104323820bdb4eb1342773a0a381d7e1533fc277351f179c6f5