On Tue, Dec 22, 2020 at 12:00:03AM -0000, * * wrote:
I ran into the following issue with connman recently. I would have
prefered to open a Jira ticket for that but I don't seem to be able to
request access to https://01.org/jira/projects/CM
which is rather
expected though. I hope this is the right place to post this in this
context, please someone tell me otherwise.
I've just cleanup all stale issues in the Jira. The idea was that we can
use it for new bugs reports. It's useless if we as community can't login
in. Furthermore, the configuration of this Jira is also targeted to
Intel's product development and has lot's of bells and whistles upstream
never will use.
Thus I was pondering to use something else. Obvious choice are a
gitlab/github but we don't need the rest they offer, especially the
workflow with PR, as the development happens here on the mailing list.
So I am not sure what to do here.
# cat settings
# connmanctl connect wifi_[...]
Error /net/connman/service/wifi_[...]: Input/output error
# cat settings
We use GLib's key file API to read and write the settings file. The
problem might be we that we don't escape the special chars when writing
the passhphrase and later we retrieve it using a plain
g_key_file_get_string(). The documenation says
'... this function handles escape sequences like \s.'
So clearly we need to encode the string when saving it to settings.
Also note that most modern WiFi tools (e.g. wpa_supplicant) offer
possibility to store hashed passphrases rather than clear ones in
their config files, for 2 good reasons:
1. It is safer and good practice to store a hashed password rather than a clear one;
2. a hash will never have any special character issue such as the one
described in this ticket.
There was a lot discussion about this in the past. I can't remember why
we have decided to keep them in plain text though. Just note, to declare
'it's safer' without a context doesn't say anything. What's the
vector, what is the asset, what does the attacker gain with it, ..w. are
the question to answer first.
As a side note, my WiFi password do start with a double quote
character as well as ending witht a backslash. I was not specifically
looking for trouble but it seems I have been very "unlucky" with the
password generator I used at the time I setup the network.
See it positive, you are good tester. You find the bugs!
I have since plugged my rPi to my network via ethernet rather than
WiFi for bandwidth reasons so it is not a blocker to me anymore, but I
believe I may not be the only one hitting this wall so it may worth a
Thanks for the report I'll think I know exactly where the problem is.