Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-12-21 11:52:34 +01:00
Code Releases Activity
f6cfcb8ca2
iwd/autotests/testSAQuery-spoofing/connection_test.py

80 lines
2.3 KiB
Python
Raw Normal View History

auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
#!/usr/bin/python3
import unittest
import sys
sys.path.append('../util')
import iwd
from iwd import IWD
from iwd import PSKAgent
from iwd import NetworkType
from hwsim import Hwsim
auto-t: prepare autotests for test-runner re-write The tests basically remained the same with a few minor changes. The wiphy_map and in turn hostapd_map are no longer used. This was already partially converted a long time ago when the 'config' parameter was added to HostapdCLI. This patch fully converts all autotests to use 'config' rather than looking up by interface. Some test scripts were named 'test.py' which was fine before but the new rewrite actually loads each python test as a module. The name 'test' is too ambiguous and causes issues due to a native python module with the same name. All of these files were renamed to 'connection_test.py'.
2020-09-11 01:12:22 +02:00
from hostapd import HostapdCLI
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
from time import sleep
class Test(unittest.TestCase):
def test_connection_success(self):
hwsim = Hwsim()
auto-t: updated autotests to use hwsim.get_radio This removes all the duplicated code where the interfaces are iterated and the radio/hostapd instances are created. Instead the two new APIs are used to get each instance, e.g.: hapd = HostapdCLI(config='ssid.conf') radio = hwsim.get_radio('radX')
2019-06-11 18:25:54 +02:00
hostapd = HostapdCLI(config='ssidCCMP.conf')
radio = hwsim.get_radio('rad0')
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
wd = IWD()
psk_agent = PSKAgent("secret123")
wd.register_psk_agent(psk_agent)
auto-t: removed ';' from many autotests At some point a stray ';' got added into an autotest in a section of code that is heavily copy pasted. So in turn nearly all the autotests have this stray ';' after list_devices (and a few in other places).
2018-12-14 20:15:26 +01:00
devices = wd.list_devices(1)
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
device = devices[0]
auto-t: update all tests to remove bad scanning logic This changes all tests to use the default get_ordered_network behavior rather than some custom or incorrect logic. Any use of scan_if_needed=True has been removed since this is now the default. Also any explicit scanning has been removed for tests which do not require it (where the default behavior is good enough).
2021-08-12 22:38:11 +02:00
ordered_network = device.get_ordered_network('ssidCCMP')
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
self.assertEqual(ordered_network.type, NetworkType.psk)
condition = 'not obj.connected'
wd.wait_for_object_condition(ordered_network.network_object, condition)
ordered_network.network_object.connect()
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
auto-t: fix SAQuery-spoofing test This test occationally failed due to a badly timed DBus scan triggering right when hwsim tried sending out the spoofed frame. This caused mac80211_hwsim to reject CMD_FRAME when the timing was just right. Rather than always starting a DBus scan we can rely on periodic scans and only DBus scan if there are no networks in IWD's list. A scanning check was also added prior to sending out the frame and if true we wait for not scanning. This is more paranoia than anything.
2021-02-05 19:09:11 +01:00
# Ensure IWD is not scanning. This causes problems with mac80211_hwsim
# where CMD_FRAME will fail during a scan. This is due to the frame not
# having the same frequency as the radio (since hwsim is off-channel)
if device.scanning:
condition = 'not obj.scanning'
wd.wait_for_object_condition(device, condition)
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
# Spoof a disassociate frame. This will kick off SA Query procedure.
auto-t: use .frequency property in SAQuery-spoofing test
2021-08-13 01:12:32 +02:00
hwsim.spoof_disassociate(radio, hostapd.frequency, device.address)
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
auto-t: SAQuery-spoofing replace sleep with condition wait By sleeping for 4 seconds IWD had plenty of time to fully disconnect and reconnect in time to pass the final "connected" check. Instead use wait_for_object_condition to wait for disconnected and expect this to fail. This will let the test fail if IWD disconnects.
2021-10-19 20:19:05 +02:00
# ensure hostapd responds and SA Query does not timeout
with self.assertRaises(TimeoutError):
condition = 'obj.state == DeviceState.disconnected'
wd.wait_for_object_condition(device, condition, 4)
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
# Since disassociate was spoofed we should still be connected
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
auto-t: add SA Query tests Two autotests: 1. Tests SA Query procedure when the AP goes down. In this case the AP goes down ungracefully, now allowing it to send out any deauth frames. When the AP comes back up, IWD still thinks its connected. The AP will then send unprotected disassociate frames so the client can re-connect. This kicks off the SA Query procedure, which the AP will not respond to. At this point we can deauth and reconnect to the AP. 2. Test SA Query procedure when a disassociate frame has been spoofed. In this case we receive an unprotected disassociate frame and start SA Query. The AP should then respond to the SA query within the timeout. We then know the frame was spoofed and can remain connected.
2018-01-31 18:56:00 +01:00
device.disconnect()
condition = 'not obj.connected'
wd.wait_for_object_condition(ordered_network.network_object, condition)
wd.unregister_psk_agent(psk_agent)
@classmethod
def setUpClass(cls):
pass
@classmethod
def tearDownClass(cls):
IWD.clear_storage()
if __name__ == '__main__':
unittest.main(exit=True)
Copy Permalink