hanneary commented 4 months ago

Public Suffix List (PSL) Pull Request (PR)

Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.

Checklist of required steps

[x] Description of Organization
[x] Robust Reason for PSL Inclusion
[x] DNS verification via dig
[x] Run Syntax Checker (make test)
[x] 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) in the affected section

Submitter affirms the following:

[x] 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)

[x] This request was not submitted with the objective of working around other third-party limits

[x] The Guidelines were carefully read and understood, and this request conforms
[x] The submission follows the guidelines on formatting and sorting

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)

[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

Evervault is data privacy and security company. We provide various tools and infrastructure designed to help developers and companies process sensitive data securely. For example, Relay is an encryption proxy that typically sits between a browser and a user's infrastructure. Evervault hosts the proxy which encrypts/decrypts data and the user hosts the code on the other end.

This is being submitted on behalf of Evervault. I am Hannah Neary, an engineer at the company.

Organization Website: https://evervault.com/

Reason for PSL Inclusion

Number of users this request is being made to serve: ~3000 estimated users

We proxy traffic to users own hosted apps at [app-id].relay.evervault.app
We want to restrict these apps' use of cookies to their own personal subdomain

DNS Verification via dig

Results of Syntax Checker (`make test`)

yahesh commented 4 months ago

Looking at the sorting of the block this seems to be okay. The block for Evervault was added after Evennode. However, after the new block for Evervault there is a pre-existing block for eDirect Corp. which is located in the wrong place.

hanneary commented 4 months ago

Looking at the sorting of the block this seems to be okay. The block for Evervault was added after Evennode. However, after the new block for Evervault there is a pre-existing block for eDirect Corp. which is located in the wrong place.

I just moved eDirect corp to the right spot

simon-friedberger commented 3 months ago

[x] Expiration (Note: Must STAY >2y at all times)
- [x] evervault.app expires 2027-12-07
- [x] evervault.dev expires 2027-11-20
[x] DNS _psl entries (Note: Must STAY in place)
[x] Tests pass
[x] Sorting
[x] Reasoning/Organization description

simon-friedberger commented 3 months ago

I think you don't want those wildcards.

simon-friedberger commented 3 months ago

@hanneary Any updates?

hanneary commented 2 months ago

@hanneary Any updates?

Hi @simon-friedberger apologies for that I missed that notification. I think you're right about the wildcard, I'm going to update now

simon-friedberger commented 2 months ago

@hanneary Please rebase to fix the conflicts.

hanneary commented 2 months ago

@hanneary Please rebase to fix the conflicts.

Done!