[MIR] libmspack

Bug #1386991 reported by Scott Kitterman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libmspack (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

    Availability: libmspack is already be in Ubuntu universe and built for all architectures.

    Rationale: Clamav has used an embedded copy of libmspack for some time. In the current release, the ability to use an external, system version has been added. This would be better. Effectively the code is in Main already via clamav. Moving the libmspack package to Main is a better, more maintainable way to have it there. This is also used in LibreOffice, so having the system version in Main should help there too.

    Security: The security history and the current state of security issues in the package must allow us to support the package for at least 9 months (60 for LTS support) without exposing its users to an inappropriate level of security risks. This requires checking of several things that are explained in detail in the subsection Security checks.

    Quality assurance: Package is a library that needs no configuration and asks no questions. There are no open bugs in Debian or Ubuntu. Upstream seems quiescent, but not dead. There do not appear to be any long term issues that would impact supportability.

There are no open bugs in Ubuntu or Debian, but I couldn't find an upstream bug tracker:
https://bugs.launchpad.net/ubuntu/+source/libmspack
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=libmspack

The package is well done and meets standard MIR requirements such a symbols file, watch file, etc.

The package does not deal with exotic hardware.

    UI standards: N/A

    Dependencies: All depends/build-dep are in Main

    Standards compliance/Maintenance: Standards compliance is good. Packaging is a very vanilla dh7 with autofoo package that is trivial to understand. Maintained in Debian and synced. If approved, I'll subscribe the clamav team to bugs. This is a pretty simple package.

    Background information: See above. Already in Main due to embedding in clamav and other packages.

Security checks

    Check how many vulnerabilities the package had in the past and how they were handled by upstream and the Debian/Ubuntu package:

        http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libmspack - Three CVEs one in 2005 (of the embedded copy in clamav) and two in 2010. Nothing since.

        http://secunia.com/advisories/search/?search=libmspack reports are similar. All are resolved.

        Ubuntu CVE Tracker: Nothing listed.

    Security relevant binaries: This is a package that unpacks various formats of often untrusted data (particularly in the clamav use) so it's inherently security sensitive to a degree.

Changed in libmspack (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Adam Conrad (adconrad) wrote :

This looks fine to me. ScottK assures me that the embedded copy is the same version, so this is really just shuffling code around to make it less opaque and more maintainable. Would be good if we could eliminate other embedded copies in the same pass, but getting more consumers for the library shouldn't block the MIR for clamav's sake. ACKing and promoting.

Revision history for this message
Adam Conrad (adconrad) wrote :

Override component to main
libmspack 0.4-1 in vivid: universe/misc -> main
libmspack-dbg 0.4-1 in vivid amd64: universe/debug/extra/100% -> main
libmspack-dbg 0.4-1 in vivid arm64: universe/debug/extra/100% -> main
libmspack-dbg 0.4-1 in vivid armhf: universe/debug/extra/100% -> main
libmspack-dbg 0.4-1 in vivid i386: universe/debug/extra/100% -> main
libmspack-dbg 0.4-1 in vivid powerpc: universe/debug/extra/100% -> main
libmspack-dbg 0.4-1 in vivid ppc64el: universe/debug/extra/100% -> main
libmspack-dev 0.4-1 in vivid amd64: universe/libdevel/optional/100% -> main
libmspack-dev 0.4-1 in vivid arm64: universe/libdevel/optional/100% -> main
libmspack-dev 0.4-1 in vivid armhf: universe/libdevel/optional/100% -> main
libmspack-dev 0.4-1 in vivid i386: universe/libdevel/optional/100% -> main
libmspack-dev 0.4-1 in vivid powerpc: universe/libdevel/optional/100% -> main
libmspack-dev 0.4-1 in vivid ppc64el: universe/libdevel/optional/100% -> main
libmspack-doc 0.4-1 in vivid amd64: universe/doc/optional/100% -> main
libmspack-doc 0.4-1 in vivid arm64: universe/doc/optional/100% -> main
libmspack-doc 0.4-1 in vivid armhf: universe/doc/optional/100% -> main
libmspack-doc 0.4-1 in vivid i386: universe/doc/optional/100% -> main
libmspack-doc 0.4-1 in vivid powerpc: universe/doc/optional/100% -> main
libmspack-doc 0.4-1 in vivid ppc64el: universe/doc/optional/100% -> main
libmspack0 0.4-1 in vivid amd64: universe/libs/optional/100% -> main
libmspack0 0.4-1 in vivid arm64: universe/libs/optional/100% -> main
libmspack0 0.4-1 in vivid armhf: universe/libs/optional/100% -> main
libmspack0 0.4-1 in vivid i386: universe/libs/optional/100% -> main
libmspack0 0.4-1 in vivid powerpc: universe/libs/optional/100% -> main
libmspack0 0.4-1 in vivid ppc64el: universe/libs/optional/100% -> main
Override [y|N]? y
25 publications overridden.

Changed in libmspack (Ubuntu):
status: New → Fix Released
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

mspack seems to be long gone in LibreOffice -- the last commit I found refering to it is:

 https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=a1a5161af5d5c468849716688befdd0a7d5cfd53;hp=21c53810716624eb53dd4f06228c86064fa800d8

Actually, if any LibreOffice version ever had mspack, it was ancient versions 3.3/3.4.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 1386991] Re: [MIR] libmspack

On Wednesday, October 29, 2014 12:51:16 you wrote:
> mspack seems to be long gone in LibreOffice -- the last commit I found
> refering to it is:
>
> https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=a1a5161af5d5
> c468849716688befdd0a7d5cfd53;hp=21c53810716624eb53dd4f06228c86064fa800d8
>
> Actually, if any LibreOffice version ever had mspack, it was ancient
> versions 3.3/3.4.

Thanks for checking. My mistake.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.