- add a Contact section to the services page with the fingerprint, the key file and the keyserver link - say that account requests must be encrypted with GPG - show the GPG key and fingerprint in the people card - publish the public key at /squid.asc
43 lines
648 B
HTML
43 lines
648 B
HTML
<h1>{{nav_services}}</h1>
|
|
|
|
<p>
|
|
{{intro}}
|
|
</p>
|
|
|
|
<h2 id="account">{{account_h}}</h2>
|
|
|
|
<p>
|
|
{{account_p1}}
|
|
<strong>{{contact_shown}}</strong>
|
|
({{at_hint}}),
|
|
{{account_p2}}
|
|
{{account_gpg}} <a href="#contact">{{contact_h}}</a>.
|
|
</p>
|
|
|
|
<h2 id="contact">{{contact_h}}</h2>
|
|
|
|
<p>
|
|
{{contact_p1}}
|
|
</p>
|
|
|
|
<p>
|
|
{{contact_fingerprint}} <code>{{gpg_fingerprint}}</code>
|
|
</p>
|
|
|
|
<p>
|
|
<a href="{{gpg_key}}">{{contact_key}}</a>,
|
|
<a href="{{gpg_keyserver}}">{{contact_keyserver}}</a>.
|
|
</p>
|
|
|
|
{{service_sections}}<h2 id="donate">{{donate_h}}</h2>
|
|
|
|
<p>
|
|
{{donate_p}}
|
|
<a href="bitcoin:{{btc}}"><code>{{btc}}</code></a>
|
|
</p>
|
|
|
|
<h2 id="terms">{{terms_h}}</h2>
|
|
|
|
<p>
|
|
{{terms_p}}
|
|
</p>
|