Skip to content

Empire daemon stops forwarding output of emp run #1113

@16m

Description

@16m

Hello,

I tried using remind101/empire:bfb5dafa5018ff8aae447154358a5ab2738d4103 and when running emp run, it looks like the empire daemon stops forwarding the container output after few seconds.

I ran a shell and quickly executed commands cmd1 to cmd9 (to make debugging easier):

$ emp run -a busybox sh

Pulling from library/busybox
Digest: sha256:3e8fa85ddfef1af9ca85a5cfb714148956984e02f00bec3f7f49d3925a91e0e7
Status: Image is up to date for busybox@sha256:3e8fa85ddfef1af9ca85a5cfb714148956984e02f00bec3f7f49d3925a91e0e7

/ # cmd1
sh: cmd1: not found
/ # cmd2
sh: cmd2: not found
/ # cmd3
sh: cmd3: not found
/ # cmd4
sh: cmd4: not found
/ # cmd5
sh: cmd5: not found
/ # c

My shell stopped outputting right after the c of cmd6, but I kept typing and running the commands, and I could see the empire daemon was still up and showing the commands in its log (I omitted some parts of the output to make it shorter):

-----------------------------------------------------
c2017/10/17 11:17:34 DEBUG: Response sqs/ReceiveMessage Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 200 OK
Content-Length: 240
Connection: keep-alive
Content-Type: text/xml
Date: Tue, 17 Oct 2017 11:17:34 GMT
Server: Server
X-Amzn-Requestid: XXXXX


-----------------------------------------------------
2017/10/17 11:17:34 DEBUG: Request sqs/ReceiveMessage Details:
---[ REQUEST POST-SIGN ]-----------------------------
POST / HTTP/1.1
Host: sqs.eu-west-1.amazonaws.com
User-Agent: aws-sdk-go/1.7.3 (go1.7.6; linux; amd64)
Content-Length: 165
XXXXXXX
Accept-Encoding: gzip


-----------------------------------------------------
md1
sh: cmd1: not found
/ # cmd2017/10/17 11:17:35 DEBUG: Request cloudformation/DescribeStacks Details:
---[ REQUEST POST-SIGN ]-----------------------------
POST / HTTP/1.1
Host: cloudformation.eu-west-1.amazonaws.com
User-Agent: aws-sdk-go/1.7.3 (go1.7.6; linux; amd64) Waiter
Content-Length: 87

-----------------------------------------------------
2
sh: cmd2: not found

-----------------------------------------------------

sh: cmd3: not found
/ # 2017/10/17 11:17:37 DEBUG: Response ecs/DescribeServices Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 200 OK
Content-Length: 12632
Connection: keep-alive
Content-Type: application/x-amz-json-1.1
Date: Tue, 17 Oct 2017 11:17:37 GMT
Server: Server
X-Amzn-Requestid: XXXXX

-----------------------------------------------------
4
sh: cmd4: not found
/ # cmd5
sh: cmd5: not found

-----------------------------------------------------

sh: cmd6: not found
/ # 2017/10/17 11:17:43 DEBUG: Response sqs/ReceiveMessage Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 200 OK
Content-Length: 240
Connection: keep-alive
Content-Type: text/xml
Date: Tue, 17 Oct 2017 11:17:43 GMT
Server: Server
X-Amzn-Requestid: XXXXX

-----------------------------------------------------
7
sh: cmd7: not found
/ # 2017/10/17 11:17:48 DEBUG: Response sqs/ReceiveMessage Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 200 OK
Content-Length: 240
Connection: keep-alive
Content-Type: text/xml
Date: Tue, 17 Oct 2017 11:17:48 GMT
Server: Server
X-Amzn-Requestid: XXXXX

I tried several times with different images/shells and the behaviour is consistent. This doesn't happen with remind101/empire:0.12.0.

Thanks for reading!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions