Daniel Pocock <[email protected]> writes: > The user callback strcmp_otp may need to return an error rather than > just rejecting an OTP value. > > response = 0: OTP accepted > response > 0: OTP mismatch > response < 0: internal failure (e.g. memory allocation), don't try again > > I propose the patch below to allow this > > The callback could potentially put details of the error in the > strcmp_handle, for use by user code
Thanks for the patch. I agree it looks useful. Committed, and will be in soon to be released 1.10.3. Cheers, Simon
