scyld cloud workstation documentation · contents 1 about scyld cloud workstation3 2 introduction 5...

Scyld Cloud WorkstationDocumentation

Release 7.1.8

Penguin Computing

June 12, 2018

CONTENTS

1 About Scyld Cloud Workstation 3

2 Introduction 5

3 Release Notes 73.1 v7.1.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2 v7.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.3 v7.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.4 v7.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.5 v7.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.6 v7.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.7 v6.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.8 v6.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.9 v6.0.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.10 v5.0.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.11 v5.0.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.12 v5.0.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.13 v5.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.14 v5.0.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.15 v5.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.16 v5.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.17 v5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.18 v3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.19 v3.0.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.20 v3.0.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.21 v3.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.22 v3.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.23 v3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.24 v2.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.25 v2.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.26 v2.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.27 v2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.28 v2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Server Requirements 134.1 Server OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.2 Server Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.3 Server NVIDIA Drivers (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.4 Server Screen Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.5 OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.6 SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

i

5 Client Requirements 155.1 Client Hardware and Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.2 Client Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6 Installation 176.1 Required Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.2 CentOS 6 (RPM): Fresh Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.3 CentOS 6 (RPM): Updating an Existing Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.4 Windows 7: Fresh Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.5 Windows 7: Updating an Existing Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.6 Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7 Flexera License Management 217.1 Obtaining a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.2 Installing a Trial License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.3 Installing a Floating or Node-Locked License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.4 Testing your Floating / Node-Locked License Install . . . . . . . . . . . . . . . . . . . . . . . . . . 22

8 Setup 258.1 Applying Config File Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258.2 Config File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268.3 Settings Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298.4 Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

9 Usage 399.1 Using the Linux Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399.2 Using the Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399.3 Change the Config File Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409.4 Log Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409.5 Selecting a Video Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.6 Sign In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.7 User Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419.8 Paste Text from the Local Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.9 Change Screen Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.10 Downscale Screen Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.11 Enable 4K Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429.12 Video Bit-Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439.13 Sign Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

10 Collaboration 4510.1 Set the maximum number of concurrent clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4510.2 Collaboration Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4510.3 Control Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4510.4 Add New Guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4610.5 Pause Guest Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4610.6 Ban Guests and Revoke Invites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4610.7 User Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4610.8 Give Keyboard and Mouse Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

11 Performance 4711.1 Network Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4711.2 Client Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4711.3 Server Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4711.4 Further Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

ii

12 Frequently Asked Questions / Troubleshooting 4912.1 What do I do if Windows shows a black screen instead of a login screen? . . . . . . . . . . . . . . . 4912.2 Why does Google Chrome 61-62 show inaccurate colors? . . . . . . . . . . . . . . . . . . . . . . . 4912.3 How many users can sign in at a time? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4912.4 Can LDAP credentials be used at the sign in page? . . . . . . . . . . . . . . . . . . . . . . . . . . . 4912.5 I’m only seeing a gray rectangle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4912.6 How do I press Ctrl+Alt+Del? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5012.7 How do I press Ctrl+N, Ctrl+T, Ctrl+W, Ctrl+Tab, Ctrl+Page Up, or Ctrl+Page Down? . . . . . . . . 5012.8 What ports do I need to open? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5012.9 Can I run my applications? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5012.10 Will it run on my iPad / mobile device? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5012.11 Is there audio support? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5112.12 Can I cut, copy, and paste? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5112.13 What graphics cards do you support? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5112.14 How many NVIDIA GRID GPUs do I need? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5112.15 What do I do if Windows reports: “The program can’t start because LIBEAY32.dll is missing from

your computer.” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5112.16 What Xorg.conf options do I need for an NVIDIA GRID / Tesla card over GPU passthrough? . . . . 51

13 End User License Agreement 53

14 Thirdparty License Agreements 59

15 Indices and tables 73

Index 75

iii

Scyld Cloud Workstation Documentation, Release 7.1.8

Contents:

CONTENTS 1


2 CONTENTS

CHAPTER

ONE

ABOUT SCYLD CLOUD WORKSTATION

Scyld Cloud Workstation 7.1.8, commit 9fb94c60d68a60bdb95b644ffc49b7efbc0ce5b6.

3


4 Chapter 1. About Scyld Cloud Workstation

CHAPTER

TWO

INTRODUCTION

Scyld Cloud Workstation is a web server that provides secure, easy remote access to teams working on Windows andLinux workstations through standard web browsers, eliminating the need for client-side installations and changes tofirewall policies.

This document describes system requirements, installation, configuration, and usage.

5


6 Chapter 2. Introduction

CHAPTER

THREE

RELEASE NOTES

Attention: We recommend moving changes from your old config file to the latest config file.

3.1 v7.1.8

• Fixed native client blank connect dialogue appearing after service restarts

• Fixed native client black screen when reconnecting after Windows 10 service restarts

• Fixed native client scroll bars not appearing when reconnecting after Windows 10 service restarts

• Fixed Windows 10 service becoming unavailable after signing out

• Suppressed mouse cursors always shows in Windows 10

• Added HiDPI support for Windows stream encoder

• Fixed Linux log file location

3.2 v7.1.1

• Improved handling of scenarios where Windows has no console session

• Improved handling of scenarios where RDP session is active

• Documented ‘Escape’ workaround for black windows login screen issue

• Changed default XML config file value for Server.IdleUserTimeout to 120

• Fixed missing OpenSSL libraries in Windows

• Fixed client EULA

3.3 v7.1.0

• Changed video bit-rate selection to be based on screen resolution

• Lower latency for native client due to optimizations on color conversion and frame rendering

7


3.4 v7.0.2

• Added OpenSSL v1.0.2n libraries to Windows native-client

3.5 v7.0.1

• Fixed Windows password changing documentation

• Fixed config file automatically inserting StreamVideoSource tags

• Removed Windows wrapper batch script

3.6 v7.0.0

• Added 4K resolution support to native-client. Additional server-side setup is required. See the Enable 4KSupport section for more information.

• Improved frame-rate performance of native-client

• Added MD5 hash of configuration file to start-up output

• Upgraded QT to 5.9.2

• Improved native-client window resize behavior

• Improved native-client fullscreen behavior to downscale graphics when remote desktop is larger than the clientscreen size

3.7 v6.1.1

• Fixed image blurring when enabling unique frames

3.8 v6.1.0

• Added ability to sign in with Linux and Windows OS credentials

• Added ability to transmit only unique video frames with Server.Video.UniqueFramesOnly config setting(true by default)

3.9 v6.0.3

• Added browserless ‘native’ client for CentOS 7 and Windows 7

• Fixed relative paths for Server.LicensePath

• Updated fonts, icons, and colors

• Changed from Windows NSIS installer to MSI installer

8 Chapter 3. Release Notes


3.10 v5.0.7

• Fixed “too many files open” error for generic stream video source

3.11 v5.0.6

• Improved error handling for disconnects during inactivity

• Changed default idle user timeout to 2 hours

3.12 v5.0.5

• Fixed black winlogon screen for stream video source

3.13 v5.0.4

• Fixed screen size changing in Windows

3.14 v5.0.3

• Fixed handling of poor network connections

• Windows installer preserves *.dat, *.lic files on update

3.15 v5.0.2

• Fixed blackscreen when using IE 11 over a VPN

• Fixed systemd service status check

3.16 v5.0.1

• Fixed init script false-positive when license checkout fails

• Fixed systemd service script

• Reduced log output on license checkout retries

3.17 v5.0.0

• Added CPU-based (stream) video source option

• Added idle user timeout (Server.IdleUserTimeout takes minutes. Disabled by default)

• Added ability to update Server.Auth settings at runtime (except Server.Auth.Enabled)

3.10. v5.0.7 9


• Added ability to auto-select a video source

• Added Flexera License Management

• Added ability to specify license file with Server.LicenseFile config setting

• Added ability to delay service start with Server.StartDelay config setting

• Renamed Server.WebSocketServer.Secure to Server.Secure

• Renamed Server.WebSocketServer.Port to Server.Port

• Renamed Server.ServiceLogFile to Server.BootLogFile

• Renamed debug0.txt to boot.log and debug1.txt to scyld-cloud-workstation.log

• Changed Windows install directory to C:\Program Files\Penguin Computing\Scyld Cloud Workstation

• Changed Windows service startup from Automatic to Delayed

• Changed log messages

• Fixed guests getting kicked out if one of multiple hosts signs out

• Fixed handling of IPv6 addresses

• Fixed guest toolbar being hidden while paused

• Fixed duplication of guest alerts

• Fixed guest video when starting out paused

3.18 v3.1.0

• Added support for CentOS 7 (requires LightDM / MATE desktop environment)

• Added Floating UI

• Added adjustable screen resolutions limits

• Added Server.Video.MaxWidth and Server.Video.MaxHeight to config file

• Updated QoS algorithm

• Windows installer preserves *.crt, *.cer, *.pem, *.key, and *.der files on update

• Set default max frame rates to 30

• Fixed Firefox keyboard issue for remote Windows services

3.19 v3.0.4

• Increased send timeout values

• Added Server.VideoSendTimeout, Server.DataSendTimeout, and Server.ReceiveTimeout to config file

3.20 v3.0.3

• Fixed QoS adaptive frame rate algorithm



3.21 v3.0.2

• Fixed IE11 fullscreen keyboard and scrollbars

3.22 v3.0.1

• Fixed unexpected multi-user client timeouts

3.23 v3.0.0

• Added keyboard and mouse sharing for collaboration

• Added guest invites for collaboration

• Added text paste from local clipboard support

• Added remote desktop auto-lock on disconnect

• Updated QoS algorithm

• Updated user interface style

• Updated default SSL ciphers

• Compatible with v2.3 config file

3.24 v2.3.2

• Updated default SSL ciphers

3.25 v2.3.1

• Fixed Command/Windows key getting stuck

• Fixed cursor disappearing during Windows UAC

3.26 v2.3.0

• Improved decode performance

• Improved QoS responsiveness

• Improved mouse scrolling. Ticks are now server-dependent

• Added code authenticity check

• Fixed OS X command key

• Improved version number system

• Fix for null cursor

3.21. v3.0.2 11


• Fix for missing HTML icons

• Added support for 16x16 cursors in Windows

• Improved web-page refresh

3.27 v2.2.0

• Added local cursor

• Added basic QoS / dynamic frame rate updates

• Simplified configuration file by relying more on defaults

• Updated interface controls to be centered, sleeker

• Updated default openSSL.server.cipherList string to include !RC4

• Updated default openSSL.server.verificationMode to relaxed

• Fixed cursor in Firefox Fullscreen

• Fixed mouse wheel

• Fixed screen crop

• Added auto-lock (disabled by default)

• Authentication screen can now be disabled in config

• RPM installer preserves old config file by default

3.28 v2.1.0

• Added screen resolution change support (Windows, Linux)

• ScyldCloudAuth “JSON Syntax Error” fix

• Silent / Quiet Windows installer


CHAPTER

FOUR

SERVER REQUIREMENTS

This section describes the hardware and software requirements for the workstation hosting the Scyld Cloud Worksta-tion server.

4.1 Server OS

Scyld Cloud Workstation is supported and tested on the following 64-bit operating systems:

• Windows 7, 8

• CentOS 6, 7

Beta support is available for:

• Ubuntu 12, 14, 16

Attention: There is a known graphics issue with GNOME Shell based systems (GNOME 3 and GDM) onmachines that do not have an attached monitor. For these systems, MATE desktop environment and LightDM canbe used as a workaround.

If you require other versions of Windows, RedHat, and Debian based flavors of Linux, please contact Penguin Com-puting for additional support.

4.2 Server Hardware

Scyld Cloud Workstation is supported on the following server hardware configurations:

Server-Side Recommended MinimumCPU > Intel Core i5, Dual-Core > Intel Core i5, Dual-CoreMemory > 2 GB > 2 GBGPU Any Any

4.3 Server NVIDIA Drivers (Optional)

Scyld Cloud Workstation supports NVIDIA GRID GPUs such as the NVIDIA GRID K2 and Tesla M60. Drivers thatsupport the NVIDIA GRID SDK are required. The following combinations have been successfully tested with version7.1.8:

13


OS NVIDIA Driver ReleaseWindows 7 347.88 354.99 369.49CentOS 6 354.41 361.42

Warning: The following issues are known for NVIDIA device drivers in Linux:• 331.62: the remote mouse cursor is not hidden when the local mouse cursor is active.• 340.46: changing the screen resolution via the xrandr command halts video stream.• 367.35, 367.57: changing the screen resolution via the xrandr command halts video stream.

4.4 Server Screen Resolutions

The performance of the remote access is partly dependent on the server’s screen resolution and the client’s ability toprocess that resolution quickly.

Scyld Cloud Workstation allows system administrators to pick a maximum screen resolution width and height in theconfig file (disabled by default). If the user attempts to change the screen resolution above this setting, then the videoscales down automatically. This can alleviate situations where users set the screen resolution so high that their clientmachine becomes unusuable.

For most users, we recommend a resolution of 1600x900. If you’d like to test higher screen resolutions, we recommenddoing so with gradual increases.

Warning: Changing screen resolutions has two known issues:1. Multiple rapid resolution changes may lead to service instability. Changing the screen resolution more

than 5 times over a few seconds may cause the service to restart or quit.

For more information about changing screen resolutions, see Change Screen Resolution.

4.5 OpenSSL

OpenSSL is an open source implementation of the SSL and TLS protocols and must be installed on the server host.Most Linux distributions have this installed by default, but this should be downloaded and installed manually inWindows before you can install Scyld Cloud Workstation.

For Windows hosts, download the latest Win64 OpenSSL package (either full or light versions will work) from ShiningLight Productions: https://slproweb.com/products/Win32OpenSSL.html

Note: OpenSSL 1.0 is required and is supported through December 31, 2019. OpenSSL 1.1 is currently not supportedwith Scyld Cloud Workstation.

4.6 SSL Certificate

An SSL certificate signed by a trusted certificate authority is used to provide encryption and authentication for aclient’s HTTPS connection to the Scyld Cloud Workstation web server. By default, Scyld Cloud Workstation comeswith a self-signed SSL certificate and private key that should not be used in secure production environments.

For more information on generating SSL certificates, see Setup.

14 Chapter 4. Server Requirements

https://slproweb.com/products/Win32OpenSSL.html

CHAPTER

FIVE

CLIENT REQUIREMENTS

This section describes the hardware and software requirements for the connecting client.

5.1 Client Hardware and Network

We recommend using clients with the following minimum specs.

Client-Side RecommendedCPU > Intel Core i5, Dual-CoreMemory > 2 GBNetwork Bandwidth > 5.5 MbpsNetwork Latency < 80 ms

Note: Acceptable network latency is application dependent. For certain applications, users may find 150 ms tobe acceptable. Performance may degrade if the client is running background applications that consume significantamounts of CPU time, memory, or network bandwidth.

5.2 Client Web Browsers

The following web browsers are supported and listed in order of performance:

• Chrome 30+

• FireFox 27-37, 39+

• Internet Explorer 11+

• Safari 7+

Note: Chrome 30+ provides the best performance and is recommended.

These browsers by default enable TLS 1.2, WebGL and WebSocket features that are necessary for security and optimalScyld Cloud Workstation performance. While WebSocket support is a hard requirement, Scyld Cloud Workstation iscapable of running without WebGL support at reduced performance levels.

The following links can be used to determine if your browser supports necessary features for an optimal Scyld CloudWorkstation experience:

15


Browser Feature Test for Browser SupportSecurity Protocol TLS 1.2 https://www.ssllabs.com/ssltest/viewMyClient.htmlWebGL https://get.webgl.org/WebSockets http://websocketstest.com/

Note: TLS 1.2 is the current standard used to secure HTTPS connections as of the writing of this document.

16 Chapter 5. Client Requirements

https://www.ssllabs.com/ssltest/viewMyClient.html

https://get.webgl.org/

http://websocketstest.com/

CHAPTER

SIX

INSTALLATION

The Scyld Cloud Workstation server can be installed as a Windows 7 or CentOS 6/7 service.

6.1 Required Files

Installation of Scyld Cloud Workstation requires the following files:

• The Scyld Cloud Workstation installation package for your operating system:

– CentOS 6 and 7: scyld-cloud-workstation-7.1.8-1.x86_64.rpm

– Windows 7: Scyld Cloud Workstation-7.1.8.1.msi

• The Scyld Cloud Workstation license file

If you wish to use a license server to centralize management of system licenses you will also require the Scyld FlexLMinstallation package and a license file (scyld-flexlm.lic).

6.2 CentOS 6 (RPM): Fresh Install

Download and install the latest NVIDIA GRID drivers for your OS: http://www.nvidia.com/download/index.aspx

Use the rpm command to install the Scyld Cloud Workstation RPM.

Important: Scyld Cloud Workstation includes a default private key, certificate file, username, and password that arenot secure and should be changed. See Setup for more information once installation is complete.

The installer performs the following actions:

• Scyld Cloud Workstation files are installed to /opt/scyld-cloud-workstation.

• scyld-cloud-workstation.init is installed to /etc/init.d and has its security context changed tosystem_u:object_r:bin_t:s0.

• A line of code is added to /etc/gdm/Init/Default that allows scyld-cloud-workstation to restart whenthe service is enabled by chkconfig and gdm restarts. To prevent scyld-cloud-workstation from starting whengdm starts, use the chkconfig command: chkconfig --del scyld-cloud-workstation.

The name of the RPM may be different depending on the version of Scyld Cloud Workstation.

Use the rpm -ivh command:

17

http://www.nvidia.com/download/index.aspx


% sudo rpm -ivh scyld-cloud-workstation-7.1.8-1.x86_64.rpm

Follow the quickstart instructions that appear on the terminal and then proceed to: Flexera License Management.

6.3 CentOS 6 (RPM): Updating an Existing Install

If you are performing an update, use the rpm -Uvh command:

% sudo rpm -Uvh scyld-cloud-workstation-7.1.8-1.x86_64.rpm

The new RPM may include new settings that are not present in your existing XML config file.You must merge the settings found in scyld-cloud-workstation.xml.rpmnew into your existingscyld-cloud-workstation.xml file.

Attention: We recommend using the latest config file as a starting point and moving changes from your old configfile into the new one.

Important: If you are updating over an existing Scyld Cloud Workstation installation, your old config file will be pre-served. The new package may include an XML config file with newer / updated settings. Merge the new settings foundin scyld-cloud-workstation.xml.rpmnew with the existing scyld-cloud-workstation.xml file.

Once this update is successful, proceed to: Flexera License Management.

6.4 Windows 7: Fresh Install

If you haven’t done so already, download and install the latest NVIDIA GRID driver for your OS from:http://www.nvidia.com/download/index.aspx

Note: For virt-manager users: virt-manager’s graphical console will no longer work after installing the NVIDIAGRID driver and restarting Windows.

To get the virt-manager graphical console to work again, start the Windows VM in ‘Safe Mode’ by restarting the VM,commanding it to “Force Off”, and restarting the VM again. Select “Safe Mode with Networking” from the menu thatappears.

Double-click on the Scyld Cloud Workstation-7.1.8.1.msi installer. Follow the instructions in the GUI to completeinstallation. Hit “Cancel” at any time to abort. Confirm that you’d like to start Scyld Cloud Workstation as a serviceto have Scyld Cloud Workstation start automatically.

On some systems (such as those using virt-manager’s graphical console), a reboot may be required after installation toensure that the NVIDIA GRID card is activated.

Scyld Cloud Workstation is intended to run automatically as a service in Windows. While it is possible to start it upas a normal application, Scyld Cloud Workstation must be run as a service in order to support:

• Windows sign out and sign in

• screensavers with passwords

• Windows User Access Control


18 Chapter 6. Installation

http://www.nvidia.com/download/index.aspx


6.5 Windows 7: Updating an Existing Install

Double-click on the Scyld Cloud Workstation-7.1.8.1.msi installer. Follow the instructions in the GUI to completeinstallation. Hit “Cancel” at any time to abort. Confirm that you’d like to start Scyld Cloud Workstation as a serviceto have Scyld Cloud Workstation start automatically.


Important: If you are updating over an existing Scyld Cloud Workstation installation, your old con-fig file will be preserved. The new package may include an XML config file with newer / up-dated settings. Merge the new settings found in C:\Program Files\Penguin Computing\ScyldCloud Workstation\Defaults\scyld-cloud-workstation.xml with the existing C:\ProgramFiles\Penguin Computing\Scyld Cloud Workstation\scyld-cloud-workstation.xml file.


6.6 Client Installation

Install any of the following browsers:

• Chrome 30+

• Internet Explorer 11+

• FireFox 27+

• Safari 7+

Note: Chrome 30+ provides the best performance and is recommended.

6.5. Windows 7: Updating an Existing Install 19


20 Chapter 6. Installation

CHAPTER

SEVEN

FLEXERA LICENSE MANAGEMENT

As of version 5.0.0, Scyld Cloud Workstation uses the Flexera License Management system to ensure compliance withthe terms and regulations described in the End-User License Agreement. This section talks about the types of licenses,how to obtain a license, and how to use your license.

7.1 Obtaining a License

Licenses can be requested by contacting Penguin Computing (http://www.penguincomputing.com) [email protected].

7.2 Installing a Trial License

Trial licenses are named scyld-cloud-workstation.lic and must be copied to the Scyld Cloud Worksta-tion host at /opt/scyld-cloud-workstation/bin for Linux hosts or C:\Program Files\PenguinComputing\Scyld Cloud Workstation for Windows hosts.

7.3 Installing a Floating or Node-Locked License

Follow these steps on the Scyld FlexLM host:

1. Install the Scyld FlexLM license server package (distributed by Penguin Computing) on a host that has networkaccess to all Scyld Cloud Workstation hosts.

2. Copy the license file (scyld-flexlm.lic) to /opt/scyld-flexlm/bin for Linux hosts orC:\Program Files\Penguin Computing\Scyld FlexLM for Windows hosts.

3. In scyld-flexlm.lic, find the line that looks like: VENDOR PENGUIN PORT=<port>. The last tokenis the vendor port number (typically 28282). Change your firewall to allow incoming connections to the vendorport.

4. Now find the line that looks like: SERVER this_host ANY <port>. The last token is the license serverport number. If the port is not listed, assume it is 27002. Change your firewall to allow incoming connectionsthe license server port.

5. Restart your firewall and the Scyld FlexLM service.

Follow these steps on each Scyld Cloud Workstation host:

1. Open the configuration file located at /opt/scyld-cloud-workstation/bin/scyld-cloud-workstation.xmlfor Linux and C:\Program Files\Penguin Computing\Scyld CloudWorkstation\scyld-cloud-workstation.xml for Windows.

21


2. Find the Server.LicenseFile setting in the configuration file. If it does not exist you will need to add a<LicenseFile></LicenseFile> tag inside the <Server></Server> tag.

3. Set the value of Server.LicenseFile to the port and host of the license server using the port@hostsyntax (or just @host if the Scyld FlexLM server is using the default port (27002).

For example, if Scyld FlexLM was running on port 27002 on a host with hostname iceberg:

<Server>...<LicenseFile>27002@iceberg</LicenseFile>...

</Server>

If you are unsure what port and hostname (or IP address) to use, look at the SERVER line in thescyld-flexlm.lic file. The host name will be second token and the port will be the forth token. Inthe example above this would look like:

SERVER iceberg 0011223344 27002

Important: If the hostname or port of your license server has changed, you will need to update this setting and restartthe Scyld Cloud Workstation service.

Note: Flexera typically creates a $HOME/.flexlmrc file in Linux or a Windows registry setting to cache successfullicense checkout locations for future use.

The order of precedence for license searching paths is as follows:

1. PENGUIN_LICENSE_FILE environment variable

2. LM_LICENSE_FILE environment variable

3. Server.LicenseFile configuration setting

4. Flexera cache

7.4 Testing your Floating / Node-Locked License Install

To test if the Scyld Cloud Workstation host can checkout licenses from the Scyld FlexLM host, sign into the ScyldCloud Workstation host and use the lmutil tool:

lmutil lmdiag [-c license-file]

For example, if your Scyld FlexLM server is running on port 27002 and the IP address is 192.168.1.7, a successful testwill look like:

lmutil lmdiag -c [email protected]

lmutil - Copyright (c) 1989-2016 Flexera Software LLC. All Rights Reserved.FlexNet diagnostics on Fri 12/1/2010 08:00

-----------------------------------------------------License file: 27002@192.168.1.7-----------------------------------------------------"scw" v1.000, vendor: PENGUIN, expiry: 01-aug-2017

22 Chapter 7. Flexera License Management


License server: 192.168.1.7nodelocked license locked to NOTHING (hostid=ANY) starts: 1-jan-1990, expires: 01-aug-2017

This license can be checked out-----------------------------------------------------

If license checkout fails, the output of this command can be useful for troubleshooting license checkout issues. If youwould like additional support, please contact Penguin Computing at [email protected].

Once the license file is installed, proceed to: Setup.

7.4. Testing your Floating / Node-Locked License Install 23

mailto:[email protected]


24 Chapter 7. Flexera License Management

CHAPTER

EIGHT

SETUP


Configuration values are defined by nested XML elements in the scyld-cloud-workstation.xml config file.In Linux this can be found at /opt/scyld-cloud-workstation/bin/scyld-cloud-workstation.xmland in Windows this can be found at C:\Program Files\Penguin Computing\Scyld CloudWorkstation\scyld-cloud-workstation.xml. This section describes properties in the config file.

For the purpose of this document, we refer to properties by using dot notation. For example,config.Server.LogLevel indicates that LogLevel is a property within Server, which is a property withinconfig. Since all properties begin with ‘config’, for brevity we ignore it. Properties are case-sensitive.

Warning: The config file and private key files contains sensitive information that can compromise security ifan attacker can read it. We strongly recommend limiting read and write access to the root / system administratoraccount.

Warning: Scyld Cloud Workstation includes a default private key, certificate file, username, and password thatare not secure and should be changed.

8.1 Applying Config File Changes

Saved changes to the config file are only applicable once the service restarts. The Server.Auth.ShadowPassword settingis the one exception to this rule - saved changes to it are applicable immediately.

In Linux you can restart the service using the service command:

service scyld-cloud-workstation restart

In Windows you can restart the service using the Services tool. First open the Task Manager by right-clicking onthe Task Bar and select Start Task Manager. At the Task Manager, go to the Services tab and click onServices. Right-click on scyld-cloud-workstation in the the list of services and select Restart fromthe dropdown of actions.

The Scyld Cloud Workstation sign-in page should return after a few seconds.

25

8.2 Config File Settings


The default config file comes with appropriate values for nearly all of the server settings.

In this section we discuss config settings that are commonly changed from the default config file.

8.2.1 License Management

For more information on license management, please see: Flexera License Management.

8.2.2 Server Authentication

User’s are authenticated using credentials defined by the config file or by the ScyldCloudAuth web service. To disableany of these, simply comment out these elements by wrapping them with .

Authentication is enabled by default and in should not be disabled in production systems. Server.Auth.Enabled shouldalways be set to true.

There are several authentication schemes supported by Scyld Cloud Workstation. Each system is independent and canbe enabled in parallel.

• Config File Authentication

• ScyldCloudAuth Authentication

• OS Credential Authentication

Config File Authentication

Config File Authentication uses credentials stored in the config file. The following settings control Config File Au-thentication:

• Server.Auth.Username

• Server.Auth.ShadowPassword

• Server.Auth.MinPasswordLength

The ShadowPassword is set by calling scyld-cloud-workstation.sh --passwd in Linux with sudo privi-leges or scyld-cloud-workstation.exe /passwd in Windows as an Administrator.

Config File Authentication can be disabled by commenting or removing Server.Auth.Username andServer.Auth.ShadowPassword.

ScyldCloudAuth Authentication

ScyldCloudAuth Authentication uses the ScyldCloudAuth proxy service for authentication. To enable Scyld-CloudAuth for authentication, set:

• Server.Auth.ScyldCloudAuth.URL

• Server.Auth.ScyldCloudAuth.Allow

26 Chapter 8. Setup


• Server.Auth.ScyldCloudAuth.Deny

ScyldCloudAuth can be disabled by commenting or removing Server.Auth.ScyldCloudAuth.URL.

OS Credential Authentication

The credentials accepted by your remote Windows or Linux host can be used to sign into Scyld Cloud Workstation.This supports ActiveDirectory for Windows, and LDAP / PAM for Linux.

Important: While config file or ScyldCloutAuth usernames can be used to sign in to Scyld Cloud Workstation at anytime, only a single set of OS credentials can only be used to sign-in at a time. This prevents different OS credentialsfrom signing in at the same time.

This feature can be disabled by setting Server.Auth.OSAuthEnabled to false or removing it from the config file.

8.2.3 Server Security

The cipher list will determine what ciphers are used to encrypt communication between your clients and your server.It is always a good idea to keep your server’s OpenSSL updated to the latest version.

We recommend using the default values for openSSL.server.cipherList.

8.2.4 Firewall

Your server host’s firewall needs to allows incoming connections to the server over port 443 if you are using useHTTPS or port 80 if you are using HTTP.

In Windows these rules are automatically set by the installer and removed by the uninstaller.

In Linux, you will have to update your firewall using iptables. In most cases, adding the following line to your rules file(CentOS/RHEL: /etc/sysconfig/iptables) and restarting the iptables service will allow incoming HTTPStraffic.

# Allow all https-A INPUT -p tcp --dport 443 -j ACCEPT

Change 443 to 80 in the line above to accept incoming HTTP traffic over port 80 instead.

8.2.5 HTTPS / SSL Certificates

HTTPS is required to make all of your interactions with the server secure.

To ensure that connections are using the latest TLS protocol (as of 2015), set openSSL.server.requireTLSv1_2 to trueand enable HTTPS by setting Server.Secure to true.

Set openSSL.server.privateKeyFile and openSSL.server.certificateFile to the appropriate private key and SSL certificatepaths.

If you have set a passphrase for your private key you will need to setopenSSL.server.privateKeyPassphraseHandler.options.password.

An SSL certificate signed by a trusted certificate authority (CA) is used to encrypt and authenticate communicationbetween a browser and server. To obtain an SSL certificate from a CA, you need to generate a certificate signingrequest (CSR) and submit it to the CA. A list of popular CA’s is given below:

8.2. Config File Settings 27


• https://www.digicert.com/

• http://www.entrust.com/ssl-certificates/

• http://www.geotrust.com/

• https://www.thawte.com/

Attention: You need to install OpenSSL on your server to complete the setup.• Windows: https://slproweb.com/products/Win32OpenSSL.html• Linux: yum install openssl or apt-get install openssl

The following sections describe how to use the openSSL command to create a new private key and CSR, a new CSRfrom an existing private key, and a self-signed SSL certificate (not recommended).

Create a Private Key and a CSR

Use the openssl command to creates a 2048-bit private key (domain.key) and a CSR (domain.csr). If your CAsupports SHA-2, add the -sha256 option to sign the CSR with SHA-2.

openssl req -newkey rsa:2048 -nodes -sha256 -keyout domain.key -out domain.csr

Fill out the prompted questions to complete the CSR.

Warning: The contents of your private key should never be shared with anyone.

Create a CSR from an Existing Private Key

To create a CSR from an existing private key:

openssl req -key domain.key -new -out domain.csr


Create a Private Key and Self-Signed SSL Certificate

You can create a self-signed SSL certificate instead of having one signed by a CA. The disadvantage to this is thatin order to establish trust between the browser and the server, you must make a security exception for this certificatewhen you visit the page or install it in every browser.

openssl req \-newkey rsa:2048 -nodes -sha256 -keyout domain.key \-x509 -days 365 -out domain.crt


Warning: The contents of your private key should never be shared with anyone.

Create a Self-Signed SSL Certificate from an Existing Private Key

To create a self-signed certificate from an existing private key:

28 Chapter 8. Setup

https://www.digicert.com/

http://www.entrust.com/ssl-certificates/

http://www.geotrust.com/

https://www.thawte.com/

https://slproweb.com/products/Win32OpenSSL.html


openssl req \-key domain.key -new \-x509 -sha256 -days 365 -out domain.crt


8.3 Settings Glossary

In this section we describe all of the settings available in the config file.

Note: All changes to Scyld.Auth settings except Scyld.Auth.Enabled take effect without a service restart.

8.3.1 Server.LogLevel

The verbosity of output in the log file.

The LogLevel value can be any one of the following (ordered least-to-most verbose): ‘none’, ‘fatal’,‘critical’, ‘error’, ‘warning’, ‘notice’, ‘information’, ‘debug’, and ‘trace’.

8.3.2 Server.LogFormat

Format of the output. By default, Scyld Cloud Workstation does not display a timestamp with each logmessage. To add timestamps to all of your output, open the scyld-cloud-workstation.xml andset LogFormat to: %Y-%m-%d %H:%M:%S %q%q: %s:%u: %t.

8.3.3 Server.LogFile

A path to the log file of the Scyld Cloud Workstation server. By default this can be found in the directoryof the Scyld Cloud Workstation executable and is named scyld-cloud-workstation.log. Formore information on log output, see Log Output.

Changed in v5.0.0. Default value changed.

8.3.4 Server.BootLogFile

Windows only. A path to the log file of the Scyld Cloud Workstation meta-server. By default this can befound in the directory of the Scyld Cloud Workstation executable and is named boot.log. For moreinformation on log output, see Log Output.

Changed in v5.0.0. Previously named Server.ServiceLogFile in v2.2.0. Default value changed

8.3.5 Server.LocalCursor

Determines if the client’s local cursor should be shown instead of the remote cursor. Enabling local cursortypically improves the user experience. Defaults to true.

Added in v2.2.0.

8.3. Settings Glossary 29


8.3.6 Server.AutoLock

Determines if Scyld Cloud Workstation calls on the OS to lock the desktop upon disconnecting from theweb page. Experimental. Defaults to false.

Warning: NOTE: In Linux, screen locking is achieved by entering Ctrl+Alt+l on behalf of theuser. While this will lock the screen for most, this feature is not guaranteed to work on all Linuxsystems.

Updated in v5.0.0.

8.3.7 Server.IdleUserTimeout

The length of time (in minutes) that users must be inactive before all users are disconnected. This featureis disabled if value is 0.0 or less. Defaults to 120.

Added in v5.0.0.

8.3.8 Server.Port

The port number used by the server. Defaults to 443 if Server.Secure is true or 80 if Server.Secure isfalse.

8.3.9 Server.Secure

Determines if the server operates over HTTPS (recommended). Defaults to true.

8.3.10 Server.LicenseFile

Specifies a license file path or a port@host address where a Scyld FlexLM license server is hosted.If the default license server port is being used (27002), then @host is also acceptable. Defaults toscyld-cloud-workstation.lic.

For more information on installing license files, see Flexera License Management

Added in v5.0.0.

8.3.11 Server.StartDelay

Specifies a sleep time to delay the start-up of Scyld Cloud Workstation in seconds. Defaults to 0.

Added in v5.0.0.

8.3.12 Server.Auth.Enabled

Determines if authentication is enabled and valid credentials are required to sign-in (recommended). De-faults to true.

If false, then all authentication is disabled and any credentials can be used to sign-in.

30 Chapter 8. Setup


Note: Changing this value takes effect after a service restart.

8.3.13 Server.Auth.Username

Declares a username to be used in combination with the password defined byServer.Auth.ShadowPassword at the Scyld Cloud Workstation sign in page.

Config File Authentication can be disabled by commenting or removing Server.Auth.Username andServer.Auth.ShadowPassword. To This must be specified with Server.Auth.ShadowPassword and is notnecessarily the same as the username used by the remote operating system.

Note: Changing this value takes effect without a service restart.

Changed in v5.0.0.

8.3.14 Server.Auth.ShadowPassword

A shadowed password used to sign in to the Scyld Cloud Workstation sign in page. Con-fig File Authentication can be disabled by commenting or removing Server.Auth.Username andServer.Auth.ShadowPassword. The format is as follows:

$6$<salt>$<hash>

The initial 6 value should never be changed and signals that SHA-512 should be used. The <salt> andthe plain text password are used to create the hashed password using the UNIX crypt method. Seehttp://linux.die.net/man/3/crypt for more information on UNIX crypt.

Password rules are dependent on length:

Length Password Restrictions8-11 Use mixed case characters, numbers, and symbols12-15 Use mixed case characters and either numbers or symbols16-19 Use mixed case characters20+ No restrictions

We recommend using passphrases of four randomly generated english words (i.e. “mail design kickoffice” for the best combination of usability and security.

Warning: Even though the ShadowPassword value encrypts your password, its contents shouldremain private. If you suspect that any part of the ShadowPassword has been compromised, pleasechange your password immediately using our password update utility:

• Linux: scyld-cloud-workstation.sh --passwd• Windows: scyld-cloud-workstation.exe /passwd


Changed in v5.0.0.


http://linux.die.net/man/3/crypt


8.3.15 Server.Auth.MinPasswordLength

The length of the password that is hashed and stored as Server.Auth.ShadowPassword. This may be set aslow as 8, but we recommend at least 12 characters.


Changed in v5.0.0.

8.3.16 Server.Auth.FailAttempts

The number of unsuccessful sign in attempts a client is allowed before the server temporarily rejectsfuture requests from that client for a time period specified by Server.Auth.FailDelay. This helps reducebrute force attacks.


Changed in v5.0.0.

8.3.17 Server.Auth.FailDelay

The length of time that the server will reject sign in requests from clients that repeatedly fail to sign in.See Server.Auth.FailAttempts for more information.


Changed in v5.0.0.

8.3.18 Server.Auth.ScyldCloudAuth.URL

The URL to the Scyld Cloud Auth authentication web service. Only applies to Scyld Cloud Managerproducts.


Changed in v5.0.0.

8.3.19 Server.Auth.ScyldCloudAuth.Allow

A list of <Username></Username> elements. Each <Username> element enables a usernameto be authenticated by ScyldCloudAuth. Usernames elements can use asterisk wildcard characters (i.e.*@penguincomputing.com will enable all usernames that end in @penguincomputing.com).


Changed in v5.0.0.

32 Chapter 8. Setup


8.3.20 Server.Auth.ScyldCloudAuth.Deny

A list of <Username></Username> elements. Each <Username> element disables a username tobe authenticated by ScyldCloudAuth. Usernames that are mentioned by both the Deny and Allow list aredenied.

Usernames elements can use asterisk wildcard characters (i.e. *@penguincomputing.com will en-able all usernames that end in @penguincomputing.com).


Changed in v5.0.0.

8.3.21 Server.Auth.Session.DefaultTimeout

The lifetime (in seconds) of a session token that starts upon successfully signing in. Session tokens letyou access protected resources from the server such as creating a new remote-visualization connection.Increasing this value means a longer period of time you can access the resources without signing in again.

Existing remote-visualization connections are unaffected by session token timeouts. Defaults to 60 sec-onds.


Changed in v5.0.0.

8.3.22 Server.Auth.OSAuthEnabled

Determines if authentication using OS credentials is enabled. Defaults to true.

Important: While config file or ScyldCloutAuth usernames can be used to sign in to Scyld CloudWorkstation at any time, only a single set of OS credentials can only be used to sign-in at a time. Thisprevents different OS credentials from signing in at the same time.

Note: Changing this value takes effect after a service restart.

Added in v6.1.0.

8.3.23 Server.Auth.Session.OnSignIn

The path of a script to execute immediately after signing in. The script is passed the system account nameof the user as an argument. By default this is not set, but it can be used for custom sign-in initialization.


Changed in v5.0.0.



8.3.24 Server.VideoSource

The video capture mechanism. Currently supports nvfbc, stream, and auto. The default is auto.

Set to auto if you’d like the system to use nvfbcwhen the service detects an NVIDIA GRID compatiblecard and stream in all other cases.

Set to nvfbc only if you have an NVIDIA GRID SDK compatible graphics card and driver.

Set to stream to use our CPU-based encoding solution.

Changed in v5.0.0.

8.3.25 Server.Video.MaxWidth

Any server-side video that exceeds this width is scaled down to this value. This is primarily used toprevent clients from receiving video with resolutions so high that the client can not process them fastenough.

A value of -1 disables this threshold.

Defaults to 1920.

Updated in v5.0.0. Changed default.

8.3.26 Server.Video.MaxHeight

Any server-side video that exceeds this height is scaled down to this value. This is primarily used toprevent clients from receiving video with resolutions so high that the client can not process them fastenough.

A value of -1 disables this threshold.

Defaults to 1080.

Updated in v5.0.0. Changed default.

8.3.27 Server.Video.StartFrameRate

Initial frame rate. Measured in frames per second. Defaults to 24.

Added in v2.2.0.

8.3.28 Server.Video.MinFrameRate

The lowest valid frame rate for a connection. Measured in frames per second. Defaults to 2.

Added in v2.2.0.

8.3.29 Server.Video.MaxFrameRate

The highest allowable frame rate for a connection. Measured in frames per second. Defaults to 60.

34 Chapter 8. Setup


8.3.30 Server.ConcurrentClients.MaxClientCount

The maximum number of clients that can be connected at a time. Defaults to 6.

Added in v3.0.0.

8.3.31 Server.QoS.Enabled

Enables the automatic adjustment of frame rate to adapt to current performance conditions. Frame rate willstart at Server.Video.StartFrameRate and jump between Server.Video.MinFrameRateand Server.Video.MaxFrameRate.

Setting this to false will cause the server to send a constant frame rate speci-fied by Server.Video.StartFrameRate. Server.Video.MinFrameRate andServer.Video.MaxFrameRate are ignored in this case.

Defaults to true.

8.3.32 openSSL

All elements within the openSSL tag are described in the Poco SSLManager documentation.

8.3.33 openSSL.server.privateKeyFile

The path to the file containing the private key for the certificate in PEM format (or containing both theprivate key and the certificate). This path can be absolute or relative to the xml config file. Required forHTTPS support.

8.3.34 openSSL.server.certificateFile

The path to the file containing the server’s or client’s certificate in PEM format. Can be omitted if the thefile given in privateKeyFile contains the certificate as well. This path can be absolute or relative to thexml config file.

8.3.35 openSSL.server.verificationMode

Specifies whether and how peer certificates are validated (see the Poco Context class for details). Validvalues are none, relaxed, strict, and once. Defaults to none.


8.3.36 openSSL.server.loadDefaultCAFile

Boolean value. Specifies wheter the builtin CA certificates from OpenSSL are used. Defaults to true.

8.3.37 openSSL.server.cipherList

Specifies the supported ciphers in OpenSSL notation.



http://pocoproject.org/docs/Poco.Net.SSLManager.html

http://pocoproject.org/docs/Poco.Net.Context.html


8.3.38 openSSL.server.privateKeyPassphraseHandler.name

Defaults to KeyFileHandler. The name of the Poco class used for obtaining the passphrase foraccessing the private key. If your private key does not use a passphrase, this value is ignored.

Added in v2.2.0. Default value changed.

8.3.39 openSSL.server.privateKeyPassphraseHandler.options.password

The private key passphrase (ignored if there is no passphrase for the private key).

8.3.40 openSSL.server.invalidCertificateHandler.name

This should be set to ConsoleCertificateHandler. The name of the class used for confirming invalid cer-tificates. Defaults to RejectCertificateHandler.


8.3.41 openSSL.server.cacheSessions

This should be set to false. Enables or disables session caching.

8.3.42 openSSL.server.extendedVerification

Enable or disable the automatic post-connection extended certificate verification.

8.3.43 openSSL.server.requireTLSv1_2

Require a TLSv1.2 connection. Defaults to true.


8.3.44 openSSL.client.verificationMode

Specifies whether and how peer certificates are validated when the server acts as a client to a third-partyhost (see the Poco Context class for details). Valid values are none, relaxed, strict, and once.Defaults to relaxed. Setting this value to none is not recommended.

Added in v3.0.0.

8.3.45 openSSL.fips

Enable or disable OpenSSL FIPS mode. Only supported if the OpenSSL version that this library is builtagainst supports FIPS mode.

36 Chapter 8. Setup

http://pocoproject.org/docs/Poco.Net.Context.html


8.4 Client Settings

Clients and browsers that meet the requirements listed in Client Requirements support TLS 1.2, WebGL, and Web-Sockets by default and require no further setup.

Attention: Contact your system administrator if TLS 1.2, WebGL, or WebSockets are disabled.

8.4. Client Settings 37


38 Chapter 8. Setup

CHAPTER

NINE

USAGE

In this section we describe how to start and stop the Scyld Cloud Workstation service in either Linux or Windows onthe remote server. We then talk about how to connect and interact with the remote desktop interface.

9.1 Using the Linux Service

To start, stop, or restart the scyld-cloud-workstation, open a terminal with root or sudo privileges and use the servicecommand:

service scyld-cloud-workstation startservice scyld-cloud-workstation stopservice scyld-cloud-workstation restart

To run scyld-cloud-workstation directly rather than as a service (this is usually only useful for debugging purposes),use the scyld-cloud-workstation.sh start-up script. Usage information can be obtained by passing the --help flag.

usage: scyld-cloud-workstation OPTIONSscyld-cloud-workstation -- a GPU accelerated remote desktop web service.

--daemon Run application as a daemon.--pidfile=path Write the process ID of the

application to given file.-h, --help display help information on command

line arguments-vsvideosource, --videosource=videosource choose videosource (nvfbc, stream)-q, --quiet hide the console when running-pwd, --passwd update the password

9.2 Using the Windows Service

To use the scyld-cloud-workstation service, we must verify that the service is registered with the OS and then start theservice.

9.2.1 Open a Command Prompt as an Administrator

1. Sign in as a user that is an Administrator.

2. Click on the Windows Start menu.

3. In the Search box, type Command Prompt, but don’t hit Enter just yet.

39


4. Right-click on the Command Prompt and select Run as administrator.

9.2.2 Register the Windows Service

To register the windows service, use the scyld-cloud-workstation.exe command:

scyld-cloud-workstation.exe /registerService /startup=automatic

The scyld-cloud-workstation will now automatically start on reboot.

Note: Service registration should already be handled by the installer. If you the message below, verify that scyld-cloud-workstation has been properly installed. This is usually a sign that the PATH environment variables are notpointing at the scyld-cloud-workstation.exe.

'scyld-cloud-workstation.exe' is not recognized as an internal orexternal command, operable program or batch file.

9.2.3 Start and Stop the Windows Service

To start and stop the registered windows service without rebooting, use the net command:

net start scyld-cloud-workstationnet stop scyld-cloud-workstation

9.3 Change the Config File Password

Scyld Cloud Workstation lets you optionally store a username and hashed password in the config file for authenti-cation. The credentials specified by Server.Auth.Username and Server.Auth.ShadowPassword attributes are entirelyindependent from LDAP, the remote operating system, and ScyldCloudAuth.

You can change this password by calling scyld-cloud-workstation.sh --passwd in Linux orscyld-cloud-workstation.exe /passwd in Windows from a command line. This password change takeseffect without a service restart.

Password strength requirements are described in the Setup chapter under Server.Auth.ShadowPassword.

Important: This only changes the Server.Auth.ShadowPassword entry in the config file. It does not change thepasswords used by the remote operating system, LDAP, or ScyldCloudAuth.

9.4 Log Output

Log output is organized by priority levels (from highest to lowest: Fatal, Critical, Error, Warning, Notice, Information,Debug, and Trace). scyld-cloud-workstation by default prints Information level messages to /var/log/messages.

Setting LogLevel to information will log all server starts/stops, sign-in attempts, socket connects/disconnects,video source plays/pauses, and additional warning/error messages. This is usually sufficient for production usage.

To see debug and higher level output, open the scyld-cloud-workstation.xml config file and set LogLevel to debug.

40 Chapter 9. Usage


In Linux, debug and higher level log messages can be found at: /opt/scyld-cloud-workstation/bin/scyld-cloud-workstation.log.

In Windows, debug and higher level log messages can be found at: C:\Program Files\PenguinComputing\Scyld Cloud Workstation\log\boot.log and C:\Program Files\PenguinComputing\Scyld Cloud Workstation\log\scyld-cloud-workstation.log.

Note: You can change the path of the output by opening the scyld-cloud-workstation.xml config file andsetting Server.LogFile to a new destination.

By default, Scyld Cloud Workstation does not display a timestamp with each log message. To add a timestamp to allof your output, open the scyld-cloud-workstation.xml and set LogFormat to: %Y-%m-%d %H:%M:%S%q%q: %s:%u: %t.

9.5 Selecting a Video Source

Scyld Cloud Workstation currently supports two video sources:nvfbc and stream.

For most users an appropriate default video source will be automatically detected based on the system’s configuration.Hosts that have an NVIDIA GRID card with a compatible NVIDIA GRID driver installed default to nvfbc. All othersystems will default to stream.

To override the video source, specify --videosource=<nvfbc|stream> or change Server.VideoSourcein the config file.

9.6 Sign In

Once the Scyld Cloud Workstation server has started, users can connect their networked client to the server bytyping the server’s URL into the web browser. Servers using the HTTPS protocol (default) have URLs like this:https://<server-hostname-or-ip>.

This will take you to the Scyld Cloud Workstation sign in page. Submit the username and password encrypted in theconfig file or by ScyldCloudAuth to sign in.

As a third option, you can use your OS specific credentials to sign in.

Important: While config file or ScyldCloutAuth usernames can be used to sign in to Scyld Cloud Workstation at anytime, only a single set of OS credentials can only be used to sign-in at a time. This prevents different OS credentialsfrom signing in at the same time.

After signing in you will see a gray canvas that will turn into a remote visualization display within a few seconds. Atthis point you can interact with the remote operating system. Other users will be prevented from signing into the webservice until you sign out.

9.7 User Controls

The control buttons allow you to enter fullscreen mode, submit Ctrl-Alt-Del to the remote OS, or sign out fromScyld Cloud Workstation session.

9.5. Selecting a Video Source 41


Key-combinations such as Ctrl+N, Ctrl+W, and Ctrl+T are not relayed to Scyld Cloud Workstation in mostbrowsers. Chrome users can work around this issue by running Chrome in “app mode” by appending the--app=<url> flag when calling it from a command line or shortcut.

Key-combinations such as Ctrl-Alt-Del are intercepted by the client OS and must be sent to Scyld Cloud Work-station via control buttons.

9.8 Paste Text from the Local Clipboard

Text can be pasted from the local client into the remote desktop.

To paste text from a local Linux / Windows clipboard into the remote Linux / Windows desktop, press Ctrl+V.

To paste text from a local OS X clipboard to the remote Linux / Windows desktop, use your browser’s menu systemto select Edit -> Paste. This transfers the local clipboard to the remote clipboard. Once this is done, you can useCtrl+V or use your remote application’s paste feature.

Note: Only characters that are supported by both the client and server can be pasted.

9.9 Change Screen Resolution

Warning: Changing screen resolutions has one known issues:1. Multiple rapid resolution changes may lead to service instability. Changing the screen resolution more

than 5 times over a few seconds may cause the service to restart or quit.

In Windows, right click on the desktop and select Screen resolution. Change the resolution dropdown to yourdesired resolution and then click ‘OK’.

In Linux, if you are using a first generation NVIDIA GRID card (i.e., K1, K2) in a headless configuration (i.e. youare using the UseDisplayDevice none option in your /etc/X11/xorg.conf file), you will have to opena command prompt and use the xrandr --fb <width>x<height> command. For example, if you’d like tochange the screen resolution to 1920x1080, you would enter: xrandr --fb 1920x1080.

Otherwise change your screen resolution by using the provided Linux OS tools (dependent on distribution).

9.10 Downscale Screen Resolution

System administrators have the ability to restrict the maximum screen resolution in the con-fig file at scyld-cloud-workstation.xml using the Server.Video.MaxWidth andServer.Video.MaxHeight settings. This is useful for preventing clients from being overwhelmed by theprocessing power required to work with high-resolution video.

If the user attempts to use a higher screen resolution, the user will get an alert and the video will be scaled down.

9.11 Enable 4K Support

As of v7.0.0 it is possible to support 4K desktops with the native, non-browser based client. This feature is not enabledby default and requires a configuration file change to disable the default screen size and bitrate caps. We recommend

42 Chapter 9. Usage


having a downlink of at least 20 Mbps to support the increased screen size.

In future releases 4K support will be enabled automatically.

Note: If you are not going to use 4K resolutions then leave the following settings at their defaults by commentingthem out or deleting them from the config file. The default screen size and bitrate caps are used to ensure a good userexperience for slower clients.

The following steps enable 4K support:

1. Open the xml config file.

2. Add the Server.Video.MaxWidth and Server.Video.MaxHeight tags with the value set to -1 todisable the resolution cap.

3. Save the config file and restart the service.

Note: NVIDIA GRID products (such as a Tesla M60) require an NVIDIA Quadro Virtual Datacenter Workstationlicense to use 4K resolutions. Contact NVIDIA for more information.

9.12 Video Bit-Rate Selection

As of v7.1.0, the default video bit-rate is calculated by using a linear regression of two values: 2500 kbps at 1280x720and 5000 kbps at 1920x1080. A system administrator can customize bit-rates for different resolutions by adding twoor more resolution and bit-rate pairings within the Server.Video.AvgBitRate config file setting. The syntax isas follows:

<width>x<height>=<bitrate>,<width>x<height>=<bitrate>,...

Example 1: the following is equivalent to the default bit-rate values: 1280x720=2500k,1920x1080=5000k.

Example 2: the following can be used to specify a single average bit-rate setting across all resolutions:1024x768=2m,1600x900=2m.

The linear regression algorithm is based on the two closest resolutions to allow a fine-grained bit-rate control. If thevalue only specifies one resolution and bit-rate, the service will use 0x0=128k as one of the two linear regressionpoints.

9.13 Sign Out

Windows and Linux users must change users by using the remote OS’s log out / log in feature. Scyld Cloud Worksta-tion does not support “fast user switching” and the service must be restarted if this happens.

Closing your browser or signing out of the Scyld Cloud Workstation session does not sign you out of the remoteoperating system. Use the remote OS’s signing-out capability to sign out of the remote OS.

9.12. Video Bit-Rate Selection 43


44 Chapter 9. Usage

CHAPTER

TEN

COLLABORATION

Multiple users can now share control of the same desktop. There are two types of users in this case: regular Host usersand temporary Guest users.

Hosts are are fully trusted users who have an account on the system and have complete control over what a Guest canaccess. An ongoing session begins when one Host is signed in and ends when the last Host leaves. All Guests andInvites are removed when an ongoing session ends.

Guests are users who are invited to join an ongoing session. As a Host, this can be useful when you want to share aworkstation with a remote colleague who should not have a permanent account on the system.

This section describes how a Host adds and manages Guest users.

Important: The Guest alerts and interface buttons described below are not visible in fullscreen mode.

10.1 Set the maximum number of concurrent clients

By default the server only allows 6 users to be signed on at any given time. This number can be changed by asystem administrator by adding a Server.ConcurrentClients.MaxClientCount setting in the config fileat scyld-cloud-workstation.xml.

10.2 Collaboration Quick Start

At a high level, adding a new guest involves three steps:

1. A Host creates an Invite Link and sends it to Guest users

2. A Guest opens the Invite Link, enters a Guest name, and attempts to sign in

3. A Host accepts the Guest’s sign in request

Hosts can use the control buttons to pause video to all Guests or ban all Guests and revoke all pending Invites. Hostscan also click on user buttons to kick individual Guests or give keyboard and mouse control.

10.3 Control Buttons

At the top of the screen there are a row of buttons that allow you to type special keys such as Ctrl + Alt + Del,add guests, pause all guest video, ban all guests, and sign out. Press Ctrl + F12 to show / hide these buttons.

45


10.4 Add New Guests

Hosts can invite a group of guests by creating an Invite Link. Click on the ‘Add Guests’ button.

In the form that appears, specify how many guest sign ins you’d like this link to be good for. It is best practice to selectthe minimum number you will need.

The next form will show the generated Invite Link. Copy and send this link to Guest users and then close the form.

Warning: Anyone who receives an Invite Link can request Guest access to your system. While these links expireover time and are limited by how often they can be used it is best practice to keep this link confidential.

When Guests use this link to request a sign in, an alert will appear to all Hosts asking whehter the user should beAccepted or Declined.

Important: It is best practice to verify the incoming user’s identity via a phone call, text message, or other trustedcommunication channel.

When a Guest signs in, their username becomes reserved until all Hosts sign out. Guest usernames must be uniqueand consist of only letters, numbers, and underscores. Once the session ends, all Guest usernames are freed again foruse.

10.5 Pause Guest Video

Guest video can be toggled by clicking on the ‘Pause Guests’ button.

10.6 Ban Guests and Revoke Invites

Guests can be banned for the session either individually or all at the same time using the ‘Ban Guests’ button. Hostscan not be banned.

10.7 User Buttons

At the bottom of the screen there are a row of buttons containing usernames and status icons. The first button willalways be “You”, indicating the user button for the user signing in. Clicking on the user button will show statusinformation (including frame rate) and actions that can be taken on that user, such as banning or giving keyboard /mouse control.

Usernames that end with an asterisk are Hosts. Press Ctrl + F12 to show / hide these buttons.

10.8 Give Keyboard and Mouse Control

A Host can give any other user control of the keyboard and mouse using the ‘Give Keyboard and Mouse Control’button.

46 Chapter 10. Collaboration

CHAPTER

ELEVEN

PERFORMANCE

Playback performance depends on three bottlenecks (in order of significance): network quality, client load, and serverload. In this section we talk about each of these and how to determine which bottleneck requires attention.

11.1 Network Quality

Network quality can be measured as a combination of latency, throughput, and stability. When determining networkquality you may want to run Scyld Cloud Workstation on its own to guarantee that other applications or clients are notconsuming large amounts of network resources at the same time.

Latency between the client and server can be measured using ping times. Acceptable latency depends on the appli-cations being used. CAD users, for example, may find ping times up to 150 ms to be quite usable and 300 ms to beusable for sporadic use. Testing and demoing of applications like Google Earth are typically over 802.11g connectionswith ping times of 30-80 ms.

When running fullscreen animations at 1440x900, Scyld Cloud Workstation has a typical throughput consumption of4 Mbps. Throughput consumption drops dramatically when pixels on the screen do not change. We conservativelyrecommend 5.5 Mbps. This is typically not a bottleneck for Scyld Cloud Workstation since it’s common for clientsand servers to have more than 4 Mbps of bandwidth, but it is still worth remembering.

11.2 Client Load

Decoding is largely dependent on the web browser implementation and the CPU performance of the client. Werecommend using Chrome as it performs best with Scyld Cloud Workstation in testing.

CPU performance depends on the hardware and the load on the system. We test on modern CPUs such as the multi-core Intel i5s and i7s from 2011 and later. When evaluating playback performance, verify that other applications arenot also consuming large amounts of CPU time.

Decreasing screen resolution on the server-side is another option for reducing load on the client. While we recommend1600x900, users may find that 1280x720 offers a better overall experience.

If you are running the non-WebGL version of Scyld Cloud Workstation, performance is expected to be consider-ably slower (depending on the CPU). Lowering the remote server’s screen resolution and using Chrome is stronglyrecommended in this case.

11.3 Server Load

Server load is typically not a large bottleneck since Scyld Cloud Workstation does not consume much server-side CPUtime. GPU consumption does increase, but for NVIDIA GRID cards the display capture and encoding is done on a

47


part of the GPU that is independent of computation.

11.4 Further Help

If you have additional questions about perormance, please contact Penguin Computing at [email protected].

48 Chapter 11. Performance



CHAPTER

TWELVE

FREQUENTLY ASKED QUESTIONS / TROUBLESHOOTING

12.1 What do I do if Windows shows a black screen instead of a loginscreen?

We’ve observed in Windows 2012 that the login screen will occasionally not appear until you hit the ‘Escape’ key.

12.2 Why does Google Chrome 61-62 show inaccurate colors?

Newer versions of Google Chrome (Chrome 61 and 62) use the ICC profile provided by the local OS rather thanforcing its own color profile. This may make the colors appear different from what you may see in other browsers orin the Native Client.

As a workaround you can enter chrome://flags/#force-color-profile in your Chrome URL bar andselect sRGB from the dropwdown. Then close and restart Chrome.

12.3 How many users can sign in at a time?

Scyld Cloud Workstation currently supports multiple signed in users at a time. Currently this defaults to 6. This valuecan be changed in the config XML file via the Server.ConcurrentClients.MaxClientCount option.

12.4 Can LDAP credentials be used at the sign in page?

Yes. There are two ways to support this.

Traditionally support for LDAP currently comes as part of the Scyld-Cloud-Manager package. Scyld Cloud Work-station can be configured to authenticate through Scyld-Cloud-Auth, which can talk to LDAP. To connect to a Scyld-Cloud-Auth service, open the config file, set Server.Auth.ScyldCloudAuth.URL, and add one or more Username ele-ments to the Server.Auth.ScyldCloudAuth.Allow.

As of v6.1.0, Scyld Cloud Workstation passes credentials directly to the remote operating system. This feature isenabled by default, but it can be disabled by setting Server.Auth.OSAuthEnabled to false.

12.5 I’m only seeing a gray rectangle.

This is either caused by caching problems, an unsupported screen resolution, or an unexpected error between the clientand server.

49


Try signing out, opening a new web browser, and trying again. If the problem persists, check the web browser’sJavaScript Console and the Scyld Cloud Workstation log file (Linux: /var/log/messages) for errors.

If you are a CentOS user, verify that Xorg is running on DISPLAY :0 by running ps aux | grep X. If you donot see a line that looks like Xorg :0, you may need to restart X by running init 3 and init 5 in CentOS.

If you are a Windows user and you are using the NvFBC videosource, verify that NvFBC is enabled by run-ning NvFBCEnable.exe -checkstatus as an Administrator. If it is disabled, you can enable it with theNvFBCEnable.exe -enable command.

12.6 How do I press Ctrl+Alt+Del?

There is a shortcut button for this keyboard combination at the bottom of the Scyld Cloud Workstation video screen.

12.7 How do I press Ctrl+N, Ctrl+T, Ctrl+W, Ctrl+Tab, Ctrl+Page Up, orCtrl+Page Down?

By default, Google Chrome (aka Chromium) intercepts certain specific keyboard combinations before Scyld CloudWorkstation can receive them. There is a special “app mode” available for Chrome users that can be activated at thecommand line by appending the --app=<url> flag. For example:

google-chrome --app=https://host/

This will open a borderless Chrome browser that will relay many of these key combinations to Scyld Cloud Work-station. If this is something you will do often, we recommend creating a shortcut with a flag to your Scyld CloudWorkstation host.

Note: Certain keyboard combinations, such as Ctrl+Alt+Del and Alt+Tab are intercepted by the client operatingsystem and are not relayed to the Scyld Cloud Workstation interface.

12.8 What ports do I need to open?

By default, Scyld Cloud Workstation must be able to accept incoming requests over HTTPS port 443 (or port 80 ifyou are using HTTP).

12.9 Can I run my applications?

Scyld Cloud Workstation is completely unaware of what applications are being run on the remote operating system. Inother words, if your application can run directly on the remote host, it can be displayed on Scyld Cloud Workstation.

12.10 Will it run on my iPad / mobile device?

We do not yet officially support iPad or mobile devices, but we have had some success getting view-only functionalityto work with an iPhone SE.

50 Chapter 12. Frequently Asked Questions / Troubleshooting


12.11 Is there audio support?

We do not support audio at this time, but please let us know if adding this feature would be important to you.

12.12 Can I cut, copy, and paste?

You can copy text from the local desktop to the remote desktop. See Paste Text from the Local Clipboard for moreinformation.

12.13 What graphics cards do you support?

See Server Hardware.

12.14 How many NVIDIA GRID GPUs do I need?

As of v5.0, NVIDIA GRID GPUs are no longer required to run Scyld Cloud Workstation.

12.15 What do I do if Windows reports: “The program can’t start be-cause LIBEAY32.dll is missing from your computer.”

This error message typically means that OpenSSL 1.1, which does not provide LIBEAY32.dll, is installed.

Scyld Cloud Workstation requires that an OpenSSL 1.0 compatible library (such as OpenSSL 1.0.1 or OpenSSL 1.0.2)is installed on the server side. OpenSSL will continue to receive security updates until December 31, 2019.

12.16 What Xorg.conf options do I need for an NVIDIA GRID / Teslacard over GPU passthrough?

First, find the appropriate BusID for your graphics card using the following command:

lspci | grep VGA | sed 's/\./:/'...00:07:0 VGA compatible controller: NVIDIA Corporation GK107GL [GRID K1] (rev a1)

The BusID is the first token 00:07:0. If you used lspci on its own, remember that periods must be replaced withcolons before they can be used in an Xorg.conf file.

For older NVIDIA GRID cards (K1 or K2) add the BusID and the “UseDisplayDevice” “none” option. Modify theXorg.conf file so that the Device and Screen sections look similar to the following:

Section "Device"Identifier "Device0"Driver "nvidia"VendorName "NVIDIA Corporation"BusID "00:07:0"

EndSection

12.11. Is there audio support? 51


Section "Screen"Identifier "Screen0"Device "Device0"Monitor "Monitor0"DefaultDepth 24Option "UseDisplayDevice" "none"SubSection "Display"

Virtual 1440 900Depth 24

EndSubSectionEndSection

For NVIDIA Tesla M60 users add the BusID (note: the syntax below is also valid). You may also want to specifya DPI (as needed) if images on the screen appear too wide or narrow. Modify the Xorg.conf file so that the Devicesection looks similar to the following:

Section "Device"Identifier "Device0"Driver "nvidia"VendorName "NVIDIA Corporation"BoardName "Tesla M60"BusID "PCI:0:07:0"Option "DPI" "96x96"

EndSection

52 Chapter 12. Frequently Asked Questions / Troubleshooting

CHAPTER

THIRTEEN

END USER LICENSE AGREEMENT

Penguin Computing Inc.45800 Northport Loop West, Fremont, CA 94538Tel: 415-954-2800 - Fax: 415-954-2899www.penguincomputing.com

Penguin Computing Software End User License Agreement

Last revised: 1/4/2012

LEGAL NOTICE - READ CAREFULLY BEFORE INSTALLING OR OTHERWISE USINGTHIS SOFTWARE.

This License Agreement (the "Agreement") is a legal agreement betweenyou, a single legal entity ("End User"), and Penguin Computing("Penguin"). This Agreement governs your use of the Scyld softwaredefined below (the "Software") and any accompanying written materials(the "Documentation"). You must accept the terms of this Agreementbefore installing, downloading, accessing or otherwise using suchSoftware and documentation.

By "ACCEPTING" at the end of this Agreement, you are indicating thatyou have read and understood, and assent to be bound by, the terms ofthis Agreement. If you are an individual working for a company, thenyou represent and warrant you have all necessary authority to bindyour company to the terms and conditions of this Agreement.

If you do not agree to the terms of the Agreement, you are not grantedany rights whatsoever in the Software or Documentation. If you are notwilling to be bound by these terms and conditions, do not "ACCEPT" theEULA and remove the software from the system immediately.

END USER LICENSE AGREEMENT FOR SCYLD SOFTWARE

1. Definitions.

1.1 "Clustered System" means a collection of computer systems managedby the Software and for which the total number of computers in thesystem is specified in the End User purchase order.

1.2 "Master Node" means the computer or computers designated as theMaster Node(s) in the applicable End User purchase order, where theSoftware is initially installed and from which the total number ofcomputers comprising the Clustered System are managed.

53


1.3 "Software" means the software provided under this Agreement byPenguin or its authorized distributor or reseller and for which theapplicable End User purchase order specifies: (i) the Software to belicensed by End User (ii) the Master Node(s) (iii) the license feesand (iv) the total number of computers in the Clustered System forwhich End User has paid applicable license fees and the term of theSoftware usage. The Software is comprised of a collection of softwarecomponents that fall into three (3) categories: (a) "Scyld UnpublishedSoftware" which is owned by Penguin and/or its licensors and licensedunder the terms of this Agreement (b) "Scyld Published Software"which is owned by Penguin and licensed under the GPL version 2 opensource license or such other open source license as Penguin may electin its sole discretion and (c) "Open Source Software" which is ownedby various entities other than Penguin and is subject to the "opensource" or "free software" licenses, including but not limited toGeneral Public Licenses (GPL), Lesser General Public License (LPGL),Apache, Artistic, BSD, IBM Public, Mozilla, Omron, Open Group PublicLicense, and Python licenses.

1.4 "Client Connections" means the simultaneous connections betweenany software client and Software, where a connection creates apersistent and unique Software session per software client.

2. License.

2.1 License Grant. Subject to the terms and conditions of thisAgreement, Penguin grants to End User a nonexclusive,non-transferable, non-sub licensable right and license to (a)reproduce (solely to download and install), perform, and execute theScyld Unpublished Software on the specified Master Node(s), solely forEnd User's internal purposes, and (i) solely for use on the number ofcomputers in the Clustered System and (ii) not to exceed the maximumnumber of Client Connections for which End User has paid the requiredlicense fees for the authorized term and (b) make one (1) copy of theScyld Unpublished Software and Documentation for backup and/orarchival purposes only.

2.2 Restrictions. The End User shall not, and shall not permit anythird party to: (a) sell, lease, license, rent, loan, or otherwisetransfer the Scyld Unpublished Software or Documentation, with orwithout consideration (b) permit any third party to access or use theScyld Unpublished Software or Documentation (c) permit any thirdparty to benefit from the use or functionality of the ScyldUnpublished Software via a timesharing, service bureau, or otherarrangement (d) transfer any of the rights granted to End User underthis Agreement (e) reverse engineer, decompile, or disassemble theScyld Unpublished Software (f) modify or create derivative worksbased upon the Scyld Unpublished Software or Documentation, in wholeor in part (g) reproduce the Scyld Unpublished Software orDocumentation, except as expressly permitted in Section 2.1 above (h)remove, alter, or obscure any proprietary notices or labels on theScyld Unpublished Software or Documentation (i) use the ScyldUnpublished Software for any purpose other than expressly permitted inSection 2.1 above or (j) use the Scyld Unpublished Software for morethan the total number of computers, or longer than the authorized termthe End User is licensed for pursuant to Section 2.1 above.

2.3 Open Source Software. The Open Source Software and Scyld Published

54 Chapter 13. End User License Agreement


Software are not subject to the terms and conditions of Sections 2.1,2.2, or 6. Instead, each item of Open Source Software and ScyldPublished Software is licensed under the terms of the end-user licensethat accompanies such Open Source Software and Scyld PublishedSoftware, as may be located in the product packaging or availableon-line. End User agrees to abide by the applicable license terms forany such Open Source Software and Scyld Published Software. Nothing inthis Agreement limits End User's rights under, or grants End Userrights that supersede, the terms and conditions of any applicable enduser license for the Open Source Software or Scyld PublishedSoftware. In particular, nothing in this Agreement restricts EndUser's right to copy, modify, and distribute any of the Open SourceSoftware and Scyld Published Software that is subject to the terms ofthe GPL and LGPL. For the Open Source Software and Scyld PublishedSoftware subject to the GPL and LGPL, for a period of three (3) yearsfollowing End User's receipt of the Software, End User may contactPenguin at the address below in writing and request a copy of thesource code for such Open Source Software or Scyld Published Softwareat Penguin's then-current fees.

3. Ownership. The Software is licensed, not sold. Penguin and itslicensors retain exclusive ownership of all applicable worldwidecopyrights, trade secrets, patents, and all other intellectualproperty rights throughout the world, and all applications andregistrations relating thereto, in and to the Scyld UnpublishedSoftware, Scyld Published Software, and Documentation, and any full orpartial copies thereof, including any additions or modifications tothe Scyld Unpublished Software and Documentation. End Useracknowledges that, except for the limited license rights expresslyprovided in this Agreement or the Open Source Licenses, as applicable,no right, title, or interest to the intellectual property in theSoftware or Documentation is provided to End User, and that End Userdoes not obtain any rights, express or implied, in the Software orDocumentation. All rights in and to the Software not expressly grantedto End User in this Agreement or the Open Source Licenses, asapplicable, are expressly reserved to Penguin and its licensors. The"Scyld, "Scyld Beowulf", "Scyld ClusterWare" and "Scyld Computing"trademarks and associated logos are the trademarks of Penguin and itsaffiliates. This Agreement does not permit End User to use the Penguintrademarks.

4. Limited Warranty. TO THE MAXIMUM EXTENT PERMITTED UNDER APPLICABLELAW, THE SOFTWARE IS PROVIDED AND LICENSED "AS IS" WITHOUT WARRANTY OFANY KIND, EXPRESSED OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OFMERCHANTABILITY, NON- INFRINGEMENT, TITLE OR FITNESS FOR A PARTICULARPURPOSE. PENGUIN DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THESOFTWARE WILL MEET THE END USER'S REQUIREMENTS OR THAT THE OPERATIONOF THE SOFTWARE WILL BE ERROR FREE OR APPEAR PRECISELY AS DESCRIBED INTHE ACCOMPANYING DOCUMENTATION.

5. Limitation of Liability. TO THE MAXIMUM EXTENT PERMITTED BYAPPLICABLE LAW, PENGUIN NOR ANY OF ITS AUTHORIZED DISTRIBUTORS,RESELLERS AND LICENSORS WILL BE LIABLE TO END USER FOR ANY INCIDENTALOR CONSEQUENTIAL DAMAGES, LOST PROFITS, LOST OPPORTUNITIES, LOSTSAVINGS, OR LOST DATA OR COST OF COVER ARISING OUT OF THE USE ORINABILITY TO USE THE SOFTWARE OR DOCUMENTATION OR ANY SERVICESHEREUNDER, HOWEVER CAUSED ON ANY THEORY OF LIABILITY (INCLUDINGCONTRACT, STRICT LIABILITY, OR NEGLIGENCE), EVEN IF PENGUIN, ITS

55


AUTHORIZED DISTRIBUTORS, RESELLERS OR LICENSORS HAVE BEEN ADVISED OFTHE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL PENGUIN'S AGGREGATELIABILITY UNDER THIS AGREEMENT EXCEED THE AMOUNT ACTUALLY PAID BY ENDUSER TO PENGUIN FOR THE SOFTWARE GIVING RISE TO THE CLAIM. END USERACKNOWLEDGES THAT THE AGREEMENT REFLECTS AN ADEQUATE AND ACCEPTABLEALLOCATION OF RISK.

6. Confidential Information. Scyld Unpublished Software and thestructure, organization, and code of the Scyld Unpublished Software,including but not limited to the shell scripts of the ScyldUnpublished Software, are confidential and proprietary information("Confidential Information") of Penguin and/or its licensors. End Useragrees to safeguard such Confidential Information with a degree ofcare commensurate with reasonable standards of industrial security forthe protection of trade secrets and proprietary information such thatno unauthorized use is made of such information and no disclosure ofany part of its contents is made to anyone other than End User'semployees whose duties reasonably require such disclosure in order toeffectuate the purposes of this Agreement.

7. Term and Termination. This Agreement will remain in effect untilterminated or for the authorized term of license usage. End User mayterminate this Agreement by removing the Scyld Unpublished Softwarefrom End User's computers, ceasing all use thereof, and destroying allcopies of the Scyld Unpublished Software and Documentation andcertifying to Penguin that it has done so. Any breach of thisAgreement by End User will result in the immediate and automatictermination of this Agreement and licenses granted by Penguin herein,and End User shall cease all use of and destroy all copies of theScyld Unpublished Software and Documentation and certify to Penguinthat it has done so. In addition to termination, Penguin will have theright to pursue any other remedies available to it under law or inequity.

8. Export Controls. End User acknowledges and agrees that the Softwareand Documentation which is the subject of this Agreement may becontrolled for export purposes. End User agrees to comply with allUnited States export laws and regulations including, but not limitedto, the United States Export Administration Regulations, InternationalTraffic in Arms Regulations, directives and regulations of the Officeof Foreign Asset Control, treaties, Executive Orders, laws, statutes,amendments, and supplement thereto. End User assumes soleresponsibility for any required export approval and/or licenses andall related costs and for the violation of any United States exportlaw or regulation.

9. U.S. Government End Users. The Software is a "commercial item" asthat term is defined at 48 C.F.R. 2.101 (OCT 1995), consisting of"commercial computer software" and "commercial computer softwaredocumentation" as such terms are used in 48 C.F.R. 12.212 (SEPT1995). Consistent with 48 C.F.R. 212 and 48 C.F.R. 227.7202-1 through227.7202-4 (JUNE 1995), all U.S. Government End Users acquire theSoftware with only those rights set forth herein.

10. Miscellaneous. This Agreement is the final, complete and exclusiveagreement between the parties relating to the Software andDocumentation, and supersedes all prior or contemporaneous proposals,representations, understandings, or agreements relating thereto,



whether oral or written. Software shall be deemed irrevocably acceptedby End User upon installation. No waiver or modification of theAgreement will be valid unless signed by each party. The waiver of abreach of any term hereof will in no way be construed as a waiver ofany other term or breach hereof. The headings in this Agreement do notaffect its interpretation. End User may not assign or transfer any ofits rights or obligations under this Agreement to a third partywithout the prior written consent of Penguin. Any attempted assignmentor transfer in violation of the foregoing will be null and void. Ifany provision of this Agreement is held by a court of competentjurisdiction to be unenforceable, the remaining provisions of thisAgreement will remain in full force and effect. This Agreement isgoverned by the laws of the State of California without reference toconflict of laws principles that would require the application of thelaws of any other state. The United Nations Convention on Contractsfor the International Sale of Goods shall not apply to thisAgreement. All disputes arising out of this Agreement will be subjectto the exclusive jurisdiction of the state and federal courts locatedin San Francisco County, California, and the parties agree and submitto the personal and exclusive jurisdiction and venue of thesecourts. Should you have any questions about this Agreement, or if youdesire to contact Penguin, please contact us by mail at PenguinComputing, Inc., 501 2nd Street, Suite 310, San Francisco, CA 94107.

57

CHAPTER

FOURTEEN

THIRDPARTY LICENSE AGREEMENTS

Third Party Open Source License Terms Guide

This Software incorporates certain open software in its stack. Thelicense terms associated with this software require that we givecopyright and license information, and this Third Party Open SourceLicense Terms Guide (“TPOSLTG”) provides those details.

1. Licensing terms Bootstrap

The MIT License (MIT)

Copyright (c) 2011-2016 Twitter, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included inall copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.

Source, as of 03/27/17: https://github.com/angular-ui/bootstrap/blob/master/LICENSE

2. Licensing terms Broadway.js

Copyright (c) 2011, Project Authors (see AUTHORS file)All rights reserved.

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:

* Redistributions of source code must retain the above

59


copyright notice, this list of conditions and the followingdisclaimer.

* Redistributions in binary form must reproduce the abovecopyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materialsprovided with the distribution.

* Neither the names of the Project Authors nor the names of itscontributors may be used to endorse or promote productsderived from this software without specific prior writtenpermission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORSBE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE,DATA, OR PROFITS OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OFTHE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

--

The 3-clause BSD above applies to all code except for codeoriginating from the Android project (the .cpp files inAvc/). Those files are under the Android project's Apache 2.0license.

Source, as of 03/27/17: https://github.com/mbebenita/Broadway/blob/master/LICENSE

3. Licensing terms ffmpeg

Most files in FFmpeg are under the GNU Lesser General PublicLicense version 2.1 or later (LGPL v2.1+). Read the fileCOPYING.LGPLv2.1 for details. Some other files haveMIT/X11/BSD-style licenses. In combination the LGPL v2.1+ appliesto FFmpeg.

Some optional parts of FFmpeg are licensed under the GNU GeneralPublic License version 2 or later (GPL v2+). See the fileCOPYING.GPLv2 for details. None of these parts are used bydefault, you have to explicitly pass --enable-gpl to configure toactivate them. In this case, FFmpeg's license changes to GPL v2+.

Specifically, the GPL parts of FFmpeg are:

libpostprocoptional x86 optimization in the files

libavcodec/x86/flac_dsp_gpl.asmlibavcodec/x86/idct_mmx.clibavfilter/x86/vf_removegrain.asm

the following building and testing toolscompat/solaris/make_sunver.pl

60 Chapter 14. Thirdparty License Agreements


doc/t2h.pmdoc/texi2pod.pllibswresample/swresample-test.ctests/checkasm/*tests/tiny_ssim.c

the following filters in libavfilter:vf_blackframe.cvf_boxblur.cvf_colormatrix.cvf_cover_rect.cvf_cropdetect.cvf_delogo.cvf_eq.cvf_find_rect.cvf_fspp.cvf_geq.cvf_histeq.cvf_hqdn3d.cvf_interlace.cvf_kerndeint.cvf_mcdeint.cvf_mpdecimate.cvf_owdenoise.cvf_perspective.cvf_phase.cvf_pp.cvf_pp7.cvf_pullup.cvf_repeatfields.cvf_sab.cvf_smartblur.cvf_spp.cvf_stereo3d.cvf_super2xsai.cvf_tinterlace.cvf_uspp.cvsrc_mptestsrc.c

Should you, for whatever reason, prefer to use version 3 of the(L)GPL, then the configure parameter --enable-version3 willactivate this licensing option for you. Read the fileCOPYING.LGPLv3 or, if you have enabled GPL parts, COPYING.GPLv3 tolearn the exact legal terms that apply in this case.

There are a handful of files under other licensing terms, namely:

The files libavcodec/jfdctfst.c,libavcodec/jfdctint_template.c and libavcodec/jrevdct.c aretaken from libjpeg, see the top of the files for licensingdetails. Specifically note that you must credit the IJG in thedocumentation accompanying your program if you only distributeexecutables. You must also indicate any changes includingadditions and deletions to those three files in thedocumentation. tests/reference.pnm is under the expatlicense.

External libraries

61


FFmpeg can be combined with a number of external libraries, whichsometimes affect the licensing of binaries resulting from thecombination. Compatible libraries

The following libraries are under GPL:

frei0rlibcdiolibrubberbandlibvidstablibx264libx265libxavslibxvid

When combining them with FFmpeg, FFmpeg needs to be licensed asGPL as well by passing --enable-gpl to configure.

The OpenCORE and VisualOn libraries are under the Apache License2.0. That license is incompatible with the LGPL v2.1 and the GPLv2, but not with version 3 of those licenses. So to combine theselibraries with FFmpeg, the license version needs to be upgraded bypassing --enable-version3 to configure. Incompatible libraries

There are certain libraries you can combine with FFmpeg whoselicenses are not compatible with the GPL and/or the LGPL. If youwish to enable these libraries, even in circumstances that theirlicense may be incompatible, pass --enable-nonfree toconfigure. But note that if you enable any of these libraries theresulting binary will be under a complex license mix that is morerestrictive than the LGPL and that may result in additionalobligations. It is possible that these restrictions cause theresulting binary to be unredistributable.

The Fraunhofer FDK AAC and OpenSSL libraries are under licenseswhich are incompatible with the GPLv2 and v3. To the best of ourknowledge, they are compatible with the LGPL.

The NVENC library, while its header file is licensed under thecompatible MIT license, requires a proprietary binary blob at runtime, and is deemed to be incompatible with the GPL. We are notcertain if it is compatible with the LGPL, but we require--enable-nonfree even with LGPL configurations in case it is not.

Source as of 03/27/17: https://github.com/FFmpeg/FFmpeg/blob/master/LICENSE.md

4. Licensing terms of Poco

The Boost Software License 1.0

Permission is hereby granted, free of charge, to any person ororganization obtaining a copy of the software and accompanyingdocumentation covered by this license (the "Software") to use,reproduce, display, distribute, execute, and transmit theSoftware, and to prepare derivative works of the Software, and topermit third-parties to whom the Software is furnished to do so,all subject to the following:



The copyright notices in the Software and this entire statement,including the above license grant, this restriction and thefollowing disclaimer, must be included in all copies of theSoftware, in whole or in part, and all derivative works of theSoftware, unless such copies or derivative works are solely in theform of machine-executable object code generated by a sourcelanguage processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE ANDNON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OROTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISINGFROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OROTHER DEALINGS IN THE SOFTWARE.

Source as of 03/27/17: https://pocoproject.org/license.html

5. Licensing terms OpenSSL

LICENSE ISSUES==============

The OpenSSL toolkit stays under a double license, i.e. both theconditions of the OpenSSL License and the original SSLeaylicense apply to the toolkit. See below for the actual licensetexts.

OpenSSL License---------------

/* ====================================================================

* Copyright (c) 1998-2017 The OpenSSL Project. All rights reserved.

** Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

** 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

** 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

** 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

** 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* [email protected].

*

63


* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

** 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

** THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES

* LOSS OF USE, DATA, OR PROFITS OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

** This product includes cryptographic software written by Eric Young

* ([email protected]). This product includes software written by Tim

* Hudson ([email protected]).

**/

Original SSLeay License-----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])

* All rights reserved.

** This package is an SSL implementation written

* by Eric Young ([email protected]).

* The implementation was written so as to conform with Netscapes SSL.

** This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson ([email protected]).

** Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

** Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.



* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young ([email protected])"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson ([email protected])"

** THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES LOSS OF USE, DATA, OR PROFITS OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

** The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

Source as of 03/27/17: https://www.openssl.org/source/license.html

6. Licensing terms NVIDIA GRID SDK

NVIDIA GRID Software License Agreement

IMPORTANT NOTICE - PLEASE READ THIS NVIDIA GRID SOFTWARE LICENSEAGREEMENT CAREFULLY BEFORE USING THE SOFTWARE. USE OF THISSOFTWARE IS SUBJECT TO THIS AGREEMENT. YOU WILL BE ASKED TOREVIEW AND EITHER ACCEPT OR NOT ACCEPT THE TERMS OF THISAGREEMENT.

This GRID Software License Agreement (“Agreement”) is a legalagreement between you (“You” or “Licensee”) and NVIDIA Corporation("NVIDIA") which governs the use of NVIDIA GRID frame capture andhardware-accelerated video encoding API’s and associated samplesource code, header files and documentation provided or otherwisemade available to you ("Software"). By downloading, installing,or otherwise using the Software, you agree to be bound by theterms of this Agreement. If you do not agree to the terms of thisAgreement, do not download, install or otherwise use the Software.If You are an entity, You acknowledge that the individualaccepting the Agreement has appropriate authority to do so and tobind You.

The Software is protected by copyright laws and internationalcopyright treaties, as well as other intellectual property laws

65


and treaties. The Software is not sold, and instead is onlylicensed for use, strictly in accordance with this document. GRIDhardware products are protected by various patents, and are sold,but this Agreement does not cover that sale, since it may notnecessarily be sold with the Software. This Agreement sets forththe terms and conditions of the Software only. Any other use ofthe applicable driver software by Licensee will only be under theterms of a separate license agreement from NVIDIA.

SECTION 1 - LICENSE

1.1 License Grant. Provided that Licensee is in compliance withthe terms and conditions of this Agreement, NVIDIA grants toLicensee a nonexclusive, non-transferable, worldwide, revocable,limited, royalty-free, fully paid-up license to: (i) use,reproduce, modify and prepare derivative works of the Softwaresolely for Your own internal development and testing of theSoftware with Licensee’s product(s) and/or service(s) (“LicenseeProduct”) for use with GRID or Quadro 4000+ products only (ii)reproduce and use the Software internally only with GRID or Quadro4000+ products to provide the Licensee Product services and (iii)reproduce and distribute the Software (in object code only)bundled with Licensee Product for use only with GRID or Quadro4000+ products to Licensee’s customers and grant to Licensee’scustomers a sublicense to use the Software as compiled withLicensee Products for use only with GRID or Quadro 4000+ productsunder a written, legally enforceable agreement that has the effectof protecting the Software and the rights of NVIDIA under terms noless restrictive than this Agreement.

1.2 Limitations. Unless otherwise authorized in the Agreement,Licensee shall not otherwise assign, sublicense, lease, or in anyother way transfer or disclose Software to any third party.Licensee shall not reverse- compile, disassemble,reverse-engineer, or in any manner attempt to derive the sourcecode of the Software from the object code portions of theSoftware. Licensee acknowledges and agrees this Software islicensed for use only in conjunction with NVIDIA GRID and Quadro4000+ hardware products. Use of the Software in conjunction withother NVIDIA hardware products or non-NVIDIA hardware and/orsoftware products is not licensed hereunder.

1.3 No Other License. Except as expressly stated in thisAgreement, no license or right is granted to Licensee directly orby implication, inducement, estoppel or otherwise. NVIDIA shallhave the right to inspect or have an independent auditor inspectLicensee’s relevant records to verify Licensee’s compliance withthe terms and conditions of this Agreement.

SECTION 2 - CONFIDENTIALITY

2.1 Confidential Information. Licensee acknowledges and agreesthat the Software, documentation and other information (if suchother information is identified as confidential or should bereasonably recognized as confidential under the circumstances)provided to Licensee by NVIDIA hereunder (collectively,"Confidential Information") constitute the confidential and



proprietary information of NVIDIA and that Licensee's protectionthereof is an essential condition to Licensee's use and possessionof the Software. Licensee shall retain all ConfidentialInformation in strict confidence and not disclose it to any thirdparty or use it in any way except as permitted by this Agreement.Licensee shall exercise at least the same amount of diligence inpreserving the secrecy of the Confidential Information as it usesin preserving the secrecy of its own most valuable confidentialinformation, but in no event less than reasonable diligence.Notwithstanding the foregoing, all documents and other tangibleobjects containing or representing NVIDIA Confidential Informationand all copies thereof which are in the possession of Licenseeshall be and remain the property of NVIDIA and shall be promptlyreturned to NVIDIA upon termination of this Agreement.

2.2 Contractor. If Licensee wishes to have a third partyconsultant or subcontractor ("Contractor") perform work onLicensee’s behalf which involves access to or use of Software,Licensee shall obtain a written confidentiality agreement from theContractor which contains terms and obligations with respect toaccess to or use of Software no less restrictive than those setforth in this Agreement and excluding any distribution orsublicense rights, and use for any other purpose than permitted inthis Agreement. Otherwise, Licensee shall not disclose the termsor existence of this Agreement or use NVIDIA's name in anypublications, advertisements, or other announcements withoutNVIDIA's prior written consent. Unless otherwise provided in thisAgreement, Licensee does not have any rights to use any NVIDIAtrademarks or logos.

SECTION 3 - OWNERSHIP OF SOFTWARE AND INTELLECTUAL PROPERTY RIGHTS

3.1 Ownership. All rights, title and interest to all copies ofthe Software remain with NVIDIA, subsidiaries, licensors, or itssuppliers. The Software is copyrighted and protected by the lawsof the United States and other countries, and international treatyprovisions. Licensee may not remove any copyright notices from theSoftware. NVIDIA may make changes to the Software, or to itemsreferenced therein, at any time and without notice, but is notobligated to support or update the Software. Except as otherwiseexpressly provided, NVIDIA grants no express or implied rightunder any NVIDIA patents, copyrights, trademarks, or otherintellectual property rights.

3.2 Modifications. Licensee holds all rights, title and interestin the modifications to and derivative works of the Software thatLicensee creates, subject to NVIDIA’s underlying intellectualproperty rights to the Software provided, however that Licenseegrants NVIDIA an irrevocable, perpetual, nonexclusive, worldwide,royalty-free paid-up license to make, have made, use, have used,sell, license, distribute, sublicense or otherwise transferderivative works to the Software created by Licensee that addfunctionality or improvement to the Software.

3.3 Feedback. Licensee has no obligation to give NVIDIA anysuggestions, comments or other feedback (“Feedback”) relating tothe Software. However, NVIDIA may use and include any Feedbackthat Licensee voluntarily provides to improve the Software or

67


other related NVIDIA technologies. Accordingly, if Licenseeprovides Feedback, Licensee agrees NVIDIA and its licensees mayfreely use, reproduce, license, distribute, and otherwisecommercialize the Feedback in the Software or other relatedtechnologies without the payment of any royalties or fees.

3.4 Third Party Technology. Licensee acknowledges and agrees thatit is Licensee’s sole responsibility to obtain any, additional,third party licenses required to make, have made, use, have used,sell, import, and offer for sale Licensee Products that include orincorporate any third party technology and content relating toaudio and/or video encoders and decoders from, including but notlimited to, Microsoft, Thomson, Fraunhofer IIS, Sisvel S.p.A.,MPEG-LA, and Coding Technologies (“Third Party Technology”).Licensee acknowledges and agrees that NVIDIA has not granted toLicensee under this Agreement any necessary patent rights withrespect to the Third Party Technology. As such, Licensee’s use ofthe Third Party Technology may be subject to further restrictionsand terms and conditions. Licensee acknowledges and agrees thatLicensee is solely and exclusively responsible for obtaining anyand all authorizations and licenses required for the use,distribution and/or incorporation of the Third Party Technology.

3.5 Licensee Indemnity. Licensee shall, at its own expense fullyindemnify, hold harmless, defend and/or settle any claim, suit orproceeding that is asserted by a third party against NVIDIA andits officers, employees or agents, to the extent such claim, suitor proceeding arising from or related to Licensee’s failure tofully satisfy and/or comply with the third party licensingobligations related to the Third Party Technology (a “Claim”). Inthe event of a Claim, Licensee agrees to: (a) pay all damages orsettlement amounts, which shall not be finalized without the priorwritten consent of NVIDIA, (including other reasonable costsincurred by NVIDIA, including reasonable attorneys fees, inconnection with enforcing this paragraph) (b) reimburse NVIDIAfor any licensing fees and/or penalties incurred by NVIDIA inconnection with a Claim and (c) immediately procure/satisfy thethird party licensing obligations before using the Softwarepursuant to this Agreement.

SECTION 4 - NO WARRANTIES

THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIEDWARRANTY OF ANY KIND, INCLUDING WARRANTIES OF MERCHANTABILITY,NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. NVIDIA DOESNOT REPRESENT OR WARRANT THAT THE SOFTWARE WILL MEET LICENSEE’SREQUIREMENT OR THAT THE OPERATION OF THE SOFTWARE WILL BEUNINTERRUPTED OR ERROR FREE.

SECTION 5 - LIMITATION OF LIABILITY

IN NO EVENT SHALL NVIDIA, ITS SUBSIDIARIES, LICENSORS, ORSUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTALOR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUTLIMITATION, LOSS OF USE, LOSS OF DATA, BUSINESS INTERUPTION ORLOST PROFITS) IN CONNECTION WITH THIS AGREEMENT OR ARISING OUT OFTHE USE OF OR INABILITY TO USE THE SOFTWARE, EVEN IF NVIDIA HASBEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME



JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FORIMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THEABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHERLEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. IN NOEVENT SHALL WILL NVIDIA’S AGGREGATE LIABILITY ARISING OUT OF THISAGREEMENT EXCEED ONE HUNDRED UNITED STATES DOLLARS (USD$100). THELICENSEE IS SOLELY RESPONSIBLE FOR THE PROTECTION AND BACK-UP OFALL DATA AND SOFTWARE.

SECTION 6 - TERM AND TERMINATION

6.1 Term. This Agreement is effective until (i) automaticallyterminated if Licensee fails to comply with any of the terms andconditions of this Agreement or (ii) earlier terminated by NVIDIAin accordance with Section 6.2 (Termination).

6.2 Termination. In the event of actual or threatened breach ofthis Agreement by Licensee, NVIDIA may terminate this Agreementand the licenses granted hereunder, in addition to any otherremedies it may have. If Licensee commences or participates inany legal proceeding against NVIDIA, then NVIDIA may, in its solediscretion, suspend or terminate all license grants and any otherrights provided under this Agreement. Upon termination, Licenseeshall immediately cease using and immediately return all copies ofthe Software to NVIDIA, or destroy the Software and certify toNVIDIA in writing that such actions have been completed.

6.3 Survival. Those provisions in this Agreement, which by theirnature need to survive the termination or expiration of thisAgreement, shall survive termination or expiration of theAgreement, including but not limited to Sections 2, 3, 4, 5, 6.2,6.3, and 7.

SECTION 7 - MISCELLANEOUS

This Agreement shall be deemed to have been made in, and shall beconstrued pursuant to, the laws of the State of Delaware. Thestate and/or federal courts residing in Santa Clara County,California shall have exclusive jurisdiction over any dispute orclaim arising out of this Agreement. This Agreement is the final,complete and exclusive agreement between the parties relating tothe subject matter hereof, and supersedes all prior orcontemporaneous understandings and agreements relating to suchsubject matter, whether oral or written. If any provision of thisAgreement is inconsistent with, or cannot be fully enforced under,the law, such provision will be construed as limited to the extentnecessary to be consistent with and fully enforceable under thelaw. This Agreement, and Licensee’s rights and obligationsherein, may not be assigned, subcontracted, delegated, orotherwise transferred by Licensee without NVIDIA’s prior writtenconsent, and any attempted assignment, subcontract, delegation, ortransfer in violation of the foregoing will be null and void. Theterms of this Agreement shall be binding upon permittedassignees. The Parties acknowledge that they are independentcontractors and no other relationship, including partnership,joint venture, employment, franchise, master/servant orprincipal/agent, is intended by this Agreement. Neither Partyshall have the right to bind or obligate the other. Failure by

69


either Party to enforce any provision of this Agreement will notbe deemed a waiver of future enforcement of that or any otherprovision. Licensee shall not ship, transfer or export theSoftware into any country, or use the Software in any manner,prohibited by the United States Bureau of Industry and Security orany export laws, restrictions or regulations.

1NVIDIA GRID Software License Agreement v.f.nstr02

Source as of 03/27/17: GRID-SDK 2.2 installer from NVIDIA Corporation

7. Licensing terms of screen-capture-recorder as agreed upon with Roger Pack on 03/27/17

Copyright (c) 2017, Roger Pack ([email protected] )All rights reserved.

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:

1. Redistributions of source code must retain the above copyrightnotice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the abovecopyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORSBE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE,DATA, OR PROFITS OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OFTHE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

The views and conclusions contained in the software anddocumentation are those of the authors and should not beinterpreted as representing official policies, either expressed orimplied, of the FreeBSD Project.

Source as of 03/27/17, modified were copyright year and copyrightholder: https://en.wikipedia.org/wiki/BSD_licenses

8. Licensing terms AW_SAS64

Source as of 03/27/17:https://softltd.wordpress.com/simulate-ctrl-alt-del-in-windows-vista-7-and-server-2008/

AW_SASxx DLLs and other materials included in the FreeDistribution Package



END USER LICENSE AGREEMENT TERMS AND CONDITIONS

Please read the terms and conditions of this license agreement(the "License") before installing the computer software (the"Software"). By installing and using the Software you accept andagree to the terms of this License. This License constitutes theentire agreement concerning the Software between you and JosePascoa. If you do not agree with these terms and conditions,promptly uninstall or remove the Software.

The term "Software" includes, and these terms and conditions alsoapply to, any updates, modifications and upgrades to the Softwarethat you may receive after the initial release.

1. License Grant. This License permits you to use the suppliedaw_sasxx DLLs in any software you develop and distribute, sell orgive away according to your own criteria, except, Use of theSoftware with with any product that is distributed as Open Sourceor is distributed under the terms of GNU General Public License(GPL) or where the Source Code of the application is required tobe freely distributed is NOT ALLOWED. You agree that you will notmodify, adapt, rename or translate, or disassemble, decompile,reverse engineer or otherwise attempt to discover the source codeof any parts of the Software supplied in EXE or DLL form.

2. Jose Pascoa DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS ORIMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR PARTICULAR PURPOSE. Jose Pascoa does not warrant thatthe Software, its use, operation or your ability to use theSoftware will be uninterrupted or error-free or that all Softwareerrors will be corrected. Jose Pascoa does not warrant that theSoftware or service will meet your requirements.

3. Limitations of Liability. In no event shall Jose Pascoa beliable for any damages to you or any other party whether arisingout of contract or from tort including loss of data, profits orbusiness or other special, incidental, exemplary or consequentialdamages, even if Jose Pascoa has been advised of the possibilityof such loss or damages. Jose Pascoa’s cumulative liability shallnot exceed the license fee paid, which is none in this case, foruse of this Software and Documentation.

Jose Pascoa is a registered Software Developer, with address inLisbon, Portugal

71

CHAPTER

FIFTEEN

INDICES AND TABLES

• genindex

• search

73


74 Chapter 15. Indices and tables

INDEX

OopenSSL.client.verificationMode, 36openSSL.fips, 36openSSL.server.cacheSessions, 36openSSL.server.certificateFile, 35openSSL.server.cipherList, 35openSSL.server.extendedVerification, 36openSSL.server.invalidCertificateHandler.name, 36openSSL.server.loadDefaultCAFile, 35openSSL.server.privateKeyFile, 35openSSL.server.privateKeyPassphraseHandler.name, 35openSSL.server.privateKeyPassphraseHandler.options.password,

36openSSL.server.requireTLSv1_2, 36openSSL.server.verificationMode, 35

SServer.Auth.Enabled, 30Server.Auth.FailAttempts, 32Server.Auth.FailDelay, 32Server.Auth.MinPasswordLength, 31Server.Auth.OSAuthEnabled, 33Server.Auth.ScyldCloudAuth.Allow, 32Server.Auth.ScyldCloudAuth.Deny, 33Server.Auth.ScyldCloudAuth.URL, 32Server.Auth.Session.DefaultTimeout, 33Server.Auth.Session.OnSignIn, 33Server.Auth.ShadowPassword, 31Server.Auth.Username, 31Server.AutoLock, 29Server.BootLogFile, 29Server.LocalCursor, 29Server.LogFile, 29Server.LogFormat, 29Server.LogLevel, 29Server.Port, 30Server.Secure, 30Server.Video.MaxClientCount, 34Server.Video.MaxFrameRate, 34Server.Video.MinFrameRate, 34Server.Video.StartFrameRate, 34Server.VideoSource, 33

75

scyld cloud workstation documentation · contents 1 about scyld cloud workstation3 2 introduction 5...

Documents