Skip to content

Conversation

@kmanley
Copy link
Contributor

@kmanley kmanley commented Jan 8, 2016

I gave some more thought to your concerns about disabling nc checking and I think you're right, it's not a good idea. So I bit the bullet and implemented this PR. It uses a fixed size bitset to track the nc values seen for each nonce and also implements stale=true (issue #24). If an nc is seen that is out of range, we simply treat it as if the nonce expired and use stale=true to avoid the client popping up an authentication dialog. nc values can arrive out of order, if a replay is seen it is detected and auth fails. I have implemented this in my proxy server and it's working great now. LMK if you have any questions.

@kmanley
Copy link
Contributor Author

kmanley commented Jan 8, 2016

Sorry this has gotten a bit messy, if it's easier I can send you a new PR from my master which is up to date with all the PRs I sent you.

@abbot
Copy link
Owner

abbot commented Oct 6, 2018

Hi. If you are still interested in merging this, can you please rebase against current master? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants