View Single Post
Old 09-27-2016, 11:41 AM   #17
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by zxczxc View Post
- - - - -
Any information on how to FORCE a value?
We have root after all...

Thanks
I do not have a 'precooked, re-heat and use' answer for that.
Two thoughts -

lipc is just a specialized wrapper around d-bus.
If access controls are set at the lipc level, you might be able to 'go under' those controls using d-bus utilities directly.

At the (presumed) lowest level they may be controlled in the system key data base.
Use the on-board kdb utility to list those db entries (which might be what lipc is doing above as part of its d-bus wrapper functions).

kdb without arguments gives you a handle on basic usage.

The kdb database is in a read-only structure but some of the add-ins modify it by "mount --bind ... ..." something over the entry that needs to be different.
ah, maybe ss does that (something of NiLuje's does).
knc1 is offline   Reply With Quote