regen master
This commit is contained in:
@@ -603,7 +603,7 @@ zone "eng.example.com" {
|
||||
"<strong class="userinput"><code>hmac-sha256</code></strong>",
|
||||
"<strong class="userinput"><code>hmac-sha384</code></strong>"
|
||||
and "<strong class="userinput"><code>hmac-sha512</code></strong>"
|
||||
have any meaning. The secret is a base-64 encoded string
|
||||
have any meaning. The secret is a Base64 encoded string
|
||||
as specified in RFC 3548.
|
||||
</p>
|
||||
|
||||
|
||||
@@ -1232,7 +1232,7 @@
|
||||
number of required bits preceded by a dash, e.g.
|
||||
<code class="literal">hmac-sha1-80</code>. The
|
||||
<em class="replaceable"><code>secret_string</code></em> is the secret
|
||||
to be used by the algorithm, and is treated as a base-64
|
||||
to be used by the algorithm, and is treated as a Base64
|
||||
encoded string.
|
||||
</p>
|
||||
|
||||
@@ -8891,7 +8891,7 @@ example.com CNAME rpz-tcp-only.
|
||||
<p>
|
||||
The <span class="command"><strong>trusted-keys</strong></span> statement can contain
|
||||
multiple key entries, each consisting of the key's
|
||||
domain name, flags, protocol, algorithm, and the Base-64
|
||||
domain name, flags, protocol, algorithm, and the Base64
|
||||
representation of the key data.
|
||||
Spaces, tabs, newlines and carriage returns are ignored
|
||||
in the key data, so the configuration may be split up into
|
||||
|
||||
Reference in New Issue
Block a user