As mpengine will unpack arbitrarily deeply nested archives and supports many obscure and esoteric archive formats (such as Amiga ZOO and MagicISO UIF), there is no practical way to identify an exploit at the network level, and administrators should patch as soon as is practically possible.
WTF
Archive bomb anyone? This isn't a new concept, right?
Doing IO intensive work, e.g. build large code base, I always have to deactivate the real time monitor - it slows down the whole process, or worded differently: turning off mpengine almost half's the build time. Reading more and more horror stories about its inner workings and design, it's time to get rid of it for good.
WTF
Archive bomb anyone? This isn't a new concept, right?
Doing IO intensive work, e.g. build large code base, I always have to deactivate the real time monitor - it slows down the whole process, or worded differently: turning off mpengine almost half's the build time. Reading more and more horror stories about its inner workings and design, it's time to get rid of it for good.