-
Notifications
You must be signed in to change notification settings - Fork 181
Conversation
Fixed the failing test |
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 🍻 |
I've actually just started writing a comment on there, since we use this heavily @mayflower.. So we are definitely interested in keeping this alive and up to date. I guess @fpletz, @codec, @fadenb and possibly @marco-jantke, might want to chime in, too. What's the best way to support you? |
That is awesome! 💥 🙌 💪 🍻 🎆 Well, if you guys are up for it I can provide write access to one of you and you can start hacking away, merging PRs, closing issues... 😄 I'll be around to help out and provide feedback whenever needed but unfortunately I'm very unlikely to have the time to test changes or write code. Once you guys are ready to cut a release, just open up PR and WDYT? |
@globin IMHO we should remove at least the |
@@ -36,7 +36,7 @@ def sudo_wrapper | |||
|
|||
def ensure_lxc_installed! | |||
begin | |||
sudo_wrapper.run("/usr/bin/which", "lxc-create") | |||
sudo_wrapper.run("/usr/bin/env", "which", "lxc-create") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we prepend "/usr/bin/env"
to every path in the sudo_wrapper instead of fixing this for every command manually? There are some more similar cases in the networking code where tools like ip
and brctl
are called.
Tempfile can be created in /run, too.
This fixes commands that currently rely on hardcoded paths and break on systems like NixOS that don't have all binaries in /usr/bin etc.
Updated and rebased |
Definitively would love to see that in a release :) |
👍 |
That breaks avoiding sudo passwords on Ubuntu 14.04 when running vagrant ssh.
|
Also, I think the sudo wrapper is actually not compatible with nix. If it allows calling commands with /usr/bin/env, then an attacker could just add whatever binaries they want to the user's path and call them. |
Fix released in 1.2.1 |
This fixes some minor issues in regard to NixOS compatibility mostly
due to the fact that NixOS only has the binaries
/usr/bin/env
and/bin/sh
in deterministic absolute locations.
Additionally this removes the copying of the template to the lxc template
path, which is in a read-only mount on NixOS and a non-deterministic location.
Instead it uses the absolute path to the template which is supported since lxc 1.0.