The issue seems caused by the zuluCrypt-cli binary reading the SUDO_UID variable and calling seteuid(SUDO_UID) if present. We can workaround the problem by unsetting the SUDO_UID variable in the test suite - but that will not prevent somebody from running `sudo zuluCrypt-cli --test` on the installed system.
Opened a bug upstream: https:/ /github. com/mhogomchung u/zuluCrypt/ issues/ 209
The issue seems caused by the zuluCrypt-cli binary reading the SUDO_UID variable and calling seteuid(SUDO_UID) if present. We can workaround the problem by unsetting the SUDO_UID variable in the test suite - but that will not prevent somebody from running `sudo zuluCrypt-cli --test` on the installed system.