Skip to content
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

Update links/references to transferred repositories #39989

Closed
thaJeztah opened this issue Sep 25, 2019 · 7 comments · Fixed by #39990
Closed

Update links/references to transferred repositories #39989

thaJeztah opened this issue Sep 25, 2019 · 7 comments · Fixed by #39990

Comments

@thaJeztah
Copy link
Member

We transferred a couple of repositories to the moby org; GitHub redirects them from the old location, but we should not rely on those redirects, and update references to them to use the new location;

Old location New location
https://github.com/jhowardmsft/docker-ci-zap https://github.com/moby/docker-ci-zap
https://github.com/jhowardmsft/docker-signal https://github.com/moby/docker-signal
https://github.com/jhowardmsft/busybox https://github.com/moby/busybox
https://github.com/jhowardmsft/busybox64 not transferred should not be referenced anywhere
https://github.com/jhowardmsft/docker-tdmgcc https://github.com/moby/docker-tdmgcc
@thaJeztah
Copy link
Member Author

@ddebroy @stefanberger

/cc @jhowardmsft

@thaJeztah
Copy link
Member Author

oops, apologies @stefanberger - meant to type @StefanScherer (github autocomplete 🙄)

@stevewithey
Copy link

FYI the redirect doesn't seem to have been set up for the docker-ci-zap repo and now a security researcher is cyber squatting on the old url... Fortunately they are a good person and are notifying people who use the old url, but it would be good to fix that...

@thaJeztah
Copy link
Member Author

Ugh, thanks for the heads-up. Looks like the happened because jhowardmsft changed his handle after we moved the repositories, which broke the redirects, and made the old name available for others to use 😞. I guess people would only run into this when building EOL versions of the code (and/or old mentions of that repository), but still not great.

@stevewithey
Copy link

Thanks, it's referenced in a few blog posts and other places across the web, I've contacted Microsoft and done a PR on one of their scripts that references the old url too: microsoft/nav-arm-templates#197

@thaJeztah
Copy link
Member Author

@stevewithey you mentioned that the squatter reached out to people; do you happen to have contact details for them? If so, could you send an email to security@docker.com ? (We could then reach out to them, and our contacts at GitHub to reserve the namespace, and to (re-)install redirects).

@stevewithey
Copy link

Sorry for the delay. You can reach out to them through the email in the code here: https://github.com/jhowardmsft/docker-ci-zap/blob/master/zap.go#L13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants