RageLtMan
RageLtMan
This is neat stuff, thank you. Any chance of an x64 version for parity (and utility, not a lot of x86 targets around anymore and WOW64 tends to "count toward...
@araout42 - thank you sir, encoders are long-lived tools in the satchel so the more working ones we have, the merrier.
This discussion might be relevant to [rex-socket #43](https://github.com/rapid7/rex-socket/pull/43) and @gwillcox-r7 as the behavior you're currently observing and upon which this output relies ends up falling-through Rex Socket to the OS...
Ah, thanks for the correction. Interesting problem, reproducible from my version as well: ```ruby Rex::Socket::RangeWalker.new('localhost').to_enum(:each).to_a => ["127.0.0.1", "0.0.0.1"] ``` Probably a rex-socket issue in that case, which i'm happy to...
Got it: ```ruby > before.to_enum.to_a => ["127.0.0.1", "0.0.0.1"] > after.to_enum.to_a => ["127.0.0.1", "::1"] ``` `Rex::Socket::Host` needed to "figure out" whether it's IPv6 or not during its init. PR incoming on...
Worth mentioning that not all systems resolve dual-stack for `localhost`: ```sh $ grep localhost /etc/hosts 127.0.0.1 localhost ::1 ip6-localhost ip6-loopback ``` and when using the native resolver: ```ruby > Rex::Socket.class_variable_get(:@@resolver)...
Regarding the datastore `SSL` option - i've run into that before, its a mess to clean up. @MetasploitTeam: what do folks think about changing the server mixin's DS option to...
Offhand, i can't come up with any situation where the `split` approach would produce an error - so i _think_ this works. Question on my mind is _why_ this was...
`git blame` says @smcintyre-r7 (@zeroSteiner) last touched that section but the commit (11ca76cacc) is following the prior pattern in the file. @smcintyre-r7: could you please peek at this? I think...
> This is cool. I'm also a fan of SSM's [port forwarding](https://aws.amazon.com/blogs/mt/use-port-forwarding-in-aws-systems-manager-session-manager-to-connect-to-remote-hosts/). Why do you hate me so? :stuck_out_tongue: I was hoping to stop this @ a proper WS-based session...