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

[Google] session socket read fuzzing #18

Closed
Fitblip opened this issue Apr 13, 2012 · 2 comments
Closed

[Google] session socket read fuzzing #18

Fitblip opened this issue Apr 13, 2012 · 2 comments

Comments

@Fitblip
Copy link
Member

Fitblip commented Apr 13, 2012

Just learning sulley, so if this is already taken care of I apologize.

When defining a session it would be nice to have the option to specify if a
socket read should occur.

Example:
sess.connect(s_get("helo"))
sess.connect(s_get("helo"), s_get("mail from"))

When moving between the 'helo' request and 'mail from' request we should
try not reading from the socket and closing the connection.

From my understanding by reading the documentation a session is always
followed from start to end of the request graph. Part of this socket read
fuzzing would be to stop the session between requests and close the socket
without reading.

This would catch sig pipe issues in server processes.

@Fitblip
Copy link
Member Author

Fitblip commented Apr 13, 2012

I'm running on too little sleep, but I think I see what he's saying. I think he's trying to break up the state machine, so that after sending a "HELO" you close the connection and then try just a straight "MAIL FROM". I may be mis-reading though, I'm running on little to no sleep XD.

@Fitblip
Copy link
Member Author

Fitblip commented Sep 17, 2012

You can already do this, but he's defining the blocks improperly. The pgraph stuff really helps with this, because you get to see what the order of connections will be. Invalid.

@Fitblip Fitblip closed this as completed Sep 17, 2012
jtpereyda pushed a commit to jtpereyda/sulley that referenced this issue Nov 24, 2015
…-sel:udp-checksum-fuzz to develop

UTs passing; seems to be basically working.

* commit '600f05e7a2b6458ecd03488cba04ad4e1782cb22':
  FUZZ-5 Fixed pull request fix comments.
  FUZZ-5 Bug fixes for UDP checksum fuzzing.
  FUZZ-5 Checksum field is now mutating!
  FUZZ-5 after merging Size/Checksum fixes, the UDP checksum is a lot simpler. Working now!
  FUZZ-5 UDP work in progress. The recursion+callback method in Checksum is getting too  convoluted. We may need to step back and refactor.
  FUZZ-5 Wrote design for UDP Checksum in Sulley.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant