Remix.run Logo
▲ lakeviewterrace 5 hours ago

So they don't actually know what this network is, just who owns the IP space... time for a blog post to advertise our week-old service!

There is no evidence that physically ties this to the WH. It could be in a security lab for all they know. Or a guest network for the news media.

▲Terr_ 5 hours ago | parent | next [-]

> There is no evidence that physically ties this to the WH.

They don't need to be physically inside a specific building to be a networking security problem.

The core issue is whether an outsider has bypassed your firewall and can send+receive traffic from a node which is getting more trust than it deserves. If they've compromised the computer's microphone/camera/wifi-control that's an additional problem.

▲lakeviewterrace 4 hours ago | parent [-]

[flagged]

▲itishappy 2 hours ago | parent | prev | next [-]

"We don't know where the devices that appear to have breached the WH network are located. For all we know, they could be in Beijing or Moscow."

That seems significantly worse.

▲1e1a 5 hours ago | parent | prev [-]

Perhaps ping time measurements could help identify where the devices are physically located.

▲0cf8612b2e1e 3 hours ago | parent [-]

If you were really sneaky, could you add some small jitter to the network responses to make it more difficult to locate?

▲fn-mote 18 minutes ago | parent | next [-]

Jitter is not a defense against statistical analysis. Additional lag might be what you want.

▲cowlevel 2 hours ago | parent | prev [-]

No. You would need to add hundreds of milliseconds depending on the sender's location.