5 ms·
How does ReactOS attempt avoiding being affectable by malware? Does it "fully" inherit the "attack surface" of the system it tries to be compatible to? Or are t
by mdp2021 5y ago
How does ReactOS attempt avoiding being affectable by malware? Does it "fully" inherit the "attack surface" of the system it tries to be compatible to? Or are there improvements? Is one supposed to run anti-malware software over it (or keep it networkless)?
- mschuster91 5y ago> Is one supposed to run anti-malware software over it (or keep it networkless)? As the biggest vector for malware is not an insecure operating system but user negligency (e.g. by opening malicious attachments in e-mails), it is advisable to have anti-malware software on every machine, regardless of the operating system.
- maskedinvader 5y agoThis seems no longer true with apples imessage 0 click example [0] for instance. Perhaps you can say using iPhone and iOS which has such a crazy bug is user negligency . - [0] - https://9to5mac.com/2021/07/19/zero-click-imessage-exploit/ https://9to5mac.com/2021/07/19/zero-click-imessage-exploit/
- alophawen 5y agoThis is nothing new, back in Windows 95 days you could run arbitrary code on a machine just by sending network data. It is also the kind of bugs that tend to get fixed fast once they are discovered. The biggest attack vector has for many years been user negligence like randomly opening email attachments, following strange links or just click yes on any pop up.
- marcodiego 5y ago> following strange links or just click yes on any pop up If a system security can be compromised just by clicking strange links and clicking "yes" to pop-ups, then the system is to blame, not the user.
- marcodiego 5y ago> biggest vector for malware is not an insecure operating system but user negligency This is victim blaming. Windows have been teaching users to install from third parties since 90's, added auto-run features to removable media, hid files extensions making it difficult to detect files that could do harm, took a decade to implement processes isolation, never added a good package manager and spent years making fun of FLOSS. Windows users may have a twisted view about security. I personally heard a few of them saying things like "linux is safe because nobody uses it" or "you MUST use an anti-virus". They may sound naive of negligent but in fact, they were carefully trained for decades to behave that way.
- mschuster91 5y agoYou have exactly the same issue in Mac users, though. Yes, Apple has an app store and added confirmation prompts and certificate checks in executables for everyone else, but people still download random stuff and ignore all security warnings.
- marcodiego 5y agoThe problems are nowhere near the same level. AFAIK MacOS users have to, at least, move a package to a certain folder for installing it. It is not something that happens by accident or just clicking yes. EDIT: For people enlightening me about the other ways to install or run binaries on MacOS: thanks for the info! I have really little experience with MacOS, but my GF uses a MacBook and I know it is not as easy to be used in deceptive ways as Windows is. So, considering the other ways to install or run apps on MacOS, to they run the app inside a sandbox? Do they need the user to type a password? Do they run with limited permissions? Do they need explicitly working around notarization to run?
- qwytw 5y agoYou don't actually need to install .app containers by moving them to the Applications folder you can run them from anywhere. In fact they are just basically folders with a binary file inside so it's basically the same as downloading an .exe on Windows and just launching them (of course on modern macOS they run in a sandbox and require explicit permission to access any files outside of it). Apps shipped in a .pkg do need to be installed, though. But from an user standpoint the process is almost identical to a Windows installer wizard.
- CountSessine 5y agoThat is, historically, completely false. Windows before WinXP SP2 was a wide-open door for malware. I still remember the whole summer of malware where the IT had to do an emergency shutdown of the whole building network at the switch to stop Blaster from spreading one afternoon. So hopefully ReactOS, while implementing Win2k, includes the XPSP2 mitigations?
- projct 5y agoBlaster was a worm (self-transmitting and replicating without user interaction.) I was in IT when it came out. XP SP2 had the firewall enabled by default in 2001, which blocked incoming SMB protocol requests and other related ports by default ("file and printer sharing" exception checkbox.) Additionally, a security patch for Blaster was released July 16 2003. Blaster itself showed up August 11 2003, so you had almost an entire month to evaluate the security patch. So in order to be affected by Blaster they had to 1. enable sharing of folders on client machines (connecting to servers does not require this firewall exception.) and 2. fail to apply a security patch for a wormable exploit in a timely fashion. That's not wide-open, that's (if they have control of client machines) IT department failure to act responsibly.
- mdp2021 5y ago> That's not wide-open I remember, around 2003, laptops getting infected just by getting connected to the Internet. It can be appropriate to use the expression «a wide-open door for malware».
- CountSessine 5y ago1. We were a video game studio with a lot of graphic artists passing around a lot of game assets. 2. I’m pretty that I’ve got it wrong and it was Sasser, not Blaster.
- ashtonkem 5y ago> e.g. by opening malicious attachments in e-mails And how pray tell do those malicious emails take over a system if an insecure OS isn’t at fault too?
- Underphil 5y agoThis does not answer the question. If you don't know the answer, it's best not to respond.
- mixmastamyk 5y agoMostly not. A lot of the attack surface has not been implemented yet. :-D When it has, fewer services are running at startup. Generally, it doesn't copy the atrocious early security default configs that were later changed. Don't believe it ships with an old browser or email client, so ~60% of potential issues gone right there.