View Single Post
Old Yesterday, 04:03 PM   #5
DeLitCommonPotoo
Member
DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!DeLitCommonPotoo rocks like Gibraltar!
 
Posts: 13
Karma: 100010
Join Date: Mar 2026
Device: Kindle Paperwhite 11th Gen
Quote:
Originally Posted by batonebo View Post
Thorium is unnecessary, you can simply decrypt the epub/pdf/etc directly.

This (local) browser-based file (download and open in browser) does the whole decryption alone. Source code at rad:z41uCZqyBUSRQoBCQq4Bpq8ZSCHKr (radicle repository)
Oooh, extremely nice!

Hard to argue that a standalone (Thorium-less) Rust-based CLI (or WASM single-page web interface) is anything other than a much nicer user experience!!!

Curious though, am I reading it correctly that the extent to which spoofing goes when fetching the encrypted epub is to set the User-Agent to "ThoriumReader/windows-mac-linux/1.1"?

I guess one reason I opted for the "remoting Thorium approach" (other than the obvious of not having the cryptographic know-how to implement what's in that radicle repo), is that I perceived doing so (perhaps naively?) as being a little bit safer in terms of potential risk of being e.g. blacklisted by stores or license providers...

Do you know if Thorium itself uses that User-Agent internally? Or whether this simple spoofing approach has otherwise been used widely in the past without issue?
DeLitCommonPotoo is offline   Reply With Quote