Touch Possibility of using old NST/NSTG with proxy/certificate update

[erk]

I have a couple of these ancient e-readers.

Putting aside the utterly insulting coupon offer, is it possible to work around the EOL?

Is there any information on what changed?

The most 'obvious' failure mode would be certificate provider changes, where the root certificate isn't in the old firmware - this seems straightforward to fix with rooted devices.

[DNSB]

It may not be the certificates so much as the firmware does not support TLS 1.2+.

[nmyshkin]

Originally Posted by erk

I have a couple of these ancient e-readers.

Putting aside the utterly insulting coupon offer, is it possible to work around the EOL?

Is there any information on what changed?

The most 'obvious' failure mode would be certificate provider changes, where the root certificate isn't in the old firmware - this seems straightforward to fix with rooted devices.

What is it exactly you want to "work around"? If you just want to run the device as registered, see "The Phoenix Project" : https://xdaforums.com/t/nst-g-the-ph...oject.4673934/

Otherwise, yes, it is possible to update some certificates but not to add TLS 1.2. The certificate for the Kindle app was updated awhile back and I did one a few years ago for FBReader sync.

[GeorgeYellow]

There are some intriguing possibilities here, should you wish to develop.

While I am unaware of any public research on the BN communication protocol, it is self-documented.

Given this lack of public research, it is unclear what the protocol changeover will look like, or when it will happen. There is nothing in the current APK to suggest something beyond new SSL, new certificates, and possibly version checking.

There is a single URL in a SQLITE3 database which you can change to point the store to a resource of your own choosing.

Depending on how the new server implements version checking, you may be able to proxy requests to the server with a corrected version. If the proxy rejects the private key identifiers from the older devices, you'd have to link the account to a new device.

Implementing a new store would be possible, and not even significant effort.

However, given the fragility of everything described in this post, the easiest way of continuing to use the NST/G is to use the pipeline of rooted Android through Calibre and then usb.

[erk]

I was semi-successfully able to connect into the Nook mothership with my rooted NST.

To do this, I modified [CODE]/data/data/com.bn.devicemanager/databases/devicemanager.db[/CODE
]

With:

sqlite3 devicemanager.db "UPDATE registry SET value=\"http://192.168.1.1:8080/bncloud/serviceD?version=1\" where _id=14 ;"

On the router, I ran

mitmproxy

using the command-line

mitmproxy --mode reverse:https://bncs.barnesandnoble.com/

The NST was able to see lists and recommendations.

However, it will not actually download books due to being unable to proxy

https://netdelivery.barnesandnoble.com

For this, I would need to enable "Transparent Proxying" and update the certificate files on the Nook.

Does anyone know if this works the same as Kindle, where there is a system certificate file and a Java certificate file?

My conclusion is that older Nooks are not yet banned from the store.