http://bugs.winehq.org/show_bug.cgi?id=20738
Summary: 'hard lockup of wine' provoker Product: Wine Version: 1.1.33 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: herrold@owlriver.com
wine-1.1.33-0.el5.mh (Mike Harris packaging for CentOS 5) see: http://wiki.centos.org/AdditionalResources/Repositories for a pointer
Running the following in a CentOS 5 xen domU instance locks it up hard and kills networking
wine explorer
I have not yet reproduced, but assume I will be able to once I regain control of the unit.
Obviously, in reading further in the documentation, it seems that the file explorer is not so invoked, but it seems interesting that I could so provoke a lockup
It may have security and DDoS implications that an end application is able to take down a machine thus.
It seems that the command interpreter should check the existence of a binary, and catch and return when not a proper command.
-- Russ herrold