initial
This commit is contained in:
parent
3749a2612a
commit
b1657cf94e
@ -1,36 +0,0 @@
|
||||
Contributing to ZMap
|
||||
====================
|
||||
|
||||
ZMap accepts contributions in the form of issues and pull requests. In either
|
||||
case, before posting please [search](https://github.com/zmap/zmap/issues) to see
|
||||
if your change or bug report has been addressed previously.
|
||||
|
||||
[INSTALL](INSTALL.md#building-from-source) provides guidance on building ZMap
|
||||
from source.
|
||||
|
||||
Developing
|
||||
----------
|
||||
|
||||
- ZMap code follows the [Linux kernel style guide][kernelguide]. We maintain [a
|
||||
configuration file](/.clang-format) for `clang-format` that applies this
|
||||
style. You can use the [format.sh](/format.sh) script to apply this style.
|
||||
|
||||
- Before submitting a PR, please rebase/squash your commits down to a single
|
||||
commit. Follow these [commit message guidelines][guidelines], especially with
|
||||
regard to formatting.
|
||||
|
||||
Reviewing
|
||||
---------
|
||||
|
||||
- All commits must be reviewed in the form of a pull request by a ZMap
|
||||
maintainer. This usually means @zakird or @dadrian (or both).
|
||||
|
||||
- All pull-requests should be squash-merged into master.
|
||||
|
||||
- When squash-merging, put the PR number in the commit title. GitHub does this
|
||||
automatically in the web interface. Condense the commit messages down to a
|
||||
single message; often this can just be the commit message from the first
|
||||
commit in a PR. Follow the commit formatting guidelines [here][guidelines].
|
||||
|
||||
[kernelguide]: https://www.kernel.org/doc/Documentation/process/coding-style.rst
|
||||
[guidelines]: https://github.com/torvalds/subsurface-for-dirk/blob/master/README#L92
|
43
README.md
Normal file
43
README.md
Normal file
@ -0,0 +1,43 @@
|
||||
# zmap - mark II
|
||||
|
||||
zmap stripped of its trackers. evades fingerprinting by threat intelligence firms, service providers, and everyone in between.
|
||||
|
||||
# Why?
|
||||
|
||||
the original zmap contains values in its headers that are used to identify the traffic as belonging to zmap.
|
||||
|
||||
this makes it easy for threat intelligence agencies, isp's, and anyone else to fingerprint zmap traffic and generate alerts/tags/abuse reports accordingly.
|
||||
|
||||
# Installation
|
||||
|
||||
**dependencies**: cmake, gmp, gengetopt, libpcap, flex, byacc, json-c, libunistring, pkg-config, libjudy
|
||||
|
||||
to install the dependencies on debian based systems:
|
||||
|
||||
```
|
||||
sudo apt install -y build-essential cmake libgmp3-dev gengetopt libpcap-dev flex byacc libjson-c-dev pkg-config libunistring-dev libjudy-dev
|
||||
```
|
||||
|
||||
compile it with
|
||||
|
||||
```
|
||||
git clone https://git.supernets.org/delorean/zmap-mark-ii
|
||||
cd zmap-mark-ii
|
||||
cmake .
|
||||
make -j4
|
||||
```
|
||||
|
||||
then install it via
|
||||
|
||||
|
||||
```
|
||||
sudo make install
|
||||
```
|
||||
|
||||
# Usage
|
||||
|
||||
```
|
||||
zmap -h
|
||||
```
|
||||
|
||||
refer to [zmap's usage](https://github.com/robertdavidgraham/masscan/tree/master?tab=readme-ov-file#usage)
|
Loading…
Reference in New Issue
Block a user