If available, use system pipework, else bundled.

[rswarts]

The bundled script is in the user's home directory. If pipework is on
the system, prefer using that over sudo-ing a user editable script.

[fgrehm]

I like this but unfortunately I don't have the time to test it. If someone else is able to do that and is interested on this functionality please 👍 this PR!

[fgrehm]

Sorry for the long silence but as per GH-375 I'm looking for help to maintain this plugin and for now I'm holding back from bringing in new changes =/

If you are interested on maintaining the project and keep things moving please shoot me an email or drop a message on GH-375 so I can arrange things.

Cheers 🍻

[ghost]

It's very true that sudoing pipework which is user-writable is a bad idea, but then again, the whole sudo wrapper thing is a bit on the "shaky" side of things, a necessary hack for darker times.

Now that unprivileged containers support is coming, the sudo wrapper will become legacy. If security is the only reason for this PR, might I suggest that we let it go?

[fgrehm]

If pipework can be dropped I'm totally fine with that. And BTW, I think that and support for unprivileged containers deserves a nice 2.0 bump ;-)

[ghost]

@fgrehm it's not that pipework could be dropped, but more that pipework could be called without sudo (rendering this PR useless). Its README seems to indicate that it's possible to create the bridge within the container.

[rswarts]

I still deploy a clone with this patch applied, and I don't see unprivileged containers happening on, for example, ubuntu 14.04 any time soon. However, I have no problem with keeping that going the coming few years while 14.04 slowly goes away.

…

On Thu, Dec 14, 2017 at 6:12 PM, Virgil Dupras ***@***.***> wrote: @fgrehm <https://github.com/fgrehm> it's not that pipework could be dropped, but more that pipework could be called without sudo (rendering this PR useless). Its README seems to indicate that it's possible to create the bridge within the container. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#372 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABtYgY30h7hfv44sXn6NM2Hd1tKZByTPks5tAVbpgaJpZM4EPqRB> .

[ghost]

trusty-backports has 2.0.8, so it should be possible

[fgrehm]

Hey, sorry for the silence here but this project is looking for maintainers 😅

As per #499, I've added the ignored label and will close this issue. Thanks for the interest in the project and LMK if you want to step up and take ownership of this project on that other issue 👋