Welcome to the Invelos forums. Please read the forum rules before posting.

Read access to our public forums is open to everyone. To post messages, a free registration is required.

If you have an Invelos account, sign in to post.

    Invelos Forums->General: General Discussion Page: 1  Previous   Next
A Computer Infection that Can Never Be Cured
Author Message
DVD Profiler Unlimited RegistrantStar ContributorSrehtims
Registered: March 13, 2007
United States Posts: 1,796
Posted:
PM this userView this user's DVD collectionDirect link to this postReply with quote
A Computer Infection that Can Never Be Cured
Click here
We don't need stinkin' IMDB's errors, we make our own.
Ineptocracy, You got to love it.
"Nearly all men can stand adversity, but if you want to test a man's character, give him power." - Abraham Lincoln
DVD Profiler Unlimited RegistrantBlair
Resistance is Futile!
Registered: October 30, 2008
United States Posts: 1,249
Posted:
PM this userDirect link to this postReply with quote
I had been reading this sort of idea for years. A few years ago I saw a test that was generally a failure but worked twice after much tweaking turning it into a proof of concept.

I'm surprised it has taken so long for this to get out into the open. Now watch the mass paranoia begin!

1984, we are one step closer to you.
If at first you don't succeed, skydiving isn't for you.

He who MUST get the last word in on a pointless, endless argument doesn't win. It makes him the bigger jerk.
 Last edited: by Blair
DVD Profiler Unlimited RegistrantStar ContributorMithi
Sushi Annihilator
Registered: March 13, 2007
Reputation: Superior Rating
Germany Posts: 2,217
Posted:
PM this userEmail this userVisit this user's homepageView this user's DVD collectionDirect link to this postReply with quote
a rather sensationalist head-line, as it can be cured quite easily (at least regarding the BIOS) by erasing the RAM-portion of the BIOS, usually done by a jumper on the mainboard. Afterwards you boot the system, the ROM will be copied into the RAM again and you can work with the machine again, most likely by installing the latest software BIOS at first.

As for seeing those in the wild: if they come, so will the programs (or specialized hardware) to counter them.

Not to mention that with the upcoming UEFI the whole affair smells a bit like an attempt to scare people into accepting UEFI with it's "Secure Boot" which could users chain to a single operation system.

cya, Mithi
Mithi's little XSLT tinkering - the power of XML --- DVD-Profiler Mini-Wiki
 Last edited: by Mithi
DVD Profiler Unlimited RegistrantStar ContributorLewis_Prothero
Strength Through Unity
Registered: May 19, 2007
Reputation: Superior Rating
Germany Posts: 6,730
Posted:
PM this userView this user's DVD collectionDirect link to this postReply with quote
@ Mithi:
If I understood the article correctly the premise is that the backdoor is hardware encoded or at least implemented into the original BIOS / UEFI so that a reset wouldn't actually help.

The article seems to be the usual xenophobic junk you can find everywhere on the net.
Replace "China" with a country of your own choice and "Surveillance Software" with a topic that is likely to raise interest (Biological Warfare would be a good start).

It's interesting that those people that discover such things always live in a country far away from the author of the article. German articles of this kind usually start with "American scientists found out that ..."
It all seems so stupid, it makes me want to give up!
But why should I give up, when it all seems so stupid?


Registrant since 05/22/2003
DVD Profiler Unlimited RegistrantStar ContributorSrehtims
Registered: March 13, 2007
United States Posts: 1,796
Posted:
PM this userView this user's DVD collectionDirect link to this postReply with quote
Before PCs it was pretty common practice for programmers to a backdoor into their software.

The egotist in charge of the operating system, didn't deem it necessary to terminate a specific locked up program. But a program could spawn off 64 copies of itself.

I was working for General Electrics Advanced System Technology Operation and we had a user of our system that was always hanging up our system. We ask that be fixed in the operating system. Our egotist ignored our request.

I knew of an instruction sequence which would cause fault and could not be interrupted. I put this program with the spawning capability out on his system. As soon as this program ran the speedometer on the system hit max and everything stopped. On the console the did a list of programs, thousands of them. They were PO.
But since I didn't work for the computer department they couldn't do anything. We had a long standing battle, earlier I wanted to show him a bug that allowed any parogram to get into master mode, thus access tot the operating system. Every time I saw his user ID i terminated his program. It didn't take him long to fix that.

Programming was fun back then.
We don't need stinkin' IMDB's errors, we make our own.
Ineptocracy, You got to love it.
"Nearly all men can stand adversity, but if you want to test a man's character, give him power." - Abraham Lincoln
DVD Profiler Unlimited RegistrantBlair
Resistance is Futile!
Registered: October 30, 2008
United States Posts: 1,249
Posted:
PM this userDirect link to this postReply with quote
Quoting Srehtims:
Quote:
Programming was fun back then.

I agree. I was 6 when PCs were barely hitting the market. Through the aid of code snippits on the last page of a magazine twice a month and a reference guide, I quickly learned BASIC (QBASIC, actually) and would play around to see what I could do without actually breaking anything.

The first 'What is going on here?!' code that I ever created was a simple "if/then goto" loop that loaded in a BAT file at startup. But, again, it was fun because I knew what the problem was and was there to be able to stop it. I never created anything to cause permanent damage nor did I place something on a computer, leave, and imagine what they are going through trying to fix the issue. What would be the fun in creating a little confusion if you weren't there to see it?

Things have changed, though. You have people wanting to cause as much damage as possible for amusement and others who are just curious or trying to be helpful ("If I can create the threat before the bad guy does, it will put me one step ahead in working on countermeasures.") but unfortunately this can also accelerate the creation of more damaging viruses by giving people ideas that they had not worked out before to create them.


A few weeks ago I was reading through "10 worst computer viruses" articles, curious what each viruses different editors might agree on. One article at HowStuffWorks took a different approach not focusing solely on the worst Microsoft Windows OS viruses. It included a virus for Mac computers and another that attacked cell phones.
If at first you don't succeed, skydiving isn't for you.

He who MUST get the last word in on a pointless, endless argument doesn't win. It makes him the bigger jerk.
 Last edited: by Blair
    Invelos Forums->General: General Discussion Page: 1  Previous   Next