Daniel Sahlberg wrote on Thu, 21 Jan 2021 07:37 +00:00: > Also modified the server setup to redirect any requests for > http://svn-haxx.apache.org to https://svn.haxx.se. Only problem now is > if someone tries to access https://svn-haxx.apache.org, it will give a > certificate warning. I don't really see how we can avoid it without > having svn-haxx.a.o in the certificate. (We can't redirect the > svn-haxx.a.o DNS entry to another box since the whole purpose of that > entry is to be a CNAME target). Anyhow, nobody should be browsing that > URL anyway, it shouldn't exist anywhere except in a few mails in dev@. >
I'm not concerned about people using unofficial URLs. > > Second, I'm not happy about setting the address to dev@, for several > > reasons. One, it's not development-related traffic. Two, IIRC in Let's > > Encrypt the email address given is the "owner's" address, so if LE ever > > need to contact the PMC for whatever reason, automated or otherwise, > > that's the address they'd use. Such traffic should go to private@. > > > > I'm aware you aren't on that list, Daniel. We'll just have to loop > > you in on relevant threads. That would mirror the ACL configuration > > (for /repos/private/pmc/subversion/machines, and, IIRC, Infra's puppet > > repos too). > > Switched to private@ Thanks. Nothing received so far (just like nothing was received on dev@ previously). Cheers, Daniel
