3 ms·
It looks like this was reported as a normal bug, and the security implications weren't noticed until later. This is unfortunate, but it's also pretty normal and
by jimrandomh 4y ago
It looks like this was reported as a normal bug, and the security implications weren't noticed until later. This is unfortunate, but it's also pretty normal and hard to avoid this sort of thing happnening.
- layer8 4y agoIt was declared to be an intentional change and not a bug. If anyone would have thought through how an application expecting the old semantics will behave under the new semantics, it should have been rather obvious that silently changing the semantics is a very bad idea. It’s absolutely a case of professional negligence.