-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: fix TestImportMain not to write to current directory #22266
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
Comments
For the amd64 at least, I have the same file but it has a different size / SHA256 and a different outcome in the scan results Is the archive downloaded from https://storage.googleapis.com/golang/go1.9.1.windows-amd64.zip or some other place? |
I've verified the file at https://storage.googleapis.com/golang/go1.9.1.windows-386.zip has the correct SHA256 and does contain the x.exe file at the path OP listed. |
my plugin loads archives through web api from https://storage.googleapis.com/golang/ |
@raydac can you try on a third party system? Maybe from a Linux based OS? |
@dlsniper what do you mean? I have loaded manually zip golang sdk archives 1.9.1 for windows under Ubuntu and x.exe is presented in both zip archives, calculated sha256 are the same like described on the main download page |
Cool, so now upload the exe files from the Ubuntu machine to that website and see what results you have. The sums for the archives seem to be correct, see if anything changes for that file, x.exe |
My All scans here say it's benign. Smells like an intermediate artifact that was packaged in error. This embedded path gives an additional hint: |
@mattn the path is a bit incorrect, you need to run |
Sorry, I found it on go/src/cmd/go. As far as I can see, it is built by go. And |
BTW, It seems that *_test.go in go/src/cmd/go have some string |
CC @broady |
Specified download URL redirected from golang.org. This seems not bad. One of the antivirus software seems to detect always. |
And I uploaded x.exe contained the zip, but not detected. The result page which I posted was redirected to the page which is already reported by another user. |
So, currently, what I can say is that x.exe I uploaded is not same file as x.exe uploaded by raydac. |
@mattn this seems to be limited to the 386 distribution only. The file is present both in amd64 and 386 distros but only flagged as malicious in the 386 archive. Unfortunately does not make that very clear. Maybe someone with edit rights can change the issue name / description accordingly? |
@mattn a lot of antiviruses are red for version of x.exe from 386 version of golang sdk 1.9.1 and user of plugin also detected such signal for 32 bit version |
@raydac I checked 386 zip file.
|
But... what is |
I uploaded exe file that is compiled with GOOS=windows, GOARCH=386 on Ubuntu.
It seems some antivirus ware detect binary compiled with GOOS=windows GOARCH=386 on Linux as malicious. |
The binary is left over from running TestImportMain in cmd/go. It's harmless. We should remove it, but it's harmless. Any virus scanner that thinks the binary is a virus is wrong. |
Change https://golang.org/cl/71410 mentions this issue: |
CL 71410 OK for Go 1.9.2. |
Change https://golang.org/cl/71490 mentions this issue: |
Change https://golang.org/cl/71530 mentions this issue: |
More generally I'm concerned about these tests using $GOROOT/src/cmd/go as scratch space, especially combined wtih tg.parallel() - it's easy to believe some other test might inadvertently also try to write x.exe about the same time. This CL only solves the "didn't clean up x.exe" problem and leaves for another day the "probably shouldn't write to cmd/go at all" problem. Fixes #22266. Change-Id: I651534d70e2d360138e0373fb4a316081872550b Reviewed-on: https://go-review.googlesource.com/71410 Run-TryBot: Russ Cox <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-on: https://go-review.googlesource.com/71490
More generally I'm concerned about these tests using $GOROOT/src/cmd/go as scratch space, especially combined wtih tg.parallel() - it's easy to believe some other test might inadvertently also try to write x.exe about the same time. This CL only solves the "didn't clean up x.exe" problem and leaves for another day the "probably shouldn't write to cmd/go at all" problem. Fixes #22266. Change-Id: I651534d70e2d360138e0373fb4a316081872550b Reviewed-on: https://go-review.googlesource.com/71410 Run-TryBot: Russ Cox <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-on: https://go-review.googlesource.com/71530
go1.9.2 has been packaged and includes: The release is posted at golang.org/dl. — golang.org/x/build/cmd/releasebot, Oct 26 21:09:24 UTC |
Golang SDK 1.9.1 zip archives for Windows (both amd64 and i386) contain file /go/src/cmd/go/x.exe I could not find similar file in Linux distributive and in Go SDK 1.9 for Windows, the issue is that many antiviruses complain about the file
what is the file?
The text was updated successfully, but these errors were encountered: