Well, that's the thing. I can't see how CTR counter wraps can occur. 64-bit counters which start at zero simply don't wrap.
This case has the added benefit of you being wrong (the counterspace always starts at zero, but that doesn't mean decryption or encryption does).
And: that's not all I'm talking about.
No, it isn't. The CTR counter is part of the implementation; the nonce is part of how CTR is used by the application.
(the counterspace always starts at zero, but that doesn't mean decryption or encryption does
If you're not encrypting starting from a counter of zero, you're not using a stream cipher. (Most likely, you're using a block storage cipher.)
And: that's not all I'm talking about.
Ok. I was just guessing, because you're claiming that an impossible bug exists and refusing to give any details.
I just can't fathom the logic behind blowing off a potential crypto flaw that clearly can occur. What, to you, is the downside of letting people know that CTR can blow up in this manner?
† But, a hint, it has obviously never depended on us sending 295147905179 gigabytes to a target