Paul Whittaker1709163072

Creating a file named $HOME/.ICAClient/.eula_accepted (e.g. using "touch") will suppress the EULA dialog.

It is possible to run the ARMHF version of Workspace App (which does include PDCRYPT2.DLL) on a Pi 5, but I have found that multiple bug workarounds are needed - when connecting to a CVAD7 2203 LTSR CU4 server environment, at least (which is what I use for testing). That said, the ARM64 version connects to 2203 LTSR just fine anyway when using the installation default encryption settings. It looks to me as though PDCRYPT2.DLL (which I guess is missing from the ARM64 port because it contains difficult-to-port 32-bit ARM assembly code?) is only needed for RC5 encryption (is this used by default in recent non-LTSR server releases?). FYI I have found that when using any version of WA later than 21.11 in a Debian/Ubuntu/Raspbian client context, you must revert to using the old smart card library by changing DriverName=VDSCARDV2.DLL back to DriverName=VDSCARD.DLL in the [SmartCard] section of /opt/Citrix/ICAClient/config/module.ini, or else the client will get "stuck" on logon (even though everything seems to be working from the server perspective). I have also found that (also for > 21.11) you cannot use EnableUDPAudio=TRUE, and must change that to FALSE in the [ClientAudio] section or else wfica will crash immediately when launching. Moreover, you must not set H264Enabled=False in wfclient.ini or All_Regions.ini in any version of WA later than 20.12 when running the ARMHF client under a 64-bit kernel (which is necessary for the Pi 5, because it cannot boot a 32-bit kernel) or else wfica will crash randomly after login. This problem seems to have worsened further in the latest version of WA (24.02), where wfica will get "stuck" after logon if you attempt to turn H.264 off on all of the ports of WA for Linux, including x86_64. Our particular use case (an extremely minimal Debian variant) also requires setting GnomeKeyringDisabled and StorebrowseIPCDisabled to true in /opt/Citrix/ICAClient/config/AuthManConfig.xml, but those tweaks are probably(?) not needed on a more complete Debian/Ubuntu/Raspbian install.