QUOTE(some11 @ Apr 22 2010, 10:26 AM)
Sorry for being a n00b. but I dont get it.
What does this mean to me?!
If you have noticed, everytime you get a key from a drive, JF says "Storing key in DB" or something like that. I think it's a separate file either in your app data or in the JF directory on your computer.
But anyway, it sounds like this is 2 fold.
First (for lite-ons at least), they talk about verifying the key against the bar code. So that means that there's no longer any guessing about whether or not you get the right key before erasing the drive. You don't have to pull out an old drive, put it on there, and test to make sure that you really do have the right key. It will just say "This key matches this drive" or something like that.
The other thing it sounds like is...imagine you have lost the original files created when you dump the key (The OFW or the lite on dummy dumps). Even though you have lost the files, you should still have the key on your computer in the JF database. Their new findings will allow them to try every key you have saved in your DB until it finds the right one. Pretty cool I guess.
It can also be used for simplification. Lets say you just want to upgrade your drive to a newer firmware version. Upon querying the drive, it sounds like JF will be smart enough to load the right key and data for you automatically from the DB without you needing to manually get the firmware off the drive again, or loading your old dump files.
Thats what I got from it anyway...feel free to correct