Hi folks,
Looking for opinions and/or other alternatives on how to migrate the questions mailing list.
The problem with this one is, the address is incorporated in several documents, including our Bylaws and TLS BRs which cannot be changed without multiple ballots. There are a few different options for us to take:
Personally I’m a fan of the second option, but perhaps there are people here with alternative ideas, or that are completely against the second option.
Thoughts, please.
Regards,
Martijn
Hi Paul,
> This does not change the from header, which might be done by Google Groups.
That exactly is the issue. We currently have 2 outbound SMTP hosts for our postfix setup, it’s SES and it’s GMAIL. SES won’t accept redirect unless the original-From has been whitelisted, i.e., that won’t work. Gmail rewrites the message headers to the message is shown coming from our own gmail address, thus causing the problems listed in the “Downside” bit.
Regards,
Martijn
From: 'Paul van Brouwershaven' via Infrastructure (CA/B Forum) <infrast...@groups.cabforum.org>
Date: Wednesday, 16 October 2024 at 13:11
To: infrast...@groups.cabforum.org <infrast...@groups.cabforum.org>
Subject: [Infrastructure] Re: Migration of Questions mailing list
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
To view this discussion on the web visit https://groups.google.com/a/groups.cabforum.org/d/msgid/infrastructure/DS0PR11MB7958EF20775CAE89FD580EDAF8462%40DS0PR11MB7958.namprd11.prod.outlook.com.
That still doesn’t tackle the google part of it. They won’t accept it as such, and will rewrite
To view this discussion on the web visit https://groups.google.com/a/groups.cabforum.org/d/msgid/infrastructure/DS0PR11MB79585C58E43CA8939C2A0963F8462%40DS0PR11MB7958.namprd11.prod.outlook.com.
Hi Martjin,
I don't understand the point " this could allow a CA to circumvent a requirement", can you elaborate?
Thx
Roman
From: 'Martijn Katerbarg' via Infrastructure (CA/B Forum) <infrast...@groups.cabforum.org>
Sent: Dienstag, 15. Oktober 2024 16:50
To: infrast...@groups.cabforum.org
--
Hi Roman,
The TLS BRs have as requirement:
The CA MUST also (prior to issuing a certificate under the modified requirement) notify the CA/Browser Forum of the relevant information newly added to its CPS by sending a message to ques...@cabforum.org and receiving confirmation that it has been posted to the Public Mailing List and is indexed in the Public Mail Archives available at https://cabforum.org/pipermail/public/ (or such other email addresses and links as the Forum may designate), so that the CA/Browser Forum may consider possible revisions to these Requirements accordingly.
If the email address isn’t in use, doing that won’t help much and would technically allow a CA to bypass it. However, it’s a requirement that I don’t think has been used in a long time, hence why I think option 2 is the best option. Yet I want to give people to opportunity to not go down that route if they believe we shouldn’t.
Regards,
Martijn
From: Roman Fischer <roman....@swisssign.com>
Date: Wednesday, 16 October 2024 at 14:48
To: infrast...@groups.cabforum.org <infrast...@groups.cabforum.org>
To view this discussion on the web visit https://groups.google.com/a/groups.cabforum.org/d/msgid/infrastructure/ZR0P278MB0170DAA6B18305232FA94EF2FA462%40ZR0P278MB0170.CHEP278.PROD.OUTLOOK.COM.
To view this discussion on the web visit https://groups.google.com/a/groups.cabforum.org/d/msgid/infrastructure/SA1PR17MB6503A6CD139F22992B603C91E3462%40SA1PR17MB6503.namprd17.prod.outlook.com.
To view this discussion on the web visit https://groups.google.com/a/groups.cabforum.org/d/msgid/infrastructure/CA%2B1gtaYcMKb1E4WyHPdSpEhPMvmLyckxy-MFWd5HxWG6Bu4uGw%40mail.gmail.com.
Given that https://cabforum.org/pipermail/public/ gives a 404… 😉 I'd vote for option 2 and a clean-up ballot to fix the TLS BR "after the fact".
-Roman
To view this discussion on the web visit https://groups.google.com/a/groups.cabforum.org/d/msgid/infrastructure/SA1PR17MB6503A6CD139F22992B603C91E3462%40SA1PR17MB6503.namprd17.prod.outlook.com.