Bug 81155 - Extension Manager: Integrity Check mechanism should be implemented to avoid installing broken extensions
Summary: Extension Manager: Integrity Check mechanism should be implemented to avoid i...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
Version:
(earliest affected)
4.4.0.0.alpha0+ Master
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Extension-Manager
  Show dependency tree / graph
 
Reported: 2014-07-10 08:05 UTC by Kevin Suo
Modified: 2020-02-11 20:48 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Suo 2014-07-10 08:05:38 UTC 
This idea comes from bug 81143.

It was a time when I installed an extension, but after installaion I found that extension does not work at all, and I tried to remove it but failed.
Then reset my user profile, downloaded the extension again and installed again, now that extension works as expected.

Then I have an idea that, libreoffice should include the checksum info in the extension packages, and when isntalling, extension manager should check the integrity of the package.

By now, it's even possible to install an empty extension to libreoffice (create a new empty text file "test.oxt", then it can be installed to libreoffice).

As the official extension repo is growing, it's important to have this checksum mechanism to avoid broken packages.
Comment 1 tommy27 2014-07-12 04:55:13 UTC 
+1 valuable suggestion. status NEW