 Feedback
|
Table Of Contents
Release Notes for Cisco Secure Desktop, Release 3.1
Mac & Linux Cache Cleaner Client Requirements
Cisco Security Agent (CSA) Compatibility
Clean Cache Setting Ignored for Internet Explorer
Windows Cache Cleaner Profile Under Netscape and Mozilla
Administrator Guidelines for the VPN 3000 Series Concentrator Only
Downgrading a VPN 3000 Series Concentrator
Chunked Transfer-Encoding Required for Proxy Server On VPN 3000 Concentrator Series
Save after Changing the Hostname on a VPN 3000 Concentrator
Location Settings: Do Not Use Quotes With Registry Key Names
Keystroke Logger Detection Limitations
Cisco Secure Desktop Installation through a Proxy
Starting Applications from within Folders Created inside Secure Desktop
Delay with Internet Explorer on Windows 2000
History Not Erased With Multiple Explorer Windows
Secure Desktop Only Supports Applications Installed in the Default Location
Resolved Caveats - Release 3.1
Release Notes for Cisco Secure Desktop, Release 3.1
October 2006
Contents
These release notes include the following sections:
•
New Features and Enhancements
Introduction
These release notes describe the new features in Cisco® Secure Desktop 3.1, enhancements, changes to existing features, limitations and restrictions ("caveats"), and fixes. Read these release notes carefully prior to installing, upgrading, and configuring CSD.
Requirements
The following sections identify the platforms, browsers, clients, and applications that the CSD requires or supports.
Platforms
This release of CSD requires interoperability with a platform running one of the following releases:
•
•
Supported Browsers
CSD supports the following browsers on the client:
•
•
•
•
To administer CSD, you need one of the following browsers:
•
•
•
•
Mac & Linux Cache Cleaner Client Requirements
The Cache Cleaner for Macintosh & Linux requires that Java be installed, enabled, and working properly under the browser in use on the client. The Mac & Linux Cache Cleaner cleans only the default location of Netscape, Mozilla, or Safari.
The home directory must not contain any folder or file named .cachedlg.zip.
Cisco Security Agent (CSA) Compatibility
The Cisco Security Agent (CSA) V4.5 is compatible with both the Cisco Secure Desktop (CSD) and the Cisco SSL VPN Client (SVC) on Windows Operating Systems. Versions of CSA preceding V4.5 are not compatible with CSD/SVC.
E-mail Applications
When using an e-mail application configured to use POP3 (a standard communication protocol between e-mail applications and e-mail servers), the client downloads e-mail messages to the local computer, after which, these messages exist only on the local computer. To avoid deleting e-mail messages, CSD, at the administrator's discretion, does not remove files saved by e-mail applications, even when the application starts within the secure desktop. However, e-mail applications cannot open files created by other applications launched from within a secure desktop.
This feature applies to the following e-mail applications:
•
•
•
•
New Features and Enhancements
This release includes the following new features and enhancements:
•
•
•
•
•
As an administrator, you can also specify safe applications that are exempt from Keystroke Logger scanning.
•
•
•
•
•
•
•
Administrator Guidelines
Refer to the following sections for information you should know before installing and configuring CSD.
Note
SSL VPN Client
You can configure both the Secure Desktop component of CSD and Cisco SSL VPN Client (SVC) to run simultaneously on client PCs. If you configure CSD to permit switching between the Secure Desktop and the local desktop, the SVC connection becomes available to both. To do so, choose Secure Desktop General and check Enable switching between Secure Desktop and Local Desktop for each location.
Clean Cache Setting Ignored for Internet Explorer
Windows Cache Cleaner attempts to erase Internet Explorer's History entries, regardless of the "Clean the whole cache..." setting.
Windows Cache Cleaner Profile Under Netscape and Mozilla
To create a temporary Mozilla profile, Cache Cleaner uses the default profile as a template. If no default profile is present, Cache Cleaner looks for a profile with the same name as the logged in user. If none exists, Cache Cleaner creates a new profile.
Administrator Guidelines for the VPN 3000 Series Concentrator Only
The following guidelines apply only if CSD is running on a VPN 3000 Series Concentrator.
Downgrading a VPN 3000 Series Concentrator
Note the following before downgrading a VPN 3000 Series Concentrator equipped with CSD:
•
•
•
Downgrade a VPN 3000 Concentrator as follows:
Step 1
Caution
Step 2
Step 3
Chunked Transfer-Encoding Required for Proxy Server On VPN 3000 Concentrator Series
If you use a proxy server with WebVPN on the VPN 3000 Concentrator, the proxy server must support the Transfer-Encoding HTTP header value "chunked". One effect of not supporting this value is that mail text entries displayed by Microsoft Outlook Web Access remain in a "Loading" state instead of showing the e-mail content.
Save after Changing the Hostname on a VPN 3000 Concentrator
Secure Desktop installation (.EXE version) requires that the hostname be configured on the VPN 3000 Concentrator. Either place the Fully Qualified Domain Name (FQDN) in the "System Name" field under [Configuration > System > General > Identification], or place the host name in the "System Name" field and configure the domain name under [Configuration > System > Servers > DNS]. The host name and domain name are combined to form the FQDN (for example, systemname.domain.com).
When you change the Hostname, you must click Save under the Secure Desktop Manager to update the client installer with the new Hostname.
Client Guidelines
Be sure to communicate the following guidelines to CSD users.
Enabling Installation with NX
CSD 3.1 is not compatible with non-vendor specific No-Execute (NX), also known as Microsoft Data Execution Prevention (DEP), AMD Enhanced Virus Protection (EVP), and Intel Executable Disable (XD). Users must disable NX or the equivalent on the computer BIOS. Otherwise, CSD does not create a secure desktop.
Cisco Security Agent
Because the Secure Desktop and Cache Cleaner tightly connect with the Operating System, the Cisco Security Agent often prompts the user to confirm that the Secure Desktop components can be trusted. It is important that the user confirms that the Secure Desktop can be trusted when prompted by a dialog.
CSA Versions before V4.5 often prompt the user on the local desktop instead of the Secure Desktop; for this reason we encourage that the user upgrade to CSA V4.5 or to contact the administrator to check the "Enable switching between Secure Desktop and Local Desktop" option when configuring the Secure Desktop.
Location Settings: Do Not Use Quotes With Registry Key Names
Users must not type quotes in a Registry Key name that includes spaces.
Do Not Change Cache Locations
Cache sessions may not get cleaned if a user changes cache locations during Secure Desktop and Cache Cleaner sessions..
Keystroke Logger Detection Limitations
CSD only detects keystroke loggers, if configured, for users with Administrator privileges.
It may not be possible for CSD to detect all keystroke loggers present, including but not limited to hardware keystroke logging devices.
Cisco Secure Desktop Installation through a Proxy
To specify CSD installation through a proxy server without regard to the browser, go to the "Internet Options" control panel under Windows, click the Connections tab, and click the LAN Settings... button.
To use the ActiveX installation of CSD, go to the "Internet Options" control panel under Windows, click the Advanced tab, and enable the "Use HTTP 1.1" option.
To use the Java installation of CSD, go to the "Java" control panel under Windows, click the General tab, click the Network Settings... button, and configure the proxy.
Starting Applications from within Folders Created inside Secure Desktop
Windows treats folders created within Secure Desktop differently from other folders. An application cannot always determine the default folder location for files if you start it from within these folders. For example if you create a folder within a Secure Desktop, open the command prompt, change the directory to that folder, and run FTP, FTP does not download files (whose full paths are not provided) to that folder. We recommend that you specify the full path or explicitly change the working directory (for example by the lcd command in the case of FTP) from within the applications. This problem essentially concerns applications launched from a shell. Otherwise, no problem should occur.
Delay with Internet Explorer on Windows 2000
It can take about 45 seconds for Internet Explorer running on Windows 2000 to initiate the download of CSD if the user logs in using cached credentials (that is, if a user in an Active Directory domain logs in without a network connection to the domain controller). This scenario uses both DNS and NetBIOS to search for the domain controller, extending the connection time. To avoid this delay, instruct the user to log in using a non-domain (local) user account.
Microsoft Knowledge Base article no. 899875 (http://support.microsoft.com/default.aspx?scid=kb;en-us;899875) provides the details that address this issue.
History Not Erased With Multiple Explorer Windows
When multiple Windows 2000 Explorer windows are enabled (Windows Explorer > Tools > Folder Options > View > Launch folder windows in a separate process), Windows Explorer does not erase browser history because the information may potentially be shared by other Explorer windows. Users need to uncheck this option before starting the Cache Cleaner.
Secure Desktop Only Supports Applications Installed in the Default Location
For increased security only applications installed under the Windows and Program Files directories are accessible under the Secure Desktop. Secure Desktop does not support or allow access to applications not found in these default installation locations.
Caveats
The following sections list both the open and closed caveats in Release 3.1.
Open Caveats - Release 3.1
The open Severity 3 caveats are as follows:
•
Symptom: Secure Desktop does not start on some PCs (for example, some laptops and tablet PCs). The main.exe program consumes all of the CPU for a few minutes, then it terminates.
Condition: This problem originates from a compatibility issue with the DEP feature implemented in the hardware of some PCs, and in the software in Windows XP SP2.
Workaround: Disable DEP in the BIOS whenever possible to allow Secure Desktop to run. Also, deactivate DEP in the software if Windows XP SP2 is running.
For more information about the DEP feature in Windows XP, go to http://support.microsoft.com/kb/875352.
Resolved Caveats - Release 3.1
Release 3.1 resolves the following issues:
•
Symptom: CSD did not delete history files.
Conditions: Internet Explorer 6.0 over Windows 2000
•
Symptom: Adding a picture from the Secure Desktop Space affected the guest machine.
•
Symptom: Jasc Paint Shop Pro started in Secure Desktop displayed the following message:
The folder listed below is used to saved your user files. It is not currently accessible. C:\Documents and settings\Administrator\My Documents\My PSP8 Files\Conditions: Starting Jasc Paint Shop Pro in Secure Desktop yielded this message.
•
Symptom: Secure Desktop did not use some Netscape, Mozilla, or Firefox settings.
•
Symptom: Secure Desktop would not preserve the position of the Recycle Bin shortcut between sessions.
Conditions: Secure Desktop configured with Vault Reuse enabled.
•
Symptom: Keystroke Logger displayed a dialog box that was not resizable.
•
Symptoms: Key stroke logger detection would hang.
Condition: When deleting ActMon logger on XP SP1.
•
Symptom: CSD did not delete some cached files.
Conditions: When closing a browser, a popup window opened.
•
Symptom: CSD prompted the user connecting with Netscape, Mozilla, or Firefox to choose a profile.
Condition: This occurred when the local PC clock was adjusted outside of the certificate's valid period.
•
Symptom: Cisco SSL VPN Client could not be installed within Secure Desktop using ActiveX.
Condition: Java was not enabled and the system was running a non-NTFS file system.
•
Symptom: Command line ftp left files on the guest desktop.
Condition: This occurred when the user used command line ftp to "get" files.
•
Symptom: A file downloaded using the command line ftp did not appear in the current directory.
Condition: The user did not use the lcd command (or full path) to explicitly tell ftp where to store the file.
•
Symptom: A security module did not recognize Mozilla browser on the Secure Desktop.
Condition: The security module was installed on a per-profile basis, and users used a brand new Mozilla profile in the Secure Desktop.
•
Symptoms: The installation of SSL VPN Client did not succeed. The user was prompted on whether to install the client.
Condition: Within the Secure Desktop (on some machines only).
•
Symptom: "The requested resource is in use" error message appeared when the user tried to switch to Secure Desktop.
Condition: When the local machine had a Panicware popup blocker installed.
•
Symptom: SVC V1.0.1.116 was unable to execute within the SD space when CSD V3.0.2.275 ran on Release 4.7.1 of the VPN 3000 Concentrator.
Condition: When configured to use SVC within the SD space, CSD prompted the user as follows:
Secure Desktop suspect that a software installation will occur which is not recommended.Do you want to proceed (unrecommended)Selecting Yes at this point fails to allow the SVC to install•
Symptoms: Failure to switch to secure desktop. A message appeared and then disappeared.
Condition: The vault was not created properly. The "!" directory was not created within the Secure Desktop directory. This was likely because the storage service wasn't started in time.
•
Symptom: Proxy settings were not pushed to IE when running over SSL VPN Client inside Secure Desktop.
Conditions: CSD: 3.1.0.9, Client: XP SP2 IE 6.0
•
Symptom: Upon uninstallation of CSD from the client PC, the Internet Explorer Favorites failed to restore to the previous list.
•
Symptom: Popup blocker settings not carried over to secure desktop
Condition: When Mozilla like browsers were used
•
Symptoms: CSD would not start.
Condition: When CSD did not properly uninstalled during the upgrade.
•
Symptom: Some Explorer windows did not close when the cache cleaner exited.
Conditions: Java scripts were running that prevented the Explorer windows from closing.
•
Symptom: The installation of Secure Desktop on Japanese Windows XP would hang if a certificate was not installed. Specifically, after one clicked "Yes" in response to a Security Alert dialog box to confirm installation without a certificate, Windows would hang after displaying the message, "Please wait while the configuration is checked..."
Conditions:
–
–
–
•
Symptom: SSL VPN Client failed to install from within Secure Desktop.
Conditions: TEMP or TMP environment variables set to non-default values.
•
Symptom: Corrupted hosts file.
Conditions: Opening and closing the Applet window twice while using Application Access within a Secure Desktop.
1 Although CSD supports FireFox, the Windows Cache Cleaner does not. If you configure a location to use Windows Cache Cleaner and CSD detects Firefox, it starts Internet Explorer automatically instead.2 Available on the Secure Desktop Settings window, you can configure this setting for each configured client location type.
