RPC and new user fuc**d!

  • Thread starter Thread starter pjp
  • Start date Start date
P

pjp

Friend down the road just started taking a home pc course. Brand new IBM
appears to be a fairly good system. She's had it two days and knows little
about pc's etc. She's proboably been on the net all of a couple of hours at
best.

So guess what. Today she's on the net and all of a sudden she starts getting
the "RPC ..." message and pc reboots.

There's no other way to put it, she's ****ed and will end up spending a pile
of money for someone else to fix the problem yet she did nothing "wrong"
except use MS's product as designed.

Am I the only one that feels MS should be held to some degree of
responsibility and liability for these kind of issues. At the least they
should be providing a 1-800# so novice customers can seek help. After all
they paid for a product that is advertised a "best ..., secure ... etc.
etc."

Christ it's like a used car dealer that only guarantees the car will start
and make it off the lot after that it's ...

To continue ...

Why the hell is some personal pc even using some Remote Procedure Call? For
that matter why's it even a feature? I don't want MY pc calling out to some
other pc to "execute" any "procedure". That just seems stupid to allow that
under any but the most strict of scenarios and certainly seems completely
inappropriate for a "home pc".
 
NO. A properly secured computer is completely safe. A firewall and a good AV
would have prevented this problem. It has been known about since July 17. UT
IS THE OWNERS RESPONSIBILITY TO SECURE THEIR OWN COMPUTER.

Testy
 
In
pjp said:
and will end up spending
a pile of money for someone else to fix the problem yet she did
nothing "wrong" except use MS's product as designed.

Am I the only one that feels MS should be held to some degree of
responsibility and liability for these kind of issues.
Click to expand...


Microsoft has known about this vulnerabilty, fixed it, and has
had a patch available for it on their site for almost a month.
Anyone who follows Microsoft's recommendations and downloads and
installs the critical updates promptly is protected.

It's hardly Microsoft's fault.
 
x-no-archive: yes

Ken Blake said:
In


Microsoft has known about this vulnerabilty, fixed it, and has
had a patch available for it on their site for almost a month.
Anyone who follows Microsoft's recommendations and downloads and
installs the critical updates promptly is protected.

It's hardly Microsoft's fault.
Click to expand...

OMG, did you just say that that this issue is NOT the fault of
Microsoft?

Wow are you an ingrained fanboy! Any car that needed critical security
recalls every three days would be pulled from the assembly line, and the
class action lawsuits would fly.

But getting back to your comments... Anyone who has installed the
critical updates is "protected"? Are you sure? No critical updates
ever get revised after the fact? Never get re-released? And what are
we "protected" from? All vulnerabilities? There are no more? And
Microsoft isn't at fault for the undiscovered flaws because why? Just
because they haven't been discovered yet?
 
Back
Top