Benchmark applications should not impose root privileges #181
Description
Replying to #101 :
This is expected behavior, 3.x.x performs testing entirely inside the helper, it avoids problems: inability to write to some places, repeated authorization requests.
What on earth is the problem with "inability to write to some places"?
A benchmark application should not require root access, whether it uses a helper application or not.
- Regular users ought to be able to benchmark e.g. their external drives if the system allows them to use them.
- Users who want to benchmark a drive to which they do not have write access can use sudo, pkexec or any other equivalent to start the benchmarking application with elevated privileges.
I for one do not feel comfortable to use an application that does heavy disk I/O on a drive that contains sensitive data (like OS files) that I do not own or want to put at risk.
I'm reporting this as a bug because IMHO it is one, but I understand there's little hope to convince the author to fix it.
I am hoping for some pointers on what/how to change to skip the privilege elevation step and just run the helper as the calling user. I'm also open to contribute a reasonably done option, if there is interest for that.