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

    • Close, but it is for any application starting, not just during boot time. In fact, it probably will not improve boot time at all because during a boot, the CPU is already boosting, so a pre-boost wouldn't change anything. I agree that it isn't exciting (especially considering every other OS already does it), but it is a good thing, even if they are just playing catch up.
    • Any so called performance increase will be in milliseconds, which nobody will actually notice in real world usage.
    • All it does is use the CPU more efficiently during boot to speed up boot times. That's it. Yawn....
    • It's not a one or the other kind of thing. Software should run efficiently, and the operating system should appropriately manage the CPU clocks. You could have the best most optimized software on earth, and it will still run faster if the CPU does a better job of boosting as needed. All this is doing is pre-boosting the CPU based on user actions, instead of waiting for the normal detection mechanism to kick in. If the OS knows it is about to need more CPU, why shouldn't it use that knowledge? It's the same idea of downshifting before passing someone, instead of just burying your foot into the peddle and waiting for the transmission to figure out what you want to do.
    • Audacity 3.7.8 by Razvan Serea Audacity is a free, open source digital audio editor and recording application. Edit your sounds using cut, copy, and paste features (with unlimited undo functionality), mix tracks, or apply effects to your recordings. The program also has a built-in amplitude-envelope editor, a customizable spectrogram mode, and a frequency-analysis window for audio-analysis applications. Built-in effects include bass boost, wah wah, and noise removal, and the program also supports VST plug-in effects. You can use Audacity to: Record live audio. Record computer playback on any Windows Vista or later machine. Convert tapes and records into digital recordings or CDs. Edit WAV, AIFF, FLAC, MP2, MP3 or Ogg Vorbis sound files. AC3, M4A/M4R (AAC), WMA and other formats supported using optional libraries. Cut, copy, splice or mix sounds together. Numerous effects including change the speed or pitch of a recording. Write your own plug-in effects with Nyquist. And more! See the complete list of features. Audacity 3.7.8 changelog: #10688 Fixed an exception thrown when pasting into a newly-created track (Thanks, David Bailes (@DavidBailes)!) #10870, #10884, #10775, #10629 Fixed tone generation, waveform-scale setting, SetClip Name parameter, and clip-boundary command names for scripting and macros (Thank you, David Bailes (@DavidBailes)!) #11106 Fixed the loading of presets for the Distortion effect (A million thanks, David Bailes (@DavidBailes)!) #10947 Fixed paste into an empty audio track not preserving the source sample rate (Thanks, Juan Gabriel Colonna (@juancolonna)!) #10776 Allowed AltGr modifier in label and clip name editing (Thanks, Davide Peressoni (@DPDmancul)!) #9938 Added options to choose where silence is truncated (start/middle/end) (Thanks, Noah Rosenfield (@nosenfield)!) #9935 Added Podcast 2.0 chapters JSON export for label tracks (Thanks, Noah Rosenfield (@nosenfield)!) #10103 Improve UI on HiDPI displays on Linux/wxGTK (Thanks, Ivan A. Melnikov (@iv-m)!) #10099 Fixed MixerBoard Mute and Solo button display (Thanks, Ivan A. Melnikov (@iv-m)!) #10681 Fixed multichannel FLAC import #10999 Fixed envelope being broken after joining clips Download: Audacity 64-bit | Standalone ~20.0 MB (Open Source) Download: Audacity 32-bit | Standalone Download: Audacity ARM64 | Standalone View: Audacity Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      500
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      155
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      71
  • Tell a friend

    Love Neowin? Tell a friend!