Bug 493613

Currently as likely expected by most users, Krusader executes any executable file without confirmation.
While this is mostly desired, it does come with downsides often not considered:
- Mice tend to get unreliable with age, either missing clicks, or doubling them, the later possibly resulting in unintentional execution
- Surprise file list changes unavoidably make the mouse cursor unreliable for picking the right file every time
- Currently present panel refreshing bugs result in the selection resetting to an earlier state with I/O performance based delay, also making the keyboard not completely reliable for picking the right file
- Handling questionable executable files with no intention of executing any makes the presence of preventative safety features desirable

Initially I figured the issue was too niche and would be mostly met with a "don't be clumsy/paranoid" kind of response, but then I recently ran into something really surprising: Dolphin doesn't just have such a safety guard, it's even enabled by default.

The setting in Dolphin is: Configure -> General -> Confirmations -> When opening an executable file: [Always ask] (default) / [Open in application] / [Run script]

It seems to strike a good balance as low-risk files associated with handlers like pictures shown by a picture viewer can be still opened effortlessly, while opening an executable file pops up a confirmation window defaulting to the Cancel operation, raising the bar for execution to be pretty much intentional, while preserving the freedom of choice the usual KDE way by letting the user disable this feature.