as an alternative:
virecover currently does the right thing if it is run unprivileged.
adding a default .profile thing to execute it will achieve the same
functionality without requiring any root privileges.
additionally we will want to move recover dir to somewhere
user-controlled.
Date:Fri, 10 Nov 2017 00:12:46 +
From:co...@sdf.org
Message-ID: <20171110001246.ga6...@sdf.org>
| i could use it to delete any file in /,
The current version?
| and the hang is at boot.
As I said, it should probably be run in background, so rc doesn't
wait o
i could use it to delete any file in /, and the hang is at boot.
Date:Thu, 9 Nov 2017 21:19:09 +
From:co...@sdf.org
Message-ID: <20171109211908.ga8...@sdf.org>
| The way virecover currently works is problematic for security (see the
| recent nvi commits).
Aside from a few (potential mostly) bug fixes, the one issue that Chr
