-
Notifications
You must be signed in to change notification settings - Fork 153
Description
Guidelines
- I have read the FAQ and it doesn't cover my request.
- I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
- I'm on the latest version.
- I'm not using a test build (alpha/beta/release-candidate).
- This issue contains only one feature request.
Problem Description
One of the benefits of asymmetric encryption (compared to symmetric one) is that you don't need to know the private key (which is password protected) to encrypt the message.
In fact the way it is generally implemented is that data is encrypted with symmetric key, then that key is encrypted using asymmetric one (because asymmetric encryption is slow).
The FAQ says this feature is implemented, but if I don't specify the key in configuration the encryption is not used (I should not need to specify it).
Also either I'm doing something wrong, or it is a bug, but whenever I generate PGP key, Neo Backup creates a file that has 0 bytes. Perhaps I'm providing a wrong value for user id?
Proposed Solution
This is how it worked in Titanium Backup (RIP), the manual and scheduled backups did not require password, (the password was not stored). You only needed to provide a password when you needed to restore a backup.
Is it possible to make Neo-Backup work this way?
Alternatives Considered
No response
Relevant information
- Device: Sony Xperia 5 III
- Android Version: 12
- ROM: AOSP
- App's Version: 8.3.12