https://bugs.winehq.org/show_bug.cgi?id=49024
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello folks,
same procedure as every year? We already had such requests in the past. They have been discussed extensively and shot down for good reasons. You want to repeat that again here?
* bug 11421 ("Wine makes possible for windows virus to work?") * bug 25537 ("Wine allows access to / regardless configured ~/.wine/dosdevices") * bug 31114 ("Wine is too insecure.") * bug 33587 ("Should Wine create symbolic links to ~ directories?") * bug 42591 ("Do not auto symlink devices to dos device except for c:") * bug 45419 ("Consider adding 'read-only' option for virtual drives for better security ("read-only file system")") * bug 46525 ("Wine allows access to / regardless of configured ~/.wine/dosdevices")
Use Linux/distro provided security measures and sandboxing technologies if you need a bit more "security". Remember, there is no such thing as 100% security - even with Linux.
BTW, I've tested the compatibility of "WannaCry" with Wine in 2017 when it was a hot topic. I used a Docker container at that time because I knew what would happen. It worked as designed and encrypted everything user-writable on the exposed filesystem(s). You figured that out again - great. If "WannyCry" wouldn't have worked due to some Wine bug/API insufficiency it would have been fixed a long time ago. It's still a Windows application in the end. Same with other malware.
Regards