hi everyone,

i'm searching during all week end and didn't find an answer to my
question : why WRITE_SECURE_SETTING permission exist if you can ask
and obtain this permission?

as more as i can see, to have this permission you need to be part of
the system (argh!) or to have your apk signed with the same that the
system (argh again) ... so why this permission exist if in fact to
have the possibility to write secure setting is linked to something
else than this permission?

more of that, is it possible for a simple dev guy to be able to sign
his apk with "framework" certificate or something like that?

if it's a permission to ask, why, when you ask it, you can't have it?
it's like a bone in front a a dog, on the other side of a closed
window :-(

i like security on android : you ask permission, a disclaimer appear
to the end user when he install your apk, and see what you want to
do ... why this setting is so secure and not allow disclaimer as other
permission?

many question, i hope some google dev guys and girls can help me to
understand that...

thanks in advance,

regards,

ps: i'm on android 1.6

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to