Skip to content

Commit

Permalink
Merge pull request #589 from freedomofpress/subdomain-clarification
Browse files Browse the repository at this point in the history
Clarify requirement prohibiting subdomains
  • Loading branch information
legoktm authored Sep 4, 2024
2 parents 4ed2583 + ed81068 commit e8c70d9
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions docs/admin/deployment/landing_page.rst
Original file line number Diff line number Diff line change
Expand Up @@ -140,10 +140,11 @@ let us know and we can remove your instance from the directory.
URL and Location
----------------

Ideally you would not use a separate subdomain, but would use a path at
your top-level domain, e.g. organization.com/securedrop. This is because
TLS does not encrypt the hostname, so a SecureDrop user whose connection
is being monitored would be trivially discovered.
Your *Landing Page* must be a path at your top-level domain, e.g.
organization.com/securedrop, rather than a subdomain (e.g.,
securedrop.organization.com). This is because DNS and TLS do not always encrypt the hostname,
so a SecureDrop user whose connection is being monitored would be trivially
discovered if you were to use a subdomain.

If the *Landing Page* is deployed on the same domain as another site, you
might consider having some specific configuration (such as the security
Expand Down

0 comments on commit e8c70d9

Please sign in to comment.