diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 02f05d5..3c88a79 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -11,6 +11,30 @@ jobs:
compile:
name: ${{matrix.buildname}}
runs-on: ${{matrix.os}}
+ # SignPath Foundation requires a manual approval for every signing request,
+ # so only builds that will be released may ask for one, and whether a
+ # development build releases is only known once check-new-games has run.
+ needs: check-new-games
+ # actions: read is SignPath's - its action hands the job's GITHUB_TOKEN to
+ # SignPath, which uses it to read job details and download the artifact
+ permissions:
+ actions: read
+ contents: read
+ env:
+ # Deliberately not conditional on the SignPath secrets being set: a build
+ # that should be signed fails if they are missing, rather than quietly
+ # publishing unsigned launchers.
+ # Signed: tags, and development builds that check-new-games will release.
+ # A manual workflow_dispatch is signed on any branch too, so a SignPath
+ # change can be tried out before it is merged - it still needs approving.
+ SIGNPATH_SIGNING_ENABLED: ${{ github.actor != 'dependabot[bot]' && github.event_name != 'pull_request' && github.repository == 'Mudlet/bootstrap' && (startsWith(github.ref, 'refs/tags/') || needs.check-new-games.outputs.new-games == 'true' || github.event_name == 'workflow_dispatch') }}
+ # test-signing is left for verifying a SignPath configuration change by
+ # hand; its self-signed certificate isn't trusted, so the verify step
+ # fails such a build before anything is published.
+ SIGNPATH_POLICY_SLUG: 'release-signing'
+ # The version the release will carry, written into each Windows launcher
+ # and enforced by the artifact configuration's product-version.
+ RELEASE_TAG: ${{ startsWith(github.ref, 'refs/tags/') && github.ref_name || needs.check-new-games.outputs.tag }}
strategy:
fail-fast: false
matrix:
@@ -91,6 +115,21 @@ jobs:
chmod +x ./CI/build-qt-statemachine.sh
./CI/build-qt-statemachine.sh
+ # Builds that aren't released get 0.0.0. The launcher's version resource
+ # takes four numbers, so a tag must be vX.Y.Z.
+ - name: (Windows) Set launcher version
+ if: runner.os == 'Windows'
+ shell: bash
+ run: |
+ version="${RELEASE_TAG#v}"
+ version="${version:-0.0.0}"
+ if ! [[ "${version}" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
+ echo "::error::Release tag ${RELEASE_TAG} is not of the form vX.Y.Z."
+ exit 1
+ fi
+ echo "Launcher version: ${version}"
+ echo "LAUNCHER_VERSION=${version}" >> "$GITHUB_ENV"
+
- name: (Windows) Setup MSYS2
if: runner.os == 'Windows'
uses: msys2/setup-msys2@v2
@@ -166,25 +205,97 @@ jobs:
shell: msys2 {0}
run: $GITHUB_WORKSPACE/CI/package-win.sh
- - name: (Windows) Login to Azure
- uses: azure/login@v2
- if: runner.os == 'Windows' && github.actor != 'dependabot[bot]' && github.event_name != 'pull_request' && github.repository == 'Mudlet/bootstrap'
- with:
- creds: ${{ secrets.AZURE_CREDENTIALS }}
+ - name: (Windows) Prepare launchers for signing
+ if: runner.os == 'Windows'
+ shell: msys2 {0}
+ run: $GITHUB_WORKSPACE/CI/prepare-signing-win.sh
- - name: Get Azure access token for code signing
+ - name: (Windows) Check SignPath secrets
+ if: runner.os == 'Windows' && env.SIGNPATH_SIGNING_ENABLED == 'true'
+ shell: bash
+ env:
+ SIGNPATH_API_TOKEN: ${{secrets.SIGNPATH_API_TOKEN}}
+ SIGNPATH_ORGANIZATION_ID: ${{secrets.SIGNPATH_ORGANIZATION_ID}}
+ run: |
+ if [ -z "${SIGNPATH_API_TOKEN}" ] || [ -z "${SIGNPATH_ORGANIZATION_ID}" ]; then
+ echo "::error::This build must be signed, but SIGNPATH_API_TOKEN or SIGNPATH_ORGANIZATION_ID is not set."
+ exit 1
+ fi
+
+ # Every game's launcher goes up in one artifact, and the artifact
+ # configuration's MudletInstaller-*.exe wildcard covers the lot, so a
+ # GameList of any length still costs a single signing request.
+ - name: (Windows) Upload unsigned launchers for signing
+ id: upload-unsigned-launchers
+ if: runner.os == 'Windows' && env.SIGNPATH_SIGNING_ENABLED == 'true'
+ uses: actions/upload-artifact@v6
+ with:
+ name: unsigned-launchers
+ path: ${{env.SIGNING_DIR}}
+ retention-days: 1
+ # so re-running a job whose signing request failed can upload again
+ overwrite: true
+
+ # Extracts the signed launchers into signed-launchers/, which
+ # prepare-signing-win.sh made sure does not exist yet. The action extracts
+ # over whatever is already in its output directory, so it must not be the
+ # staging directory: the unsigned copies there would pass deploy-win.sh's
+ # check that a signed copy exists.
+ - name: (Windows) Sign launchers with SignPath
+ id: sign-launchers
+ if: steps.upload-unsigned-launchers.outcome == 'success'
+ uses: signpath/github-action-submit-signing-request@v2
+ with:
+ api-token: ${{secrets.SIGNPATH_API_TOKEN}}
+ organization-id: ${{secrets.SIGNPATH_ORGANIZATION_ID}}
+ project-slug: 'bootstrap'
+ signing-policy-slug: ${{env.SIGNPATH_POLICY_SLUG}}
+ artifact-configuration-slug: 'launchers'
+ github-artifact-id: ${{steps.upload-unsigned-launchers.outputs.artifact-id}}
+ parameters: |
+ version: ${{ toJSON(format('{0}.0', env.LAUNCHER_VERSION)) }}
+ wait-for-completion: true
+ output-artifact-directory: ${{github.workspace}}/signed-launchers
+ # Leaves time for an approver to respond, within GitHub's 6 hour job limit
+ wait-for-completion-timeout-in-seconds: 14400
+
+ # Don't take the signing request's success on trust: check that every
+ # launcher that went in came back with a valid signature before anything is
+ # published.
+ - name: (Windows) Verify launcher signatures
+ if: steps.sign-launchers.outcome == 'success'
shell: pwsh
- if: runner.os == 'Windows' && github.actor != 'dependabot[bot]' && github.event_name != 'pull_request' && github.repository == 'Mudlet/bootstrap'
run: |
- $token = (az account get-access-token --resource https://codesigning.azure.net | ConvertFrom-Json).accessToken
- "::add-mask::$token"
- "AZURE_ACCESS_TOKEN=$token" | Add-Content -Path $env:GITHUB_ENV
+ $staged = Get-ChildItem -Path "$env:GITHUB_WORKSPACE\signing-launchers" -Filter 'MudletInstaller-*.exe'
+ if ($staged.Count -eq 0) {
+ Write-Output "::error::No launchers were staged for signing."
+ exit 1
+ }
+ $failed = 0
+ foreach ($launcher in $staged) {
+ $signedPath = Join-Path "$env:GITHUB_WORKSPACE\signed-launchers" $launcher.Name
+ if (-not (Test-Path -LiteralPath $signedPath)) {
+ Write-Output "::error::SignPath returned no $($launcher.Name)."
+ $failed++
+ continue
+ }
+ $signature = Get-AuthenticodeSignature -LiteralPath $signedPath
+ if ($signature.Status -ne 'Valid') {
+ Write-Output "::error::$($launcher.Name) signature status is $($signature.Status): $($signature.StatusMessage)"
+ $failed++
+ continue
+ }
+ Write-Output "$($launcher.Name): signed by $($signature.SignerCertificate.Subject)"
+ }
+ if ($failed -gt 0) {
+ Write-Output "::error::$failed of $($staged.Count) launchers are not validly signed."
+ exit 1
+ }
+ Write-Output "All $($staged.Count) launchers are validly signed."
- name: (Windows) Deploy
if: runner.os == 'Windows'
shell: msys2 {0}
- env:
- AZURE_ACCESS_TOKEN: ${{ env.AZURE_ACCESS_TOKEN }}
run: $GITHUB_WORKSPACE/CI/deploy-win.sh
- name: (macOS) Prep for Artifact Upload
@@ -276,9 +387,12 @@ jobs:
- name: Checkout Source (for GameList.txt)
uses: actions/checkout@v6
+ # Only the packaged launchers: the Windows job's unsigned-launchers
+ # artifact must never be picked up and published.
- name: Download all platform artifacts
uses: actions/download-artifact@v7
with:
+ pattern: MudletInstaller-*
path: ./platform-artifacts
- name: Organize launchers by game
diff --git a/.signpath/artifact-configuration-launchers.xml b/.signpath/artifact-configuration-launchers.xml
new file mode 100644
index 0000000..3b1e2cb
--- /dev/null
+++ b/.signpath/artifact-configuration-launchers.xml
@@ -0,0 +1,23 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/.signpath/policies/bootstrap/release-signing.yml b/.signpath/policies/bootstrap/release-signing.yml
new file mode 100644
index 0000000..9ddbd6b
--- /dev/null
+++ b/.signpath/policies/bootstrap/release-signing.yml
@@ -0,0 +1,12 @@
+# SignPath Policy for Release Signing
+# This policy is used with the production certificate for official releases
+#
+# Policy enforcements:
+# - Artifacts must be built by GitHub Actions workflows
+# - Build must originate from the Mudlet/bootstrap repository
+# - Only GitHub-hosted runners are allowed (for open source verification)
+
+github-policies:
+ runners:
+ allowed_groups:
+ - 'GitHub Actions'
diff --git a/.signpath/policies/bootstrap/test-signing.yml b/.signpath/policies/bootstrap/test-signing.yml
new file mode 100644
index 0000000..764ab9c
--- /dev/null
+++ b/.signpath/policies/bootstrap/test-signing.yml
@@ -0,0 +1,12 @@
+# SignPath Policy for Test Signing
+# This policy is used with the self-signed test certificate during setup verification
+#
+# Policy enforcements:
+# - Artifacts must be built by GitHub Actions workflows
+# - Build must originate from the Mudlet/bootstrap repository
+# - Only GitHub-hosted runners are allowed (for open source verification)
+
+github-policies:
+ runners:
+ allowed_groups:
+ - 'GitHub Actions'
diff --git a/CI/build-win.sh b/CI/build-win.sh
index fcaadf0..aec6b8d 100644
--- a/CI/build-win.sh
+++ b/CI/build-win.sh
@@ -194,6 +194,7 @@ EOF
-DCMAKE_PREFIX_PATH="$(cygpath -w $Qt6_PREFIX)" \
-DQt6LinguistTools_DIR="${QT_LINGUIST_DIR}" \
-DCMAKE_IGNORE_PATH="${MSYSTEM_PREFIX}/lib/cmake/Qt6" \
+ -DLAUNCHER_VERSION="${LAUNCHER_VERSION:-0.0.0}" \
..
if [ $? -ne 0 ]; then
diff --git a/CI/deploy-win.sh b/CI/deploy-win.sh
index 336f556..5a5f2d6 100644
--- a/CI/deploy-win.sh
+++ b/CI/deploy-win.sh
@@ -19,7 +19,13 @@
# 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. #
###########################################################################
-# Version: 2.0.0 Rework to build on an MSYS2 MINGW64 Github workflow
+# Version: 3.0.0 Windows signing moved from Azure Trusted Signing to
+# SignPath. jsign ran here and signed each launcher in place;
+# SignPath instead signs an artifact the workflow uploads
+# between prepare-signing-win.sh and this script, so all
+# that is left to do here is pick the signed launchers back
+# up before publishing them.
+# 2.0.0 Rework to build on an MSYS2 MINGW64 Github workflow
# Exit codes:
# 0 - Everything is fine. 8-)
@@ -28,6 +34,8 @@
# 3 - Not used
# 4 - nuget error
# 5 - squirrel error
+# 7 - Signing was enabled but a launcher's signed copy is missing or could
+# not be put in place to publish
if [ "${MSYSTEM}" != "CLANG64" ]; then
echo "Please run this script from a CLANG64 type bash terminal."
@@ -58,17 +66,15 @@ else
echo "=== Building for regular build ==="
fi
-# Set up Java for code signing if Azure token is available
-if [ -n "${AZURE_ACCESS_TOKEN}" ]; then
- echo "=== Setting up Java 21 for signing ==="
- # Java is installed by default, we just need to select which version to use:
- JAVA_HOME="$(cygpath -au "${JAVA_HOME_21_X64}")"
- export JAVA_HOME
- export PATH="${JAVA_HOME}/bin:${PATH}"
- JAVA_JAR_WINPATHFILE="$(cygpath -aw "${GITHUB_WORKSPACE}/CI/jsign-7.0-SNAPSHOT.jar")"
- echo "Java setup complete for code signing"
+# Where the workflow's SignPath steps ran, the signed launchers are here.
+# prepare-signing-win.sh removed this directory before signing, so anything in
+# it came back from SignPath.
+signedDir="${GITHUB_WORKSPACE_UNIX_PATH}/signed-launchers"
+
+if [ "${SIGNPATH_SIGNING_ENABLED}" = "true" ]; then
+ echo "=== Publishing SignPath-signed launchers ==="
else
- echo "=== Code signing skipped - no Azure token provided ==="
+ echo "=== Code signing skipped - publishing unsigned launchers ==="
fi
while IFS= read -r line || [[ -n "$line" ]]; do
@@ -79,22 +85,21 @@ while IFS= read -r line || [[ -n "$line" ]]; do
cd "$PACKAGE_DIR" || exit 1
- # Remove specific file types from the directory
- rm ./*.cpp ./*.o
-
- mv "$PACKAGE_DIR/MudletInstaller.exe" "MudletInstaller-${gameName}.exe"
-
- # Sign the executable if Azure token is available
- if [ -n "${AZURE_ACCESS_TOKEN}" ]; then
- echo "=== Signing MudletInstaller-${gameName}.exe ==="
- EXECUTABLE_WINPATH="$(cygpath -aw "${PACKAGE_DIR}/MudletInstaller-${gameName}.exe")"
- java.exe -jar "${JAVA_JAR_WINPATHFILE}" \
- --storetype TRUSTEDSIGNING \
- --keystore eus.codesigning.azure.net \
- --storepass "${AZURE_ACCESS_TOKEN}" \
- --alias Mudlet/Mudlet \
- "${EXECUTABLE_WINPATH}"
- echo "Signing completed for MudletInstaller-${gameName}.exe"
+ # The workflow has already checked every signature; this guards against
+ # publishing the unsigned launcher left in PACKAGE_DIR if the signed copy is
+ # missing or can't be put in its place.
+ if [ "${SIGNPATH_SIGNING_ENABLED}" = "true" ]; then
+ signedLauncher="${signedDir}/MudletInstaller-${gameName}.exe"
+ if [ ! -f "${signedLauncher}" ]; then
+ echo "ERROR: signing was enabled but there is no signed"
+ echo "MudletInstaller-${gameName}.exe in ${signedDir}."
+ exit 7
+ fi
+ if ! cp "${signedLauncher}" "${PACKAGE_DIR}/MudletInstaller-${gameName}.exe"; then
+ echo "ERROR: could not replace the unsigned MudletInstaller-${gameName}.exe"
+ echo "with its signed copy."
+ exit 7
+ fi
fi
# Move packaged files to the upload directory
diff --git a/CI/jsign-7.0-SNAPSHOT.jar b/CI/jsign-7.0-SNAPSHOT.jar
deleted file mode 100644
index 8fdfb70..0000000
Binary files a/CI/jsign-7.0-SNAPSHOT.jar and /dev/null differ
diff --git a/CI/organize-launchers.sh b/CI/organize-launchers.sh
index 54ff30a..678a30c 100644
--- a/CI/organize-launchers.sh
+++ b/CI/organize-launchers.sh
@@ -30,7 +30,7 @@ if [ ! "$(ls -A organized-releases 2>/dev/null)" ]; then
# Look for game launcher files
case "$platform_name" in
- *MINGW64*|*Windows*)
+ *CLANG64*|*MINGW64*|*Windows*)
echo " Looking for Windows executables..."
find "$platform_dir" -name "*.exe" -type f | while read launcher; do
if [ -f "$launcher" ]; then
diff --git a/CI/prepare-signing-win.sh b/CI/prepare-signing-win.sh
new file mode 100644
index 0000000..5e15dea
--- /dev/null
+++ b/CI/prepare-signing-win.sh
@@ -0,0 +1,97 @@
+#!/bin/bash
+###########################################################################
+# Copyright (C) 2024-2024 by John McKisson - john.mckisson@gmail.com #
+# Copyright (C) 2023-2024 by Stephen Lyons - slysven@virginmedia.com #
+# #
+# This program is free software; you can redistribute it and/or modify #
+# it under the terms of the GNU General Public License as published by #
+# the Free Software Foundation; either version 2 of the License, or #
+# (at your option) any later version. #
+# #
+# This program is distributed in the hope that it will be useful, #
+# but WITHOUT ANY WARRANTY; without even the implied warranty of #
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
+# GNU General Public License for more details. #
+# #
+# You should have received a copy of the GNU General Public License #
+# along with this program; if not, write to the #
+# Free Software Foundation, Inc., #
+# 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. #
+###########################################################################
+
+# Version: 1.0.0 Split out of deploy-win.sh when Windows signing moved from
+# Azure Trusted Signing to SignPath. jsign signed each
+# launcher in place; SignPath signs an uploaded artifact, so
+# the launchers have to be named and gathered up first.
+
+# Gives each launcher its release name and gathers them all into one directory
+# for the workflow to hand to SignPath. One artifact for the whole GameList
+# means one signing request rather than one per game.
+
+# To be used AFTER package-win.sh has been run; deploy-win.sh then picks the
+# signed launchers back up.
+
+# Exit codes:
+# 0 - Everything is fine. 8-)
+# 1 - Failure to change to a directory
+# 2 - Unsupported MSYS2/MINGW shell type
+# 6 - No MudletInstaller.exe file found to work with
+# 7 - A launcher could not be renamed or staged for signing
+
+if [ "${MSYSTEM}" != "CLANG64" ]; then
+ echo "Please run this script from a CLANG64 type bash terminal."
+ echo "Current MSYSTEM is: ${MSYSTEM}"
+ exit 2
+fi
+
+cd "$GITHUB_WORKSPACE" || exit 1
+
+GITHUB_WORKSPACE_UNIX_PATH=$(echo "${GITHUB_WORKSPACE}" | sed 's|\\|/|g' | sed 's|D:|/d|g')
+
+# Both rebuilt from scratch. signing-launchers/ is what gets uploaded, so a
+# stale file in it would be signed and shipped. signed-launchers/ is where
+# SignPath extracts the result over whatever is already there, so a stale file
+# in it would be published as though it had just been signed.
+signingDir="${GITHUB_WORKSPACE_UNIX_PATH}/signing-launchers"
+signedDir="${GITHUB_WORKSPACE_UNIX_PATH}/signed-launchers"
+rm -rf "${signingDir}" "${signedDir}"
+mkdir -p "${signingDir}"
+
+while IFS= read -r line || [[ -n "$line" ]]; do
+
+ gameName=$(echo "$line" | tr -cd '[:alnum:]_-')
+
+ PACKAGE_DIR="${GITHUB_WORKSPACE_UNIX_PATH}/package-${gameName}"
+
+ cd "$PACKAGE_DIR" || exit 1
+
+ # Remove specific file types from the directory
+ rm -f ./*.cpp ./*.o
+
+ if [ ! -f "${PACKAGE_DIR}/MudletInstaller.exe" ]; then
+ echo "ERROR: no MudletInstaller executable found in ${PACKAGE_DIR} - did"
+ echo "package-win.sh complete successfully?"
+ exit 6
+ fi
+
+ # Signing only covers what is staged here, so a launcher missing from it
+ # would go unnoticed until deploy-win.sh.
+ if ! mv "${PACKAGE_DIR}/MudletInstaller.exe" "MudletInstaller-${gameName}.exe" ||
+ ! cp "${PACKAGE_DIR}/MudletInstaller-${gameName}.exe" "${signingDir}/"; then
+ echo "ERROR: could not stage MudletInstaller-${gameName}.exe for signing."
+ exit 7
+ fi
+
+ cd "$GITHUB_WORKSPACE" || exit 1
+
+done < "${GITHUB_WORKSPACE}/GameList.txt"
+
+echo "=== Launchers staged for signing ==="
+ls -l "${signingDir}"
+echo "Total staged: $(du -sh "${signingDir}" | cut -f1)"
+
+# actions/upload-artifact runs in Node.js outside MSYS2 and misinterprets Unix
+# paths like /d/a/... as D:\d\a\..., so hand it a native Windows path:
+echo "SIGNING_DIR=$(cygpath -aw "${signingDir}")" >> "$GITHUB_ENV"
+
+exit 0
diff --git a/CMakeLists.txt b/CMakeLists.txt
index c9061f8..5ea0302 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -81,6 +81,18 @@ target_link_libraries(MudletInstaller PRIVATE
if(WIN32)
+ # SignPath's artifact configuration requires every launcher to carry a
+ # product name and version, so CI passes in the release's version.
+ set(LAUNCHER_VERSION "0.0.0" CACHE STRING "Launcher version as X.Y.Z")
+ if(NOT LAUNCHER_VERSION MATCHES "^([0-9]+)\\.([0-9]+)\\.([0-9]+)$")
+ message(FATAL_ERROR "LAUNCHER_VERSION must be X.Y.Z, got '${LAUNCHER_VERSION}'")
+ endif()
+ set(LAUNCHER_VERSION_MAJOR ${CMAKE_MATCH_1})
+ set(LAUNCHER_VERSION_MINOR ${CMAKE_MATCH_2})
+ set(LAUNCHER_VERSION_PATCH ${CMAKE_MATCH_3})
+ configure_file(MudletInstaller.rc.in "${CMAKE_CURRENT_BINARY_DIR}/MudletInstaller.rc" @ONLY)
+ target_sources(MudletInstaller PRIVATE "${CMAKE_CURRENT_BINARY_DIR}/MudletInstaller.rc")
+
if(DEFINED ENV{MINGW_PREFIX})
# MINGW_PREFIX should be set by GHA
set(MSYS2_LIB_PATH "$ENV{MINGW_PREFIX}/lib")
diff --git a/COPYING b/COPYING
new file mode 100644
index 0000000..f288702
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see .
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ Copyright (C)
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+.
diff --git a/MudletInstaller.rc.in b/MudletInstaller.rc.in
new file mode 100644
index 0000000..05ece7d
--- /dev/null
+++ b/MudletInstaller.rc.in
@@ -0,0 +1,29 @@
+#include
+
+VS_VERSION_INFO VERSIONINFO
+FILEVERSION @LAUNCHER_VERSION_MAJOR@,@LAUNCHER_VERSION_MINOR@,@LAUNCHER_VERSION_PATCH@,0
+PRODUCTVERSION @LAUNCHER_VERSION_MAJOR@,@LAUNCHER_VERSION_MINOR@,@LAUNCHER_VERSION_PATCH@,0
+FILEFLAGSMASK VS_FFI_FILEFLAGSMASK
+FILEFLAGS 0
+FILEOS VOS_NT_WINDOWS32
+FILETYPE VFT_APP
+FILESUBTYPE VFT2_UNKNOWN
+BEGIN
+ BLOCK "StringFileInfo"
+ BEGIN
+ BLOCK "040904B0"
+ BEGIN
+ VALUE "CompanyName", "Mudlet"
+ VALUE "FileDescription", "MudletInstaller"
+ VALUE "FileVersion", "@LAUNCHER_VERSION@.0"
+ VALUE "InternalName", "MudletInstaller"
+ VALUE "OriginalFilename", "MudletInstaller.exe"
+ VALUE "ProductName", "MudletInstaller"
+ VALUE "ProductVersion", "@LAUNCHER_VERSION@.0"
+ END
+ END
+ BLOCK "VarFileInfo"
+ BEGIN
+ VALUE "Translation", 0x409, 1200
+ END
+END
diff --git a/README.md b/README.md
index 5686acb..aa72748 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,10 @@ cmake -B build
cmake --build build
```
+## Acknowledgements
+
+Windows code signing provided by [SignPath.io](https://about.signpath.io), certificate by [SignPath Foundation](https://signpath.org).
+
## License
-See the [Mudlet repository](https://github.com/Mudlet/Mudlet) for license information.
+MudletInstaller is licensed under the GNU General Public License, version 2 or (at your option) any later version, the same as [Mudlet](https://github.com/Mudlet/Mudlet). See [COPYING](COPYING).