diff options
| author | Kenneth Hsu <kennethhsu@gmail.com> | 2017-10-16 06:55:35 +0300 |
|---|---|---|
| committer | Kenneth Hsu <kennethhsu@gmail.com> | 2017-10-16 08:00:23 +0300 |
| commit | 3d51e9153b0a916245984953d0c5001948951759 (patch) | |
| tree | 96fa2a175842201a9914e23f50c3ad0c03835249 /thirdparty | |
| parent | 202a6641e568abe53d3d5a13b9d9ea4d8cfd0d89 (diff) | |
Avoid signing assemblies.
Using strong-named assemblies can cause difficulties with the GNU LGPL
license, which allows for one to recombine or relink their application
with modified versions of the code. While one solution is to share the
private key so that people can sign the assemblies themselves, this
would break the trust that is expected from signed assemblies. For now,
the easiest fix is to simply not sign the assemblies. Note that by
doing so, we prevent the code from being referenced from other signed
assemblies.
This also fixes an issue introduced in revision ba94d36a80 ("Added
auto-update for WindowsService and Service."), where the WindowsService
project (signed) referenced the AutoUpdater project (not signed).
We also removed instances of <SignAssembly>false</SignAssembly> to be
consistent with newly created .csproj files that do not contain the
SignAssembly element.
This was motivated by the discussion in issue #2814.
Diffstat (limited to 'thirdparty')
| -rw-r--r-- | thirdparty/UnixSupport/UnixSupport.csproj | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/thirdparty/UnixSupport/UnixSupport.csproj b/thirdparty/UnixSupport/UnixSupport.csproj index 04faad067..5400fb0a8 100644 --- a/thirdparty/UnixSupport/UnixSupport.csproj +++ b/thirdparty/UnixSupport/UnixSupport.csproj @@ -10,7 +10,6 @@ <RootNamespace>UnixSupport</RootNamespace> <AssemblyName>UnixSupport</AssemblyName> <TargetFrameworkVersion>v4.5</TargetFrameworkVersion> - <SignAssembly>true</SignAssembly> <AssemblyOriginatorKeyFile>Duplicati.snk</AssemblyOriginatorKeyFile> <ReleaseVersion>1.0</ReleaseVersion> <SynchReleaseVersion>false</SynchReleaseVersion> |