Bug 973349

Summary: Review Request: checksec - Tool to check system for binary-hardening
Product: [Fedora] Fedora Reporter: Björn 'besser82' Esser <besser82>
Component: Package ReviewAssignee: Mario Blättermann <mario.blaettermann>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mario.blaettermann, notting, package-review
Target Milestone: ---Flags: mario.blaettermann: fedora-review+
gwync: fedora-cvs+
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: checksec-1.5-2.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-13 06:11:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Björn 'besser82' Esser 2013-06-11 18:32:07 UTC
Spec URL: http://besser82.fedorapeople.org/review/checksec/checksec.spec
SRPM URL: http://besser82.fedorapeople.org/review/checksec/checksec-1.5-1.fc19.src.rpm

Description:
Modern Linux distributions offer some mitigation techniques to make it harder to exploit software vulnerabilities reliably. Mitigations such as RELRO, NoExecute (NX), Stack Canaries, Address Space Layout Randomization (ASLR) and Position Independent Executables (PIE) have made reliably exploiting any vulnerabilities that do exist far more challenging. The checksec script is designed to test what *standard* Linux OS and PaX (http://pax.grsecurity.net/) security features are being used.

As of version 1.3 the script also lists the status of various Linux kernel protection mechanisms.

checksec can check binary-files and running processes for hardening features.

Fedora Account System Username: besser82

rpmlint:
checksec.src: W: spelling-error %description -l en_US Mitigations -> Mitigation, Mitigation's, Mitigation s
checksec.noarch: W: spelling-error %description -l en_US Mitigations -> Mitigation, Mitigation's, Mitigation s
checksec.noarch: W: no-manual-page-for-binary checksec
2 packages and 1 specfiles checked; 0 errors, 3 warnings.

koji-build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5493248

Comment 1 Mario Blättermann 2013-06-11 19:23:23 UTC
$ rpmlint -i -v *
checksec.src: I: checking
checksec.src: W: spelling-error %description -l en_US Mitigations -> Mitigation, Mitigation's, Mitigation s
The value of this tag appears to be misspelled. Please double-check.

checksec.src: I: checking-url http://www.trapkit.de/tools/checksec.html (timeout 10 seconds)
checksec.src: I: checking-url http://www.trapkit.de/tools/checksec_changes.txt (timeout 10 seconds)
checksec.src: I: checking-url http://www.trapkit.de/tools/checksec.sh (timeout 10 seconds)
checksec.noarch: I: checking
checksec.noarch: W: spelling-error %description -l en_US Mitigations -> Mitigation, Mitigation's, Mitigation s
The value of this tag appears to be misspelled. Please double-check.

checksec.noarch: I: checking-url http://www.trapkit.de/tools/checksec.html (timeout 10 seconds)
checksec.noarch: W: no-manual-page-for-binary checksec
Each executable in standard binary directories should have a man page.

checksec.spec: I: checking-url http://www.trapkit.de/tools/checksec_changes.txt (timeout 10 seconds)
checksec.spec: I: checking-url http://www.trapkit.de/tools/checksec.sh (timeout 10 seconds)
2 packages and 1 specfiles checked; 0 errors, 3 warnings.


Nothing of interest so far.


---------------------------------
key:

[+] OK
[.] OK, not applicable
[X] needs work
---------------------------------

[+] MUST: rpmlint must be run on the source rpm and all binary rpms the build produces. The output should be posted in the review.
[+] MUST: The package must be named according to the Package Naming Guidelines.
[+] MUST: The spec file name must match the base package %{name}, in the format %{name}.spec unless your package has an exemption.
[+] MUST: The package must meet the Packaging Guidelines.
[+] MUST: The package must be licensed with a Fedora approved license and meet the Licensing Guidelines.
[+] MUST: The License field in the package spec file must match the actual license.
    BSD
[+] MUST: If (and only if) the source package includes the text of the license(s) in its own file, then that file, containing the text of the license(s) for the package must be included in %doc.
[+] MUST: The spec file must be written in American English.
[+] MUST: The spec file for the package MUST be legible.
[+] MUST: The sources used to build the package must match the upstream source, as provided in the spec URL. Reviewers should use sha256sum for this task as it is used by the sources file once imported into git. If no upstream URL can be specified for this package, please see the Source URL Guidelines for how to deal with this.
    $ sha256sum *
    77b8a7fd9393d10def665658a41176ee745d5c7969a4a0f43cefcc8a4cd90947  checksec.sh
    77b8a7fd9393d10def665658a41176ee745d5c7969a4a0f43cefcc8a4cd90947  checksec.sh.packaged

[+] MUST: The package MUST successfully compile and build into binary rpms on at least one primary architecture.
[.] MUST: If the package does not successfully compile, build or work on an architecture, then those architectures should be listed in the spec in ExcludeArch. Each architecture listed in ExcludeArch MUST have a bug filed in bugzilla, describing the reason that the package does not compile/build/work on that architecture. The bug number MUST be placed in a comment, next to the corresponding ExcludeArch line.
[.] MUST: All build dependencies must be listed in BuildRequires, except for any that are listed in the exceptions section of the Packaging Guidelines ; inclusion of those as BuildRequires is optional. Apply common sense.
[.] MUST: The spec file MUST handle locales properly. This is done by using the %find_lang macro. Using %{_datadir}/locale/* is strictly forbidden.
[.] MUST: Every binary RPM package (or subpackage) which stores shared library files (not just symlinks) in any of the dynamic linker's default paths, must call ldconfig in %post and %postun.
[.] MUST: Packages must NOT bundle copies of system libraries.
[.] MUST: If the package is designed to be relocatable, the packager must state this fact in the request for review, along with the rationalization for relocation of that specific package. Without this, use of Prefix: /usr is considered a blocker.
[+] MUST: A package must own all directories that it creates. If it does not create a directory that it uses, then it should require a package which does create that directory.
[+] MUST: A Fedora package must not list a file more than once in the spec file's %files listings. (Notable exception: license texts in specific situations)
[+] MUST: Permissions on files must be set properly. Executables should be set with executable permissions, for example.
[+] MUST: Each package must consistently use macros.
[+] MUST: The package must contain code, or permissable content.
[.] MUST: Large documentation files must go in a -doc subpackage. (The definition of large is left up to the packager's best judgement, but is not restricted to size. Large can refer to either size or quantity).
[+] MUST: If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present.
[.] MUST: Static libraries must be in a -static package.
[.] MUST: Development files must be in a -devel package.
[.] MUST: In the vast majority of cases, devel packages must require the base package using a fully versioned dependency: Requires: %{name}%{?_isa} = %{version}-%{release}
[.] MUST: Packages must NOT contain any .la libtool archives, these must be removed in the spec if they are built.
[.] MUST: Packages containing GUI applications must include a %{name}.desktop file, and that file must be properly installed with desktop-file-install in the %install section. If you feel that your packaged GUI application does not need a .desktop file, you must put a comment in the spec file with your explanation.
[+] MUST: Packages must not own files or directories already owned by other packages. The rule of thumb here is that the first package to be installed should own the files or directories that other packages may rely upon. This means, for example, that no package in Fedora should ever share ownership with any of the files or directories owned by the filesystem or man package. If you feel that you have a good reason to own a file or directory that another package owns, then please present that at package review time. 
[+] MUST: All filenames in rpm packages must be valid UTF-8.


[.] SHOULD: If the source package does not include license text(s) as a separate file from upstream, the packager SHOULD query upstream to include it.
[.] SHOULD: The description and summary sections in the package spec file should contain translations for supported Non-English languages, if available.
[+] SHOULD: The reviewer should test that the package builds in mock.
    See Koji build above (which uses Mock anyway).
[+] SHOULD: The package should compile and build into binary rpms on all supported architectures.
[.] SHOULD: The reviewer should test that the package functions as described. A package should not segfault instead of running, for example.
[.] SHOULD: If scriptlets are used, those scriptlets must be sane. This is vague, and left up to the reviewers judgement to determine sanity.
[.] SHOULD: Usually, subpackages other than devel should require the base package using a fully versioned dependency.
[.] SHOULD: The placement of pkgconfig(.pc) files depends on their usecase, and this is usually for development purposes, so should be placed in a -devel pkg. A reasonable exception is that the main pkg itself is a devel tool not installed in a user runtime, e.g. gcc or gdb.
[.] SHOULD: If the package has file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the file instead of the file itself.
[.] SHOULD: your package should contain man pages for binaries/scripts. If it doesn't, work with upstream to add them where they make sense.


----------------

PACKAGE APPROVED

----------------

Comment 2 Björn 'besser82' Esser 2013-06-11 19:41:10 UTC
Thanks for reviewing, Mario!
If I can take a review for you in return, just let me know.

#####

New Package SCM Request
=======================
Package Name: checksec
Short Description: Tool to check system for binary-hardening
Owners: besser82
Branches: f19 f18 el6
InitialCC:

Comment 3 Gwyn Ciesla 2013-06-11 19:43:16 UTC
Git done (by process-git-requests).

Comment 4 Fedora Update System 2013-06-11 20:05:32 UTC
checksec-1.5-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/checksec-1.5-1.el6

Comment 5 Fedora Update System 2013-06-11 20:06:16 UTC
checksec-1.5-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/checksec-1.5-1.fc18

Comment 6 Fedora Update System 2013-06-11 20:06:45 UTC
checksec-1.5-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/checksec-1.5-1.fc19

Comment 7 Björn 'besser82' Esser 2013-06-11 20:25:20 UTC
Just forgot to request el5, too.

#####

Package Change Request
======================
Package Name: checksec
New Branches: el5
Owners: besser82

Comment 8 Gwyn Ciesla 2013-06-12 12:27:29 UTC
Git done (by process-git-requests).

Comment 9 Fedora Update System 2013-06-12 12:57:40 UTC
checksec-1.5-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/checksec-1.5-2.fc19

Comment 10 Fedora Update System 2013-06-12 12:59:09 UTC
checksec-1.5-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/checksec-1.5-2.fc18

Comment 11 Fedora Update System 2013-06-12 12:59:36 UTC
checksec-1.5-2.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/checksec-1.5-2.el6

Comment 12 Fedora Update System 2013-06-12 13:00:10 UTC
checksec-1.5-2.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/checksec-1.5-2.el5

Comment 13 Fedora Update System 2013-06-12 20:06:32 UTC
checksec-1.5-2.el6 has been pushed to the Fedora EPEL 6 testing repository.

Comment 14 Fedora Update System 2013-06-13 06:11:17 UTC
checksec-1.5-1.fc18 has been pushed to the Fedora 18 stable repository.

Comment 15 Fedora Update System 2013-06-13 06:42:22 UTC
checksec-1.5-1.fc19 has been pushed to the Fedora 19 stable repository.

Comment 16 Fedora Update System 2013-06-14 02:25:32 UTC
checksec-1.5-2.fc18 has been pushed to the Fedora 18 stable repository.

Comment 17 Fedora Update System 2013-06-28 18:51:44 UTC
checksec-1.5-2.el5 has been pushed to the Fedora EPEL 5 stable repository.

Comment 18 Fedora Update System 2013-06-28 18:51:56 UTC
checksec-1.5-2.el6 has been pushed to the Fedora EPEL 6 stable repository.

Comment 19 Fedora Update System 2013-06-29 18:15:38 UTC
checksec-1.5-2.fc19 has been pushed to the Fedora 19 stable repository.