Which, when successfully exploited, lets an unauthorized attacker run arbitrary code on the remote system

Security is not an argument because you shouldn't expect it in an operating system with backdoors.

>wants security patches
>don't want to upgrade
>don't want to use a rolling release system
Just kill yourself.

Any machine with Intel ME has a backdoor.

some of my customers have huge landscapes running on hpux, most super-uber critical
got i hate that os;
then again if it crashes, thats hw issue that happens once every 3-4 year per machine because i haven't had a single crash due os shit in the last decade

youtube.com/watch?v=7Y3EtCwQXfk

Those dont run windows anyway
hpux is not critical compared to nonstop/integrity

>saying x64 as if it's the same as x86-64/amd64
I fucking hate pajeets specifically because they do shit like this and absolutely shit all over linguistics to the point where meanings of words are lost. x64 is IA64/Itanium. It's not the CISC shit in your Currydows shitbox. It's a completely different VLIW architecture, you naan eating street pooper. Thank you.

HP Integrity servers use Itanium CPUs. Those run HP-UX and OpenVMS. You use these sorts of machines and operating systems when you need decades of uptime with airtight security. Nobody runs Shitblows on IA64 hardware because it's a waste. Porting shit to IA64 gets you garbage performance and writing your own software in house for it is easier to do on systems that have tried and true development tools for professionals (ie not Winshit).

Attached: 1476906098210.png (393x297, 9K)

lol spotted the pedo
>Just kill yourself.
why are you so upset, did pacman break your xorg again?

>x64 is Itanium
it's not and it never was, kys retard

Yes it is you fucking nigger.

>not posting the ONLY worthwhile one
youtube.com/watch?v=Ropn_kwpFDU

Anarcho-Communism.

Attached: unnamedd.jpg (288x288, 18K)

Anyone that still uses XP or fucking Server 2008 in production is asking for it.
There are literally no excuses. If your company desperately relies on some obscure legacy shit port it to a newer system or get what you deserve.
And OP you turbo nigger kill yourself the exploit doesn't even affect Win 10 or Server 2019.

>en.wikipedia.org/wiki/X86-64
>x86-64 (also known as x64, x86_64, AMD64 and Intel 64)

>And OP you turbo nigger kill yourself the exploit doesn't even affect Win 10 or Server 2019.
based "i can't retard" retard

Attached: kys nigger.jpg (812x1024, 61K)

x86-64 wasn't called x64 until Micropenis started calling it that. It was usually (and still is) called amd64, since it was AMD who originally added the 64-bit extensions to x86 which they had licensed from Intel.

>>Windows 7 for 32-bit Systems Service Pack 1
>Windows 7 for x64-based Systems Service Pack 1
>Windows Server 2008 for 32-bit Systems Service Pack 2
>Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
>Windows Server 2008 for Itanium-Based Systems Service Pack 2
>Windows Server 2008 for x64-based Systems Service Pack 2
>Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
>Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1
>Windows Server 2008 R2 for x64-based Systems Service Pack 1
>Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation
>Windows XP SP3 x86
>Windows XP Professional x64 Edition SP2
>Windows XP Embedded SP3 x86
>Windows Server 2003 SP2 x86
>Windows Server 2003 x64 Edition SP2
I neither see Windows 10 nor Server 2019. But nice try kiddo, I am sure some day you will learn to read.

>you've upgraded your systems to the great, fast and secure windows 10, right user? :^)
at no point did i say or even imply windows 10 is vulnerable, imbecile

>arch
Rude
Now KYS.

i meant the shitheads deciding running their most critical apps on it

>2019
>using Windows Server whatever
Why would anyone use it these days?

seething lincuck

>implying I only use linux
KYS faggot

>implying I only use linux
>only
used once, forever pozzed :^)

If you already have Remote Desktop disabled, or are behind a NAT, this is a complete non-issue. lmao @ IPv6 fags with RDP enabled though.