| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| |\ |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
testing/calibre/APKBUILD
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* also add a patch to allow overriding of envelope-from from a
template
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |_|/
|/| | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Package description:
The purpose of Dnsenum is to gather as much information as possible
about a domain. The program currently performs the following operations:
1) Get the host's addresse (A record).
2) Get the namservers (threaded).
3) Get the MX record (threaded).
4) Perform axfr queries on nameservers and get BIND versions(threaded).
5) Get extra names and subdomains via google scraping
(google query = "allinurl: -www site:domain").
6) Brute force subdomains from file, can also perform recursion on
subdomain that have NS records (all threaded).
7) Calculate C class domain network ranges and perform whois queries
on them (threaded).
8) Perform reverse lookups on netranges ( C class or/and whois netranges).
9) Write to domain_ips.txt file ip-blocks.
|
| |
| |
| |
| |
| | |
Package description:
Perl extension for writing XML documents
|
| |
| |
| |
| |
| | |
Package description:
Perl module for manipulation and lookup of IP network blocks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Package description:
ScanSSH supports scanning a list of addresses and networks for
open proxies, SSH protocol servers, Web and SMTP servers. Where
possible ScanSSH, displays the version number of the running
services. ScanSSH protocol scanner supports random selection
of IP addresses from large network ranges and is useful for
gathering statistics on the deployment of SSH protocol servers
in a company or the Internet as whole.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Package description:
The gain of performance is reached by zero-copy mechanisms, so that
the kernel does not need to copy packets from kernelspace to userspace
and vice versa.
For this purpose, the netsniff-ng suite is libpcap independent, but
nevertheless supports the pcap file format for capturing, replaying
and performing offline-analysis of pcap dumps. Furthermore, we are
focussing on building a robust, clean and secure analyzer and utilities
that complete netsniff-ng as a support for network development, debugging
or network reconnaissance.
netsniff-ng consists of much more than only a network analyzer. Next to
the zero-copy sniffer itself, further tools like trafgen, a powerful
zero-copy network packet generator, or ifpps, a tool that provides
top-like kernel networking statistics, are being shipped.
Some use cases and features
- Open source project and free licensing
- Integrated high-performance capabilities
- Analizing and debugging of network problems or protocol implementations
- Reverse engineering of (i.e. proprietary) network protocols
- Dumping, replaying and offline analysis of pcap traces
- Focus on usability, robustness, security and functionality
- Support utility for penetration testing, network reconnaissance
- Network statistic creation (e.g. for Nagios, gnuplot)
- Powerful, flexible and performant traffic generation
- Reliable, top-like kernel networking statistics
|
| |
| |
| |
| | |
to match pkgname
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Package description:
The mr command can checkout, update, or perform other actions on
a set of repositories as if they were one combined respository.
It supports any combination of subversion, git, cvs, mercurial,
bzr, darcs, cvs, and fossil repositories, and support for other
revision control systems can easily be added.
It is extremely configurable via simple shell scripting. Some
examples of things it can do include:
- Update a repository no more frequently than once every twelve hours.
- Run an arbitrary command before committing to a repository.
- When updating a git repository, pull from two different upstreams
and merge the two together.
- Run several repository updates in parallel, greatly speeding up the
update process.
- Remember actions that failed due to a laptop being offline, so they
can be retried when it comes back online.
|
| | |
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|