Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow 0e.vc to be isolated for all subdomains by adding wildcard #2299

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

mozfreddyb
Copy link
Contributor

@mozfreddyb mozfreddyb commented Nov 30, 2024

Public Suffix List (PSL) Submission

Checklist of required steps

  • Description of Organization

  • Robust Reason for PSL Inclusion

  • DNS verification via dig

  • Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _psl TXT record in place in the respective zone(s).

  • We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)

  • No third-party limits are being worked around. This is purely to isolate all hosts under 0e.vc from each other.
  • This request was not submitted with the objective of working around other third-party limits.

  • The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, and responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.

  • The Guidelines were carefully read and understood, and this request conforms to them.

  • The submission follows the guidelines on formatting and sorting.

Abuse Contact:

  • Abuse contact information (email or web form) is available and easily accessible.

    URL where abuse contact or abuse reporting form can be found:

  • E-mail address from the entry.


For PRIVATE section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.

To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.

PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.

(Link: about propagation/expectations)

  • Yes, I understand. I could break my organization's website cookies and cause other issues, and the rollback timing is acceptable. Proceed anyways.

Description of Organization

There is no organization behind this entry. I, a single individual, intend to host various services under my domain. They will be on various subdomains of 0e.vc. Due to the fact that these various services are off-the-shelf software with their own web interfaces, I can not rely on them to use Host-bound cookies or other means of isolation.

Organization Website:
N/A

Reason for PSL Inclusion

Cookie isolation. (see above)

Number of users this request is being made to serve:

DNS Verification

Should work now.

@mozfreddyb
Copy link
Contributor Author

The TXT record is currently pointing to #896. I am updating it to point here momentarily. I assume this may take a while.

@wdhdev
Copy link
Contributor

wdhdev commented Nov 30, 2024

Are you able to fill out the template?

@mozfreddyb
Copy link
Contributor Author

Oops, looks like I was missing some checkboxes. Thanks for the call out.

@wdhdev
Copy link
Contributor

wdhdev commented Dec 2, 2024

I meant the org desc, PSL inclusion stuff.

@simon-friedberger simon-friedberger merged commit d953b2f into publicsuffix:main Dec 4, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants