This repository has been archived by the owner on Sep 18, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed last night that this gem had the peculiar
OpenSSL::SSL::VERIFY_NONE
verification mode when making requests to the Shodan API. This mode doesn't perform any verification.This can leave communication susceptible to man in the middle attacks, which I'm sure we'd much rather avoid. So I've explicitly changed that to
OpenSSL::SSL::VERIFY_PEER
to verify our peer.This PR should have no real effect on the typical usage of this gem, other than making it safer. 馃憤