Keepass best practices?

[anon9706954]

@whoami

@anon9706954

@whoami what the fuck possesses you to believe you speak on my behalf, and incorrectly at that? qubes.Filecopy is a qrexec service, so stop making up bullshit about what I have or have not recommended in this thread.

I guess, this is a misunderstanding: which stores refers to the AppVM not to qrexec. If not I do not get your point? Please explain what is wrong here and I modify.

Misunderstanding is involved, but misattribution is your primary offense in that instance. ___.
Here is a link to my one and only recommendation post in this thread:

Keepass best practices?

In terms of securing your usage of Keepass2 or KeepassXC, I would recommend the most important step is creating a separate TemplateVM and only using your keepass app of choice from AppVMs derived from that TemplateVM. By isolating your keepass app’s TemplateVM from your other TemplateVMs you run less risk of accidentally exposing your keepass database file to risk. As others mentioned, AppVMs you run any keepass-related application in do not need a network connection so remove that, and clipbo…

What you represented as my recommendation was both not my recommendation and was incorrect.

@anon9706954

edit your post to remove your incorrect summary of my recommendation

What I quoted just there is literally a request to remove everything you attributed to me from your post. ___.

You should not need me to post to clarify any of this. ___.

You seem to think that my posts in this thread stating that your (@whoami)'s recommendation to dump split-ssh and split-gpg in the same AppVM as a keepass database file is inherently insecure is my recommendation in this thread. That is simply incorrect as split-ssh and split-gpg have absolutely nothing to do with this thread’s original post and are off topic and were only brought in by you.

And I’m not going to handhold you through an explanation of how qubes.Filecopy is a qrexec service in the same way as everything else, but a qube that does not use any qrexec service is a rather useless qube for the topic of this thread. I have never made any statement, either in advice to you or on the topic of this thread to strip all qrexec services from a qube. ___.

You are not welcome to summarize my recommendation for me when I have already posted mine separately and it has nothing to do with the ___ security issues yours raises and glossed over under the guise of “personal views”. If you need to represent something I said such that you feel the need to blame or otherwise attribute it, quote it and do not paraphrase. And don’t add those insulting footnotes to attributions or quotes as the effect is to conflate the attributed person with the anecdote in the footnote and that is most certainly not my recommendation whatsoever.

I would welcome moderation that took the entirety of your posts and my replies to them and shoved them into a different thread as off topic as any and all mention of split-ssh and split-gpg is wholly off topic to the original thread, and the “personal views” vs security ___ has made it plain this is not the best place to be looking for actual advice on how to use Qubes OS without having the more user-facing internals of Qubes OS like qrexec just be written off as “here be dragons”.