-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running zxfer with restricted receive user and bin not working #32
Comments
This in inherited code, so I don't know. Looking at it, it seems the reason is that those are meant to be the paths on the remote system, so 'which zfs' from your local system, might not be the right path. I suppose you could try to depend on ZFS being in the $PATH on the remote site. I am not sure if changing this is a good idea or not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using zxfer and at the receive and having a user that does not have access to /sbin does not work.
This is because the script specifically looks for the zfs binary in /sbin/zfs instead of relying on it being in the users $PATH at two places in the script (works for me after I changed it).
The use case I have for not wanting the user to have access to /sbin is a locked down user for only receiving where I have constructed a directory with symlinks for allowed binaries to run. This directory is then added to the restricted user $PATH.
Is there a good reason for wanting it to be /sbin/zfs? (on a side note love BSDNow, keep up the good work!)
The text was updated successfully, but these errors were encountered: