Debian Package Tracker
Register | Log in
Subscribe

quagga

network routing daemons (metapackage)

Choose email to subscribe with

general
  • source: quagga (main)
  • version: 1.2.4-4
  • maintainer: Brett Parker (DMD) (DM)
  • arch: all any
  • std-ver: 4.1.1
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 0.99.23.1-1+deb8u5
  • o-o-sec: 0.99.23.1-1+deb8u5
  • oldstable: 1.1.1-3+deb9u2
  • old-sec: 1.1.1-3+deb9u2
  • stable: 1.2.4-3
  • unstable: 1.2.4-4
versioned links
  • 0.99.23.1-1+deb8u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.1.1-3+deb9u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.2.4-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1.2.4-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • quagga (13 bugs: 0, 12, 1, 0)
  • quagga-bgpd (1 bugs: 0, 1, 0, 0)
  • quagga-core (1 bugs: 0, 1, 0, 0)
  • quagga-doc
  • quagga-isisd
  • quagga-ospf6d
  • quagga-ospfd
  • quagga-pimd
  • quagga-ripd
  • quagga-ripngd
action needed
The VCS repository is not up to date, push the missing commits. high
vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.
Created: 2019-08-02 Last update: 2021-01-17 17:37
lintian reports 10 errors and 3 warnings high
Lintian reports 10 errors and 3 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2020-07-29 Last update: 2020-08-22 06:06
1 security issue in sid high
There is 1 open security issue in sid.
1 important issue:
  • CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).
Please fix it.
Created: 2017-07-28 Last update: 2020-08-07 06:08
The package has not entered testing even though the delay is over normal
The package has not entered testing even though the 2-day delay is over. Check why.
Created: 2020-08-05 Last update: 2021-01-24 07:04
1 bug tagged patch in the BTS normal
The BTS contains patches fixing 1 bug, consider including or untagging them.
Created: 2020-10-19 Last update: 2021-01-24 07:02
Depends on packages which need a new maintainer normal
The packages that quagga depends on which need a new maintainer are:
  • dh-exec (#851746)
    • Build-Depends: dh-exec
Created: 2019-11-22 Last update: 2021-01-24 05:32
Multiarch hinter reports 1 issue(s) low
There are issues with the multiarch metadata for this package.
  • quagga-doc could be marked Multi-Arch: foreign
Created: 2016-09-14 Last update: 2021-01-24 05:06
1 ignored security issue in stretch low
There is 1 open security issue in stretch.
1 issue skipped by the security teams:
  • CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).
Please fix it.
Created: 2017-07-28 Last update: 2020-08-07 06:08
1 ignored security issue in buster low
There is 1 open security issue in buster.
1 issue skipped by the security teams:
  • CVE-2017-3224: Open Shortest Path First (OSPF) protocol implementations may improperly determine Link State Advertisement (LSA) recency for LSAs with MaxSequenceNumber. According to RFC 2328 section 13.1, for two instances of the same LSA, recency is determined by first comparing sequence numbers, then checksums, and finally MaxAge. In a case where the sequence numbers are the same, the LSA with the larger checksum is considered more recent, and will not be flushed from the Link State Database (LSDB). Since the RFC does not explicitly state that the values of links carried by a LSA must be the same when prematurely aging a self-originating LSA with MaxSequenceNumber, it is possible in vulnerable OSPF implementations for an attacker to craft a LSA with MaxSequenceNumber and invalid links that will result in a larger checksum and thus a 'newer' LSA that will not be flushed from the LSDB. Propagation of the crafted LSA can result in the erasure or alteration of the routing tables of routers within the routing domain, creating a denial of service condition or the re-routing of traffic on the network. CVE-2017-3224 has been reserved for Quagga and downstream implementations (SUSE, openSUSE, and Red Hat packages).
Please fix it.
Created: 2018-03-24 Last update: 2020-08-07 06:08
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.5.1 instead of 4.1.1).
Created: 2018-02-16 Last update: 2020-11-17 05:41
testing migrations
  • excuses:
    • Migration status for quagga (- to 1.2.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • Updating quagga introduces new bugs: #957737, #964404
    • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/q/quagga.html
    • Required age reduced by 3 days because of autopkgtest
    • 541 days old (needed 2 days)
    • Not considered
news
[rss feed]
  • [2020-08-06] quagga REMOVED from testing (Debian testing watch)
  • [2019-08-04] quagga 1.2.4-4 MIGRATED to testing (Debian testing watch)
  • [2019-08-02] Accepted quagga 1.2.4-4 (source) into unstable (Brett Parker)
  • [2019-01-29] quagga 1.2.4-3 MIGRATED to testing (Debian testing watch)
  • [2019-01-26] Accepted quagga 1.2.4-3 (source amd64 all) into unstable (Brett Parker)
  • [2018-04-13] quagga 1.2.4-2 MIGRATED to testing (Debian testing watch)
  • [2018-04-02] Accepted quagga 1.2.4-2 (source) into unstable (Brett Parker) (signed by: Steve McIntyre)
  • [2018-03-24] quagga 1.2.4-1 MIGRATED to testing (Debian testing watch)
  • [2018-03-18] Accepted quagga 1.2.4-1 (source) into unstable (Brett Parker) (signed by: Steve McIntyre)
  • [2018-03-18] quagga REMOVED from testing (Debian testing watch)
  • [2018-02-23] Accepted quagga 0.99.23.1-1+deb8u5 (all source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Salvatore Bonaccorso)
  • [2018-02-23] Accepted quagga 1.1.1-3+deb9u2 (source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
  • [2018-02-16] Accepted quagga 0.99.22.4-1+wheezy3+deb7u3 (source amd64 all) into oldoldstable (Thorsten Alteholz)
  • [2017-11-18] Accepted quagga 0.99.23.1-1+deb8u4 (all source) into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates (Salvatore Bonaccorso)
  • [2017-11-14] quagga 1.2.2-1 MIGRATED to testing (Debian testing watch)
  • [2017-11-12] Accepted quagga 1.1.1-3+deb9u1 (source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
  • [2017-11-12] Accepted quagga 1.2.2-1 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2017-10-31] Accepted quagga 0.99.22.4-1+wheezy3+deb7u2 (source amd64 all) into oldoldstable (Hugo Lefeuvre)
  • [2017-04-09] quagga 1.1.1-3 MIGRATED to testing (Debian testing watch)
  • [2017-04-06] Accepted quagga 1.1.1-3 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2017-04-04] quagga 1.1.1-2 MIGRATED to testing (Debian testing watch)
  • [2017-03-29] Accepted quagga 1.1.1-2 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2017-02-12] quagga 1.1.1-1 MIGRATED to testing (Debian testing watch)
  • [2017-01-27] Accepted quagga 1.1.1-1 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2017-01-14] quagga 1.1.0-3 MIGRATED to testing (Debian testing watch)
  • [2017-01-03] Accepted quagga 1.1.0-3 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2016-12-20] quagga 1.1.0-2 MIGRATED to testing (Debian testing watch)
  • [2016-12-09] Accepted quagga 1.1.0-2 (source amd64 all) into unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2016-11-30] Accepted quagga 1.1.0-1 (source amd64 all) into unstable, unstable (Scott Leggett) (signed by: Vincent Bernat)
  • [2016-10-21] quagga 1.0.20160315-3 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 18
  • RC: 2
  • I&N: 15
  • M&W: 1
  • F&P: 0
  • patch: 1
links
  • homepage
  • lintian (10, 3)
  • buildd: logs, clang, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 1.2.4-4ubuntu1
  • 9 bugs
  • patches for 1.2.4-4ubuntu1

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing