-
Notifications
You must be signed in to change notification settings - Fork 1
Securite EN
🇬🇧 English (this page) · 🇫🇷 Français
Chaturbate Recorder ships with several defensive checks, enabled by default, before it executes anything external (third-party binaries, downloads) or writes to disk.
Before every recording launch, yt-dlp.exe and ffmpeg.exe are checked
by SHA256 hash. Two values are accepted: the one hard-coded in the
app (the version tested by the maintainer at release time) or one you've
explicitly approved yourself (trust-on-first-use — see
Installation). Either way, no binary ever runs
silently without matching one of these two known values: verification
either passes automatically, or you're explicitly asked to confirm
before anything runs.
Optional Authenticode verification (digital signature) and CA
certificate pinning also exist in the code
(AppConfig.YtDlpRequireAuthenticode, EnableCaPinning...), disabled
by default because public yt-dlp builds aren't always signed.
Every folder path provided by the user (save folder, cookies file, log
paths) is validated before use: invalid paths, directory-traversal
attempts, etc. are rejected. See Security/PathValidator.cs in the repo
for the exact rules.
The live URL to record is validated against an allow list
(chaturbate.com) and a deny list before being passed to yt-dlp — a
rejected URL shows an error message instead of being passed as-is to an
external process.
On startup, the app refuses to continue if it's running from a location deemed risky: a network share, a temporary/ephemeral folder, or a compressed NTFS folder. An explicit message asks you to move the executable to a standard local folder.
The app checks (non-blocking — a warning only) whether sensitive folders (execution, capture, or log folder) have unusually broad NTFS permissions (e.g. "Authenticated Users" with Modify rights), and logs a warning if so.
- Optional SOCKS5/HTTP proxy (see Configuration) to hide the real IP from the remote site. The app doesn't provide a proxy itself.
-
Browser cookies (
cookies.txtfile) to access content restricted to logged-in accounts — no password is ever requested, entered, or stored by the app. - Optional TLS pinning of the remote server's certificate
(
AppConfig.EnableTlsServerPinning), disabled by default.
Even the QR code shown in the "Support the project" panel is hash-checked before being loaded, to detect a possible substitution of the file on disk.
This list describes the app's own technical protections. It guarantees nothing about the content of recorded lives, the legality of recording under your jurisdiction, or Chaturbate's terms of service — it's up to you to make sure of that.