TurboTax DRM Writes to Your Boot Sector?!
ltwally writes "As reported on Slashdot (amongst other sites) recently, the latest version of TurboTax is laden with DRM software. Even worse, however, is that it apparently writes to your hard drive's boot-sector , as reported at Extreme Tech here. As I'm sure most Slashdotters already know, the boot-sector is often times used for silly things like boot-loaders and such. "
CDilla's LMS does this too, although I'm not completely convinced it's the bootsector. Still, nothing short of a low level format clears it, so it probably is.
Resistance is futile. Reactance buggers it up.
This software does NOT write to your boot sector. It writes to sector 33 on the track which contiains the boot sector.
This is certainly a Bad Thing, but not nearly as bad as writing to the boot sector would be.
Tarsnap: Online backups for the truly paranoid
If you insist on using TurboTax, use their web-based vesion; it's alway current and no software gets installed on your PC.
Personally, even though I've been using TurboTax for over 10 years, I will be using a different tax preparerer this year. I find their association with this kind of DRM crap distastful.
Can You Say Linux? I Knew That You Could.
~jeff
As I understand it, a program running as Administrator on NT can elevate its privileges to LocalSystem and do just about anything, such as write sectors to physical drives.
Will I retire or break 10K?
I vaguely remember reading on a Mac site that the TurboTax packaging rather explicitly states that the product will not run in any kind of Windows emulator (the article of course was talking about Connectix Virtual PC).
If that's the case, this boot-sector thing might be a major part of the reason why.
~Philly
.. any word on how it impacts a dual-boot box? So far, so good. I've got TT installed in WIN98. I run a triple-boot WIN98/RH8.0/Mandrake9.0, using RedHat's Grub. Works fine, boots fine.
Intuit's still a bunch of SOBs for doing such a dangerous thing, though.
"If, therefore, any be unhappy, let him remember that he is unhappy by reason of himself alone."
~Epictetus
Infact, only an os installer should write to the boot sector, anything else should be considered a virus. Infact many bioses have the option to detect and block attempts to write to the bootsector under the name of bootsector virus protection.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
I would bet the farm on the fact you could do it with VMWare. I have found that OSes installed on VMware have no knowledge of their host operating systems, nor does any disk activity from the VMware OS have any affect on the host's partitions/drives, because the 'disk' is actually just a file.
Because the mac version was $10 more AND none of the rebates in store would apply.
Karma: Chameleon (mostly due to the fact that you come and go).
it writes to the boot *track,* so it's not going to munge your partition table, but may well munge other important boot records.
Nothing belongs in that *track* other than boot information. Period.
KFG
like, by the article and stuff, it doesn't write to the MBR. It writes to sector 33 of the boot *track.*
The problem is that since the entire track is reserved for boot information, not just the sector holding your MBR, things like LILO and GRUB may be residing there as well.
Boot loaders are legitimate boot records. Software registration codes are not. They don't belong in the boot track, whether they write to the MBR or not.
KFG
Yep, it works with VMware. That's how I installed it, after reading the earlier /. story. One thing, though, you need to turn off the "hardware acceleration" in the VM configuration while starting the program (after that, you can turn acceleration back on).
After reading the earlier stories about locking to a particular machine, and possibly installing spyware, I figured I'd either return the thing or install it under VMware. The geek in me won out, so I decided to see how it'd work under VMware. I'm sure glad I didn't install it on a PC directly.
-Steve
Democracy is a poor substitute for liberty.
The defragger runs as a native NT application, not a win32 application - it needs this because it needs to be able to run before the win32 layer is loaded up. You don't need to do that kind of thing to write to the boot track, you just need Admin privledges. Details on the difference between the NT API and the win32 wrapper API for it can be found at Sysinternals.com. You can do some nifty stuff with an NT-native application, like writing Registry entries that can only be removed or modified by other NT applications, and not by anything running in the win32 layer.
I just sent this to public_relations@intuit.com, if other people do the same, InTuit will get the message that the upsets customers. No garauntee they will stop, but at least they'll no it upsets us.
7 3,881243, 00.asp
1 549232.shtm l?tid=185
"I'm a potential customer for TurboTax software. A recent discussion held at the Slashdot forum indicates that TurboTax is laden with DRM (Digital Rights Management) components, and even goes so far as to write to the boot sector of the hard drive. I wanted to know how InTuit responds to this. I can't support a company who would include such measures in their software. I understand the need to prevent piracy, but writing to the boot sector is something that only disk partitioning software and operating system installers should do. I'm eager to hear InTuits response on this matter, as it will be the deciding factor in whether I buy InTuit software.
Here are some links to the sites I am obtaining information from.
Original article claiming the action:
http://www.extremetech.com/article2/0,39
Pursuant discussion on Slashdot:
http://slashdot.org/articles/03/02/16/
PS - I'm posting a copy of this to the Slashdot forum, and intend to forward the reply to Slashdot as well."
Get This.
TurboTax also broke my DX8.1 install. Turns out, those fancy movies that come with it are Macrovision encoded. NT user? check your Services for a magical new service (I can't remember the name, I've long since ripped it a new one) which even if you disable it, running turbotax fires it right back up to automatic. Lord this gives me a new reason to get a full refund from them. How can one tell if their bootsector has some extra bits in it?
A year ago I bought the then new Logitech dual pickup optical mouse and installed the drivers from the included CD. The install looked kind of suspicious so I ran ad-aware. It reported some kind of spyware components so I removed them. The system was clean before I installed the drivers.
This really blew my mind at the time. I can see someone who provides free software doing that using the excuse that they need to make money and pay the employees, etc. But spyware with a $49.99 USA mouse ! Jeez...............
A few lawsuits for system damage by SafeCast right now wouldn't hurt either.
So what is a good utility to inspect and clean all this crap off of boot sectors 1-63, even if it does make limited-time demos forget their earlier installs?
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
Don't thank me, thank Google Sets. :)
4 0FormT axes com
TaxACT
TurboTax
TaxCut
Taxslayer
Taxcut Deluxe
TurboTax Deluxe
HD Vest
E1040 com
TaxBrain
CompleteTax
e1065
TaxesByCPA
10
TaxLogic
FileSafe
eTax YourPace
EZTaxMachine
Tax Engine
AccuTax
TaxConnection
TaxGaga
FileYour
1040 net
Taxes1 com
It fucked up my f-prot installation.
On top of that, the one-click update just sat there, so I had to download the update program and run it manually. That farked up the turbotax installation entirely. It wouldn't even run anymore. It was in the task list, but nothing worked.
Uninstalled it and reinstalled it a few times, but it didn't help. Followed the instructions on the website completely, but no luck. I spent the entire day yesterday trying to get turbotax to work.
I *had* planned on getting my taxes done this weekend. That plan was shot to hell.
I uninstalled it, and took it back to Walmart today. They didn't give me a hassle over the fact that it had been opened. I was surprised but pleased about that, since the in2it web site refund page seems to require an order number.
I hope they ship it back rather than selling it to someone else, since the drm activation took place. That serial number won't work for anyone else now.
I will never purchase turbotax again. All this hassle for a stinking $20 one-use product. They might eliminate the 5-20% piracy that might have existed, but only at the cost of losing 60% of their sales.