View Single Post
Old 08-02-2017, 11:39 PM   #742
itwtx
Junior Member
itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.itwtx got an A in P-Chem.
 
Posts: 3
Karma: 6188
Join Date: Aug 2017
Device: Aura HD, Aura One, PRS650
I would like to report a pretty serious bug.

When one tries to enable a usbnet connection with usbnet_toggle.sh script, the script checks if a dropbear process is running. If it does, the script assumes that the usbnet is up. It proceeds with killing the process and exiting.

Such a logic is only valid if the dropbear process is launched by usbnet_toggle itself, from a pbchess package. If dropbear is installed in some other way (for instance, via kobo-aura-remote or kobo-ssh), such a logic results in a dead ssh server when usbnet is up.

The problem can be easily fixed by making a condition in usbnet_toggle.sh
if [ -f /var/run/dropbear.pid ]
more restrictive. For instance
if [ -f /var/run/dropbear.pid ] && [ "$useDropbear" == "true" ] && [ -d "$vlasovsoft_usbnet" ]
itwtx is offline   Reply With Quote