FiloSottile / FiloSottile/Heartbleed
Getting timeout on all negatives?
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 451
- PR merge metrics
- No merged PRs in 30d
Description
This is with the command line tool.
Sites which I know are fixed correctly give a `SAFE` response, but sites which I believe are not give a `ERROR: heartbleed: timeout` response. I can't get a straightforward "NOT SAFE" response (or whatever it gives in that condition).
Contributor guide
Assessment
This issue has not been assessed yet.