You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to obfuscate or change protobuf definitions or even just regenerate the protobuf files with make pb the server is not able to generate implants any more.
To Reproduce
Steps to reproduce the behavior:
checkout master
make pb
start sliver-server in debug mode with dlv
generate --http ....
Error
Expected behavior
The implants should generate at least without any changes. I did check through the file and it seems some of the logic has been changed in the *.pb.go files after generating with make pb.
Screenshots
The breakpoint where panic happens:
[*] Generating new windows/amd64 implant binary
panic: interface conversion: ast.Expr is *ast.CallExpr, not *ast.CompositeLit
Desktop (please complete the following information):
The issue might be my version of protobuf. I'll change to the same version and see if that fixes it.
from tag:1.5.42:
// protoc-gen-go v1.27.1
// protoc v4.22.2
vs
// protoc-gen-go v1.36.5
// protoc v5.29.2
Edit: Manually downloading a lower version of protoc helped. I think though, that "make pb" should be integrated into the build process of the docker image as well.
Describe the bug
When trying to obfuscate or change protobuf definitions or even just regenerate the protobuf files with
make pb
the server is not able to generate implants any more.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The implants should generate at least without any changes. I did check through the file and it seems some of the logic has been changed in the *.pb.go files after generating with
make pb
.Screenshots
The breakpoint where panic happens:
Desktop (please complete the following information):
Additional context
Changes include e.g. the import and use of
unsafe
The text was updated successfully, but these errors were encountered: