diff options
author | Dimitris Zlatanidis <d.zlatanidis@gmail.com> | 2017-06-05 21:05:59 +0100 |
---|---|---|
committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2017-06-06 07:56:18 +0700 |
commit | f591f2e322a51f8622c7abd323e17879c42cd5ee (patch) | |
tree | 4eb60f8a683909237b6a41ee66a7e9b69c2b8e38 /python/PyRIC/README | |
parent | 5a01946ed94bba0bf8a3d795eeaf227af818ebbb (diff) | |
download | slackbuilds-f591f2e322a51f8622c7abd323e17879c42cd5ee.tar.gz |
python/PyRIC: Added (Linux wireless library for Python).
Signed-off-by: David Spencer <idlemoor@slackbuilds.org>
Diffstat (limited to 'python/PyRIC/README')
-rw-r--r-- | python/PyRIC/README | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/python/PyRIC/README b/python/PyRIC/README new file mode 100644 index 0000000000..175cb91527 --- /dev/null +++ b/python/PyRIC/README @@ -0,0 +1,32 @@ +PyRIC (is a Linux only) library providing wireless developers and +pentesters the ability to identify, enumerate and manipulate their +system's wireless cards programmatically in Python. Pentesting +applications and scripts written in Python have increased dramatically +in recent years. However, these tools still rely on Linux command lines +tools to setup and prepare and restore the system for use. Until now. +Why use subprocess.Popen, regular expressions and str.find to interact +with your wireless cards? PyRIC is: + + * Pythonic: no ctypes, SWIG etc. PyRIC redefines C header files as + Python and uses sockets to communicate with the kernel. + + * Self-sufficient: No third-party files used. PyRIC is completely + self-contained. + + * Fast: (relatively speaking) PyRIC is faster than using command line + tools through subprocess.Popen + + * Parseless: Get the output you want without parsing output from + command line tools. Never worry about newer iw versions and having + to rewrite your parsers. + + * Easy: If you can use iw, you can use PyRIC. + +At its heart, PyRIC is a Python port of (a subset of) iw and by +extension, a Python port of Netlink w.r.t nl80211 functionality. The +original goal of PyRIC was to provide a simple interface to the +underlying nl80211 kernel support, handling the complex operations of +Netlink seamlessly while maintaining a minimum of "code walking" to +understand, modify and extend. But, why stop there? Since its initial +inception, PyRIC has grown. PyRIC puts iw, ifconfig, rfkill, udevadm, +airmon-ng and macchanger in your hands (or your program). |