3 ms·
But by installing a self-signed certificate, that certificate is trusted for all apps, not only for mine – right? This seems like a broken permission model. I
by ptx 3y ago
But by installing a self-signed certificate, that certificate is trusted for all apps, not only for mine – right? This seems like a broken permission model.
I only want permission to modify my own app, not every app of the system. If users have to trust me (and all other developers of self-signed applications) with permission to modify all apps, that makes the whole signing rigamarole kind of pointless.
But if I do want to try this approach, do I have to install the certificate in Trusted Root Certification Authorities, or should it be in Trusted Publishers, or Trusted People? The first one would grant me even more privileges that I don't need, but what about the other two?
- mike_hearn 3y agoBTW, dead thread, I should note that the certs Conveyor generates aren't CA certificates. They have your chosen identity name in them, so you can't use it to sign for other packages.
- mike_hearn 3y agoIf you publish through the MS Store, it only costs $19 to verify an individual (one off, not a subscription) and they sign it for you. So that's pretty cheap, well within the range of a hobby project. If you don't have some kind of signed identity then the concept of "your own" app doesn't exist, so indeed in that model you get permission to do what you want more or less. That's why it requires administrator elevation, whereas real signed packages don't. Of course this model is identical to the normal pre-MSIX model where any app installer can fiddle with any other app's files. You can put it in Trusted People, I think. I'd have to check the code to see where we put it.