4858bb5899
To quote MSDN documentation:
> The lpApplicationName parameter can be NULL, in which case the executable
> name must be the first white space–delimited string in lpCommandLine. If
> the executable or path name has a space in it, there is a risk that a
> different executable could be run because of the way the function parses
> spaces. The following example is dangerous because the function will
> attempt to run "Program.exe", if it exists, instead of "MyApp.exe".
>
> LPTSTR szCmdline[] = _tcsdup(TEXT("C:\\Program Files\\MyApp"));
> CreateProcessAsUser(hToken, NULL, szCmdline, /*...*/ );
>
> If a malicious user were to create an application called "Program.exe" on
> a system, any program that incorrectly calls CreateProcessAsUser using the
> Program Files directory will run this application instead of the intended
> application.
>
> To avoid this problem, do not pass NULL for lpApplicationName.
So instead, we pass the executable to lpApplicationName instead, which avoids
the issue. MSDN says:
> The lpCommandLine parameter can be NULL. In that case, the function uses
> the string pointed to by lpApplicationName as the command line.
This also avoids the strdup since lpApplicationName is LPCSTR unlike
lpCommandLine which is LPSTR.
|
||
|---|---|---|
| .. | ||
| cmake | ||
| include/interface | ||
| platform | ||
| src | ||
| .gitignore | ||
| CMakeLists.txt | ||
| README.md | ||
| toolchain-mingw64.cmake | ||
General Questions
What is this?
The Looking Glass Host application for the Guest Virtual Machine.
What platforms does this support?
Currently only Windows is supported however there is some initial support for Linux at this time.
How do I build it?
For Windows on Windows
- download and install msys2 x86_64 from http://www.msys2.org/ following the setup instructions provided
- execute
pacman -Fyand thenpacman -Sy git make mingw-w64-x86_64-gcc mingw-w64-x86_64-cmake - run "C:\msys64\mingw64.exe"
- checkout the project
git clone https://github.com/gnif/LookingGlass.git - configure the project and build it
mkdir LookingGlass/host/build
cd LookingGlass/host/build
cmake -G "MSYS Makefiles" ..
make
For Linux on Linux
mkdir build
cd build
cmake ..
make
For Windows cross compiling on Linux
mkdir build
cd build
cmake -DCMAKE_TOOLCHAIN_FILE=../toolchain-mingw64.cmake ..
make
Building the Windows installer
Install NSIS compiler
Build the host program, see above sections.
Build installer with makensis platform/Windows/installer.nsi
The resulting installer will be at
platform/Windows/looking-glass-host-setup.exe
Where is the log?
It is in your user's temp directory:
%TEMP%\looking-glass-host.txt
Or if running as a system service it will be located in:
C:\Windows\Temp\looking-glass-host.txt
You can find out where the file is by right clicking on the tray icon and selecting "Log File Location"
High priority capture using DXGI and Secure Desktop (UAC) capture support
By default Windows gives priority to the foreground application for any GPU
work which causes issues with capture if the foreground application is consuming
100% of the available GPU resources. The looking glass host application is able
to increase the kernel GPU thread to realtime priority which fixes this, but in
order to do so it must run as the SYSTEM user account. To do this, Looking
Glass needs to run as a service. This can be accomplished by either using the
NSIS installer which will do this for you, or you can use the following command
to Install the service manually:
looking-glass-host.exe InstallService
To remove the service use the following command:
looking-glass-host.exe UninstallService
This will also enable the host application to capture the secure desktop which includes things like the lock screen and UAC prompts.
Why does this version require Administrator privileges
This is intentional for several reasons.
- NvFBC requires a system wide hook to correctly obtain the cursor position as NVIDIA decided to not provide this as part of the cursor updates.
- NvFBC requires administrator level access to enable the interface in the first place. (WIP)
- DXGI performance can be improved if we have this. (WIP)
NvFBC (NVIDIA Frame Buffer Capture)
Why isn't there a build with NvFBC support available.
Because NVIDIA have decided to put restrictions on the NvFBC API that simply make it incompatible with the GPL/2 licence. Providing a pre-built binary with NvFBC support would violate the EULA I have agreed to in order to access the NVidia Capture SDK.
Either I miss-read the License Agreement or it has been updated, it is now viable to produce a "derived work" from the capture SDK.
1.1 License Grant. Subject to the terms of this Agreement, NVIDIA hereby grants you a nonexclusive, non-transferable, worldwide, revocable, limited, royalty-free, fully paid-up license during the term of this Agreement to: (i) install, use and reproduce the Licensed Software delivered by NVIDIA plus make modifications and create derivative works of the source code and header files delivered by NVIDIA, provided that the software is executed only in hardware products as specified by NVIDIA in the accompanying documentation (such as release notes) as supported, to develop, test and service your products (each, a “Customer Product”) that are interoperable with supported hardware products. If the NVIDIA documentation is silent, the supported hardware consists of certain NVIDIA GPUs; and
To be safe we are still not including the NVIDIA headers in the repository, but I am now providing pre-built binaries with NvFBC support included.
See: https://looking-glass.hostfission.com/downloads
Why can't I compile NvFBC support into the host
You must download and install the NVidia Capture SDK. Please note that by doing so you will be agreeing to NVIDIA's SDK License agreement.
-Geoff