Skip to content

Why is this outbound traffic originating from the tradenote container? #142

Open
@lapse00

Description

@lapse00

Hello,

Concerned about privacy, I decided to deploy this solution. By sniffing outbound traffic with a container deployed on the same network as the tradenote container, I found this:

19:41:26.006292 eth0  Out IP 8e983dae0c62.45842 > ec2-54-210-243-92.compute-1.amazonaws.com.443: Flags [S], seq 791705676, win 64240, options [mss 1460,sackOK,TS val 4030211411 ecr 0,nop,wscale 7], length 0
19:41:27.018846 eth0  Out IP 8e983dae0c62.45842 > ec2-54-210-243-92.compute-1.amazonaws.com.443: Flags [S], seq 791705676, win 64240, options [mss 1460,sackOK,TS val 4030212424 ecr 0,nop,wscale 7], length 0
19:41:28.042874 eth0  Out IP 8e983dae0c62.45842 > ec2-54-210-243-92.compute-1.amazonaws.com.443: Flags [S], seq 791705676, win 64240, options [mss 1460,sackOK,TS val 4030213448 ecr 0,nop,wscale 7], length 0
19:41:29.066869 eth0  Out IP 8e983dae0c62.45842 > ec2-54-210-243-92.compute-1.amazonaws.com.443: Flags [S], seq 791705676, win 64240, options [mss 1460,sackOK,TS val 4030214472 ecr 0,nop,wscale 7], length 0

I had previously applied an iptables rule to block outbound internet access for DOCKER-USER.

What is this for? ec2-54-210-243-92.compute-1.amazonaws.com.443

Certificate:

Common Name (CN)	*.docker.com
Organization (O)	<Not Part Of Certificate>
Organizational Unit (OU)	<Not Part Of Certificate>

Thank you

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