Source: timesanitycheck
Section: misc
Priority: optional
Maintainer: linuxmangaka <linuxmangaka@gmail.com>
Rules-Requires-Root: no
Build-Depends: debhelper (>= 13),
 debhelper-compat (= 13),
 dh-apparmor,
 pkgconf,
 pkg-config,
Standards-Version: 4.6.2
Homepage: https://github.com/Kicksecure/timesanitycheck
Vcs-Browser: https://github.com/Kicksecure/timesanitycheck
Vcs-Git: https://github.com/Kicksecure/timesanitycheck.git

Package: timesanitycheck
Architecture: all
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: Checks if the system clock is sane between build timestamp and expiration date
 Reports, if clock is sane and not slower than build timestamp or faster than expiration date (configurable, default currently set to 17 MAY 2033 10:00:00). This should catch situations, where the host's clock is too much off (CMOS battery defect, user mistakenly set a very wrong date, etc.), resulting in network time synchronization tools (such as sdwdate) no longer being able to correct the clock; catch eventual bigger bugs in network time synchronization tools; and some types of attacks on network time synchronization.