Files
peardock-website/legal/security.html
T
2026-07-11 19:01:46 -04:00

103 lines
4.8 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
<title>Security Policy · PearDock Legal</title>
<meta name="description" content="Security vulnerability disclosure policy for PearDock by HoneyPeer, LLC." />
<meta name="theme-color" content="#2dd4bf" />
<link rel="icon" href="/assets/favicons/favicon.ico" sizes="any" />
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet" />
<link rel="stylesheet" href="/src/styles/global.css" />
<link rel="stylesheet" href="/src/styles/docs.css" />
<link rel="stylesheet" href="/src/styles/legal.css" />
</head>
<body>
<div class="bg-mesh" aria-hidden="true"></div>
<div data-nav data-prefix="../"></div>
<div class="docs-layout legal-layout">
<aside class="docs-sidebar" data-legal-nav></aside>
<button type="button" class="docs-sidebar-toggle" aria-label="Legal menu"></button>
<article class="docs-main legal-main">
<p class="legal-kicker">Legal</p>
<h1>Security Policy</h1>
<p class="docs-lead">
HoneyPeer, LLC takes the security of PearDock seriously.
This policy describes how to report vulnerabilities responsibly.
</p>
<p class="legal-updated">Last updated: <strong>July 11, 2026</strong></p>
<h2 id="scope">1. Scope</h2>
<p>In scope:</p>
<ul>
<li>PearDock server and client software as published by HoneyPeer;</li>
<li>Official installers and websites (peardock.boats, install.peardock.boats);</li>
<li>Cryptographic handling of peer identity and RPC transport where implemented by PearDock.</li>
</ul>
<p>Generally out of scope:</p>
<ul>
<li>Issues solely in third-party dependencies without a demonstrated impact on PearDock (report upstream when appropriate);</li>
<li>Social engineering of HoneyPeer staff;</li>
<li>Denial-of-service volume testing against production Sites without prior coordination;</li>
<li>Findings that require physical access or already-compromised admin credentials on the target host.</li>
</ul>
<h2 id="report">2. How to report</h2>
<p>
Email <a href="mailto:[email protected]">[email protected]</a> with:
</p>
<ul>
<li>description of the issue and potential impact;</li>
<li>steps to reproduce or proof-of-concept (non-destructive);</li>
<li>affected versions / commit / platform if known;</li>
<li>your contact details and any preferred credit name.</li>
</ul>
<p>Please use English if possible. Do not include sensitive personal data of third parties.</p>
<h2 id="safe">3. Safe harbor</h2>
<p>
If you make a good-faith effort to follow this policy, avoid privacy violations, service disruption, and data destruction,
and do not exploit the issue beyond what is necessary to demonstrate it, HoneyPeer will not pursue legal action against you
for that research under laws applicable to unauthorized access, to the extent we can bind ourselves.
This does not authorize attacks on third-party systems or users self-hosted instances without their permission.
</p>
<h2 id="process">4. Our process</h2>
<ul>
<li>We will acknowledge receipt when practicable;</li>
<li>We will investigate and may request more detail;</li>
<li>We aim to remediate or mitigate high-severity issues in a reasonable timeframe;</li>
<li>We may publicly credit reporters who wish to be credited after a fix is available.</li>
</ul>
<p>We do not guarantee a bug bounty payment unless a separate program is announced.</p>
<h2 id="operators">5. For operators</h2>
<p>
Production hardening guidance is available in the product docs:
<a href="/docs/security">Security &amp; threat model</a> and
<a href="/docs/operator">Operator guide</a>.
Keep PearDock and Docker updated; protect <code>SERVER_SEED</code> and peer allowlists.
</p>
<h2 id="contact">6. Contact</h2>
<p>
Contact: <a href="mailto:[email protected]">[email protected]</a><br />
HoneyPeer, LLC · DeKalb County, Georgia, USA
</p>
<div class="docs-pager">
<a href="/legal/disclaimer"><span>Previous</span><strong>← Disclaimer</strong></a>
<a class="next" href="/legal/"><span>Hub</span><strong>All legal docs →</strong></a>
</div>
</article>
</div>
<div data-footer data-prefix="../"></div>
<script type="module" src="/src/js/site.js"></script>
</body>
</html>