> They don't need it to be impossible - just difficult. As the > documents are 200 pages long they don't think anyone would > screengrab them - and if they did they would be in violation > of an NDA. They just want to make it highly unlikely that the > document would end up being emailed around.
You should make it very clear to your client, in writing, that all you can do is make it more difficult. Otherwise, you may be on the wrong end of a lawsuit when one of these documents does eventually get emailed around. > We have successfully used HTTP headers to prevent the files > from going to the cache. Now we just need to implement some > kind of crude encryption/decryption of the swf. How do you know you've successfully used HTTP headers to do this? Since all the action is on the client, how exactly can you verify that this has been successful? There are third-party products that manipulate HTTP request and response headers as a matter of course. Some of these are common consumer applications. Some of these are installed by computer manufacturers. > We're not trying to guard against pro-developers or hackers - > just against tech-savvy business people who might look in their > temporary internet files, or do a "view source" to find the > file, etc. What about the tech-savvy business person who asks his coworker in IT down the hall to grab a copy? If you're interested in a more secure solution for this, you might want to take a look at Adobe LiveCycle ES Rights Management. This will let you deliver PDFs that can only be used in very specific ways, by authorized users, using Adobe Acrobat or Adobe Reader only (no third-party PDF viewers). It's fairly expensive, but will let you make it much more difficult than any of the solutions you're considering. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
