Abusing Go's Infrastructure
reverse.put.as
Abusing Go's Infrastructure
1–10 of 80 posts
Re: Abusing Go's Infrastructure
#2Re: Abusing Go's Infrastructure
#3I would hope the Go team collaborated with GCP and Drive, as hosting malicious files is something Google has to deal with all the time. This isn't much different from other endpoints Google already allows people to put random data on.
Re: Abusing Go's Infrastructure
#4Re: Abusing Go's Infrastructure
#5it's a known issue https://github.com/golang/go/issues/31866
Re: Abusing Go's Infrastructure
#6I know pypi has some non-python projects as well. Python needs the ability to distribute wheels, which are compiled binaries, as the user may not be able to compile library code. Lots of that code is written in C, but Golang[1] is also possible. I can't find an example, but I believe I've seen this used for distributing applications (not libraries) as well. It's kinda cool to write some app in C, upload to pypi, and…
Re: Abusing Go's Infrastructure
#7I know pypi has some non-python projects as well. Python needs the ability to distribute wheels, which are compiled binaries, as the user may not be able to compile library code. Lots of that code is written in C, but Golang[1] is also possible. I can't find an example, but I believe I've seen this used for distributing applications (not libraries) as well. It's kinda cool to write some app in C, upload to pypi, and…
or even proprietary binaries, pip install nvidia-cudnn-cu12
Re: Abusing Go's Infrastructure
#8it's a known issue https://github.com/golang/go/issues/31866
That fix would help with accidents, but wouldn't someone intentionally hoping doing it just add a .mod and .go file to the root?
In the end, there is no definition of "a source control repository that is a Go module" that is robust to this sort of "attack"... although calling it an "attack" is kind of dubious, the reasons why this is a bad thing strike me as very strained and relatively weak. Mostly it hurts Google by hosting too much stuff, but, good luck bringing them down that way.
Re: Abusing Go's Infrastructure
#9- proposal: https://github.com/cue-lang/proposal/tree/main/designs/modul...
- custom registry: https://cuelang.org/docs/tutorial/working-with-a-custom-modu...
- road map: https://github.com/orgs/cue-lang/projects/10/views/8
- in 0.9.0-alpha-5, modules become enabled by default: https://github.com/cue-lang/cue/releases/tag/v0.9.0-alpha.5
For Go Sum, the Trillian project backs the transparency log: https://github.com/google/trillian
CUE plans to piggyback on the OCI options with attestations and such