> potentially increasing the risk for the other secrets stored in the same password manager.
As pointed to me by a friend, this is one reason not to give in to the convenience of the secrets manager you already use.
My use case for fnox with keepassdb back-end was partially validated but as I mentioned elsewhere in the thread, having to set master password in an env var is a bit of snag for the workflow.
keepass is great, because it doesn't require any service to operate - it's just a file. technically, you are responsible for backing it up, but more centralized options possible. I used it for 4 years pre-touchID era in a corporate setting and it worked great. For a single device. UX was very "open source", but hey - it's a free software with other focus in mind.
i know other people partitioning their secrets into multiple keepassx vault files, so the argument about using the same password manager can be interpreted differently.