Bug 625979 - [security] Please make ClamAV scan Wine executables before running them
Summary: [security] Please make ClamAV scan Wine executables before running them
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 19
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-21 05:54 UTC by Luke Hutchison
Modified: 2015-02-17 13:20 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:20:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Luke Hutchison 2010-08-21 05:54:08 UTC
Wine is getting better and better all the time, and the 1.2 release brought a great improvement in Windows compatibility. Eventually the majority of Windows viruses and trojans will run fine on Wine, which adds a massive security vulnerability to Linux, because it's entirely possible that Windows antivirus software will never run on Wine -- it hooks itself too deeply into the operating system.

We have a great on-demand Windows antivirus scanner on Linux however, ClamAV.  ClamAV should be installed as a dependency of Wine, and should be set up by default to automatically scan all executables before Wine executes them if they are not already installed in Program Files (or even the ones there too each time they are run to be safe).

I would feel a lot less skittish about using Wine if ClamAV protection was set up out of the box on Fedora and was a dependency for Wine.

There's one suggestion of how to set it up here: http://blog.burghardt.pl/2007/11/wine-with-on-access-clamav-scanning/  However there are probably lots of ways to accomplish the same thing.

Thanks!

Comment 1 Fedora End Of Life 2013-04-03 18:27:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Luke Hutchison 2015-01-06 23:41:42 UTC
Added feature request 1179507 asking that Wine be launched inside a systemd Lightweight Container to at least contain the damage of a malware attack.

Comment 3 Fedora End Of Life 2015-01-09 16:18:54 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 13:20:36 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.