GHSA-h265-g7rm-h337 (Publication in process, waiting for CVE assignment) This vulnerability would allow an authenticated attacker that is part of an organization to access items from collections to which the attacker does not belong
one thing I’m not willing to self host is vault/bitwarden. My whole life is based in my password manager. I imagine Bitwarden inc has a lot better security than me, and if I lose access to it I’m stuffed.
What are they going to get an encrypted blob.
Had this exact thing happen to me. I was hosting vaultwarden on a raspberry pi and then it fell over. My client devices had caged versions of my vault, but I couldn’t make changes to it. I quickly moved over to Bitwarden and it’s been fantastic.
yup, BW is awesome. and mostly free. I use BW too, but not self hosted.
Already updated yesterday 🤓 All hail the mighty renovate
Renovate?
I have all my compose stacks in git. They’re deployed from their git repos with Komodo.
Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.
There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo
It’s a bot to create PR’s with dependency updates
Might be a stupid question, but how are PR’s connected to your server deployment?
Copying my other comment. It opens PRs to change the tag from the docker image.
I have all my compose stacks in git. They’re deployed from their git repos with Komodo.
Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.
There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo
Renovate? Hrmmmm
Hrmmm?
