Re:Attacker with access to XML config can trigger keepass.ex...
by Macha on Friday January 27, 2023 @09:00AM
(#34546082)
Which OS is this?
The first rules out Linux (unless this is a SELinux thing?).
The second rules out Windows/Mac OS/Linux with X11.
The upstream KeePass application does not support mobile operating systems. It barely supports non-Windows, which is why when most people say they use KeePass they mean KeePassXC
Re:Attacker with access to XML config can trigger keepass.ex...
by CannisterFlux on Friday January 27, 2023 @09:33AM
(#34546438)
In Linux you can't attach to arbitrary processes depending on configuration. You can start a program with gdb, but not attach to a running one by default. It was a security upgrade a few years ago https://www.kernel.org/doc/Documentation/security/Yama.txt
Re:Attacker with access to XML config can trigger keepass.ex...
by maicro on Friday January 27, 2023 @09:24AM
(#34546346)
Maybe NixOS? I've barely played with it, but this seems like the level of isolation/paranoia that NixOS seems to offer (as far as a layman like myself understands - could be completely wrong on all counts, as usual).
Re:Attacker with access to XML config can trigger keepass.ex...
by licebmi__at__ on Friday January 27, 2023 @09:32AM
(#34546437)
I think you might be misunderstanding nixos, the tree separation will not improve security for this kind of scenario, the only guarantee that nixos offer is that the package is exactly as it’s described on nixpkgs if the store is untainted.
Re:Attacker with access to XML config can trigger keepass.ex...
by maicro on Friday January 27, 2023 @10:01AM
(#34546772)
Wouldn't be shocked at all, I mostly think of it as "Linux but with a bunch of inherent security separations introduced", which is why I thought it might be what the...grandparent at this point? is using.
Re:Attacker with access to XML config can trigger keepass.ex...
by H4ZB7 on Friday January 27, 2023 @10:34AM
(#34547147)
gotta love how every discussion pertaining to program isolation in the last 20 years is just "well all these years i thought this thing isolates processes like it ought to do", followed by a quick, "nope, it actually doesn't". i blame UN*X
Listening to global clipboard events at the OS level is a permission I have to explicitly grant.