|
Two thoughts occured to me after sleeping on the question -
Disabling a client protocol in the ssl libraries would do nothing for the non-encrypted clients.
There must be other places the change was made.
(If it is in the Amazon code, we are SoL.)
It might help if we knew what was common between 2.5.8, 3.4.1 and 3.4.2, after discarding identical files, it might be easier to judge if it is even worth looking deeper into the fix.
I will try to get some numbers on that question today by running the cataloging/audit scripts on a tree of the three source bundles.
- - - -
A third thought occured to me while writing this post.
If Amazon is still selling re-furbished DX/DXG devices, did they re-furbish the firmware also?
Perhaps some of our members who have recently purchased one of these re-furbished devices could tell us it the problem was 'fixed' by the re-furbisher.
I have at least one each, of each K2, DX and DXG model.
We could do a search for the "binary solution" if the re-furbished devices have been fixed and the owner will share a copy of the re-furbished firmware that is installed.
(I am certain that I still have the scripting to copy-out a DX image, the script I wrote for twobob.)
|