Someone please build a keebase plugin for uploading the kdbx database file as an encrypted nostr event.
Massive increase of censorship resistance for password managers.
Happy to pay a bounty.
Someone please build a keebase plugin for uploading the kdbx database file as an encrypted nostr event.
Massive increase of censorship resistance for password managers.
Happy to pay a bounty.
Just seen Keybase also exists, but the reference to .kbdx makes me think you mean KeePass?
If so I don't like the idea of publishing all my passwords to a public service like Nostr, even if encrypted. Seems like an unnecessary risk/honeypot scenario. There is the keyfile/password combo that adds another layer of encryption I guess.
I prefer security by obscurity, where a non-standard solution poses the biggest effort to attackers.
Currently I'm using syncthing to keep my keepass database in sync between my devices. It was a little bit of a pain to get working but I wanted to keep that attack surface as small as possible.
Just been down a Keybase rabbit hole. Besides being owned by Zoom it seems pretty interesting at least as a pub-priv keypair Slack alternative, for example.
Nostr proofs would be cool to add.
It's open source and fairly accessible so could be possible...
I don't know how to write keepass plugins but it would probably be better to store it as a blob since normal nostr events have a size limit.
also if it was encrypted with your nsec. then you might end up in a awkward situation if the only place you kept your nsec was your keepass db
https://cdn.satellite.earth/ac2f924358fe15295aee16242dfbac2c756cc3d84f4c51e27ef8c9a1555e10e8.kdbx
I was wondering too, how large can the kdbx get?
How's the CDN adoption going?
Are there enough relays yet?
I'm not sure but most of my kdbx files are between 400kB and 800kB, but I think most of the size comes from embedded icons.
CDN adoption is going better than I hoped. although I still need to build more tools that take advantage of the sha256 hash
And as far as I know there are only about 3-4 CDNs running right now. not enough to be censorship resistant
I'd still like it encrypted though, for the plausible deniabiliy and less likelyhood of relays targeting and deleting those events.
typical size limit is half a megabyte tho