Skip to content

Add schuldock.de for IServ GmbH/Stadt Hamburg #2492

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

Merged
merged 1 commit into from
May 27, 2025

Conversation

KimBrodowski
Copy link
Contributor

@KimBrodowski KimBrodowski commented May 27, 2025

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).

Note: See Reconsider exclusion of TLDs with limited registration terms · Issue #2486 · publicsuffix/list. DE domain registration terms cannot exceed 12 months and cannot be publicly queried. We commit to keep the domain alive.

Submitter affirms the following:

  • 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)
  • 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.
  • A role-based email address has been used and this inbox is actively monitored with a response time of no more than 30 days.

Abuse Contact: [email protected]


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

IServ GmbH is a German company providing IT solutions for the educational sector. Our main product is also called IServ. The IServ school platform is an all-in-one solution for the pedagogical side of a school's network. It provides basic functionality like e-mail, file sharing, instant messaging, calendars, a collaborative text editor etc., but also software deployment and an Active Directory domain controller as well as more education oriented features such as special examination modes for local computers and an exercise module in over 50 modules.

IServ is currently used by over 6,000 schools primarily in German-speaking regions and manages about 540,000 computers and 5,000,000 user accounts.

I'm the chief information security officer and an engineer at IServ GmbH. Previous requests for our organization have been submitted by me or my co-worker Mario Hoberg, a senior engineer at IServ GmbH.

The request is made on behalf of one of our customers, Stadt Hamburg, the 2nd largest city in Germany. We, IServ GmbH, maintain the infrastructure for this project.

We have decided to keep the record for this domain in our namespace, since the domain has been registered by us, zones are maintained by us, and we are responsible for any technical actions. Furthermore, we already have entries on the PSL for our company, so we are familiar with the processes and can maintain a closer eye over any technical requirements as they arise. Abuse contacts point to addresses provided by Stadt Hamburg, since they have organizational authority over assignments to schools. Since subdomains are not available to the general public, we do not expect any relevant abuse concerns.

Organization Website: https://iserv.de/

Reason for PSL Inclusion

We deploy IServ on-premise and cloud hosted under unique customer domains. For the city state Hamburg, one of our customers, IServ instances are deployed below schuldock.de.

Hostnames have the format s\d+.schuldock.de

Since individual schools have full control of their servers and DNS zones, we must isolate them from each other. This is why we would like the domain to be added to the PSL.

Unfortunately, it is not possible for us at this time to maintain 1 year of validity and provide 2 years of renaming validity for our de domains on the list. Our registry DENIC eG does not allow us to prolong de domains beyond the point they are already prolonged.. Our domains all automatically renew. We can affirm that we will keep this in place. Of course, we will keep _psl RRs in place, as we have with all previous submissions. Please also note that expiration dates are not public for de domains.

Number of users this request is being made to serve: 250,000

Previous requests:

DNS Verification

kab@luna:~$ dig _psl.schuldock.de TXT @8.8.8.8 +short
"https://github.com/publicsuffix/list/pull/2492"

@simon-friedberger
Copy link
Contributor

@KimBrodowski Since you seem to be the authors of the software, have you considered switching to host-only cookies?

@KimBrodowski
Copy link
Contributor Author

@KimBrodowski Since you seem to be the authors of the software, have you considered switching to host-only cookies?

Our own software isn't my primary concern. We don't set the domain value in cookies, which should make them bound to the current domain. We go even further and restrict our cookies to our own application path (/iserv ), as well as setting the secure and http only flags. The last two of course not being all that relevant for this discussion.

The problem is that you can host pretty much everything under our domains. This is due to individual customers having full control of their DNS zones and servers. This is something that does actually happen, not just mere thought experiment. The domains are public suffixes in the true sense of the word. It's quite convenient for customers to use our base systems for their own applications as well, since we take care of operating system updates, tls certificates etc.

We also make use of 3rd party software that doesn't always behave correctly. We of course hope to catch those cases before they are deployed to customers, but correct browser behavior makes this safer.

PSL entries also enforce correct ratelimit behavior for 3rd parties. Before you get the pitchfork going, I know that ratelimits are a bit of a red flag around here, please let me clarify that I specifically don't mean ratelimit increases. When those are needed, we apply for those directly with e.g. LetsEncrypt and we have done so successfully multiple times in the past. The problem is that these exemptions only give you an additional increased limit, but don't stop customers from locking other customers out by doing silly or malicious things. Since these kind of requests don't go through our infrastructure, our ability to counter or even monitor these is limited.

@KimBrodowski
Copy link
Contributor Author

KimBrodowski commented May 27, 2025

For the record: Shared domain usage is also not default for our deployments. The overwhelming majority of customers use one or multiple dedicated domains. We don't even charge for the primary domain (within reason).

Shared domain usage is most prevalent for cloud deployments, because during the SARS-CoV-2 pandemic, we offered services free of charge, for certain customers like Stadt Hamburg, who want subdomains as part of their deployments and of course for test and development installations. The later two actually have entries on the PSL as well, since guidelines limiting that were not present at the time these were applied for.

iserv.host, the subject of the previous PR, is something new for us. Before, we did not have a shared namespace for all customers. The software making use of that is also not live yet.

Copy link
Member

@dnsguru dnsguru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Repeat submitter of previously vetted items, has demonstrated zero problematic useage and only high-integrity entries.
.DE does not allow >1Y renewals;

APPROVED

@dnsguru dnsguru merged commit ae6d715 into publicsuffix:main May 27, 2025
2 of 3 checks passed
@KimBrodowski KimBrodowski deleted the iserv-gmbh-schuldock.de branch May 27, 2025 22:00
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