|aeris 3826dd18ea Upgrade drone||4 months ago|
|bin||4 months ago|
|lib/cryptcheck||4 months ago|
|spec||4 months ago|
|.drone.yml||4 months ago|
|.gitignore||4 months ago|
|.rspec||4 months ago|
|.travis.yml||4 months ago|
|CODE_OF_CONDUCT.md||4 months ago|
|Gemfile||4 months ago|
|Gemfile.lock||4 months ago|
|README.md||4 months ago|
|Rakefile||2 years ago|
|cryptcheck-engine.gemspec||4 months ago|
CryptCheck needs support of old, unsecured and so deprecated protocols (SSLv2, SSLv3…) or cipher suite (RC4, 3DES…) to be able to fully cover SSL/TLS verifications.
OpenSSL 1.0 is necessary to support such deprecated things, but new TLS features like TLSv1.3 requires 1.2. And currently, Ruby is tied to a single OpenSSL binding, only old Ruby version (2.3) supports OpenSSL 1.0 and at the opposite, only 2.5+ supports 1.2.
It will be a real mess to use multiple binding to fully check a server
This project is a SSL/TLS pure Ruby implementation to remove CryptCheck OpenSSL dependency and so to support together old and new SSL/TLS features.
**/!\ DON'T USE IT IN PRODUCTION /!**
This is not a cryptographic safe implementation!
Add this line to your application's Gemfile:
And then execute:
Or install it yourself as:
$ gem install cryptcheck-engine
TODO: Write usage instructions here
After checking out the repo, run
bin/setup to install dependencies. Then,
rake spec to run the tests. You can also run
bin/console for an
interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run
bundle exec rake install. To
release a new version, update the version number in
version.rb, and then
bundle exec rake release, which will create a git tag for the version,
push git commits and tags, and push the
Bug reports and pull requests are welcome on GitHub at https://github.com/aeris/cryptcheck-tls. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
Everyone interacting in the Cryptcheck::Engine project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct .