This team blog intends to provide interesting and useful info about Technical Communication Suite, FrameMaker, RoboHelp and related issues in Technical Communication.
Contributors include Mahesh Kumar Gupta, Product Manager - Adobe FrameMaker, Adobe Technical Communication Suite and Ankur Jain - Product Manager, Adobe RoboHelp. There is also an active contribution from members of the product engineering teams.
Summary: A critical vulnerability exists in the current version of RoboHelp Server 8. This vulnerability could result in an unauthenticated user uploading and executing arbitrary code.
Solution: Adobe recommends all RoboHelp Server 8 users update their RoboHelp installations by applying the update using the instructions below:
1. Stop Tomcat service if its running.
2. Backup the following files:
a. \WEB-INF\classes\adobe\robohelp\server\Publish.class
b. \WEB-INF\classes\adobe\robohelp\server\Publish$1.class
c. \WEB-INF\classes\adobe\robohelp\server\Publish$PublishData.class
d. \WEB-INF\classes\adobe\robohelp\server\Publish$SessionData.class
e. \WEB-INF\classes\adobe\robohelp\server\Publish$SessionManager.class
f. \WEB-INF\classes\adobe\robohelp\server\CircularArray.class
g. \WEB-INF\classes\adobe\robohelp\server\CServerConstants.class
h. \WEB-INF\classes\adobe\robohelp\server\RoboHelpServer.class
i. \WEB-INF\web.xml
3. Extract and copy the files from the update zip to the relevant folder. Select "Yes to All" at the "Confirm Folder Replace" prompt.
4. Start Tomcat service.
A Security Advisory has been posted in regards to the RoboHelp Server 8 issue as mentioned in the Adobe RoboHelp blog on September 4 ("Potential RoboHelp Server 8 Issue"). A critical vulnerability exists in the current version of RoboHelp Server 8. This vulnerability could result in an unauthenticated user uploading and executing arbitrary code.
We are in the process of developing a fix for the issue, and expect to provide an update by September 18, 2009.
Adobe is aware of reports of a remote pre-authentication exploit in RoboHelp Server 8. We are currently investigating this potential issue and will have an update once we get more information.
Open letter to our Customers on the recent Customer Support issues
In the recent past, there have been increasing instances of dissatisfaction with Adobe's Customer Support. Lambert Walsh, Vice President - Technical Services @ Adobe, recently issued an open letter to Adobe Customers on what is being done to address this situation.
Please note that any unresolved issues can also be directed to adbecare@adobe.com for help.
FrameMaker 9 introduces a new variable <$chaptertitlename>, which is available for use in a template document of a Folder in a hierarchical book. FrameMaker enables the author to use this variable in the template file associated with a Folder. The value of this variable provides the name of the Folder title.
Authors might need to update the Book in order to correctly reflect the value of this variable in the template document. For all other documents which are neither Folder template file nor part of the FM book,<$chaptertitlename> variable will reflect the filename of the file in which it is used.
Embedded along is a small demo on how to use <$chaptertitlename> in a book.
I have tried using this variable to add an introduction to a section in my book. Also i have taken care of clubbing the different sections in the book using Folders introduced in FrameMaker 9. The sectional introduction documents in the book reflect the title which has been used to name the Folders in the book. I have included this Sectional title to create the Table of Contents of the book. Just changing the Folder title as needed allows me to modify the title of the Introduction document as well as the TOC of the book.
I'm sure authors could also use this variable specifically to their needs. Suggestions and feedback are welcome.