Once again I am seeing certain individuals suggesting that disabling Smack is a "workaround to make development easier". Do not believe these people. They do not have your best interests at heart. They are the same people who suggest that you do your testing as root, or that your application will run faster if you make the private data directory publicly writeable. Sure, it will seem like you are making better progress for a while, but eventually you will have to deal with the harsh reality that you have made decisions about how your program should work that are invalid in the real Tizen environment.
Everyone working on Tizen 3 should read https://wiki.tizen.org/wiki/Security:SmackThreeDomainModel which describes the way Smack is being used in Tizen 3. If you have questions do not hesitate to ask them. The Tizen 3 model is different from the Tizen 2 model. If you read the wiki page you will see that it is simpler and generally requires less of developers than before. The key points are to use the default manifest (as described in the wiki page) and don't relabel files. If you need to run a process in a domain that isn't defined the new domain needs to be documented before it is deployed.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
