OEM Software
February 28th, 2010 by rechromeAs a scrapbook enthusiast who fully believes in putting her computer and graphic programs to full use when it comes to altering pictures to fit my scrapbook layouts to perfection, I long ago became a fan of the software program Adobe Photoshop Elements. For the record, I am currently running version 3, though two newer versions are available. It has continued to meet my needs and I see no reason to run out and spend money on a new version just yet. Originally I chose it as a much cheaper alternative to the full fledged Adobe Photoshop, as it has always allowed for quite a large amount of photo editing, including such editing basics as converting color photos to black & white or sepia tone, and more playful alterations such as using artistic and special effect brushes.
Recently, I became aware of what is referred to as an Action when in discussion about graphic programs in general. An Action is a series of edits bundled into what appears to be a simple single action, but is actually a series of actions, allowing the software program the Action is run in, to alter your photograph in a much more detailed, yet much less time-consuming way than one would be able to do without the Action. If I have not lost you after that explanation, some examples of Actions that I have since used include turning a single photograph into numerous puzzle pieces or several photos into what looks like a film reel, all with little effort on my part beyond loading the photograph into my workspace and applying the chosen Action to it.
I had previously learned, wrongly, I might add at this point, that an Action could not be run in such a basic program as Elements, and needed a full featured program such as Adobe Photoshop. Thankfully I learned this was not so. While not all Actions made for Adobe Photoshop will run in Adobe Photoshop Elements, many will, some dependent on which version of Elements you are running too, so do keep this in mind if you decide to try out Actions in your own copy of Adobe Photoshop Elements.
To begin to use them, you first must install them into the correct directory and make sure that all elements of the Action are available for the program to read. This can involve various steps, some that beginning users might be a bit more reluctant to do than more advanced users, but really are not that difficult as long as the proper steps are followed.
For example, after installing a new Action to the proper file, double check that the Elements program itself is closed, then open the file Adobe on your hard drive, (on my computer, I left clicked once on My Computer, and double left clicked my C drive, which happens to be my local drive). From there I double left clicked Adobe Photoshop Elements (in my case Adobe Photoshop Elements 3), and continued to double left click Previews, Open Cache, open Effects Cache, and then selected and deleted the three files within. I then closed all of the folders. Once closed, you will reopen the program Adobe Photoshop Elements itself, so when the program loads, it will rebuild these three files you just deleted, in turn finding the newly installed Actions, and giving the program the opportunity to show the actions in the program's menus for easy access and use.
The simplest way to do any of this is to use a third party creator of an Action that has been designed for use in Elements. My favorites and the most straightforward Actions when it comes to installation I have found come from a website created by Panos Efstathiadis titled PanosFX. On this site are clearly written directions for downloading Actions to Adobe Photoshop Elements, and getting them up and running.
If you have always wanted to try some high-end graphic editing, but your budget cannot afford a high-end graphic program, this might be the solution to your dilemma, and all within even the tightest budget.
In response to two critical vulnerabilities in Acrobat and Adobe Reader 9.3, yesterday Adobe released the 9.3.1 update for both applications; users of the older 8.x versions can update to 8.2.1 to resolve the security issues. One of the two vulnerabilities addressed would allow a malicious PDF to make unauthorized cross-domain requests; the other could crash the PDF application and possibly allow an attacker to gain access to other parts of the system.
The first flaw is related to a Flash Player issue that was revealed last week; if you have not updated Flash to the latest version (10.0.45.2 as of this moment, see your version & current versions here) & you aren't blocking Flash, you should go get the latest build right away. Although you can configure auto-update notifications in Flash Player, it's not clear if Mac OS X clients are consistently getting these reminders to update.
Even though Mac users are far less likely to be targeted by malware than our Windows-using friends and family, vigilance is still critical. Security analysis firm ScanSafe reported that it saw the percentage of exploits delivered via PDF files rise from 56% at the beginning of 2009 all the way up to 80% in the 4th quarter, so keeping those Adobe apps current — or, better yet, using Apple's Preview app as the default PDF reader on Mac OS X — is only prudent.
The Acrobat and Reader Trust Model:
Acrobat and Reader 9, with Enhanced Security turned on, allows only same-origin data downloads and multimedia operations [see "Enhanced Security in Adobe Acrobat 9 and Adobe Reader 9"]. In practical terms, this means that if you open a PDF file in a browser and it contains a streaming video, as long as the video was added with the Acrobat 9 video tool and it is streaming in from the same server that hosts the PDF file, the video will simply play without the user being prompted with a security warning. This is exactly what you'd want.
However, if the user saves that same PDF file to their desktop, their copy of the PDF file is no longer in the same domain as the video, it's on the desktop but the video is still referencing the server. When the user opens the file from their desktop, they'll be prompted to "Allow" a connection to the server that is streaming video.
PDF with Streaming Video In Browser
PDF with Streaming Video opened from Desktop
If you are using hosted services or are streaming video from a server other than the one that hosts the PDF file, you can create a cross-domain policy file to allow other servers to be trusted. Below are two different links to the same file. The first will open the PDF file in a new browser window, the second will download the PDF file so you can open it from your desktop. The PDF file contains a Yahoo Map that references 4 different domains on the Yahoo servers. My cross-domain policy file is set up to allow cross-domain access to all four of those servers. So when the file is viewed from the browser, the first link, you get a very clean experience with no security warnings.
PDF file with embedded YahooMap In Browser
PDF file with embedded YahooMap opened from Desktop
If you open the file from your desktop after downloading it, the second link, your experience is quite a bit different. First, you'll be prompted to allow the PDF file to access my server which actually hosts the SWF that plays inside the PDF file.
Then the SWF will try to access some assets that I also have referenced on the server. You should click "Remember my action for this site" or you'll be prompted many times as the SWF accesses the same resource each time it places a pin on the map.
After all of that, you'll need to allow the SWF to access each of the four Yahoo domains that the Yahoo map API requires to generate the map.
With behavior this different, it's hard to believe that this is the exact same file. The difference in the behavior is simply due to the same-origin and cross-domain policy rules. When a PDF file is opened from the desktop, the PDF file itself is considered it's own domain. So, as long as all of the resources needed to play the multimedia in that PDF file are embedded, you won't see any security warnings. Unfortunately, this will never be the case with streaming video or any PDF file that uses web services. So - we had to come up with another solution.
Establishing Trust: Opting In
As I mentioned above, when a PDF file is opened from the desktop, it is considered to be it's own domain. Nothing that the PDF file references outside of itself will be considered trusted by default, additionally some of the most powerful and interesting JavaScripts will be disabled by default and require elevated privileges [add link to SDK definition] to run.
You can override these restrictions for content that is specifically trusted, in other words, content that you know where it's coming from and you were expecting to get it. As the PDF author you can take certain steps to help establish trust, which I'll discuss below, but - ultimately - your end users will need to opt in to trusting your content. The remainder of this article discusses how to help them do that.
Certify your Documents:
This is my preferred method of establishing trust. When the Adobe Reader or Acrobat opens a certified document and the certificate used has been trusted to allow for Dynamic content, Embedded High privilege JavaScript, your document will be able to function properly without security warnings regardless of where the user places the file. Additionally, the user will have the assurance not only that the document came from you but also that it has not been modified or tampered with while it was on the way to them.
The added benefit of certifying documents is that the user will only need to install and configure your certificate once, then all documents that are certified by you will work properly and without restriction.
To see how this works, download and configure my certificate by clicking on the link below.
Download my Certificate
When you open the FDF file, you will be prompted to import my contact information. Note: The contact information will be imported into Acrobat or Reader, not your contact management system. Click the "Set Contact Trust" button to configure my certificate further.
In the "Trust" tab, check all of the boxs and then click "OK".
After you see the import message, you can close out of all of the dialogs.
After installing and permissioning my certificate, try opening the certified version of the Yahoo Map example, you should be able to use it without security warnings.
Certified PDF file with embedded YahooMap opened from Desktop
You can get a certificate from one of Adobe's Certified Document Services (CDS) partners or use one of your own. One additional point to note is that the Adobe CDS service can be used to automatically certify to the recipient that the author's identity has been verified by a trusted organization and that the document has not been altered in any way. It does not automatically grant the additional permissions required to play unembedded Dynamic content or other high privilege operations. Your users will need to set these permissions manually as detailed above.
Read more about Adobe's Certified Document Services (CDS) and find a CDS partner
Because there is a fee associated with getting a certificate issued from our CDS partners, certifying a document my not be the best solution for all users. To get the same behavior as a certified document without using a certificate, Privileged Locations are an excellent option.
Privileged Locations:
Enhanced Security provides a method for specifying locations on your hard drive to store trusted content. Privileged locations can be a single file, a directory, or a host. You'll need to ask your users to create a folder on their desktop, assign that as a trusted folder in the Acrobat preferences and then to place any files that they receive from you into that folder. By saving your files to that special folder, they are opting in and those files will function without the Enhanced Security restrictions.
To specify a privileged location through the user interface see "Specify privileged locations for trusted content" in the Acrobat 9 help
Because Certified documents are secured and thus not fully editable in Acrobat, the Privileged Locations solution is best if you are creating PDF files with Dynamic content and your users will be modifying the file in significant ways. That is, something other than filling in form fields or commenting, which are the only two types of changes permitted by "certified" documents.



