kenzuya/unshackle
1
0
Fork 2
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-11-12 20:15:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deployed a7d6791 with MkDocs version: 1.6.1

Browse Source
This commit is contained in:
2026-09-12 21:14:05 +00:00
parent 82cbad5c3e
commit f5a17df145
8 changed files with 118 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
reference/configuration/vaults/index.html
+9
View File
@@ -2094,6 +2094,15 @@ name) and a <code>name</code>, plus backend-specific keys.</p>
stores it.</li>
</ul>
</div>
<div class="admonition note">
<p class="admonition-title">Bad content keys</p>
<p>A content key from a vault is proven by a short FFmpeg decode of the decrypted output.
A content key that fails the decode is written to the <code>bad_keys</code> table of every <code>SQLite</code>
vault with the name of the vault that supplied it, and every vault lookup skips a flagged
pair from then on. Only the <code>SQLite</code> backend stores flags. A <code>serve</code> instance with
<code>server_cdm</code> flags a pair the same way when a remote client reports it, so a server whose
<code>key_vaults</code> hold no <code>SQLite</code> entry cannot remember a bad content key.</p>
</div>
<h2 id="vault_timeout"><code>vault_timeout</code><a class="headerlink" href="#vault_timeout" title="Permanent link">&para;</a></h2>
<ul>
<li><strong>Type:</strong> <code>float</code> &nbsp;·&nbsp; <strong>Default:</strong> <code>10.0</code></li>