Low level driver reuse by Malware?

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Simon Zerafa

Simon Zerafa

Member
Sep 18, 2020
19
23
Hi Steve,

I was listening to the Risky Business podcast and the discussion turned to malware and specifically the reuse of code and drivers (particularly low level hardware drivers).

A though then struck that any low level hardware drivers developed for SR 7.0 might run the risk of reuse on Windows for nefarious purposes?

Without knowing how cross compatible RTOS and Windows code might be then I don't know if this could be a issue or not. You will probably know though.

Clearly the availability of a signed(?} kernel level driver which has access to storage media might not be the best idea ever 😉

I suspect this may be a non issue or you already have a cunning plan to avoid this but, just in case!

Kind Regards

Simon Zerafa
 
This seems to be a worry about something that is impracticable to actually happen. "Living off the land" implies that code is already in place (in general) for use. Code for a different OS is unlikely to be in place in a running Windows OS. Additionally, OS software is coded in layers, and RTOS32 has a layer that makes it look partially like Windows, but the underlying parts are going to be very different, and incompatible. (The company could not have binary compatibility at all levels without actually using Microsoft code and thus getting sued.)
 
You must log in or register to reply here.
Top Bottom
Back