Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
internal/crypto: Decrypt overlap rules are a bit off #1190
There seems to be a problem with the
Which isn't that helpful. There is already a discussion about it at golang/go#21279 but I think it means that
I don't think it's a problem right now, but it might become one as the CTR implementation is optimized.
Also, I'm not sure what this is supposed to mean in the
@FiloSottile Happened to read on r/golang about restic and saw this issue. It's not immediately clear to me right now if the buffer reuse which I try to avoid in general is being FORBIDDEN or ALLOWED here? When I interpreted the doc comments in #731 (comment) the language seemed to be granting specific permission to ALLOW buffer reuse, was it meant to be interpreted as a implementation detail of the interface which would imply such use is unsafe?