Safe Exam Browser, Version 3.x

Refactored version of Safe Exam Browser for Windows with Chromium as integrated browser engine.

Requirements

SEB 3.x requires the prerequisites listed below in order to work correctly. These are automatically installed with the setup bundle and need only be manually installed when using the MSI packages.

.NET Framework 4.7.2 Runtime: https://dotnet.microsoft.com/download/dotnet-framework/net472
Visual C++ 2015 Redistributable: https://www.microsoft.com/en-us/download/details.aspx?id=53840

Project Status

DISCLAIMER
The builds linked below are for testing purposes only. They may be unstable and should thus never be used in a production environment! Always use the latest, official release version of SEB.

Aspect	Status	Details
Release Build		https://sebdev-let.ethz.ch/project/appveyor/seb-win-refactoring
Test Build		https://ci.appveyor.com/project/dbuechel/seb-win-refactoring
Test Run		https://ci.appveyor.com/project/dbuechel/seb-win-refactoring
Code Coverage		https://codecov.io/gh/SafeExamBrowser/seb-win-refactoring
Issue Status		https://github.com/SafeExamBrowser/seb-win-refactoring/issues
Downloads		https://github.com/SafeExamBrowser/seb-win-refactoring/releases
Development		n/a
Repository Size		n/a

Updated

Build Instruction

License file

Please find End User License Agreement file under "Setup\Resources\License.rtf"

Prerequisites

Make sure that .NET Framework and Visual C++ Redistributable (see links above) installed
You will need Visual Studio 2019 (not tested on 2017 version)
Install the latest stable version of WIX Toolset https://wixtoolset.org/releases/v3.11.2/stable
Install WiX Toolset Visual Studio 2019 Extension https://marketplace.visualstudio.com/items?itemName=WixToolset.WixToolsetVisualStudio2019Extension
Install Windows 10 SDK (requried to sign assemblies) https://go.microsoft.com/fwlink/?LinkID=698771
Inside a folder where to you installed Windows SDK search for "signtool.exe". There should be at least 2 locations, something like:

x86 -> c:\Program Files (x86)\Windows Kits\10\bin\x86\
x64 -> c:\Program Files (x86)\Windows Kits\10\bin\x64\

Next, depends on your system architecture (I assume you have 64bit windows installed), copy to clipboard a path to "signtool.exe"
We need to make sure that path is accessible from Windows command line. Go to Environment System settings:

Press WIN + PAUSE buttons on a keyboard
Click the "Advanced System Settings" link on the left. In the next dialog, you will see the Environment Variables... button in the bottom of the Advanced tab.
Under the lower table (System variables) click "Create" and give a name "Win10SDK", and paste a path you have copied at step 7.
Scroll a table and search for "PATH", double click on it.
Create a new record: "%Win10SDK%" or "%Win10SDK%" (depends on trailing backslash symbol in the path you've added in previous step)
Click OK and close all system windows (Win 10 doesn't require a reboot here, not sure about other versions)

Cloning Git sources

Clone git repository git clone --recursive https://github.com/grepp/seb-win-refactoring.git
Fetch updates git fetch
(Skipped if you did it before). git submodule init --"Chrominimum"
Pull SEB sources by using git pull and chrominimum sources as a Git submodule git submodule update

** Now you can open a solution in your Visual Studio and build a solution ** ** Do not forget to select RELEASE configuration for solution otherwise you will get a assemblies with debug information included ** ** Also, for successful build the Bundlesetup project you should build solution in the following configurations 'Release x86' and 'Release x64' **

Certificate for development

Please install OpenSSL. Windows version could be found here: http://slproweb.com/products/Win32OpenSSL.html
Run OpenSSL Command-Line prompt
Switch to 'Cerfiticate' folder inside a solution directory
execute openssl openssl.exe
paste following command req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout monito_private.key -out monito_certificate.crt
openssl pkcs12 -export -out monito.pfx -inkey monito_private.key -in monito_certificate.crt
When password asked, for development purposes please use '123' as a password
Copy monito.pfx file into "Monito.Version" project with replacememnt an existing certificate PFX container
PROFIT!! now we have a pfx container with certificate and a private key

For production version it must been changed to a special valid certificate So, here what we should do to reconfigure it:

Right-click on Setup/SetupBundle project -> Properties -> Build events
Check "Pre-Build" events. For each line which starting from "signtool" please check parameter options and modify it for a proper certificate
Also please check files "Setup.wixproj" and "SetupBundle.wixproj" in editor (like notepad) for a correct signtool parameters (like filename and passowrd).

Versioning

Since version number is a part of security subsystem - hash generation, please note that each time you change a version number, and old data like browserExamKey won't be valid anymore. To change (increment) a version number please modify a version tag inside "Monito.Version.csproj" file or you may use Visual Studio UI (Right-click -> Properties -> Package)

grepp / seb-win-refactoring