Wifite2 in Macosx (osx)

[j1m1l0k0]

Using wifite on OSX .

This possibility exists using the airport monitor? would only change in the source code ? aircrack -ng has been compiled successfully with the recover - wps ??

[derv82]

I'll try to procure a Mac to test this out on. There's definitely ways of detecting if the system is OSX/Darwin, so if there's special commands that need to be run on OSX, the script can run them. I just don't know what's different between OSX and Linux systems like Kali.

[j1m1l0k0]

I will test on a virtualbox using Hackint0sh osx yosemite and post the result here.

Thanks derv82

[ethanke]

trying to install it, actually the main problem i face is the iwconfig. Someone have an idea for a replacement on macOS ?

[cardiforia]

Is it possible to make it work on MacOS 13.1 Ventura?

[sealldeveloper]

Hello, visiting this also. Is there any updates to this?

[SHLEAK]

Based on the issue and comments provided in the GitHub repository, it seems that the primary problem is related to using wifite2 on macOS. Here are some possible solutions:

• Solution 1: Use a Linux distribution instead of macOS. As mentioned in the comments, wifite2 has been tested on Linux systems like Kali and seems to work without any issues. Since the script is primarily designed for Linux, using a Linux distribution instead of macOS might be the easiest solution.

• Solution 2: Install missing dependencies. The error related to iwconfig suggests that the wireless tools package might be missing on the macOS system. Installing the wireless-tools package might resolve this issue. To install wireless-tools, use the following command:

  brew install wireless-tools

  This command installs wireless-tools using Homebrew, a popular package manager for macOS.

• Solution 3: Modify the script to work with macOS. If wifite2 is required to be used on macOS, modifying the script to work with macOS might be necessary. This could involve changing the source code to replace Linux-specific commands with equivalent macOS commands. However, this might require some knowledge of the differences between Linux and macOS systems.

  One possible approach to modify the script is to use the uname command to detect the operating system and execute different commands based on the detected system. For example, the following code snippet checks the operating system and sets the IWCONFIG variable accordingly:

  if [[ "$(uname)" == "Darwin" ]]; then
      IWCONFIG="airport"
  else
      IWCONFIG="iwconfig"
  fi

  This code sets the IWCONFIG variable to airport if the operating system is macOS, and to iwconfig otherwise.

• Solution 4: Use a virtual machine. Another option is to use a virtual machine to run a Linux distribution and use wifite2 inside the virtual machine. This approach has the advantage of keeping the macOS system separate from the Linux system and avoiding any compatibility issues. VirtualBox is a popular virtual machine software that can be used to create a virtual machine and install a Linux distribution. Once the virtual machine is set up, wifite2 can be installed and used inside the virtual machine.

These are some possible solutions that might help resolve the issue with using wifite2 on macOS.

[cjacksonuk]

was this solution successful for getting iwconfig to use airport? what script to modify? or is there any way to get a macos modded version of wireless-tools working (its not available as a brew install)