adfoster-r7

## Release notes Improves the `CIPCTlv` definition for the `exploits/windows/local/anyconnect_lpe` module

Thanks!

Looks like this is now an error in newer versions of Active Support: ``` Failures: 1) IceCube::Occurrence to_s accepts a format option to comply with ActiveSupport Failure/Error: expect(occurrence.to_s(:short)).to eq time_now.to_s(:short)...

This fixes one of the tests for me :+1: Before ``` rspec ./spec/examples/to_yaml_spec.rb:80 # IceCube::Schedule to_yaml should be able to make a round-trip to YAML with .day_of_year rspec ./spec/examples/to_yaml_spec.rb:114 #...

Looks like following your pattern for the final remaining test worked for my env :+1: ```diff diff --git a/spec/examples/to_yaml_spec.rb b/spec/examples/to_yaml_spec.rb index 7166110..913cd05 100644 --- a/spec/examples/to_yaml_spec.rb +++ b/spec/examples/to_yaml_spec.rb @@ -134,7 +134,7...

Closing this as it's an environment issue which can be resolved by configuring `ulimit` I'm not against a PR to have a hard session limit, which we could cross-reference with...

Cross-referencing: https://github.com/rapid7/metasploit-framework/pull/17336 - potentially better OS architecture detection would be a good follow on from the OS version detection API PR

Could you post exact replication steps if you're hitting any issues :+1: It might be easier to create a fresh issue to ensure the issue isn't lost

@TheKevinWang Following your steps, the listener is still alive for me: ``` msf6 payload(cmd/windows/powershell_reverse_tcp) > [*] Command shell session 1 opened (192.168.123.1:4444 -> 192.168.123.147:49695) at 2024-01-18 10:12:28 +0000 sessions Active...

> Closing this issue, as the underlying issue is apparently due to Ruby behaviour: https://bugs.ruby-lang.org/issues/16476 I haven't tested it; but Ruby 3.3 is out now - and apparently there's changes...