Skip to content

Sliver implants don't work anymore #187

@whotwagner

Description

@whotwagner

When attackmate generates an implant, the implant looks in sliver like:

 Name         Implant Type   Template   OS/Arch           Format   Command & Control            Debug
============ ============== ========== ============= ============ ============================ =======
 badimplant   session        sliver     linux/amd64   EXECUTABLE   [1] https://faaacebook.com   false

The c2 should use the mtls-protocol. Manually generated implants look like following:

Name          Implant Type   Template   OS/Arch           Format   Command & Control               Debug
============= ============== ========== ============= ============ =============================== =======
 GREEK_VELDT   session        sliver     linux/amd64   EXECUTABLE   [1] mtls://faaacebook.com:443   true

It's time to check the sliver-py api and check if the protobuf-schema changed in sliver and extend the options in a way, that mtls dns aso are useable too.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions