Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Steve Dodd <steved424@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Fwd: bypassing wireguard using firejail
Date: Fri, 10 May 2019 17:18:39 +0100	[thread overview]
Message-ID: <CAJ6XMjH23+k+hu0AighRFX4352O1r332mhd28p=+tw3n0T4+ZQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ6XMjFxfm=0L2URLzn8pkZY1y4zU+mskgd7ykRKOjXSza4tSA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]

[sent to author only originally by mistake - I hate Gmail]

On Fri, 10 May 2019 at 12:56, Sitaram Chamarty <sitaramc@gmail.com> wrote:

> I am able to bypass the VPN by using firejail (which is a
> sandbox program to run untrusted applications).
>

I'm not 100% clear on your setup .. Have you got a network namespace set
up? If not, you haven't got much security anyway, I suspect. It turns out
it's not too hard .. you're welcome to my hacky scripts if you're
interested.

Not sure if firejail would still be able to escape a network namespace by
default, but I'm sure it's possible to drop a capability somewhere or
similar if it is.

S.

[-- Attachment #1.2: Type: text/html, Size: 1103 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2019-05-10 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 11:54 Sitaram Chamarty
2019-05-10 14:06 ` Jordan Glover
2019-05-10 14:39   ` Sitaram Chamarty
     [not found] ` <CAJ6XMjFxfm=0L2URLzn8pkZY1y4zU+mskgd7ykRKOjXSza4tSA@mail.gmail.com>
2019-05-10 16:18   ` Steve Dodd [this message]
2019-05-11  1:08     ` Fwd: " Sitaram Chamarty
2019-05-11 11:34       ` Steve Dodd
2019-05-14  4:05         ` Sitaram Chamarty

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='CAJ6XMjH23+k+hu0AighRFX4352O1r332mhd28p=+tw3n0T4+ZQ@mail.gmail.com' \
    --to=steved424@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).