From: Sitaram Chamarty <sitaramc@gmail.com>
To: Steve Dodd <steved424@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Fwd: bypassing wireguard using firejail
Date: Sat, 11 May 2019 06:38:57 +0530 [thread overview]
Message-ID: <20190511010857.GA15995@sita-dell> (raw)
In-Reply-To: <CAJ6XMjH23+k+hu0AighRFX4352O1r332mhd28p=+tw3n0T4+ZQ@mail.gmail.com>
On Fri, May 10, 2019 at 05:18:39PM +0100, Steve Dodd wrote:
> [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.
I don't think it has anything to do with my wireguard setup.
If you meant firejail setup, it is when I use "--net" (which,
according to the manpage, "Enable[s] a new network namespace and
connect[s] it to this ethernet interface", that the bypass
happens.
> 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.
The answer, as I'd kinda suspected (and indicated in my original
mail) is that root can always bypass the vpn. For firejail
specifically there's a setting (thanks Jordan Glover) to prevent
that specific escape, which I have now set.
Some other tool, if it's running as root or is suid root, can
still bypass wireguard, regardless of how it is setup.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-05-11 1:09 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 ` Fwd: " Steve Dodd
2019-05-11 1:08 ` Sitaram Chamarty [this message]
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=20190511010857.GA15995@sita-dell \
--to=sitaramc@gmail.com \
--cc=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).