Stories
Slash Boxes
Comments

SoylentNews is people

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Interesting) by turgid on Thursday October 23 2025, @01:34PM (3 children)

    by turgid (4318) Subscriber Badge on Thursday October 23 2025, @01:34PM (#1421899) Journal

    Assuming the malware makes Windows system calls then why wouldn't it? In the MS-DOS days, viruses used to bypass the OS completely and even intercept BIOS calls and redirect them to custom routines. There were these techniques called stealth and tunneling. If Windows's memory protection is badly broken, then I suppose they could still do this. If they're running under WINE, then the whole of memory will look completely different and they probably won't work.

    Starting Score:    1  point
    Moderation   +2  
       Interesting=2, Total=2
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • Flagged Comment by Anonymous Coward on Monday October 27 2025, @06:56AM (#1422440)

  • (Score: 2, Insightful) by Anonymous Coward on Friday October 31 2025, @03:01AM

    by Anonymous Coward on Friday October 31 2025, @03:01AM (#1422847)

    Exactly so. WINE even provides better compatibility than Windows for things like you mention. Such is the use case for WINE on WSL. However, that is the rhetorical point made. Should you scan Windows executables for Windows viruses run on WINE? The answer is "yes" if you are worried about accidentally running one and it causing problems with your system.

  • (Score: 0) by Anonymous Coward on Friday November 14 2025, @09:36AM

    by Anonymous Coward on Friday November 14 2025, @09:36AM (#1424309)

    Maybe one day "everything" will be on WINE: https://blog.hiler.eu/win32-the-only-stable-abi/ [hiler.eu] 🤣