posted on Apr, 19 2010 @ 12:42 PM
Originally posted by LieBuster
reply to post by discordantone
Trouble is 60% of all new laptops have a ET call home program built into the bios so even if you take a hammer to your hard drive and run sco unix you
are still being watched and beleive it or not but even printers are printing a hidden bit pattern on each page so they can watch you.
Some laser printers do this. However, we do both ports and core mods to BIOSes for classified projects (we're one of the few), I've got ports to
quite a few chipsets here on the source safe, and not a one has an "ET call home program" in it. And yes, they're all in source code, no bin files
except for what we generate.
I'm not even sure how an OS call could call a BIOS routine outside of the ACPI stuff. There's very little in there that's in a form that a
protected mode OS could use.
On startup, it's definitely not "calling home". About the only thing in there that uses the Ethernet is the net boot routine, if it's enabled.
It's a real pain to do some of this stuff at the BIOS level - it's all assembler.
Yeah i know it sounds like science fiction but do a google and let me know if you think i'm wrong.
Ok, I think you're wrong. Not so much on the printer thing, but definitely on the BIOS issue.
MAC Address + IP + HTTP was never about protecting uses and was allways about tracking users and 1984 with Google/EBAY/YouTube being the bigest
players trying to fight it out with MS.
How do you expect the data to find their way back to you, with no fixed address? I don't believe I've EVER seen any sort of multi-drop data network
that didn't have to have some way of identifying sender and receiver in the protocol wrapper.