Nowadays we can find all sorts of tools i.e. Aircrack Suite, Metasploit, Burpsuite etc. for Windows too!

So why use Linux? e.g. I am using aircrack on Windows what will be my disadvantage?

My laptop "Asus x205ta" doesn't support Linux out of the box, and even if I install Linux somehow, not all hardware is supported.

closed as primarily opinion-based by AviD Sep 2 '16 at 12:08

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    Can we please not turn this into an infantile OS war. – Tobias Sep 1 '16 at 20:41
  • As far as pure applications testing is concerned where we mostly rely on proxies and other supporting automated tools. I have never had an issue using Windows. – Shurmajee Sep 2 '16 at 5:46
  • You seem to be starting with an assumption that Linux is an absolute requirement for pentesting, which seems either misguided or trolling. There are plenty of tools of all sorts for any OS, even if these are not equal there is definitely no clear advantage that applies to all scenarios across the board. Basically what I'm saying is, as @Tobias already said - DO NOT TURN THIS INTO A SILLY OS RELIGIOUS WAR. Use what you know, use whatever fits your needs best - it doesn't matter, if you know what you're doing it's not the tools that make the difference. – AviD Sep 2 '16 at 12:07
  • On 2nd thought this question is basically demanding opinions of which you prefer. Unless this is completely reformulated to actually ask a specific, objective question, it should be closed. – AviD Sep 2 '16 at 12:09

Overall, this question is rather broad, and will likely have an issue with opinions obscuring facts, so I'll try to keep this answer purely-factual.

say e.g. am using aircrack in windows what will be my disadvantage ?

We can answer that right from the developers of Aircrack:

From Tutorial: Getting Started:

This tutorial is focused on linux. Yes, I realize that linux is a problem for many people. Unfortunately Microsoft Windows simply does a poor job supporting the aircrack-ng suite. This is primarily due to the proprietary nature of the operating system and wireless card drivers. See Tutorial: Aircrack-ng Suite under Windows for Dummies for more details. Bottom line, don't use the aircrack-ng suite under Windows. There is little or no support for it.

And from Tutorial: Aircrack-ng Suite under Windows for Dummies:

First and foremost, Windows is virtually useless for wireless activities due to the huge number of restrictions. The restrictions do not come from the aircrack-ng suite so please don't ask for enhancements.

Here is a quick recap of the limitations:

  • Very few supported wireless cards: There are very few wireless cards which will work with the aircrack-ng suite. Most laptops come with Intel-based cards and none of these are supported. See the following links: Compatibility, Drivers, Which Card to Purchase and Tutorial: Is My Wireless Card Compatible? for more information. It is also important to note that there is little or no documentation accurately describing which version of the third party drivers you require for each card.

  • Dependency on third parties: The Windows world is highly proprietary and thus the source code for the drivers is not available publicly. As a result, no troubleshooting or fixes are available from the aircrack-ng team for these third party drivers. If there is a problem, you are on your own.

  • Limited operating system support: The Windows version works best with WinXP. It does not support Win98, some people have reported success with Win2000 but many have been unsuccessful with it and Vista is not supported. There is some evidence that a few people have aircrack-ng working under Vista but most people report failures. So basically, your best chance of success is under WinXP.

  • Passive capture of packets: Most people want to test the WEP security on their own access point. In order to do this, you must capture in the order of 250,000 to 2,000,000 WEP data packets. This is a lot of packets. With Windows, you can only capture packets passively. Meaning, you just sit back and wait for the packets to arrive. There is no way to speed things up like in the linux version. In the end, it could take you days, weeks, months or forever to capture sufficient packets to crack a WEP key.

  • Limited GUI: Most of the aircrack-ng suite tools are oriented towards command line utilization. There is only a very limited GUI available to assist you. So you must be more technically literate to successfully use these tools. Thus, if you are used to running a Windows installer then clicking your way to happiness, you are going to be exceedingly unhappy and lost with aircrack-ng.

  • Technical Orientation: Dealing with wireless requires a fair amount of operating system, basic wireless and networking knowledge. If you don't have this or are not prepared to do your own research, then you will find the tools and techniques bewildering. Do not expect people on the forums or IRC to answer basic knowledge questions. It is up to you to have these skills before starting out.

If you truly want to explore the world of wireless then you need to make the commitment to learn and use linux plus the aircrack-ng suite linux version. An easy way to start is to utilize the Backtrack live distribution. This distribution has the aircrack-ng suite plus patched drivers already installed which jumpstarts your learning process. BackTrack information can be found here.

So as a quick overview, the developers of Aircrack state that support for Windows is very limited, not because they haven't developed full support, but because the platform itself limits what they can do.


It's mainly for historic reasons, although a lot of the tools I use for post-exploitation are basically built into most linux distributions. Grep, sed, wget and so on are right there, both on all my dists, and in the target environment, which makes it very convenient.

  • same could be said for people very skilled at PowerShell. There is no 'better' system. There is only a personal favor, or specific attack targeting OS level (0-days for example) – Yorick de Wid Sep 1 '16 at 20:29
  • Yes, that is my point, hence the "It's mainly for historic reasons." – Tobias Sep 1 '16 at 20:39

Not the answer you're looking for? Browse other questions tagged or ask your own question.