View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005383Kali LinuxGeneral Bugpublic2019-04-05 14:012020-12-01 10:48
Reporterbfbcping Assigned Tosteev  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2019.1 
Fixed in Version2019.2 
Summary0005383: Cannot attach to new hidden network on USB with persistence
Description

After performing an apt-get upgrade, a USB install with persistence cannot attach to a new hidden (non-broadcasting) network. Instead, the network GUI crashes. Similar attempts through terminal attachments to the same networks similarly fail. This has been attempted using multiple USB drives, multiple computers, and multiple hidden networks. The issue was difficult to determine as attaching to the network before the first apt-get upgrade will save it and allow you to attach to it after reboot, but forgetting the network and attempting to re-attach (or attach to any hidden network) results in the network dialog crashing and no connection being made.

Steps To Reproduce

Write ISO to USB drive
Shrink live partition and create persistence partition on remainder of drive
Boot machine on live USB
Pull up terminal on the persistence partition and issue 'echo "/ union" > persistence.conf' command
Reboot and select persistence
Connect to any network and run apt-get upgrade -y
When finished, ensure that any connected hidden network (if connected) is forgotten
Reboot and select persistence
Try to connect to a hidden wireless network.

Activities

bfbcping

bfbcping

2019-04-05 14:41

reporter   ~0010478

This has only been tried when attaching to a wireless network with WPA2 enabled.
bfbcping

bfbcping

2019-04-05 20:44

reporter   ~0010480

It occurred to me that I always ran:
apt-get update -y && apt-get upgrade -y

I don't imagine it makes the end result different, but that was my procedure.
bfbcping

bfbcping

2019-06-20 12:42

reporter   ~0010713

It appears that this was fixed from 2019.1 to 2019.2.
I don't see where I can close the issue, but if anyone is there to admin, please close it. It's fixed.
steev

steev

2019-06-20 17:59

manager   ~0010714

Thanks for letting us know, resolved in 2019.2.

Issue History

Date Modified Username Field Change
2019-04-05 14:01 bfbcping New Issue
2019-04-05 14:41 bfbcping Note Added: 0010478
2019-04-05 20:44 bfbcping Note Added: 0010480
2019-06-20 12:42 bfbcping Note Added: 0010713
2019-06-20 17:59 steev Assigned To => steev
2019-06-20 17:59 steev Status new => resolved
2019-06-20 17:59 steev Resolution open => fixed
2019-06-20 17:59 steev Fixed in Version => 2019.2
2019-06-20 17:59 steev Note Added: 0010714
2020-12-01 10:48 g0tmi1k Priority high => normal