This commit is contained in:
Rustam Zagirov
2019-05-13 19:48:57 +03:00
committed by Marwan Sulaiman
parent 33fdc92c48
commit ffc64825ce
+2 -2
View File
@@ -25,7 +25,7 @@ The reasons for needing a Checksum DB is explained in the linked proposal above.
### Why Proxy a Checksum DB?
This is quite important. Say you are a company that is running an Athens instance, and you don't want the world to konw about where your
This is quite important. Say you are a company that is running an Athens instance, and you don't want the world to know about where your
repositories live. For example, say you have a private repo under `github.com/mycompany/secret-repo`. In order to ensure that the Go client
does not send a request to `https://sum.golang.org/lookup/github.com/mycompany/secret-repo@v1.0.0` and therefore leaking your private import path to the public, you need to ensure that you tell Go to skip particular import paths as such:
@@ -42,4 +42,4 @@ As the Athens company maintainer, you can run Athens with the following configur
`NoSumPatterns = ["github.com/mycompany/*] # or comma separted env var: ATHENS_GONOSUM_PATTERNS`
This will ensure that when Go sends a request to `<athens-url/sumdb/sum.golang.org/github.com/mycompany/secret-repo@v1.0.0>`, Athens will return a 403 and failing the build ensuring that the client knows something is not configured correctly and also never leaking those import paths
This will ensure that when Go sends a request to `<athens-url/sumdb/sum.golang.org/github.com/mycompany/secret-repo@v1.0.0>`, Athens will return a 403 and failing the build ensuring that the client knows something is not configured correctly and also never leaking those import paths