-
Notifications
You must be signed in to change notification settings - Fork 13
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
connman_curses will try to connect to a protected network with an empty password #12
Comments
Hi,
And it does, here's how everything plays out:
I'm afraid this isn't possible due to the
I believe so. |
It's as you said, if a wrong password is given connman_curses will keep asking for the correct one, if an empty passwords is given then it will just keep trying to connect without asking again. As for your explanation I guess it's connman fault then. Thanks for the clarification =) |
Has someone of you searched on connman side? or contacted someone of connman? I propose to keep that issue opened until we get an entry in the bug tracker of connman or something like that. The connman team could say: "you should not send an empty password, just validate your input." In that case, the bug is here. |
The My apologies if the explication was unclear. |
Hello,
Thanks for the awesome program, lately I've been playing with
connman_curses
and found a strange behavior when failed to set a password for a protected (wpa/personal) network.Testcase
connman_curses
wifi technology
connman_curses
fails to connect with the following messageInvalid argument/value.
(I think that's fine because I forgot to insert the password)<Esc>
to go back to the network list window (In my opinion it should go back to the credentials window instead)[ERROR] Unidentified call back: status: -1, jobj: { "ERROR": [ "In progress" ] }
After this the only way to reconfigure the desired network is by restarting connman. (sudo service connman restart)
Expected behavior: Connman_curses should keep asking for credentials while they're not given
The text was updated successfully, but these errors were encountered: