checksec | Does large-scale package analysis
kandi X-RAY | checksec Summary
kandi X-RAY | checksec Summary
checksec is a Python library. checksec has no bugs, it has no vulnerabilities and it has low support. However checksec build file is not available. You can download it from GitHub.
This is a rough port of the checksec.sh script by Tobias Klein to Python. My analysis code combines the original checksec (bash script), rpm-chksec (Steve’s script) and Grant’s Go port into one Python code base. The idea behind this exercise is to make analysis of packages easier and more accessible. One of the cool things is that you can analyze packages for different Operating System(s) seamlessly while running a single OS. Additionally, my code works for all RHEL and Fedora versions (and even deb based distributions). The analysis code doesn’t install any packages on the system, is host OS agnostic and is quite fast (scales linearly).
This is a rough port of the checksec.sh script by Tobias Klein to Python. My analysis code combines the original checksec (bash script), rpm-chksec (Steve’s script) and Grant’s Go port into one Python code base. The idea behind this exercise is to make analysis of packages easier and more accessible. One of the cool things is that you can analyze packages for different Operating System(s) seamlessly while running a single OS. Additionally, my code works for all RHEL and Fedora versions (and even deb based distributions). The analysis code doesn’t install any packages on the system, is host OS agnostic and is quite fast (scales linearly).
Support
Quality
Security
License
Reuse
Support
checksec has a low active ecosystem.
It has 66 star(s) with 21 fork(s). There are 9 watchers for this library.
It had no major release in the last 6 months.
checksec has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of checksec is current.
Quality
checksec has 0 bugs and 0 code smells.
Security
checksec has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
checksec code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
checksec does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
checksec releases are not available. You will need to build from source code and install.
checksec has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions are not available. Examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi has reviewed checksec and discovered the below as its top functions. This is intended to give you an instant insight into checksec implemented functionality, and help decide if they suit your requirements.
- Analyze a rpm file
- Determine whether the symbol is enabled
- Process an ELF file
- Return enabled tags
- Scan the given buffer
- Close the clamd socket
- Read the response from clamd
- Parse an HTTP response
- Load data files
- Load repositories
- List section
- List sections
- Analyze a package
- Fetch url to destination
- Query the server
- Receive a response from clamd
- Shutdown the Clamd
- Reload the server
- Test for a non - regression test
- Ping the server
Get all kandi verified functions for this library.
checksec Key Features
No Key Features are available at this moment for checksec.
checksec Examples and Code Snippets
No Code Snippets are available at this moment for checksec.
Community Discussions
Trending Discussions on checksec
QUESTION
linker flag `execstack` not applied at `.rodata`, `.data`, or `.bss` section.... What is Wrong?
Asked 2021-Aug-14 at 21:43
Currently I am studying system exploit, and find some interesting system exploit called buffer overflow using shellcode. I wrote shellcode terminating current process using exit(0) systemcall. Below, there is my code.
...ANSWER
Answered 2021-Aug-10 at 14:38The title says "execstack not applied at .rodata, .data, or .bss sections".
That's correct:
execstack is a linker flag that "Marks the object as requiring executable stack."
It does nothing about .data, .bss or .rodata.
When I run your program (on x86_64), I get:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install checksec
You can download it from GitHub.
You can use checksec like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
You can use checksec like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
