I don't know anything about wpa, so my answer is not specific to wpa or the problem in first paragraph. This is only about the second paragraph.
When I need to run something as non-root from adb shell, I usually just do: su uid# For example: adb shell root@manta:/ # id uid=0(root) gid=0(root) context=u:r:shell:s0 root@manta:/ # su 1010 root@manta:/ $ id uid=1010(wifi) gid=1010(wifi) context=u:r:su:s0 root@manta:/ $ id I think chown only does what you want if you also set the setuid bit. On Wednesday, October 30, 2013 9:41:51 AM UTC-7, Bruno Correia wrote: > > Hi all, > > I'm trying to cross-compile the wpa_cli, so that in the future i can > change some of it's methods. > At the moment, I can cross-compile the wpa_cli using the > arm-linux-gnueabi-gcc, but when I push the wpa_cli into my Android and try > to run it, it remains in loop trying to connect to the wpa_supplicant. > > According to what i could ascertain, the wpa_supplicant and wpa_cli of the > system, run as wifi group. However, when i run my wpa_cli with adb, the > proccess always run as root. Even if i use "chown wifi.wifi wpa_cli". Could > the problem be here? > > Any guess why this is happening? > > Best Regards, > Bruno Correia > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
