open roku .pkg after encrypting

We agree that we should not allow side-loading of .pkg files. When we added that capability, we weren't thinking of the use case of a developer sharing a package with a third party client. This ability is there for now, but in an upcoming release we'll take it away.

Endless, when you share your .pkg do you also plan on sharing the passwd to the key? We're thinking of not allowing any side-loading of .pkg files so even if the client had the key (to create their own future updates) they wouldn't have access to the source in the .pkg.

--Kevin

"RokuKevin" wrote:
We agree that we should not allow side-loading of .pkg files. When we added that capability, we weren't thinking of the use case of a developer sharing a package with a third party client. This ability is there for now, but in an upcoming release we'll take it away.

Great! Thanks!

"RokuKevin" wrote:
Endless, when you share your .pkg do you also plan on sharing the passwd to the key? We're thinking of not allowing any side-loading of .pkg files so even if the client had the key (to create their own future updates) they wouldn't have access to the source in the .pkg.

Not typically, no. I usually only provide the password/key with the source.
I can actually see some value in being able to side-load a .pkg file, so requiring the password to do so seems like a reasonable compromise.