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
http://bugs.winehq.org/show_bug.cgi?id=20738
Mike A. Harris mharris@mharris.ca changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mharris@mharris.ca
http://bugs.winehq.org/show_bug.cgi?id=20738
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Jeff Zaroyko jeffz@jeffz.name 2009-11-17 23:29:03 --- This doesn't appear to have anything to do with Wine. If your Xen instance hangs, file a bug with that project. Resolving invalid.
http://bugs.winehq.org/show_bug.cgi?id=20738
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2009-11-17 23:29:14 --- closing invalid.