- #CITRIX VIEWER 11.8.2 FOR MAC#
- #CITRIX VIEWER 11.8.2 FULL#
- #CITRIX VIEWER 11.8.2 SOFTWARE#
- #CITRIX VIEWER 11.8.2 PLUS#
- #CITRIX VIEWER 11.8.2 WINDOWS#
#CITRIX VIEWER 11.8.2 FOR MAC#
The Receiver for Mac 11.8 might exit unexpectedly on Mac OS X 10.8.6 while mounting Apple Filing Protocol (AFP) or Server Message Block (SMB) shares. The Receiver for Mac 11.8 might exit unexpectedly. The Receiver for Mac 11.8 might exit unexpectedly on Mac OS X 10.8.6. Additionally, if the main window is minimized, a white window might appear where it was displayed last.Īfter upgrading from NetScaler 9.x to 10.x, attempts by the Receiver for Mac to authenticate to NetScaler fail. Clicking the parent window can cause the main window to take focus instead of the email window.
Receiver for Mac 11.8.2 contains all fixes that were included in Receiver for Mac 11.8, and the following, new fixes:įloating tooltip bubbles can take focus from the email window in Microsoft Outlook 2003. VD3D might crash with DisplayLink monitors.Ĭitrix Viewer can consume 100 percent of CPU when an error message appears.Ĭompared to: Citrix Receiver for Mac 11.8 The Cmd-Tab keystroke might not be sent to the session. Server-to-client content redirection might not work with sites that have bad certificates.Ĭitrix Viewer might crash during connect if the VirtualDrivers line of modules file is commented out or empty.Ī desktop session window might not restore after minimize.Ĭtrl-Esc might drop the Citrix Viewer out of full-screen mode. Users might not be able to add a store in OpenDNS environment.Ĭitrix Viewer can crash in audio channel. Receiver might not connect to session when the Mac is configured to use a proxy PAC file.
#CITRIX VIEWER 11.8.2 FULL#
Users might be unable to send Ctrl-Alt to session in full screen.
When using OS X 10.8.3 with Receiver for Mac 11.8 and connecting to a Presentation Server 4.0 farm, the screen might not refresh automatically when opening a published desktop.įull screen on a secondary monitor can hide the menu on the main monitor when in legacy monitor mode. On Mac OS X 10.10, when App Nap is triggered, Receiver might drop the connection to the server. Mathematica might not show drop-down menus. When the default cursor changes to the text cursor while in front of a black text window, the cursor might not invert its color to white to make the text cursor visible.Ĭopying text from a published application to a local application might produce extra line breaks. Receiver might not recognize client name in the default.ica when listed under an application-specific entry. When administrators attempt to shadow sessions, the ICA session might show as black and might not automatically redraw when initiated. The drop-down menu might still be visible after the parent window has been moved.ĭownloading from Firefox Mozilla to the Mac client drive can cause failures.Īpplication names from Receiver for Mac 11.8.2 might show up as blank on StoreFront and are not be accessible for opening if the name begins with a tilde (~).
#CITRIX VIEWER 11.8.2 PLUS#
Receiver for Mac 11.9 contains all fixes that were included in Receiver for Mac 11.8 and 11.8.2, plus the following, new fixes: Receiver for Mac 11.8 Receiver for Mac 11.9Ĭompared to: Citrix Receiver for Mac 11.8.2
IBM HTTP Server 8.The following issues were fixed in Receiver for Mac 11.
#CITRIX VIEWER 11.8.2 WINDOWS#
Windows Server 2003 with MS13-095 installed Windows Server 2003 SP2 +Hotfixes (Partial) Internet Explorer 7+ under Windows XP SP3
#CITRIX VIEWER 11.8.2 SOFTWARE#
It is highly recommended to research your software solely or to inquire into the matter directly with your vendors before SHA-2 signature algorithm certificates implementation.Īpache 2.x or higher, with OpenSSL 1.1.x or higher *Ĭisco ACE module software version A4(1.0) We used various sources for the list creation, but we cannot guarantee that all the data provided below is accurate. The new and updated versions of the software are released by vendors to satisfy the new security standards.īelow we provided the list of the SHA-2 compatible servers, browsers and Operating Systems. It is time to check whether the software you are using is compatible with SHA-2. In the nearest future all trusted certificates within the industry will be signed with the SHA-2 signature algorithm only, as the certificates signed with SHA-1 are considered to be vulnerable. The full transition to SHA-2 is already applied to the certificates we offer.
0 kommentar(er)
