Debian Package Tracker - jakarta-jmeter

general

source: jakarta-jmeter (main)
version: 2.13-4
maintainer: Debian Java Maintainers (archive) [DMD]
uploaders: Emmanuel Bourg [DMD] – Onkar Shinde [DMD]
arch: all
std-ver: 4.1.5
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.5.1-1
oldstable: 2.11-2+deb8u1
old-bpo: 2.13-1~bpo8+1
stable: 2.13-2
testing: 2.13-4
unstable: 2.13-4

versioned links

2.5.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.11-2+deb8u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.13-1~bpo8+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.13-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.13-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

jmeter
jmeter-apidoc
jmeter-ftp
jmeter-help
jmeter-http
jmeter-java
jmeter-jms
jmeter-junit
jmeter-ldap
jmeter-mail
jmeter-mongodb
jmeter-tcp

action needed

A new upstream version is available: 4.0 high

A new upstream version 4.0 is available, you should consider packaging it.

Created: 2017-11-21 Last update: 2018-09-19 13:15

lintian reports 15 warnings high

Lintian reports 15 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2015-03-07 Last update: 2018-08-14 07:53

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2018-1287: In Apache JMeter 2.X and 3.X, when using Distributed Test only (RMI based), jmeter server binds RMI Registry to wildcard host. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.
CVE-2018-1297: When using Distributed Test only (RMI based), Apache JMeter 2.x and 3.x uses an unsecured RMI connection. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.

Please fix them.

Created: 2018-02-11 Last update: 2018-08-06 08:04

2 security issues in buster high

There are 2 open security issues in buster.

2 important issues:

CVE-2018-1287: In Apache JMeter 2.X and 3.X, when using Distributed Test only (RMI based), jmeter server binds RMI Registry to wildcard host. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.
CVE-2018-1297: When using Distributed Test only (RMI based), Apache JMeter 2.x and 3.x uses an unsecured RMI connection. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.

Please fix them.

Created: 2018-08-06 Last update: 2018-08-06 08:04

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2018-09-11 Last update: 2018-09-19 17:35

Multiarch hinter reports 2 issue(s) low

There are issues with the multiarch metadata for this package.

jmeter-apidoc could be marked Multi-Arch: foreign
jmeter-help could be marked Multi-Arch: foreign

Created: 2016-09-14 Last update: 2018-09-19 17:19

2 ignored security issues in jessie low

There are 2 open security issues in jessie.

2 issues skipped by the security teams:

CVE-2018-1287: In Apache JMeter 2.X and 3.X, when using Distributed Test only (RMI based), jmeter server binds RMI Registry to wildcard host. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.
CVE-2018-1297: When using Distributed Test only (RMI based), Apache JMeter 2.x and 3.x uses an unsecured RMI connection. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.

Please fix them.

Created: 2018-02-11 Last update: 2018-08-06 08:04

2 ignored security issues in stretch low

There are 2 open security issues in stretch.

2 issues skipped by the security teams:

CVE-2018-1287: In Apache JMeter 2.X and 3.X, when using Distributed Test only (RMI based), jmeter server binds RMI Registry to wildcard host. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.
CVE-2018-1297: When using Distributed Test only (RMI based), Apache JMeter 2.x and 3.x uses an unsecured RMI connection. This could allow an attacker to get Access to JMeterEngine and send unauthorized code.

Please fix them.

Created: 2018-02-11 Last update: 2018-08-06 08:04

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.2.1 instead of 4.1.5).

Created: 2018-08-20 Last update: 2018-08-26 08:17

news

[rss feed]

[2018-08-06] jakarta-jmeter 2.13-4 MIGRATED to testing (Debian testing watch)
[2018-07-31] Accepted jakarta-jmeter 2.13-4 (source) into unstable (Emmanuel Bourg)
[2017-11-08] jakarta-jmeter REMOVED from testing (Debian testing watch)
[2017-07-29] jakarta-jmeter 2.13-3 MIGRATED to testing (Debian testing watch)
[2017-07-23] Accepted jakarta-jmeter 2.13-3 (source all) into unstable (tony mancill)
[2016-11-04] jakarta-jmeter 2.13-2 MIGRATED to testing (Debian testing watch)
[2016-10-28] Accepted jakarta-jmeter 2.13-2 (source all) into unstable (Emmanuel Bourg)
[2016-06-05] Accepted jakarta-jmeter 2.11-2+deb8u1 (source all) into proposed-updates->stable-new, proposed-updates (Emmanuel Bourg)
[2016-05-20] Accepted jakarta-jmeter 2.13-1~bpo8+1 (source all) into jessie-backports, jessie-backports (Emmanuel Bourg)
[2016-04-05] jakarta-jmeter 2.13-1 MIGRATED to testing (Debian testing watch)
[2016-03-30] Accepted jakarta-jmeter 2.13-1 (source all) into unstable (Emmanuel Bourg)
[2015-12-12] jakarta-jmeter 2.11-5 MIGRATED to testing (Debian testing watch)
[2015-12-06] Accepted jakarta-jmeter 2.11-5 (source all) into unstable (Markus Koschany)
[2015-11-03] jakarta-jmeter 2.11-4 MIGRATED to testing (Britney)
[2015-10-28] Accepted jakarta-jmeter 2.11-4 (source) into unstable (Markus Koschany)
[2015-07-22] jakarta-jmeter 2.11-3 MIGRATED to testing (Britney)
[2015-07-16] Accepted jakarta-jmeter 2.11-3 (source all) into unstable (Emmanuel Bourg)
[2014-09-24] jakarta-jmeter 2.11-2 MIGRATED to testing (Britney)
[2014-09-18] Accepted jakarta-jmeter 2.11-2 (source all) into unstable (Emmanuel Bourg)
[2014-07-23] Accepted jakarta-jmeter 2.11-1 (source all) (Emmanuel Bourg) (signed by: tony mancill)
[2014-04-22] jakarta-jmeter 2.8-2 MIGRATED to testing (Debian testing watch)
[2014-04-11] Accepted jakarta-jmeter 2.8-2 (source all) (Emmanuel Bourg)
[2013-07-16] jakarta-jmeter 2.8-1 MIGRATED to testing (Debian testing watch)
[2013-07-05] Accepted jakarta-jmeter 2.8-1 (source all) (Emmanuel Bourg)
[2013-07-03] Accepted jakarta-jmeter 2.5.1-2 (source all) (Emmanuel Bourg)
[2012-05-22] jakarta-jmeter 2.5.1-1 MIGRATED to testing (Debian testing watch)
[2012-05-12] Accepted jakarta-jmeter 2.5.1-1 (source all) (Onkar Shinde) (signed by: tony mancill)
[2012-05-03] jakarta-jmeter 2.4-3 MIGRATED to testing (Debian testing watch)
[2012-04-23] Accepted jakarta-jmeter 2.4-3 (source all) (Onkar Shinde) (signed by: tony mancill)
[2011-09-28] jakarta-jmeter 2.4-2 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 4
RC: 0
I&N: 2
M&W: 2
F&P: 0
patch: 0

links

homepage
lintian (0, 15)
buildd: logs, clang, reproducibility
popcon
browse source code
edit tags
security tracker

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.13-4
3 bugs (1 patch)