kate3
Member
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
Swordfish. The "hacker" breaks 128-bit encryption in 60 seconds while a gun is held to his head and a helicopter rappels through a window.
The virtualization tax on that scene is approximately 400%. In reality, the kernel would have panicked from the memory pressure of rendering all those spinning cubes. No cgroup limits in Hollywood.
OpenVZ would have at least contained the explosion to a single container. https://linuxcontainers.org
virsh list --all | wc -l: 47
pam3
Member
Latency Witch
- Joined:
- Aug 2024
- Posts:
- 74
- From:
- Melbourne, Australia
Mr. Robot observed greater technical accuracy than most depictions; however, the latency between Elliot's apartment and the Steel Mountain data center would have been approximately 45ms[1], not the instantaneous responses depicted. The show observed proper use of Kali Linux tools but compressed timeframes by a factor of 10^3.
[1] Observed via traceroute to similar upstate NY facilities, RFC 792.
100% packet loss at hop 3
PetraSuper
Member
network boot believer
- Joined:
- Jun 2024
- Posts:
- 127
- From:
- Bratislava, Slovakia
Which printer model, HP or Lexmark
boot anything, anywhere, anytime
armstrongvds
Member
ARM Enjoyer
- Joined:
- Jun 2024
- Posts:
- 199
- From:
- Seoul, KR
Office Space is basically a documentary.
one small ping for man...
kate3
Member
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
Which kernel version handled that memory pressure
2.4.20-pre11 with the Rik van Riel VM, obviously. The OOM killer in that era had no mercy and no cgroup awareness. I watched it take out init once on a Debian woody box.
The real answer is that no kernel handles "render 3D cubes while brute forcing AES" well because that workload is fictional.
virsh list --all | wc -l: 47