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

Add support for single character reads as fallback for STARTTLS #732

Closed
wants to merge 2 commits into from

Conversation

typingArtist
Copy link
Contributor

@typingArtist typingArtist commented Apr 30, 2017

Reading text for STARTTLS has moved into a separate function. The function handles switching between the modes (line-based vs. character-based reading) autonomously.

Fixes #731

This PR is based on #730.

@typingArtist typingArtist changed the title 731 add support for single character reads as fallback for STARTTLS Add support for single character reads as fallback for STARTTLS Apr 30, 2017
@drwetter
Copy link
Owner

drwetter commented May 4, 2017

Thx @typingArtist .

You have a test host for me (tarpit) (dm/pm/whatsover)?

@drwetter
Copy link
Owner

drwetter commented May 8, 2017

  1. It's a cool idea!

  2. doesn't fly yet, seems to hang at SSLv3 'reading server hello... \nTLS message fragments:'

  3. debugging info seems to be different if it is a tarpit host, i.e. if first line read in starttls_read_one_line() fails

  4. testssl.sh uses double square brackets as single ones are an external command (try which ] in bash)

Cheers, Dirk

@drwetter drwetter closed this May 24, 2019
@drwetter drwetter reopened this May 24, 2019
@drwetter
Copy link
Owner

Hi @typingArtist ,

I would like to close this for housekeeping reasons: As said it's a good idea but would need a bit of work. last but not least the branch you tried to patch against (2.9dev), is dead.

@typingArtist
Copy link
Contributor Author

Ah, I have completely forgotten about that. Would you accept fixes rebased on current dev branch?

Also, what shall we do about testing? I see two options here:

  1. Create a permanent public server for the sole purpose of tarpit testing
  2. Create a temporary server-like local thread that simulates a tarpit STARTTLS server

I’d like to go with option 2 but I first have to learn about Perl testing anyway.

@drwetter
Copy link
Owner

Ah, I have completely forgotten about that. Would you accept fixes rebased on current dev branch?

No prob. There's no current dev branch :-) After release (or shortly before) of 3.0 there will be a 3.1dev branch

Create a temporary server-like local thread that simulates a tarpit STARTTLS server

I’d like to go with option 2 but I first have to learn about Perl testing anyway.

  1. sounds fine to me. But I don't expect to write a unit test for that rare species. It's ok if we have something to test against.

OT: In general (@ all) unit tests are documented here and if one looks a existing scripts that should suffice.

Ok to close the PR and you resubmit when 3.1dev is there?

@typingArtist
Copy link
Contributor Author

Sure. I do.

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.

None yet

2 participants