|
![]() |
|
Thread Tools | Search this Thread |
![]() |
#1 |
Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 40
Karma: 6042
Join Date: Nov 2011
Device: SONY PRS505
|
Possibility of using old NST/NSTG with proxy/certificate update
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. |
![]() |
![]() |
![]() |
#2 |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 38,882
Karma: 153006036
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
It may not be the certificates so much as the firmware does not support TLS 1.2+.
|
![]() |
![]() |
![]() |
#3 | |
Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 35
Karma: 1037
Join Date: Nov 2021
Device: Nook Simple Touch (2), Nook Simple Touch w/Glowlight (2)
|
Quote:
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. |
|
![]() |
![]() |
![]() |
#4 |
Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 48
Karma: 50000
Join Date: Nov 2017
Device: Nook, Kindle
|
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. |
![]() |
![]() |
![]() |
#5 |
Enthusiast
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 40
Karma: 6042
Join Date: Nov 2011
Device: SONY PRS505
|
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: Code:
sqlite3 devicemanager.db "UPDATE registry SET value=\"http://192.168.1.1:8080/bncloud/serviceD?version=1\" where _id=14 ;" Code:
mitmproxy Code:
mitmproxy --mode reverse:https://bncs.barnesandnoble.com/ However, it will not actually download books due to being unable to proxy Code:
https://netdelivery.barnesandnoble.com 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. |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Touch The NSTG turns 10 and gets a makeover! | nmyshkin | Barnes & Noble NOOK | 4 | 10-14-2022 02:36 PM |
Can't Update NST Glow | edent | Barnes & Noble NOOK | 4 | 08-06-2014 11:13 AM |
is a NST Glowlight worth upgrading from NST? | crashed | Which one should I buy? | 2 | 05-13-2012 12:55 PM |
Using calibre in a proxy. fetching metadata proxy authentication required | shiftymorgan | Calibre | 8 | 05-13-2011 03:45 AM |
possibility of future update improving boot time | thorne | enTourage Archive | 11 | 02-21-2011 11:10 PM |