Thanks Peter.
"If you encrypt it, how is the update routine going to unencrypt it for legitimate users"
We were hoping the RH Adobe Air feature would allow us to encrypt the .air file and also provide an option to unencrypt it during install. But I guess that is not an option.
All of our users are internal customers, but that will not always be the case. Our servers are internal to both our users as well as to us. But we do not want someone to pull the file down and be able to run it outside of the application. Does that make sense?
I apologize if my questions were not clearer. Maybe these will help:
1) Can the help content be protected in a manner that it cannot be used outside of the application? Password protection would be acceptable.
2) Can the Air file be updated from a web server over a SSL connection without the user having to enter credentials? Is this built into the update mechanism?
3) Are the contents of the Air help file encrypted or protected (for sensitive information)?
1) Can the help content be protected in a manner that it cannot be used outside of the application? Password protection would be acceptable. |
No. See the answer to 3.
2) Can the Air file be updated from a web server over a SSL connection without the user having to enter credentials? Is this built into the update mechanism? |
The updated .AIR and the XML can be on a web server. I have an update file on my site for demo purposes. If you knew the path and file name, you would be able to download it. I would need to test everything but I don't think the user could find that path from the help or when an auto update runs. You can set up a similar test. So when auto update runs, they get the help but not the source. They do not get the new AIR file.
3) Are the contents of the Air help file encrypted or protected (for sensitive information)? |
Anyone who has the AIR runtime can install it.
What is in this help file, the recipe for Kentucky Fried Chicken? 
Joking apart, once the customer has the help file, they can print every last topic. You want to disable print. OK, I'll have a go and cut and paste. Find a way to disable that and I will take a screen capture. Stop that and I will get my camera out. If there really is something so sensitive that you need to go to these lengths, maybe you should have a word with Charlie's Angels. Being more serious, maybe auto-update doesn't suit your scenario unless your tests confirm the user does not get the path to the update location and you are happy that is sufficient.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge