Tiny Core Base > CorePlus
Installation of aircrack-ng,hashcat,hcxdumptool,hcxpcaptools,reaver
Sashank999:
I think GUIs and Window Managers interfere with each other and thus creating the prob. Is there any tool to unload tc extension ? (not deleting them).
I actually created all the three tcz -
* aircrack-ng for all executables
* aircrack-ng-dev for all libraries
* aircrack-ng-doc for all manpagesBut man pages are not loading with "man aircrack-ng". What to do
Rich:
Hi Sashank999
--- Quote from: Sashank999 on June 08, 2020, 09:45:07 PM --- ... But man pages are not loading with "man aircrack-ng". What to do
--- End quote ---
When you entered:
--- Code: ---man aircrack-ng
--- End code ---
you received an error message. Error messages provide clues as to what the problem is.
By keeping that information to yourself, we have to guess what the problem is.
Here are my guesses:
1. You did not install man.tcz or man-db.tcz if you are running x86_64.
2. you did not install aircrack-ng-doc.tcz.
Sashank999:
I did not load -doc tcz. Sorry. My bad. :-[
Sashank999:
Can anyone say me how to find the dependencies of aircrack-ng ?
Their site says :
Autoconf
Automake
Libtool
shtool
OpenSSL development package or libgcrypt development package.
pkg-config
Airmon-ng requires ethtool and rfkill
If USB bus is present, lsusb
If PCI/PCIe bus is present, lspci
LibNetlink 1 (libnl-dev) or 3 (libnl-3-dev and libnl-genl-3-dev) development packages. It can be disabled by passing –disable-libnl to configure.
Kernel headers and gcc as well as make have to be installed on your system (build-essential on Debian based distributions)
make and Standard C++ Library development package (Debian: libstdc++-dev)
But I think some of them are required for only compiling and not for running.
When I ran aircrack-ng with only some (Xvesa, aterm,wifi, firmware,jwm), it said some requirements (iw.tcz, ethtool.tcz, usbutils.tcz, pci-utils.tcz, rfkill.tcz). I installed them and it is running fine.
Juanito:
There are several kinds of dependencies:
* direct - applications in bin and sbin and libraries in lib will not work without them
* optional - libs in lib/subdirectory where the application will work without them
* runtime - not in the above, but the application will not work without them
You can test for direct and optional dependencies with ldd:
--- Code: ---$ ldd /usr/local/bin/flwm
$ ldd /usr/local/lib/libX11.so
$ ldd /usr/local/lib/gstreamer-1.0/libgstcairo.so
--- End code ---
To find runtime dependencies, run the application from the command line and check for errors about missing items.
Tinycore uses a recursive dependency system - this means that if libA depends on libB, which in turn depends on libC, there is only a need to list libA as a dependency.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version