https://bugs.winehq.org/show_bug.cgi?id=8332
--- Comment #24 from Sebastian Lackner <sebastian(a)fds-team.de> ---
(In reply to oiaohm from comment #23)
> After reading the system ping hack. Yes it contains a bad practice.
>
> Use of system command should be frowned on. Issue 1 with system is the
> possibility of coder error. Issue 2 the command line has to be broken up
> into null terminated strings any how. Something out of exec commands should
> be used.
> http://linux.die.net/man/3/execv
>
I thought I mentioned it here already, but seems like I didn't. Inspired by
Brunos idea I've added a similar proof-of-concept patch to Wine Staging, which
addresses exactly these problems:
https://github.com/wine-compholio/wine-staging/blob/master/patches/iphlpapi…
Using exec in Wine in general is not necessarily bad, but it would of course be
better to have only one "ping service" running instead of one application for
each request. Besides that the idea seems to work very well and is indeed
sufficient for a lot of applications, especially because additional
input/output parameters are translated.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8332
oiaohm <oiaohm(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oiaohm(a)gmail.com
--- Comment #23 from oiaohm <oiaohm(a)gmail.com> ---
After reading the system ping hack. Yes it contains a bad practice.
Use of system command should be frowned on. Issue 1 with system is the
possibility of coder error. Issue 2 the command line has to be broken up into
null terminated strings any how. Something out of exec commands should be used.
http://linux.die.net/man/3/execv
But this bad practice is quite minor.
Setting "sudo setcap cap_net_raw+epi /usr/bin/wine-preloader" from a security
point of view is extremely horrible.
1) not every application requires these privileges.
2) How much code really need to be running with these privilages
As what is said under windows you don't need privilege todo these operation.
Ping due to having privilege flag does not mean wine needs it on the loader.
Question should wine have a /usr/bin/wine-icmp that is coded to perform all the
icmp functionality of Windows.
--The privilege issue is certainly outside of Wine but I think it's better to
leave this open. Otherwise equivalent bugs will be opened over and over
again.--
Yes privilege issue is kinda outside wine. But wine has to operate correctly
in these privileged environments. Sometimes this means breaking parts off
into independent applications to perform higher privilege tasks. If something
should be broken off that is a wine question.
Can wine icmp.dll function if all the functionality of the icmp.dll was
implemented as a native independent executable that icmp.dll call by exec or
equal. If so this is most likely what should happen as then "setcap
cap_net_raw+epi" would only have to be granted on that limited code area.
Harder issue is the fact you cannot sudo setcap cap_net_raw+epi some.exe file
and have that executable only with the lifted privilege.
Binding ports under 1024 being restricted exists for reason. Again this is
another item that could be done by an indpendant application to the loader.
https://en.wikipedia.org/wiki/Authbind is example of this. Binding ports
under 1024 it would be great there was a file /etc/wine/ports listing what
ports wine applications could in fact bind on. Like you don't want dhcp/dns
ports taken over by a wine application because you were just restarting a
server.
Yes these independent applications could check if the executable the loader is
using has the right applied cap values before processing the request as well as
having special configuration files.
So each time we need to set a cap on loader to work the question need to be
asked should/can this functionality be an independent helper executable.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=24923
Summary: Wine doesn't allow to use/list bitmap fonts like
Terminus
Product: Wine
Version: 1.3.5
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: t.artem(a)mailcity.com
Wine doesn't allow to use nor lists system wide bitmap fonts like Terminus
(http://fractal.csie.org/~eric/wiki/Terminus_font).
(checked out by running Notepad - Terminus is not the list of fonts which are
allowed to select/use).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35461
Bug ID: 35461
Summary: Synergy server causes mouseover events to fail in
World of Warcraft
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chris(a)bjelleklang.org
Classification: Unclassified
Running wine 1.7.11, same issue appears in older versions as well.
When running the synergy server, any mouseover events will fail (silently) in
World of Warcraft. This affects the game pretty badly, as no tooltips or
mouseover menus is visible. They do appear once you click on a button, but
that's not really positive for the gameplay experience.
Not sure if this is fixable or caused by wine, but let me know if additional
information is required.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=27888
Ken Sharp <imwellcushtymelike(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |ABANDONED
--- Comment #6 from Ken Sharp <imwellcushtymelike(a)gmail.com> ---
Application unavailable.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1432
Anastasius Focht <focht(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |grendal74.geo(a)yahoo.com
--- Comment #5 from Anastasius Focht <focht(a)gmx.net> ---
*** Bug 38682 has been marked as a duplicate of this bug. ***
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1432
Anastasius Focht <focht(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |piotr.kosek(a)o2.pl
--- Comment #4 from Anastasius Focht <focht(a)gmx.net> ---
*** Bug 24737 has been marked as a duplicate of this bug. ***
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=1432
Anastasius Focht <focht(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |focht(a)gmx.net
Component|gdi32 |user32
Hardware|Other |x86
Version|unspecified |20030618
OS|other |Linux
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38759
Bug ID: 38759
Summary: WM_USER (and +1, +2) are being sent to application
windows
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jasonwinter(a)hotmail.com
Distribution: ---
My programs use WM_USER, WM_USER+1 and WM_USER+2 for various functions, but
they seem to be sent these messages by WINE when the mouse moves around the
window involved, possibly during repainting. This doesn't happen in Windows.
I've changed my offsets of 0x0400 to add 0x0280 (I now start acting on messages
at 0x0680 instead) and it's fixed - but it's clearly a bug in WINE.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.