Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aircrack-ng not saved session file when program interrupt by SIGTERM #2606

Open
itmagpro opened this issue Apr 7, 2024 · 0 comments
Open

Comments

@itmagpro
Copy link

itmagpro commented Apr 7, 2024

When I run v1.7 on Debian 10 for try remember password:

aircrack-ng -a 2 -b xxxxx -w paswd.txt -N user.sess user.cap

File user.sess created with content:

/home/yuzver/wifi/brut
00:00:00:00:00:00
0 1216631 83716
8
aircrack-ng
-a
2
-b
xxxxx
-w
paswd.txt
user.cap

But when interrupt aircrack-ng by CTRL+C, then session file not saved and dissapear ;(

Then I create user.sess by hand with same content and run:

aircrack-ng -R user.sess

After interrupt by run pkill aircrack-ng and user.sess file again dissapear ;(

WARNING! QUESTION!

Which profit we can get from this aircrack-ng -N session_file behavior, when user.sess file dissapeared after any interrupt!?

Profit from this session file may be only in case when:

  1. all power lost;
  2. force restart or power off by press buton on PC.

In any other case aircrack-ng -N session_file not provide any profit!

P.S. I think, this is bug and that aircrack-ng don't must delete session_file when get SIGTERM signal!

Also I want know which mean line 2 (00:00:00:00:00:00), line 3 (0 1216631 83716), line 4 (8)?

  • 83716 - keys tested
  • 0 1216631 - which mean this value?

Where I can read description about session_file format, if this posible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant