-
-
Notifications
You must be signed in to change notification settings - Fork 236
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
imported and not used error when use literals #481
Comments
Nicely spotted. This is likely because of #360; The easiest fix is probably to appease the "imported and not used" check in some way, such as by removing unused imports after literal obfuscation. cc @lu4p |
Because of the We could just ignore version suffixes, however package names can be entirely independent from their path, therefore we should somehow do the same analysis as the compiler. Related Todo: https://github.com/burrowers/garble/blob/master/internal/literals/literals.go#L145 |
Yeah, we definitely need type information to resolve this, because with syntax alone, Go imports aren't clear. Luckily, we do already have type information. |
to determine if it still needs to be imported after literal obfuscation Fixes #481
What version of Garble and Go are you using?
What environment are you running Garble on?
go env
OutputWhat did you do?
when I build the following go with garble
What did you see instead?
when I run
garble -literals -debug build ARS
it will handle an exception as follow:but with go build it work properly
more importantly, it run properly with non-literals encrypt mode
but with go build it work properly
The text was updated successfully, but these errors were encountered: