How to invalidate asset hash on file permission change?

[disordered]

For example, if I have DockerImageAsset, which includes a file which had its' permissions changed, the asset hash remains the same.
Besides writing my own "extra hash" for this, is there some flag or mode I can set to make it consider file permissions when calculating asset hashes?

I found comments in issues mentioning that people manually look for hash changes during deployment, but that is just unreliable.