Hey vuln researchers: you might think that custom domain for your 0-day or whatever is cute, but if you registered it recently, odds are a lot of mature orgs won't be able to see it. Please, just use your blog URL.
@feld That is not how sharing information works.
In addition, I'd like to be able to share the news of vulnerabilities with technically-minded people at work who might be affected, but I send them a link and, if they're using the corporate network, all they get is an error message.
Additionally, what's your plan when someone moves a very important project off GitHub to a newly registered domain? How are you going to fix your pipelines when you block domains just because they're new?
This policy sounds great for Janet in accounting but terrible for everyone who actually knows what they're doing with their computers
@feld If your pipeline depends on something that can just migrate to an newly registered domain, you are doing something very wrong. Especially when your pipeline seems important enough that you seemingly can't wait for your org's responsible person to unblock that domain.
Also, even though it is annoying to raise tickets to get such NRD unblocked, I prefer that over my org getting hacked. With the ticket, at least a second human has a look at that domain.
@mttaggart why would they not be able to see it?