RageLtMan

@wvu: i've exposed the various infrastructure hooks you'd need to start digging into the port-forwarding thing (or even some custom SSM document that raises Pythagoras' ghost to haunt target systems)....

WebSocket shells work as of 43d746c: ```ruby (2023-01-03)09:28 (S:2 J:0)msf exploit(multi/handler) > sessions 2 [*] Starting interaction with 2... Shell Banner: $ ----- $ whoami whoami ssm-user $ pwd pwd...

@jmartin-r7 - there's gonna be a few of those weird things since the repo into which i dump the working files is not the same as my framework, also why...

@zeroSteiner - how do you want to handle output/reporting/etc? Should i throw in a scanner mixin or do we just want a pretty Rex table with the contents of that...

@smcintyre-r7: cant comment on the region piece, but that is a requirement in the API call. Updating the DS option to be required seems the most straightforward approach. Any issue...

Regarding the `exit` bit - will need to dig into that, i normally ctrl+c my sessions to get out of them but its either my having missed some "end of...

i have no idea how @h00die's commit is attached to this all of a sudden - digging.

@smcintyre-r7 - re the `exit ` bit: looks like `close` isn't working correctly, `SsmChannel` records the socket close, but then it seems that the underlying `Channel` tries to call `opcode`...

Anecdotally, i think that `exit` thing is a bigger problem and we're leaking a resource somewhere. I left framework running all weekend on the current state, using the SSM sessions...

Given that the shell colorizes and seems to be a full PTY, its definitely not your standard command-shell... might also be why my in-shell-TLV-transport thing is barfing.