In his memoir, Gerstner described the turnaround as difficult and often wrenching for an IBM culture that had become insular and balkanized. After he arrived, over 100,000 employees were laid off from a company that had maintained a lifetime employment practice from its inception. Long allowed by their managers to believe that employment security had little reference to performance, thousands of IBM employees had grown lax, while the top-performing employees complained bitterly in attitude surveys. In the goal to create one common brand message for all IBM products and services around the world, under Gerstner's leadership the company consolidated its many advertising agencies down to just Ogilvy & Mather. Layoffs and other tough management measures continued in the first two years of his tenure, but the company was saved, and business success has continued to grow steadily since then.
We're also introducing GoStringUngarbler, a command-line tool written in Python that automatically decrypts strings found in garble-obfuscated Go binaries.
The meeting was the animals who evolved to not be able to consume this, lived in more harsh conditions than those that had the readily available sugar. Evolution.
I've been running OpenWRT on my home router since ca 2017, and I found LuCI both quite intuitive, and immensely powerful. Simple things are simple, complex or difficult things are possible, with just clicking around.
Unfortunately if something can't be done with LuCI, you're pretty much on your own - the documentation for the internals is scarce and expects you to be an expert/developer.
It's still pretty slow, but overall correct. There's tricks, like reader connections and a single writer connection to reduce contention. There was a blog post on here detailing some speedups in general.
The implementation is just wrong from what's been presented. basic jitter (20-100ms), and a dynamic payload size are what's actually missing here. The question now becomes though how interactive should your session be. Timing the connection latency might help to an extent, but this is about mitm and you don't necessarily know where your adversary is (first hop, or towards the end). Batching keystrokes would also help here.
Basically there are two "modes" in normal mode OpenSSH is content to idle with no packets moving except any requested keepalives. In "chaff mode" currently they try to send a chaff packet every time they can to disguise your keypresses, but they forgot keystrokes will just get bundled into the existing chaff packet, growing it, so it stands out as special.
All they need to do is retain the "chaff mode" but when they have a keystroke ready to be sent they should suppress the chaff that would otherwise go in the same packet.
No need for "basic jitter" or "dynamic payload size" that I can see, with this change the packets are indistinguishable in terms of size or (encrypted) content, and they have no more or less jitter than would be normal for the network they're traversing.
They will also need to increase the minimum size of a non-chaff keystroke to be the size of the largest keystroke that they wish to keep confidential; 3 bytes is a minimum for the basic control characters (e.g. arrow keys which are ESC '[' X where X depends on the arrow direction).
I did find it interesting that the return keystroke was of a differing size to other characters; on unix systems it should just send a ^J.
By your definition then nothing would be "plays anywhere". H.264 is about the closest you can get. And depending on Profiles it is about to become patent free where license will no longer be required.
