lang-team website no longer exists

[tmandry]

https://lang-team.rust-lang.org/ is a 404, even though the repo has a gh-pages branch with an index.html there. I don't have admin on the rust-lang/lang-team repo so I can't investigate further.

cc #83

[Mark-Simulacrum]

It needs to have a CNAME file in the root of gh-pages, like this: rust-lang/lang-team@cb04d13

[nikomatsakis]

It seems to work for me now...

[Mark-Simulacrum]

Whatever automation is creating the branch needs to write that file too.

[Qwuke]

@Mark-Simulacrum Added a fix here: rust-lang/lang-team#239

[pietroalbini]

Had to remove the lang-team.rust-lang.org domain name from DNS as a malicious actor took control of the domain name while the cname file was not present. We're discussing in infra how to proceed here.

[nikomatsakis]

@pietroalbini yikes!

[RalfJung]

a malicious actor took control of the domain name

So did an external actor get control of the rust-lang.org zone? I hope not.^^ But if not then I don't understand why the domain can't just be made to point to the right target?

[Mark-Simulacrum]

No, we're fully in control of DNS. The problem is that GitHub pages' model for which repository owns displaying content for some DNS name is basically "whoever was first". And, if you for whatever reason stop using a DNS name, then you lose that "first" and anyone else can come along and host their own site instead of the contents of your repo.

(All github pages sites are configured with an identical DNS CNAME on our side).

[RalfJung]

Ah so it's a question of which site github serves under that hostname? I see.

Is there a timeframe for how long it takes to convince github to give the domain back to whoever controls the DNS? Would it make any sense to use some other subdomain for now until this is resolved?

[Mark-Simulacrum]

I think we can stick with just https://rust-lang.github.io/lang-team/ for now. The expectation is that we will take ownership of *.rust-lang.org at the org level, but at least one site (the Foundation's) is currently outside the org so we can't yet do that.

[pietroalbini]

Turns out that wover squatted the domain stopped doing so, manually checked just now. I wired everything up together again, it should be live once https certs are deployed.

Make sure the CNAME file will be deployed in future pushes.