deceptively reading valid data from various buffers in the application and hardware stack
And as far as that goes, & not that I know, particularly, but FastCopy also contains a (self-contained) hash utility that by default (appears to) invalidate any "cache" (which I'll also assume also pertains to verifications made on the copy end), & if that is the case, then there might be some means for FFS to also invalidate any cache such that at least the quoted part would no longer be of concern.
]]>