Samy Lahfa

Hey @ninjadev64, just pinging again ! For the new release, if you have time this week-end !

Hello @prurigro do you if the patchset you have shared has landed upstream yet in 6.7 ? I don't think it has but I haven't checked really thoroughly

We can use pseudo random generation [random](https://docs.python.org/3/library/random.html) in the standard lib, then or [secrets](https://docs.python.org/3/library/secrets.html) which is better for more random security value generation. Both do not need any new dependencies...

Is there any news so far, latest release 10.8.x have been seeing any fixes on the listed endpoints? Is it possible to know if a compatibility break will ever happen...

@mavink such protection is hassle to work with/use and provides barely limited protection as the htaccess can be bruteforced. Unless you add IP bans/fail2ban to mitigate bruteforce attacks on the...

I agree with @pktiuk it should be possible to break compatibility, just put it under an experimental checkbox or a checkbox that says this will break all functionality with 3rd...

@joshuaboniface what do you think about adding experimental/breaking change behind a checkbox or a settings on the server side ? So that the migration path can be tested by users...

Ran into this issue as well using `podman`, will see if docker does not have this issue, I've tried `Remmina`, `xfreerdp` (version 2 and 3), and also tried to run...

That seems to work @Moon1moon but only in the shell spawned from ``` podman unshare --rootless-netns ``` Then inside that shell, you can connect using `xfreerdp` and it does work...

Anyone has any clue why exactly there are some RDP connections issue on the host machine running the container with Podman specifically ? Any way to move forward or pinpoint...