Hi Grant,

As for use cases, I believe Drew and I have just presented a very real world 
and credible use case. This use case, when measured in shipping unit volumes 
that likely continues to make it one of the largest single (and possibly 
aggregate) connman implementations, is all the more real world.

Sure, real world use case but still very specific ;-)


What alternative proposals would you suggest that provide similar functionality 
and utility in a manner that do not rely on side-channel approaches leveraging 
unofficial, unsupported implementation internals of connman?

Myself I believe we may have to think at one point about a proper provisioning/configuration/settings management api. Something that could solve at once all issues related to this, with proper access rights on the dbus interface etc..., which then would also provide a proper api for some ui about it. This idea might just be off though.

But since I am not the maintainer you could go for a small patch for your own usage adding such PassPhrase back. It should be small enough not to give to much work to maintain besides connman tree I guess.

Wait for Patrik's return for his opinion.

Tomasz
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman

Reply via email to