Generate a self signed certificate on Windows Server using makecert

Przykład:

Generujemy certyfikat do szyfrowania plików (EFS)

1. Tworzymy certyfikat dla lokalnego CA

makecert -n "CN=RootCA" -r -sv RootCA.pvk RootCA.cer

podczas generowania podajemy hasła

2. Importujemy certyfikat RootCA.cer do stora "Local Computer/Trustes Root Certification Authorities"

3. Generujemy certyfikat służący do szyfrowania plików z możliwością wyeksportowania certyfikatu wraz z kluczem prywatnym (do pfx)

Na poniżej stronie znajdziemy interesujący nas OID

http://support.microsoft.com/kb/287547

Can use encrypted file systems (EFS)
szOID_EFS_CRYPTO 1.3.6.1.4.1.311.10.3.4

makecert -sk EFSCert -iv RootCA.pvk -n "CN=EFSCert" -ic RootCA.cer -eku 1.3.6.1.4.1.311.10.3.4 -sr localmachine -ss my -sky exchange -pe EFSCert.cer

Aby zdefiniować swój termin wygaśnięcia certyfikatu korzystamy z przełącznika -e

Jeśli nie ograniczymy daty ważności certyfikatu to jego termin wygaśnięcia zostanie ustawiony na 2040-01-01

makecert -sk EFSCert -iv RootCA.pvk -n "CN=EFSCert" -ic RootCA.cer -eku 1.3.6.1.4.1.311.10.3.4 -e 01/01/2016 -sr localmachine -ss my -sky exchange -pe EFSCert.cer

4. Certyfikat pojawi się w storze "Local Computer/Personal/Certyficates" co wynika z przełączników -sr i -ss

5. W celu instalacji certyfikatu na innym serwerze, należy go wyeksportować wraz z kluczem prywatnym (do pfx) oraz zaimportować na docelowej maszynie. Należy także pamiętać o imporcie naszego RootCA (RootCA.cer) do stora "Local Computer/Trustes Root Certification Authorities".

Powyższa instrukcja

Działa z wersją makecert.exe -

6.0.6000.16384 (vista_rtm.061029-1900) - Microsoft® Windows® Operating System

Nie działa z wersją :

5.131.2157.1 - Microsoft(R) Windows (R) 2000 Operating System

5.131.1863.1 - Microsoft(R) Windows NT(R) Operating System

Strona makecert

http://msdn.microsoft.com/en-us/library/aa386968%28v=vs.85%29.aspx

Microsoft® Windows® Software Development Kit Update for Windows Vista™

http://www.microsoft.com/en-us/download/details.aspx?id=23719

Windows software development kit (SDK)

http://msdn.microsoft.com/en-us/library/windows/desktop/hh852363.aspx

SSH Keys - ssh: Exited: String too long

W celu wygenerowania pary kluczy do autoryzacji w usłudze ssh zainstalowałem OpenSSH keygen:

openssh-keygen - 5.8p2-2 - OpenSSH keygen.

Po wygenerowaniu pary kluczy przekopiowałem klucz publiczny na zdalny serwer
Niestety próba połączenia zwróciła błąd:

ssh -i /root/.ssh/id_rsa  root@remotehost
ssh: Exited: String too long

Rozwiązanie:
Klucze trzeba wygenerowac za pomocą dostępnego w OpenWRT dropbearkey

localhost

dropbearkey -t rsa -f /root/.ssh/id_rsa
dropbearkey -y -f /root/.ssh/id_rsa | grep ssh-rsa > /root/.ssh/id_rsa.pub
scp /root/.ssh/id_rsa.pub root@remotehost:/root

Remotehost

cat /root/id_rsa.pub >> /etc/dropbear/authorized_keys
chmod 600 /etc/dropbear/authorized_keys

localhost

ssh -i /root/.ssh/id_rsa root@remotehost

BusyBox v1.15.3 (2011-11-11 18:03:51 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

2011-11-12 - r28934
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 Backfire (10.03.x, latest version. Always.) -------
  * 1/3 shot Kahlua    In a shot glass, layer Kahlua
  * 1/3 shot Bailey's  on the bottom, then Bailey's,
  * 1/3 shot Vodka     then Vodka.
 ----------( by obsy, http://eko.one.pl/ )----------
Booted from internal flash
root@remotehost:~$

Do czego można to wykorzystać?
Np. Backup

tar czf - /overlay | ssh -i /root/.ssh/id_rsa root@backupserver "cat > /mnt/backupdir/backup-host1-$(date +%Y-%m-%d-%s).tgz"

Backup and Restore ACL NTFS with SetACL

Przeniesienie uprawnień NTFS (DACL) pomiędzy zasobami:

Backup uprawnień NTFS z server1

SetACL.exe -on "\\server1\c$\test" -ot file -actn list -lst "f:sddl;w:d,o,g" -rec cont -bckp "d:\tmp\acl-ntfs.txt"

Edytuj plik "acl-ntfs.txt"
Zmień ścieżki UNC z "\\?\UNC\server1\c$\test" na "\\?\UNC\server2\c$\test"


Restore uprawnień NTFS na server2

SetACL.exe -on "\\server2\c$\test" -ot file -actn restore -bckp "d:\tmp\acl-ntfs.txt" -log "log.txt"

Jeśli chcesz wykonać backup i restore uprawnień na zasobie sieciowym (SACL) to w sekcji -lst trzeba dodać "s", czyli:

-lst "f:sddl;w:d,s,o,g"

 
Strona projektu:
http://sourceforge.net/projects/setacl/
http://helgeklein.com/

Źródła:
http://bog.no/index.php/artikler/2-how-to-backup-ntfs-acl

WSUS Offline Update - zawsze świeże poprawki

WSUS Offline Update - http://www.wsusoffline.net/
To bardzo przydatne narzędzie, które pozwoli na pobranie wszystkich niezbędnych poprawek dla systemów Microsoft, zapisanie ich w pliku ISO, oraz w trybie offline (bez dostępu do Internetu) zainstalowanie ich na naszej maszynie.
Oprogramowanie udostępnia GUI za pomocą, którego możemy wybrać interesujący nas system Windows oraz pakiet MS Office do którego chcemy pobrać dodatki, a także utworzyć pliki ISO z poprawkami.

Z powyższego GUI skorzystamy za każdym razem jeśli będziemy chcieli  dokonać aktualizacji.

Microsoft publikuje poprawki do swoich systemów w drugi wtorek każdego miesiąca.
Jeśli chcemy mieć zawsze świeże poprawki, możemy zautomatyzować cały proces pobierania i tworzenia plików ISO za pomocą skryptu.

Skrypt pobiera poprawki:
Poprawki do systemów operacyjny Microsoft:

• Windows XP PL x86
• Windows 2003 EN x86
• Windows 2003 EN x64
• Windows 2008 x86
• Windows 2008 x64
• Windows Vista x86
• Windows Vista x64
• Windows 2008 R2
• Windows 7 x86
• Windows 7 x64

Poprawki do pakietu Microsoft Office

• MS Office XP,  2003, 2007, 2010 PL

@echo off

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd wxp plk /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd w2k3 enu /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd w2k3-x64 enu /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd w60 glb /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd w60-x64 glb /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd w61 glb /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd w61-x64 glb /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd ofc glb /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd o2k3 plk /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\DownloadUpdates.cmd o2k7 plk /includedotnet /verify /exitonerror

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd wxp plk

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd w2k3 enu

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd w2k3-x64 enu

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd w60 glb

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd w60-x64 glb

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd w61 glb

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd w61-x64 glb

call d:\Download\wsusoffline\cmd\CreateISOImage.cmd ofc plk

Skrypt konfigurujemy tak, aby uruchamiał się cyklicznie: w moim przypadku druga środa każdego miesiąca o 4:00 rano.

Po zakończeniu pobierania poprawek, tworzone są obrazy ISO z poprawkami dla konkretnych systemów i pakietów office w katalogu wsusoffline\iso\

Próba włamania do TL-WR1043N z OpenWRT Backfire

Próba miała na celu analizę logów z routera zebranych podczas próby ataku na sieć WiFi.

Do testów użyto:

• Router TP-Link TL-WR1043ND z alternatywnym firmware OpenWRT Backfire 10.03.1-rc4 [AP:AP:AP:AP:AP:AP]
• Klient podłączony do AP [C1:C1:C1:C1:C1:C1]
• WLAN 11g USB Adapter – Chipsert ZyDAS ZD1211B – [C2:C2:C2:C2:C2:C2]
• System operacyjny BackTrack 4 R2

Konfiguracja TL-WR1043ND

Dystrybucja: OpenWRT Backfire 10.03.1-rc4
Kompilacja: 2011-02-26 - r25718

root@server:~# uname -a
Linux server 2.6.32.27 #7 Sat Feb 26 15:25:42 CET 2011 mips GNU/Linux

Wykonane testy:

TEST 1. Injection test
(http://www.aircrack-ng.org/doku.php?id=injection_test)

root@bt:~# aireplay-ng -9 -a AP:AP:AP:AP:AP:AP -e test -B mon0

13:51:22 Waiting for beacon frame (BSSID: AP:AP:AP:AP:AP:AP) on channel 5
13:51:22 Trying broadcast probe requests...
13:51:22 Injection is working!
13:51:24 Found 1 AP

13:51:24 Trying directed probe requests...
13:51:24 AP:AP:AP:AP:AP:AP - channel: 5 - 'test'
13:51:25 Ping (min/avg/max): 8.055ms/22.076ms/138.223ms Power: -50.72
13:51:25 29/30: 96%

13:51:25 Trying directed probe requests for all bitrates...

13:51:25 AP:AP:AP:AP:AP:AP - channel: 5 - 'test'
13:51:28 Probing at 1.0 Mbps: 13/30: 43%
13:51:29 Probing at 2.0 Mbps: 23/30: 76%
13:51:31 Probing at 5.5 Mbps: 23/30: 76%
13:51:32 Probing at 6.0 Mbps: 24/30: 80%
13:51:33 Probing at 9.0 Mbps: 22/30: 73%
13:51:34 Probing at 11.0 Mbps: 24/30: 80%
13:51:35 Probing at 12.0 Mbps: 23/30: 76%
13:51:36 Probing at 18.0 Mbps: 26/30: 86%
13:51:37 Probing at 24.0 Mbps: 24/30: 80%
13:51:38 Probing at 36.0 Mbps: 24/30: 80%
13:51:39 Probing at 48.0 Mbps: 24/30: 80%
13:51:40 Probing at 54.0 Mbps: 26/30: 86%

Logi AP

Apr 13 19:51:27 hostapd: wlan0: STA 00:ad:81:0d:12:57 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:33:9d:9e:04:c0 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:42:51:e9:95:6d IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:64:ad:5c:24:66 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:be:04:79:ef:c9 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:a1:76:b1:77:6f IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:e0:24:f1:ed:37 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:94:29:77:7d:be IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:d4:ec:65:85:63 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:bf:0e:74:93:f4 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:8e:19:34:99:63 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:22:6d:4f:87:f2 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:b3:5c:58:3b:21 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:ab:fa:2f:1f:8d IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:5b:1d:bd:e2:65 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:f2:70:7e:26:09 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:e1:49:76:31:d0 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:69:e4:2c:c1:1f IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:a6:a1:43:5c:e3 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:0c:b7:00:ca:99 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:51:27 hostapd: wlan0: STA 00:65:bc:0a:e3:e3 IEEE 802.11: did not acknowledge authentication response
Apr 13 19:56:28 hostapd: wlan0: STA 00:ad:81:0d:12:57 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:33:9d:9e:04:c0 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:42:51:e9:95:6d IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:64:ad:5c:24:66 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:be:04:79:ef:c9 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:a1:76:b1:77:6f IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:e0:24:f1:ed:37 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:94:29:77:7d:be IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:d4:ec:65:85:63 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:bf:0e:74:93:f4 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:8e:19:34:99:63 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:22:6d:4f:87:f2 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:b3:5c:58:3b:21 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:ab:fa:2f:1f:8d IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:5b:1d:bd:e2:65 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:f2:70:7e:26:09 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:e1:49:76:31:d0 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:69:e4:2c:c1:1f IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:a6:a1:43:5c:e3 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:0c:b7:00:ca:99 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:28 hostapd: wlan0: STA 00:65:bc:0a:e3:e3 IEEE 802.11: disassociated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:ad:81:0d:12:57 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:33:9d:9e:04:c0 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:42:51:e9:95:6d IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:64:ad:5c:24:66 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:be:04:79:ef:c9 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:a1:76:b1:77:6f IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:e0:24:f1:ed:37 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:94:29:77:7d:be IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:d4:ec:65:85:63 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:bf:0e:74:93:f4 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:8e:19:34:99:63 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:22:6d:4f:87:f2 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:b3:5c:58:3b:21 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:ab:fa:2f:1f:8d IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:5b:1d:bd:e2:65 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:f2:70:7e:26:09 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:e1:49:76:31:d0 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:69:e4:2c:c1:1f IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:a6:a1:43:5c:e3 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:0c:b7:00:ca:99 IEEE 802.11: deauthenticated due to inactivity
Apr 13 19:56:29 hostapd: wlan0: STA 00:65:bc:0a:e3:e3 IEEE 802.11: deauthenticated due to inactivity

TEST 2. Fake authentication
(http://www.aircrack-ng.org/doku.php?id=fake_authentication)

root@bt:~# aireplay-ng -1 0 -e test -a AP:AP:AP:AP:AP:AP -h C2:C2:C2:C2:C2:C2 mon0

Logi AP

Apr 13 20:38:09 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:09 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:12 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:12 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:15 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:15 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:18 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: authenticated
Apr 13 20:38:18 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:21 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:21 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:24 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:24 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:27 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:27 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:30 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:30 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:33 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:33 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:36 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:36 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:39 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:39 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:42 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:42 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:45 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:45 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
Apr 13 20:38:48 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: No WPA/RSN IE in association request
Apr 13 20:38:48 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: did not acknowledge authentication response
...
Apr 13 20:43:10 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: disassociated due to inactivity
Apr 13 20:43:11 hostapd: wlan0: STA C2:C2:C2:C2:C2:C2 IEEE 802.11: deauthenticated due to inactivity

TEST 3. Capturing
(http://www.aircrack-ng.org/doku.php?id=airodump-ng)

root@bt:~# airodump-ng -c 5 --bssid AP:AP:AP:AP:AP:AP -w test mon0

Logi AP

Brak

TEST 4. Deauthentication
(http://www.aircrack-ng.org/doku.php?id=deauthentication)

root@bt:~# aireplay-ng -0 2 -a AP:AP:AP:AP:AP:AP -c C1:C1:C1:C1:C1:C1 mon0

15:44:21 Waiting for beacon frame (BSSID: AP:AP:AP:AP:AP:AP) on channel 5
15:44:22 Sending 64 directed DeAuth. STMAC: [C1:C1:C1:C1:C1:C1] [87|107 ACKs]
15:44:22 Sending 64 directed DeAuth. STMAC: [C1:C1:C1:C1:C1:C1] [ 0|63 ACKs]

Logi AP

Apr 13 21:44:22 hostapd: wlan0: STA C1:C1:C1:C1:C1:C1 IEEE 802.11: authenticated
Apr 13 21:44:22 hostapd: wlan0: STA C1:C1:C1:C1:C1:C1 IEEE 802.11: associated (aid 1)
Apr 13 21:44:22 hostapd: wlan0: STA C1:C1:C1:C1:C1:C1 WPA: pairwise key handshake completed (RSN)
Apr 13 21:44:22 dnsmasq-dhcp[1364]: DHCPREQUEST(br-lan) 10.0.0.10 C1:C1:C1:C1:C1:C
Apr 13 21:44:22 dnsmasq-dhcp[1364]: DHCPACK(br-lan) 10.0.0.10