feat: isolate simultaneous RDP fixture profiles
This commit is contained in:
@@ -904,6 +904,12 @@ response”. If the public browser hostname has an AAAA record, `rdp-access up
|
||||
--bind 0.0.0.0` must own a tracked IPv6-to-IPv4 forward and expose its
|
||||
`ipv6_forward` status; this prevents a browser selecting IPv6 for the WebSocket
|
||||
from silently taking a different, refused path.
|
||||
The helper preserves the single-fixture `default` profile for compatibility;
|
||||
simultaneous already-running VM gateways use a unique `RDP_ACCESS_PROFILE` (or
|
||||
`--profile`) with separate runtime/project state and HTTP/tunnel ports, while
|
||||
`RVBOX_TEST_VBOX_HOST`, the documented VM/snapshot identity variables, and
|
||||
`RDP_ACCESS_VRDE_PORT` select the actual target. Profile isolation does not
|
||||
override the native controller's exclusive lease for prepare/reset operations.
|
||||
|
||||
For this provisioned lane, the approved host-only credential-file location is
|
||||
`/home/cabbage/.local/share/rvbox-secrets/rvbox-win10-test.password`. It must
|
||||
|
||||
Reference in New Issue
Block a user