Live data from Hacker News

Fun with Red Star OS

sizeof.cat

21–30 of 179 posts

Re: Fun with Red Star OS

#22
post #16
post #9

Earlier quoted context omitted.

This could be true, or it could recognize that it is running in a VM and change its behavior. This is a somewhat common trait of malware meant to throw off security researchers.

Why are VMs so bad at virtualizing? An ideal VM should be indistinguishable from a real machine. For example a virtualized system running Android should generate fake IMU data, not sit at 0 linear acceleration all the time. And have a real-looking fake IMEI, not a string of 0s.

I talked to a security researcher about it a few years ago and as I understood it it's a cat and mouse game. They are trying to mimic real phones but the malware authors always find a new way to tell whether it's fake.

Re: Fun with Red Star OS

#23
post #16
post #9

Earlier quoted context omitted.

This could be true, or it could recognize that it is running in a VM and change its behavior. This is a somewhat common trait of malware meant to throw off security researchers.

Why are VMs so bad at virtualizing? An ideal VM should be indistinguishable from a real machine. For example a virtualized system running Android should generate fake IMU data, not sit at 0 linear acceleration all the time. And have a real-looking fake IMEI, not a string of 0s.

Hi, virt engineer here. Partly because it a very hard problem (in fact, theoretically impossible if you include timing attacks), but mainly because you don't need to emulate the hardware very accurately in order to get common operating systems to run. Getting them to run is all that we're paid to do, and that's a difficult enough job already.

One strange aspect of this is that only a narrow range of current OSes run under virtualization. Qemu is great for running, say, current versions of Linux or Windows, but absolutely terrible if you try to run Linux 1.0 or Windows 95 or Solaris/x86 or any uncommon OS. (I tried a few of these several years ago out of curiosity, and none of them would even boot.) The reason is that we don't emulate enough of the corner cases in CPUs and devices to run those operating systems. eg. The SATA device only emulates the commands issued by drivers of modern operating systems, not every single command and dark corner of the real hardware.

To be fair there are emulators that try much harder to be cycle accurate, especially the ones designed to run old games. The MisTER is the current king here, but that uses an expensive FPGA and can just about emulate a 486 PC.

Re: Fun with Red Star OS

#24
post #8
post #7

Earlier quoted context omitted.

Apple would never write software that scans your files and reports material your XOR USG does not like, without your knowledge.

This must be sarcasm.

Poe's Law in action.[0]

[0] https://en.wikipedia.org/wiki/Poe's_law

Re: Fun with Red Star OS

#25
post #16
post #9

Earlier quoted context omitted.

This could be true, or it could recognize that it is running in a VM and change its behavior. This is a somewhat common trait of malware meant to throw off security researchers.

Why are VMs so bad at virtualizing? An ideal VM should be indistinguishable from a real machine. For example a virtualized system running Android should generate fake IMU data, not sit at 0 linear acceleration all the time. And have a real-looking fake IMEI, not a string of 0s.

Real hardware is finicky and complex. It would be very slow to virtualize every hardware device in a system to a level not distinguishable to software. If you do shoot for complete accuracy (e.g. projects like 86Box), you take at least a ~100x performance hit, and also lose out on useful features like dragging files into/out of the VM.

Re: Fun with Red Star OS

#28
post #16
post #9

Earlier quoted context omitted.

This could be true, or it could recognize that it is running in a VM and change its behavior. This is a somewhat common trait of malware meant to throw off security researchers.

Why are VMs so bad at virtualizing? An ideal VM should be indistinguishable from a real machine. For example a virtualized system running Android should generate fake IMU data, not sit at 0 linear acceleration all the time. And have a real-looking fake IMEI, not a string of 0s.

The goal is usually cooperative virtualisation, not adversarial virtualisation. Most people don't need to hide that the environment is a VM, because the OS and applications by and large don't care about that.

Re: Fun with Red Star OS

#29
post #13
post #2

Off-topic: the font in this blog renders very poorly. I know the solution is to disable remote fonts in ublock origin, but that means that websites that use fonts to show icons will not work properly. Has anybody found a solution?

> Has anybody found a solution? Frontend designers should stop using remote fonts, or fonts at all, for icons.

And all bad programmers should stop being bad programmers, easy.

Maybe if you don't have something useful to add to the conversation, you should refrain from adding anything at all.

Re: Fun with Red Star OS

#30
post #23
post #16

Earlier quoted context omitted.

Why are VMs so bad at virtualizing? An ideal VM should be indistinguishable from a real machine. For example a virtualized system running Android should generate fake IMU data, not sit at 0 linear acceleration all the time. And have a real-looking fake IMEI, not a string of 0s.

Hi, virt engineer here. Partly because it a very hard problem (in fact, theoretically impossible if you include timing attacks), but mainly because you don't need to emulate the hardware very accurately in order to get common operating systems to run. Getting them to run is all that we're paid to do, and that's a difficult enough job already. One strange aspect of this is that only a narrow range of current OSes run…

How does software-based x86 emulation (ie OG Connectix Virtual PC) compare to current hardware-assisted virtualization? Were older methods more cycle accurate than what’s in use now?
Post reply on HN