This tool includes 3 statically-linked libraries:
     - OpenSSL cryptographic library
     - Vmime "C++ class library for working with RFC-822 and MIME messages"
       (basically email stuff)
     - Iniparser library for parsing of .ini configuration files

In addition, the binary contains statically-linked bits of code,
that GCC (Mingw-w64) adds to binaries.

* OpenSSL
  We're using a version of this library from before its relicense to
  Apache 2.0 finalized. License info can be found in openssl-1.1.0h/LICENSE.

  Library's website: https://www.openssl.org/

* Vmime
  This is a GPLv3-licensed library with exception for OpenSSL. License info
  can be found in vmime-master/COPYING and vmime-master/COPYING.OpenSSL.

  Library's website: https://www.vmime.org/

* Iniparser
  Small, MIT-licensed C library. License text can be found
  in iniparser-4.1/LICENSE. Additionally, many modifications were
  applied, that are GPLv3-compatible (and in fact, public domain).

  Library's source repository: https://github.com/ndevilla/iniparser/

* LibGCC & friends
  I don't know details of what runtime bits GCC links in, but there are
  definitely some. I don't think any of the licenses requires me to provide
  sources for those, but nevertheless - the entire toolchain (hence also its
  runtime libraries) can be found in Debian:

      https://packages.debian.org/buster/g++-mingw-w64

  It also has links to sources on the right side of every page, under the
  "Download Source Package" text. I actually used Devuan to build programs,
  but it seems to be using the same Mingw-x64 packages, so it doesn't matter.

* My code
  Copyright (C) 2021 Wojtek Kosior, dual licensed under either:
       - GNU GPL, version 3 or (at Your option) any later version
       	 (license text in LICENSES/GPLv3.txt)
       - 0BSD (license text in LICENSES/0BSD.txt)
  My code is that in project's topmost directory + some big modifications
  in Iniparser and a small ugly modification in Vmime.