From: Wade Simmons <wade@wades.im>
To: wireguard@lists.zx2c4.com
Subject: wireguard-ios license
Date: Mon, 4 Mar 2019 12:01:25 -0500 [thread overview]
Message-ID: <CAF63tRoybmhewSoPwuX+uLxiRxXU=FOLa4vzYWi1CU9NZj19qw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 595 bytes --]
Most of the files in wireguard-ios have the MIT license specified in their
header, but there are a few files that specify GPL:
wireguard-go-bridge/wireguard.h
wireguard-go-bridge/Makefile
WireGuard/WireGuard/Crypto/x25519.c
WireGuard/Shared/Model/key.h
WireGuard/Shared/Model/key.c
WireGuard/WireGuard/UI/macOS/View/highlighter.h
WireGuard/WireGuard/UI/macOS/View/highlighter.c
I assume that these are incorrect as the root README and COPYING files
specify MIT, but I wanted to double check here first. Can anyone verify or
fix these headers?
Thanks,
Wade Simmons
[-- Attachment #1.2: Type: text/html, Size: 816 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-03-08 15:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF63tRoybmhewSoPwuX+uLxiRxXU=FOLa4vzYWi1CU9NZj19qw@mail.gmail.com' \
--to=wade@wades.im \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).