lockdown
make it harder for attackers to compromise your system

NEW: Take a look at the new package tracker: tracker.debian.org/pkg/lockdown

general

source
lockdown (optional, misc)
version
0.2
distro
oldoldstable
maint
Matt Taggart
std-ver
3.9.8
VCS
Git (browse)

versions ... ...pool

o-o-stable
save 0.2

binaries

todo

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

problems

  • The package has not yet entered testing even though the 5-day delay is over. Check why.
  • The package is severely out of date with respect to the Debian Policy. Latest version is 4.7.0 and your package only follows 3.9.8...
  • This package is neither part of unstable nor experimental. This probably means that the package has been removed (or has been renamed). Thus the information here is of little interest ... the package is going to disappear unless someone takes it over and reintroduces it into unstable.

testing migration

excuses:
  • Migration status for lockdown (- to 0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
  • Issues preventing migration:
  • Updating lockdown introduces new bugs: #958587.
  • Not built on buildd: arch all binaries uploaded by taggart, a new source-only upload is needed to allow migration
  • Impossible Build-Depends(-Arch): lockdown -> dh-systemd/13.2.1/amd64
  • Additional info:
  • Piuparts tested OK - https://piuparts.debian.org/sid/source/l/lockdown.html
  • 1751 days old (needed 5 days)

news RSS

bugs

all bug history graph
0
RC
0
I&N
0
M&W
0
F&P
0

patches

Debian