Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: al so <volkswak@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard for site-to-site VPN use case
Date: Thu, 22 Mar 2018 06:11:19 +0000	[thread overview]
Message-ID: <CAKXLc7cmK1SAuNR6p+99Y-diakNyNAQe9LMK1=ea9-Lm=_3kEQ@mail.gmail.com> (raw)
In-Reply-To: <CAJrqK=0X1gerGN=OVCNp-eNqw1S9N9OLQDMQCV4GQVN0dXHw-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

On Wed, Mar 21, 2018, 22:41 al so <volkswak@gmail.com> wrote:

> How does Wireguard compare to Tinc and ZeroTier in terms of ease of use
>> and security.
>>
>> I looked at Tinc. Seems pretty easy to setup being Decentralized Mesh
>> architecture. Security doesn't seem good. No exploits reported may be due
>> to no large commercial deployments.
>>
>> ZeroTier seems pretty secure. And Generic. Not sure how well it fits
>> Site-to-Site VPN case.
>>
>>
>> Going back to my original question:
>> How does Wireguard compare to Tinc and ZeroTier in terms of ease of use
>> and security.
>>
>> -volk
>>
>
Given the terms of comparison, the best answer only you can give ;-)
Really. Have a look at wireguard, use it and then you can answer your
question.

WG can be used both for mesh and S2S.

Kalin.

[-- Attachment #2: Type: text/html, Size: 1871 bytes --]

      reply	other threads:[~2018-03-22  6:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJrqK=1cvf0HRx2zLH=wYr=13Y4N=mK4qjHRWgtmX4W7rkGKrQ@mail.gmail.com>
2018-03-21 21:40 ` al so
2018-03-22  6:11   ` Kalin KOZHUHAROV [this message]

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='CAKXLc7cmK1SAuNR6p+99Y-diakNyNAQe9LMK1=ea9-Lm=_3kEQ@mail.gmail.com' \
    --to=me.kalin@gmail.com \
    --cc=volkswak@gmail.com \
    --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).