For those who prefer a continuous "article", there are unrolling websites (not affiliated with the tool)
https://threadreaderapp.com/thread/1058676834940776450.html
A fun dive into windows history and backwards compatibility.
A fun dive into windows history and backwards compatibility.
I thought they found a bug in ALGOL60 code or something, which would have been funny as last week's pentest was written in an arcane language like that and likely last updated around the same time (not something we see every day; quite the opposite in terms of reinventing the wheel actually).
It might not be a great feature anymore, but it's not a bug. A 40 year old bug is things like TCP didn't have timeouts in all states, so LAST_ACK sockets should stay around forever if you follow the spec, or that if the two peers get mixed up about where the seq and ack are, each ack will elicit an ack from the other side, and if the peers are near enough to each other, that can result in gigabits of useless ack traffic that never results in data exchange (thankfully this isn't a common state; I've only seen it as a result of a bug in one OSes syncookies that was fixed, and it is likely to end with a timeout)
The error message says that the file is too large for the destination file system (despite being under 10KB). It's unambiguously a bug.