Hyper-V VM connection issues after running "Standard" about privacy.sexy HOT 5 CLOSED

Hi @0xReverse, do you have the script file you executed (you have it if you used the desktop app)? Or did you run any of the presets?

from privacy.sexy.

You can generate different combinations. I wonder about your configuration. Or did you just try "Standard", "Strict"?

I'd be happy to take action if you can figure out which script has caused this otherwise.

from privacy.sexy.

I could reproduce this on both Windows 11 Pro 23H2 and Windows 10 22H2 using Hyper-V and an Ubuntu VM.

I found that it's Enable strong RSA key requirement causes this, reverting it solves the issue.

This using Standard (binary search tree with bisect) and found out that Enable strong RSA key requirement causes this. Looking to its docs, we really want to keep them on "Standard":

But as it breaks Hyper-V connection, I believe we have to move it to Strict with a document about it breaking Hyper-V machine something like (breaks Hyper-V VMs).

Thank you for the bug report and the context.

from privacy.sexy.

Yes reverting only "RSA Key Requirement" will solve the issue.
Please report back if it solves for you or does not work.

The rest of the Standard is OK.
It should not in anyway interfere with Windows Update, or its a critical bug.

We cannot granularity control this config, once it applies, it applies to all system connections.

My further tests show that Docker, wsl, and Windows Sandbox work fine. This impacts only Hyper-V VM connection, connections to other virtualization-based solutions work fine.

from privacy.sexy.

0.13.4 is just released 🎉. Actions taken:

• Add documentation to describe potential disruptions caused by stronger RSA key requirements.
• Move RSA key script from 'Standard' to 'Strict' due to its impact on Hyper-V VMs.

Thank you @0xReverse.

Please create new issues for further ideas/problems.

from privacy.sexy.