Regarding the confusion of the DSM 7 permissions (root/user) during the installation process I got today the follow message from Synology:
Start
Yes, you may continue using root privilege ONLY if you apply a token from us to bypass the lower privilege setting this time round, without which, your package installation would fail in DSM7.0 Beta.
As mentioned in point 2 in my previous email:
To avoid future update issues, It is highly recommended that your package can be modified to match our new lower privilege framework. Please develop according to the new developer’s guide provided, and your users will still be able to carry out manual installation even if the package has yet to be approved and signed by Synology.
In case of development time or technical constraints, we provided a tentative alternative for the benefit of existing third-party packages in our Package Center.
To ensure that your current package remains functional in DSM7.0, you will be allowed to continue using the same privilege level settings for your new versions until further notice. However, you have to apply for an exemption token from us to be able to develop smoothly on your NAS device. Please note that your package will have to be officially approved and signed by Synology before your package can be released in our Package Center or to users for manual installation.
If you wish to continue running as root rather than user, please follow the instructions below:
i) Log in to the DSM of NAS device(s) that you want to develop / test on
ii) Open Support Center → Support Services → Log Generation → Check “System” → Generate logs → Download “debug.dat”
iii) Send this “debug.dat” to us by replying to this email (if you have more than one NAS device, please label the respective debug.dat clearly.)
iv) We’ll then send you the token file (each token is only valid for one specific NAS device), for which you’ll have to rename it to syno_dev_token and place it under this location → /var/packages/
v) You are all set to develop the new version using your current privilege level setting.
Our ultimate goal is still hoping for all of our package developers to be able to abide by our new privilege setting in future versions.
End