Postmodern
Postmodern
FYI [`OpenSSL::SSL::SSLContext#ssl_version=`](https://docs.ruby-lang.org/en/3.0/OpenSSL/SSL/SSLContext.html#method-i-ssl_version-3D) is deprecated, and `context.min_version = context.max_version = ` is recommended instead. However, the [`min_version=`](https://docs.ruby-lang.org/en/3.0/OpenSSL/SSL/SSLContext.html#method-i-min_version-3D)/[`max_version=`](https://docs.ruby-lang.org/en/3.0/OpenSSL/SSL/SSLContext.html#method-i-max_version-3D) methods accept slightly different values, such as `:TLS1` instead of `:TLSv1`, and do not...
Closing this as the `ronin` CLI has been totally rewritten and is much more robust now.
Looks like this is temporary blocked due to the `io-event` gem, which `async` depends on, containing C extensions and not having a JRuby version. See: https://github.com/socketry/io-event/issues/53#issuecomment-1379478408
Reported upstream to try to figure out how to specify the bind-port and bind-address of a remote connection. https://github.com/socketry/async-io/issues/59
This seems out-of-scope for `ronin-support`.
If you use `const_set` with `const_missing`, `const_missing` will only be called once per time constant.
Good idea! Would you be willing to write a Scanner using the [shodan](http://docs.shodanhq.com/ruby/index.html) gem?
Normally this would be set in `~/.ronin/config/scanners.rb` (sort of like `config/initializers/` in Rails). We could assign a file for the Shodan API key, so other ronin libraries could load it?
Use the [net-dns](https://github.com/bluemonk/net-dns#readme) gem, to get as much information as possible.
Yeah the old gem requires a much older version of ronin. `lib/ronin/ui/command_line/` was renamed to `lib/ronin/ui/cli/`. I really need to release new versions of all the gems.