RageLtMan

@gwillcox-r7: thank you. That hostsfile ingestion isn't exactly optional - its part of the `#initialize` method for the `CachedResolver`: ```ruby def initialize(config = {}) super(config) self.cache = Rex::Proto::DNS::Cache.new # Read...

Thanks for fixing that, i'm a bit confused as to what was changed as github did something funky to the git history.

Ah, you can PR to my branch from which this PR grows - easiest way to fix this stuff AFAIK. I can force-push last state (i think i have it)...

I can fill in the history on that subtree - its pretty much all my fault :smile:. The DNS work being pushed upstream has existed in my fork in different...

I've been in touch with the Arch Ruby packagers - they're rehashing 3.1 due to stdlib dependency problems in the way the 3.0 and prior packages are built. Once that's...

Already looking better than the bloodbath in mine, thank you.

I updated the other side to explicitly `require 'rex/logging'` from `core.rb` to avoid reliance on auto-loading of dependencies. Lets see what it says after that change.

Zeitwerk related - all the `require` statements were removed. Restored those.

@adfoster-r7 - ping for liveness now that 6.3's been out a bit.

Doesn't impact my end, just keeps folks from using `rex-socket` stag without Msf :). Can we have the code live in both repos until the git thing's figured out? That...