Bug#879002: Should the package be removed?

2017-11-03 Thread Markus Koschany
On Wed, 18 Oct 2017 13:29:19 +0200 Emmanuel Bourg wrote: > Upstream has moved to GitHub [1] and the last update was released in > 2014 but the security issue is still not fixed [2]. > > This was a dependency of Jenkins which is now gone. There is a slim > chance that this

Bug#879002: Should the package be removed?

2017-10-18 Thread Emmanuel Bourg
Upstream has moved to GitHub [1] and the last update was released in 2014 but the security issue is still not fixed [2]. This was a dependency of Jenkins which is now gone. There is a slim chance that this package could be useful again in the future since it's a dependency of some Apache projects

Bug#879002: Should the package be removed?

2017-10-18 Thread Raphael Hertzog
Source: libpam4j Severity: serious Hello, I just came across libpam4j while handlinge CVE-2017-12197 and I noticed that: - the package has not seen an update since 2012 - the package has no reverse dependency in Debian - upstream seems to have disappeared (the current Homepage URL is dead and