Quote:
Originally Posted by Leep
I think this makes sense to me via the people that are having problems and those that are not.
You're saying that those of us that have old adeptkeys are not having problems even though we have been forced to upgrade to DE 1.7.1 because the key script no longer finds the information needed to produce the adeptkey.der file, but we have a working key file? Very interesting. You'd have thought that the objective of forcing people to upgrade would be to change/hide the key so that neither the pdf or epub decrypting scripts would work.
thanks for your investigations
|
No I think that if you registered with an older DE version the key is still in the registry. If you upgrade the newer DE edition will use the old one (some kind of fallback - if Adobe would just change the key (method) the old e-books wouldn't work anymore). If you just installed the new one without legacy values in the registry it will create the new entry.
At the moment its ony a hunch derived from the reports I get. I haven't got these messages for myself so I can't walk through the problem.
If you want to do it right you have to compare an old with a new registry entry and see what the difference is. If that doesn't tell you much you have to debug the new DE which is probably not so much fun as it sounds
.
Anyway, I'm waiting for reproducible results (means the error doesn't come from a 'user failure') - until now we are fine with it.