Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve issue #939 #958

Merged
merged 1 commit into from
Apr 3, 2014
Merged

Resolve issue #939 #958

merged 1 commit into from
Apr 3, 2014

Conversation

hurtonm
Copy link
Member

@hurtonm hurtonm commented Apr 3, 2014

This bug is caused by fq which can terminate pipe before sending all
frames of a message first. So sometimes two messages were mixed and this
confused ZAP handler.

This patch just modifies one pipe parameter so that socket consumes all
messages before dropping the pipe.

This bug is caused by fq which can terminate pipe before sending all
frames of a message first. So sometimes two messages were mixed and this
confused ZAP handler.

This patch just modifies one pipe parameter so that socket consumes all
messages before dropping the pipe.
hintjens added a commit that referenced this pull request Apr 3, 2014
@hintjens hintjens merged commit c1f7e1f into zeromq:master Apr 3, 2014
@hintjens
Copy link
Member

hintjens commented Apr 3, 2014

Does this need backporting to 4.0.x stable?

@hurtonm
Copy link
Member Author

hurtonm commented Apr 3, 2014

I think so.

@Asmod4n
Copy link
Contributor

Asmod4n commented Apr 9, 2014

This should resolve the DoS issue when a client connects with wrong credentials to a zap enabled server? (It was enough for a client to send one malformed request and the server would crash itself...)

@hurtonm
Copy link
Member Author

hurtonm commented Apr 9, 2014

What you describe must be a different bug. Do you have a C example reproducing this bug? Is there an issue for this already?

@Asmod4n
Copy link
Contributor

Asmod4n commented Apr 9, 2014

#882 #883

what i meant was the bug where ZAP rejects a wrong credential from a client, but the server would storm the zap handler forever.

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.

3 participants