Poor WiFi BSSID string sanitation causes malformed CSV file

[AlexLynd]

Values are popping up in the wrong places and I suspect this is due to poor sanitation of WiFi names (BSSID's) which might contain commas.

[lukeswitz]

Tricky one- could be SSID with quotes in it, or commas,

It skips the firstSeen column after the name and fills in all data, stretching the csv doc to contain an extra column on the end:

(MAC & Location data redacted)

SSID	FirstSeen	AuthMode	Channel	Signal Strength	Latitude	Longitude	Altitude	Accuracy	Type
ARLO_VMB_1576818505	2023-7-20 18:12:10	[WPA2-PSK-CCMP+TKIP][ESS]	3	-90	xxxxxxxxxx	xxxxxxxxxxx	xxxxxxxx	0.820000	WIFI
Jerrynet5.0	2023-7-20 18:12:10	[WPA2-PSK-CCMP+TKIP][ESS]	11	-70	xxxxxxxxxx	xxxxxxxxxxx	xxxxxxxx	0.820000	WIFI
Kitchen speaker.o		2023-7-20 18:12:10	[ESS]	6	-86	xxxxxxxxxx	xxxxxxxxxxx	xxxxxxxx	0.820000	WIFI
Bose Wave ST (DC6885)	2023-7-20 18:11:39	[ESS]	1	xxxxxxxx	xxxxxxxx	xxxxxx	0.820000	WIFI

Confirmed by a second capture of the Kitchen speaker.o network and other networks containing similar syntax

[lukeswitz]

Another problem with the CSV was using int for the day-month min:sec. Using %02d in strDateTime fixes this when it’s written later.

[AlexLynd]

@lukeswitz heck i still have to fix the original issue, and also the wigle upload - this should be solved in the latest revision though!

[lukeswitz]

Still happens with some networks. No idea. Same as above.