-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to kill Dropbear / Dropbear settings are overwritten #32
Comments
I don’t think we can merge #33 because of implications it could have for normal users, but I’ll let coolstar decide |
@nullpixel Agreed. I'd rather just remove option to start after kill. |
I agreee setting to 127.0.0.1 maybe be somewhat difficult for the normal user. #33 only sets a check on if the plist has been created it doesn’t change the plist itself. The issue I was raising was more that the dropbear modifications are lost on each running of Electra. If it’s already there it doesn’t make sense to overwrite it and cause the user to lose their dropbear modifications. |
the overwriting is meant to be there: i purposely added it. it allows us to update the plist |
That's fair enough, thanks again for all the effort you guys are putting in :) |
With the new addition of the launchctl and dropbear being ran under launchd, the daemon is restarting the dropbear process when its being killed.
Changes to the dropbear.plist to not have to kept ssh alive and to only run on 127.0.0.1 are lost as the file is overwritten each time electra is ran.
Can electra run file_exist on the plist before overwriting the file.
electra/electra/the_fun_part/fun.c
Line 669 in e0911d2
Thanks for all your work :)
Added a pull request with some changes, runs okay on my device and the dropbear changes remain after a reboot and rejailbreak
#33
The text was updated successfully, but these errors were encountered: