Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hello:

In the Appsigner, after pointing its wizard to the correct ARM directory, it brings up a list of the files in the directory and different check-box choices for each file. I am uncertain as to the impact of some of these choices.

Specifically, there is a small data file that we have in the directory. It is a file the aplicaiton needs to use and often modify. Also, it is possible it will be slightly modified by OEMs if the applicaiton is pre-loaded onto handsets.

So, right now in the Appsigner, the "Sign" check box shows No, and the "Allow Modification" check box shows no. If I leve it that way, can the applicaiton use and modify the file freely, and could an OEM make a small change to the file, all without causign some signiture or other issue?

THanks!

We typically sign ALL of the included files to ensure that the package is complete upon install. We then mark any files that are edited by the app as 'YES' for modifiable.
What you are suggesting sounds ok, but I am slightly concerned I heard something about having the files in the package all signed....
Hope that helps.

We typically sign ALL of the included files to ensure that the package is complete upon install. We then mark any files that are edited by the app as 'YES' for modifiable.
What you are suggesting sounds ok, but I am slightly concerned I heard something about having the files in the package all signed....
Hope that helps.

ZeroCool wrote:We typically sign ALL of the included files to ensure that the package is complete upon install. We then mark any files that are edited by the app as 'YES' for modifiable.
What you are suggesting sounds ok, but I am slightly concerned I heard something about having the files in the package all signed....
Hope that helps.
Thanks!
Just to make sure I am getting you - you understand tha all files in the package must be signed?
The default on the AppSigner only seems to sign the "core" files - MIF, MOD, BAR - and by default does not sign the others. Other packages I've submited successfully included a sound file that I did not sign. However, it was a read-only file for the application.
So, I am workign to be sure I undertand signing and modifiable files, especially one that might be modified by an OEM.
Thanks.
- Sean

ZeroCool wrote:We typically sign ALL of the included files to ensure that the package is complete upon install. We then mark any files that are edited by the app as 'YES' for modifiable.
What you are suggesting sounds ok, but I am slightly concerned I heard something about having the files in the package all signed....
Hope that helps.
Thanks!
Just to make sure I am getting you - you understand tha all files in the package must be signed?
The default on the AppSigner only seems to sign the "core" files - MIF, MOD, BAR - and by default does not sign the others. Other packages I've submited successfully included a sound file that I did not sign. However, it was a read-only file for the application.
So, I am workign to be sure I undertand signing and modifiable files, especially one that might be modified by an OEM.
Thanks.
- Sean

Yes, you are correctly understanding what I am saying. We sign all of the files included in our packages.
However, we have not had any files adjusted by OEMs, so that is definitely a new wrinkle. Since you were able to have apps go out previously with files that were not signed, maybe that is the safest bet.
Sorry this isn't more conclusive...

Yes, you are correctly understanding what I am saying. We sign all of the files included in our packages.
However, we have not had any files adjusted by OEMs, so that is definitely a new wrinkle. Since you were able to have apps go out previously with files that were not signed, maybe that is the safest bet.
Sorry this isn't more conclusive...

Hello:
Thanks for the insight.
At this point I want to throw it back out to the community. I want to understand the difference between a file within a submission is unsigned, and when it is signed and makrked modifiable. If I don't sign it at all, can an application use the file, including modifying it? Or, must it be signed and marked as modifiable? It seems to me an nsigned file is open for modification by the app, but I can imagine that might not be the case.
Anyone else have experience or insights?

Hello:
Thanks for the insight.
At this point I want to throw it back out to the community. I want to understand the difference between a file within a submission is unsigned, and when it is signed and makrked modifiable. If I don't sign it at all, can an application use the file, including modifying it? Or, must it be signed and marked as modifiable? It seems to me an nsigned file is open for modification by the app, but I can imagine that might not be the case.
Anyone else have experience or insights?

Hello:
I spoke with a guy who works for a porting company we have a relationship with. He's their point on NSTL submissions and he's given me good advice before. His experience and advice was to mark as few files as possible as signed in the AppSigner, and that unsigned files would be fully available for reading and modification by the applicaiton.
I respect his advice and have made my submission basd on it, but am still curious if there are even more clear answers or guidelines tha anyone knows.

Hello:
I spoke with a guy who works for a porting company we have a relationship with. He's their point on NSTL submissions and he's given me good advice before. His experience and advice was to mark as few files as possible as signed in the AppSigner, and that unsigned files would be fully available for reading and modification by the applicaiton.
I respect his advice and have made my submission basd on it, but am still curious if there are even more clear answers or guidelines tha anyone knows.