| 1 |
Summary: Tool to check system for binary-hardening |
| 2 |
Name: checksec |
| 3 |
Version: 1.7.4 |
| 4 |
Release: 1 |
| 5 |
License: BSD |
| 6 |
Group: Development/Tools |
| 7 |
Source0: https://raw.githubusercontent.com/slimm609/checksec.sh/master/%{name} |
| 8 |
Source1: https://raw.githubusercontent.com/slimm609/checksec.sh/master/ChangeLog |
| 9 |
URL: https://github.com/slimm609/checksec.sh |
| 10 |
Requires: binutils |
| 11 |
BuildArch: noarch |
| 12 |
BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) |
| 13 |
|
| 14 |
%description |
| 15 |
Modern Linux distributions offer some mitigation techniques to make it |
| 16 |
harder to exploit software vulnerabilities reliably. Mitigations such |
| 17 |
as RELRO, NoExecute (NX), Stack Canaries, Address Space Layout |
| 18 |
Randomization (ASLR) and Position Independent Executables (PIE) have |
| 19 |
made reliably exploiting any vulnerabilities that do exist far more |
| 20 |
challenging. |
| 21 |
|
| 22 |
The checksec script is designed to test what *standard* Linux OS and |
| 23 |
PaX <http://pax.grsecurity.net/> security features are being used. |
| 24 |
|
| 25 |
As of version 1.3 the script also lists the status of various Linux |
| 26 |
kernel protection mechanisms. |
| 27 |
|
| 28 |
checksec can check binary-files and running processes for hardening |
| 29 |
features. |
| 30 |
|
| 31 |
%prep |
| 32 |
cp -p %{SOURCE1} ChangeLog |
| 33 |
|
| 34 |
%install |
| 35 |
rm -rf $RPM_BUILD_ROOT |
| 36 |
install -d $RPM_BUILD_ROOT%{_bindir} |
| 37 |
install -p %{SOURCE0} $RPM_BUILD_ROOT%{_bindir}/%{name} |
| 38 |
|
| 39 |
%clean |
| 40 |
rm -rf $RPM_BUILD_ROOT |
| 41 |
|
| 42 |
%files |
| 43 |
%defattr(644,root,root,755) |
| 44 |
%doc ChangeLog |
| 45 |
%attr(755,root,root) %{_bindir}/%{name} |