dan, 1 month ago They actually did try to optimize it a bit in v5.6.1, but the person that found the exploit was on the older unoptimized version v5.6.0.
They actually did try to optimize it a bit in v5.6.1, but the person that found the exploit was on the older unoptimized version v5.6.0.