Document Connection Doctor access control and why a block list is observable Renames the Site definition limits area to Site and Tools Limits and documents the new Connection Doctor access option: what the three modes are, why the option exists (the Forbidden IP Ranges list can only ever be as complete as the operator made it, and the Connection Doctor is what turns an unlisted internal host into a readable one), and the explicit trade that restricting it moves the support burden onto the operator. Adds a standalone "A block list is always observable" section. Anyone who can add or edit a site can infer the deny list by submitting addresses and noting which are refused. This is not fixable — the acceptance or refusal is itself the answer, whatever the error message says — and it is not specific to Panopticon. The section makes the iptables comparison explicitly: you cannot enforce a boundary against somebody without that somebody being able to detect where the boundary is. The section is written to be linkable as a considered, public position, because this will be reported as a vulnerability with an inflated impact assessment sooner or later. It states what an adversary actually learns (which addresses the operator chose to list — a fact about configuration, not about what runs there), why that knowledge is only useful as reconnaissance for a read they can be denied, that the only complete fix is not offering self-service site creation at all, and that this use case is optional and off by default. It also states the two things which remain visible regardless — blind request initiation through background tasks, and the up/down signal from uptime monitoring — so the operator's risk assessment is made against the real picture rather than a flattering one. Also adds a Connection Troubleshooting entry and a note on the Connection Doctor page itself for users who find the tool missing. Signed-off-by: Nicholas K. Dionysopoulos <nicholas@akeeba.com>
Document the Forbidden IP Ranges site definition limit (GHSA-6234-p3mh-7j3x) Covers the new Site definition limits area on the Security tab of Global Configuration: what the option is for, the deployment it is aimed at, the four accepted range formats, cloud instance metadata addresses, and a warning against copying the suggested starting list blindly onto an installation which legitimately monitors its own LAN. Also cross-references it from the places a user actually hits the problem: the self-service user setup in Users and Groups, the connection troubleshooting pointer in Managing Sites, and a new CMS-agnostic entry in Connection Troubleshooting for the generic rejection message. Signed-off-by: Nicholas K. Dionysopoulos <nicholas@akeeba.com>
Document configurable Core File Integrity checksums source [akeeba/panopticon#981] Signed-off-by: Nicholas K. Dionysopoulos <nicholas@akeeba.com>
Document user self-registration, CAPTCHA providers, and registration mail templates Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update on how to fix your session save path
Document System Configuration