Module manager offers enciphered modules with an empty CipherKey that can't be opened #83
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
schaefera/utStudyBIble#83
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found by the review of PR #82 (round 3), deferred from it.
sword/src/install/indextreats an entry whose conf hasCipherKey=(present but empty) as not locked, so the catalog offers it and it installs. After that,Module::from_confrefuses it, so it never appears in the Bible chooser: the user installs something they cannot use.Entries with a non-empty
CipherKeyare already marked locked and cannot be installed.Fix: in the index parser, treat a present
CipherKeykey (empty or not) as locked, or hide it as unusable, matchingfrom_conf. Add a test with an empty-CipherKey conf. This is a trunk path (sword/src/install*).Priority Should: this needs a repository that lists such a module, which is rare in the CrossWire lists, and the effect is a module that is installed but unusable, not data loss.