-
Notifications
You must be signed in to change notification settings - Fork 13
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
Armory and extensions #27
Comments
Isn't there any way to execute commands on the beacon without passing by the wrapper functions?
This library has unfortunately a lot of limitations. @moloch-- , can we implement this future so it will be more easier than writing wrappers around extensions that can change overtime? It can also be easier for maintaining the code up to date to the newest version of sliver so you don't have to implement command wrappers. |
@666Danger-sudo Since communications with Sliver is over gRPC via protobuf, everything is eventually going to be some wrapper function. Fortunately, the code generation for the gRPC functions has gotten a little easier to deal with. But the reality is that whenever Sliver gets changes to the If you mean this in terms of the Armory, the reason for a separate client is because Sliver does not use gRPC to handle Armory commands. So, in order for SliverPy to know what extensions exist, and for users to be able to download extensions, it has to be written separately. |
I was trying .execute(), can you tell me whats the issue here? |
Before handling #21, it makes sense to implement an Armory client so users can get the extensions or aliases they want to register or call. The armory isn't exposed via gRPC so a separate async client is needed to get the data.
The text was updated successfully, but these errors were encountered: