Repository navigation
[pgs.sh] Any domain may serve any project #132
Description
It seems that pgs.sh relies entirely on DNS records to figure out which project to serve for a custom domain. This means that, given a site hosted on pgs.sh, anyone can:
- Run
dig the.domain.comto confirm that aCNAMErecord indeed points topgs.sh, - Run
dig _pgs.the.domain.com TXTto obtain the username and project name for that site, - Create their own domain (such as
i-am-a-bad-person.com) with matching records to point at the target project (per pgs.sh docs), then - Misdirect users to their domain instead of the canonical one.
Is this permissiveness intentional?
If not, or if there is some utility in allow-listing specific domains for the project (I'm no expert, but it seems misleading domain names could be a concern), could such a mechanism be added? Perhaps a special .domains or _domains file, with a list of valid canonical domains separated by newlines, similar to Codeberg Pages?
Activity
neurosnap commentedon May 10, 2024
Hi!
Yes, the goal was to make custom domains as simple as possible -- no configuration required inside of pgs.sh.
We see this as no different than someone having a domain point to an IP address of a known website they do not own or manage.
Having said said that, we could design an allowlist of custom domains for pgs.sh.
AverageHelper commentedon May 10, 2024
Fair enough! A simple config is super great tbh, and a valid default. An optional allowlist would be nice for the paranoid among us, tho that's not a dealbreaker for me using the platform.
neurosnap commentedon May 10, 2024
Great, I'll add it to our shortlist.