Recommended Posts

Microsoft claims

Windows users running 64-bit versions of the operating system are less likely to get infected by attack code. According to Microsoft's security team said that 64-bit Windows has some of the lowest reported malware infection rates in the first half of 2009.

According to the Microsoft Malware Protection Center 64-bit malware is still exceedingly rare in the wild. Based on data gleened from Microsoft's Malicious Software Removal Tool (MSRC) the 64-bit version of Windows XP was 48 per cent less likely to be infected than the 32-bit edition during the first half of 2009; PCs running Vista 64-bit, meanwhile, were 35 per cent less likely to be infected than Vista 32-bit.

The blog said that that Windows 7 64-bit is the dominant flavor of that new OS as he touted its security. The blog claims that 64-bit Windows was safer by design than the less-powerful 32-bit version, ticking off such measures as PatchGuard, which makes it more difficult for malware to tamper with the operating system's kernel.

source

Link to comment
https://www.neowin.net/forum/topic/846834-windows-64-bit-is-safer/
Share on other sites

Heh. How many people here have EVER encountered PatchGuard? None, I bet.

It's just what redfox says, 64-bit is too fringe for anyone to bother making malware for it. The malware it does have will be of the 32-bit variety that still works because it doesn't mess with any parts of the system that are 64-bit only.

Overall, 64-bit is safer for the same reason Macs and Linux are: number of users.

If I'm going to spend an hour writing code to disable systems, would I rather spend

that hour and effect 1 million systems, or 20 million?

Look at the number of "dangerous" websites. You know what MOST of them have in common? Porn. They either have porn, or just advertise it to get you to the site. Why? Because there's more people searching for porn that anything else. It's all in the numbers of potential victims.

64 bit users arent safer than 32bit users. 32 bit malware still works on 64 bit hardware.

if anything 64 bit users are more at risk as they could be infected with 64bit malware as well as 32bit malware, 32bit users dont have this problem.

Nothing to do with patchguard and the other x64 security features in your highly qualified opinion then... :rolleyes:

64 bit users arent safer than 32bit users. 32 bit malware still works on 64 bit hardware.

if anything 64 bit users are more at risk as they could be infected with 64bit malware as well as 32bit malware, 32bit users dont have this problem.

How much x64-specific malware have you seen?

Overall, 64-bit is safer for the same reason Macs and Linux are: number of users.

Probably not. Most of the APIs, unless you are in kernel mode, is same. So, most malicious applications could still work in Windows x64. IMO, the higer security is probably the handiwork of on-for-all-programs-by-default hardware No Execute, PatchGuard and more randomization for ASLR

Nothing to do with patchguard and the other x64 security features in your highly qualified opinion then... :rolleyes:

I didnt say that & I didnt say my opinion was highly qualified, but thanks.

How much x64-specific malware have you seen?

none. but if there was none at all then the report would be pointless.

Ever had a patchguard crash? I've never heard of anyone who has as a result of malware.

Most malware doesn't try and patch the kernel. Anything that tries to patch system dlls would fail though because they'd be 64 bit as apposed to x86 which is what it would most likely target.

Most malware doesn't try and patch the kernel. Anything that tries to patch system dlls would fail though because they'd be 64 bit as apposed to x86 which is what it would most likely target.

Exactly. PatchGuard isn't very relevant in this context. Not just that, but if some malware for whatever reason wanted to patch the kernel, they could just disable PG first. A piece of malware that just sent the machine into a continuous crash loop would after all not be very useful.

PG primarily stops legitimate software from doing things it shouldn't, and that is its main purpose.

See http://en.wikipedia.org/wiki/Security_and_...ecific_features. The first 2 apply to XP 64 as well. Alas, if only Microsoft had supported XP x64 really well when it came out in April 2005.

It's like this:

- Windows users running the 64bit versions are immune against every kernel mode malware that was designed for 32bit versions of Windows. Why ?

Simply because every kernel level malware that was designed for 32bit versions of Windows rely heavily on modifying the Service Descriptor Table. Modifying the Service Descriptor Table on x64 is no longer possible, not without circumventing the Patch Guard Technology. So, all that malware that was designed for x86 is obsolete on x64.

- Windows users running either 64bit or 32bit versions of Windows are absolutely NOT immune against malware that is designed for x64. Circumventing Patch Guard is very well documented now (the very first public paper on this subject was published on Uninformed by Skape who works for MS now and Skywing, back in 2005), and more malware is being developed for x64 systems, especially that more and more users/enterprises are moving to this architecture.

To sum it up, in a couple years, there will be more malware targeting x64 systems and so this equation will shift.

Overall, 64-bit is safer for the same reason Macs and Linux are: number of users.

If I'm going to spend an hour writing code to disable systems, would I rather spend

that hour and effect 1 million systems, or 20 million?

Look at the number of "dangerous" websites. You know what MOST of them have in common? Porn. They either have porn, or just advertise it to get you to the site. Why? Because there's more people searching for porn that anything else. It's all in the numbers of potential victims.

It doesn't matter if you wrote just for 32-bit, the 32-bit virus code CAN STILL run on a 64-bit system with WOW...in simple terms, you can run a 32-bit app/virus/etc. on 64-bit windows...it doesn't matter. Now, if it's a 64-bit ONLY virus, that's a different story...as for Linux/Mac, I have no experience to comment in that area.

So your argument is null and void for Windows 64-bit systems using AMD64 (not Itanium64 versions).

Nothing to do with patchguard and the other x64 security features in your highly qualified opinion then... :rolleyes:

Haha...eye roll is right.

The comments are almost Picard face-palm worthy.

x64 was designed to be more secure. Why the **** is anyone surprised that MS says it's safer.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
    • One Year In
      slackerzz earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!