4 ms·
It took about half a year, mostly slaving away in the evenings and my day off. That was mostly because the WD firmware is pretty complex: you gotta remember alm
by Sprite_tm 12y ago
It took about half a year, mostly slaving away in the evenings and my day off. That was mostly because the WD firmware is pretty complex: you gotta remember almost 20 years of ATA/SATA/... cruft is stored away in the firmware, and the firmware doesn't help you by having any strings embedded in it.
- rasz_pl 12y agoAny plans to open it all up now (after badusb folks opened their code at https://github.com/adamcaudill/Psychson https://github.com/adamcaudill/Psychson ) ? At this point mechanical drives are pretty much dinosaurs, it would be only useful to tinkerers.
- rsync 12y ago"At this point mechanical drives are pretty much dinosaurs, it would be only useful to tinkerers" That may be true for end users / consumers, but I think that the advent of ZFS makes this particularly interesting for anyone that uses that filesystem. The reason is, unlike most "RAID" that we've all used these past 20 years, ZFS does not want you to give it a raid set, or to put a raid controller between the disks and the OS. Instead, the best practice is to present the raw disk to ZFS and let it do all the work. But that means you're more exposed to funny business on the part of the drive, etc.
- Sprite_tm 12y agoI have, mostly. All my code, minus the directly-applicable shadow-password-hack thing ((to thwart script kiddies, if you're a bit knowledgable ytou should be able to re-implement it yourself) can be gotten from http://spritesmods.com/hddhack/hddhack.tgz http://spritesmods.com/hddhack/hddhack.tgz
- mojoe 12y agoYep, I know guys who worked at WD and they mentioned how cluttered their firmware is. They have an incredibly rigorous code check-in process, which means not a lot of code gets cleaned up, only more code gets added. It sounds like a mess. Thanks for the read!