Comment 2 for bug 1943536

Thanks for the bug.

The situation is more complex than that and there is a great summary by Amos on the Debian bug - one fix is in 4.8, others to come later.
One will want to track upstream (and Debians) action on it for the next steps.

The suggestion you added do not seem to be a perfect fix for every situation, but it might serve as a workaround for anyone affected in the meantime.