- SSLyze's memory usage has been significantly reduced when scanning a lot of servers concurrently (#511).
- This will make it easier to deploy SSLyze to environments where memory is limited, such as AWS Lambda.
- For example, when queuing 100 server scans, memory usage will now reach a maximum of 150 MB, instead of 1400 MB in previous versions of SSLyze.
- Fixed errors when running
http_headerson specific server software (#517, #516). - Removed usage of pipenv and switched back to a
requirements.txt.