I notice how you had to shorten the quote of what I said to even make your argument seem valid.  I pointed out exactly how other systems allow you to create a package by creating a single simple file.  All you need is a text editor. 

Is creating a proper Debian package that hard? No.  Is it way more complicated then most other systems? Yes.  There isn't even an argument to be had here.  It's obvious to anyone who has created packages for different systems.  The only reason anyone would disagree with me here is 1. They have no experience creating packages, or 2. They intentionally want to be disagreeable.

So true! Thank you for saying it. Creating a PKBUILD, RPM spec, and other type packaging build is so simple.  Yet Debian is so complicated.  Debian really needs a better system.

I've thought about trying a VM.  I just don't know when I'd find the time though.  I must say though, I am excited about Xlibre.

@zapper

Um. . . uh . . Interesting.   LOL

How is this 3 years old and I've never seen it.

If you follow the link posted by prospero, you will see that rrqsu is simply a script for implementing sudo askpass with YAD. So it's still YAD.  The advantage is that it is an all in one script and doesn't require creating/editing system configuration files.

As for your concern for light system resources, I think you'll find  ralph.ronnquist most recent post useful.  But for a task that will run for a minute at most any used resources will be recovered very shortly.  At most it will save an unmeasurable amount of your battery.  I guess it all adds up though.

Just use YAD.

This looks great. Thanks for posting it.

A RAID member disk walks into a bar. Bartender asks what’s wrong?
“Parity error.”
“Yeah, you look a bit off.”

@chris2be8

I agree. Lots of things aren't a problem for people who understand their system. The issue is non-technical users.  Sadly it is those same user who will not made the effort to configure their system properly. Of course I'm sure those users are using sudo, so it's not an issue.

OK so let's just not make any effort and just let it all be completely proprietary and controlled by the big corps and the government.  I really only see the 2 options: FOSS or private controlled. As I said you can't stop it. Or is this just about complaining? Gloom and despair the worlds gonna end.

My point is not that it's a good situation. Just that we should at the very least go down fighting.

. . . and maybe I should of said "help level" which was what I meant.

You can't stop advancement. It's a race, but the more that it is developed in the open with an FOSS license the better.  If it's not for everyone it will be abused.

Update, commands specified using nopass are limited to the restricted PATH.  So that's good.

But it still seems that you could still do damage with a fake executable, even if a password is required.  Just put it in the local path (in $HOME)  like I did with the whoami example above and the user will be tricked to give the password.

of course a better example would be apt because why would you you'd be less likely to use root for whoami.

I had already thought of that when I made my last post, so I tested it.

I created a fake whoami file in my local path ~/.local/bin/ that simply echos HAHA!  The results:

regular user - runs the fake whoami
with sudo - runs the real whoami
with doas - runs the fake whoami

Yep security issue.  So you might want to use full path when adding nopass commands.

update : Does not affect nopass commands. See post below.