That is, a package that is built without obfuscation imports an obfuscated package. This will result in confusing compilation error messages, because the importer can't find the exported names from the imported package by their non-obfuscated names: > ! garble build ./importer [stderr] # test/main/importer importer/importer.go:5:9: undefined: imported.Name exit status 2 Instead, detect this bad input case and provide a nice error: public package "test/main/importer" can't depend on obfuscated package "test/main/imported" (matched via GOPRIVATE="test/main/imported") For now, this is by design. It also makes little sense for a public package to import an obfuscated package in general, because the public package would have to leak details about the private package's API and behavior. While at it, fix a quirk where we thought the unsafe package could be private. It can't be, because the runtime package is always public and it imports the runtime package: public package "internal/bytealg" can't depend on obfuscated package "unsafe" (matched via GOPRIVATE="*") Instead of trying to obfuscate "unsafe" and doing nothing, simply add it to the neverPrivate list, which is also a better name than "privateBlacklist" (for #169). Fixes #164. Co-authored-by: lu4p <lu4p@pm.me> |
4 years ago | |
---|---|---|
.github | 5 years ago | |
internal | 4 years ago | |
scripts | 5 years ago | |
testdata | 4 years ago | |
.gitattributes | 5 years ago | |
.gitignore | 5 years ago | |
AUTHORS | 5 years ago | |
CONTRIBUTING.md | 5 years ago | |
LICENSE | 5 years ago | |
README.md | 5 years ago | |
bench_test.go | 5 years ago | |
go.mod | 5 years ago | |
go.sum | 5 years ago | |
import_obfuscation.go | 4 years ago | |
line_obfuscator.go | 5 years ago | |
main.go | 4 years ago | |
main_test.go | 4 years ago | |
runtime_strip.go | 4 years ago |
README.md
garble
GO111MODULE=on go get mvdan.cc/garble
Obfuscate Go code by wrapping the Go toolchain. Requires Go 1.15 or later, since Go 1.14 uses an entirely different object format.
garble build [build flags] [packages]
See garble -h
for up to date usage information.
Purpose
Produce a binary that works as well as a regular build, but that has as little information about the original source code as possible.
The tool is designed to be:
- Coupled with
cmd/go
, to support modules and build caching - Deterministic and reproducible, given the same initial source code
- Reversible given the original source, to un-garble panic stack traces
Mechanism
The tool wraps calls to the Go compiler and linker to transform the Go build, in order to:
- Replace as many useful identifiers as possible with short base64 hashes
- Replace package paths with short base64 hashes
- Remove all build and module information
- Strip filenames and shuffle position information
- Strip debugging information and symbol tables
- Obfuscate literals, if the
-literals
flag is given - Removes extra information if the
-tiny
flag is given
Options
By default, the tool garbles the packages under the current module. If not
running in module mode, then only the main package is garbled. To specify what
packages to garble, set GOPRIVATE
, documented at go help module-private
.
Caveats
Most of these can improve with time and effort. The purpose of this section is to document the current shortcomings of this tool.
-
Exported methods are never garbled at the moment, since they could be required by interfaces and reflection. This area is a work in progress.
-
Functions implemented outside Go, such as assembly, aren't garbled since we currently only transform the input Go source.
-
Go plugins are not currently supported; see #87.
Tiny Mode
When the -tiny
flag is passed, extra information is stripped from the resulting
Go binary. This includes line numbers, filenames, and code in the runtime the
prints panics, fatal errors, and trace/debug info. All in all this can make binaries
6-10% smaller in our testing.
Note: if -tiny
is passed, no panics, fatal errors will ever be printed, but they can
still be handled internally with recover
as normal. In addition, the GODEBUG
environmental variable will be ignored.