@illyBytes@halva got around to skimming the paper last night, these aren't server-side oversights but cryptographic protocol design flaws password manager vaults are meant to be encrypted end to end such that a compromised server cannot leak your passwords the paper shows several ways the server can mess with your vault's contents and in some cases coerce your clients to disclose plaintext to it all in all it's probably not a huge risk since bitwarden gets regular code and security audits (which means bw servers being compromised is unlikely), but those problems need to be fixed regardless
@halva yeah tbh im just avoiding any shit with cloud providers by just using keepassxc/dx with syncthing only had 1 conflict event but solved it by just merging the oldest file (the one renamed for conflict) into the newest file and deleting the old one lol
@halva its not gonna be an issue, if you decrease the period between checks or just enable filesystem watch lol just dont do my mistake and forget to turn syncthing back on for a few days like i did x3 (what caused the conflict, 2 days ago)
had enough syncthing in my life to never use it again
Ahaaha. Almost me but in in my case I just have read to many people in the fedi getting syncthined before to not trust nor the app nor my hands for it's configuration