This is a React Native mobile application that works together with a Node.js API to recursively search through the content of ".tar.gz" files. It can be used for a wide variety of purposes, such as a text-only self-hosted Wikipedia, StackOverflow, or perhaps as a quick way to search through backed up messages or other forms of text data.
- Download the source code, and use something like NSSM or a cron job to make sure the API is always running.
- After running the API code for the first time, it should create a folder called "config", and a file called "pin.txt" inside it. Use an online (preferably offline) bcrypt hashing tool to hash a desired password, and copy-paste it into the "pin.txt" file. So for example, you could go to this website, and where it says "String to encrypt", you'd write a desired password; for this example I'll enter "test". The hash should look something like this: $2y$12$lU0Pqm2Em6jbLS0b79ENtulmIB7uGEqtagyZ7wQNgHjWuK.PMxLua. You can then copy-paste the generated hash into the "pin.txt" file so that its only contents are that string.
- Install the app by downloading the APK file from the "Releases" section.
- Open the app, and tap on the settings icon on the top right.
- Enter the IP address of the server the API is hosted on (without the "http://"), the port the API is using (970 by default), and the plaintext version of the password you hashed in step 2.
- Tap on the "Save Configuration" button.
- Any ".tar.gz" files you place outside the API folder will now show up in the "Files" page of the app. Since the API recursively looks for files, you can put them in subdirectories and they'd still show up.
- Select files you'd like to search the content of, go to the "Search" page, enter a search query, and tap on "Search X Files" (where X should be the number of files you selected).
The first 1,000 matches will be shown, but since the app starts lagging after that, the results are truncated.
To view previous searches, go to the "History" page.
Active searches can be cancelled by tapping on the "Cancel" button after starting the search. If you leave the "Search" page, the button won't be there anymore. To cancel a search without the button, you'll have to delete the output file by holding down on it in the "History" page.
It should be, yes. The API and app both use encryption since version 1.1.0. Both the server and client generate RSA keys (the private keys are never shared or sent to one another), and most of the data is encrypted with AES-256-CTR by them before being sent as either a request or response. The only data that isn't encrypted is the ID of the output files, but this is useless and can't be used to gain access to the actual data or output content.
To describe an example scenario such as the app requesting the list of files the server has, the following would happen:
The server's public key is requested by the app. The user's PIN is encrypted with AES-256, and the AES-256 key is encrypted with the server's public key. The user's public key is then sent to the "/files" endpoint of the API along with the encrypted PIN. The server uses its private key to decrypt the AES key, and uses the AES key to decrypt the PIN. It then fetches the list of files, encrypts it using AES, encrypts the AES key with the user's public key, and sends it back. The user finally uses their private key to decrypt the AES key, and uses the AES key to decrypt the list of files, which get shown to the user. The IV (initialization vector) used by AES is different each time as well.
