Community rules and privacy
The short version
Be specific, be kind, and never paste anything you do not have permission to
share.
Rules
- Authorized systems only. Describe the lab or the system you own. Do not
ask for help attacking a third party, a public IP, or an employer without
written authorization.
- Sanitize before you paste. Replace usernames, hostnames, public IPs,
tokens, cookies, keys and customer names. Use RFC 5737 addresses
(192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24) and example.com.
- Show the check. A question with the exact command, the expected result
and the actual result gets a better answer than "it doesn't work."
- No exploit development, credential theft, or real-target intrusion.
Defensive analysis, verification and reporting are in scope.
- One question per discussion. Long multi-part threads are hard to mark
solved and hard to search.
- No spam, affiliate links, or AI-generated answers passed off as your own
verification. You may use AI; say where you used it and what you checked.
- Respect privacy. Do not repost another member's material outside the
forum without permission.
Privacy guidance for logs
- Keep the smallest excerpt that shows the event. Forty lines beat four thousand.
- Remove session tokens and authorization headers entirely; do not just mask
the first characters.
- If a screenshot contains a browser tab, a notification, a hostname or a path,
crop it or redact it before uploading.
- Attachments are member-only and downloadable through a permission-checked
route. Do not re-upload them elsewhere.
Moderation
A moderator may edit a post to remove sensitive data, move it to the right tag,
or close it with a reason. Repeated unsafe posts lose posting access. Appeals go
to the moderator in the same discussion, not in DMs.
Honest support expectation
Questions are reviewed in batches, with priority for unanswered questions that
include a sanitized input and a check. There is no guaranteed response time.
The queue is visible in Ask the Lab; if your question is urgent and
production-impacting, say so in the first line and use your own incident process
first.