mbarulli on Nostr: Apparently, the domain clipperz.is and the associated online password manager are ...
Apparently, the domain clipperz.is and the associated online password manager are blocked in these countries (and certainly others too). I guess those governments are not big fans of strong cryptography.
Clipperz is a project I co-created in 2005 – way before the W3C pushed browsers to provide native support for cryptographic primitives. Back then, the only way for a web app to execute a cryptographic protocol was to rely on Javascript code, which was slow and fragile.
Therefore, we had to write our own Javascript cryptographic library and build on top of them. We provided users with tools to run the whole app locally, and they could also check that the open source code was the same as the one running in the browser (a precursor of what became known as deterministic builds).
Of course, we were mocked by the whole security community, with very few exceptions (one being npub1xyd5ja34s4nk0l6urnh69wx9ep6uuxz2ujrkm2f8n6pfhgqa6y5s2xn6n2 ). We didn't care because we had a lot of fun, a reassuring security review from Cure53, and the love of many thousands of users.
With the evolving support of browsers for cryptographic algorithms, the online password manager became faster and more robust.
Clipperz has been running smoothly since 2005, happily serving its loyal and generous users, and it has never suffered a security breach of any sort.

Clipperz is a project I co-created in 2005 – way before the W3C pushed browsers to provide native support for cryptographic primitives. Back then, the only way for a web app to execute a cryptographic protocol was to rely on Javascript code, which was slow and fragile.
Therefore, we had to write our own Javascript cryptographic library and build on top of them. We provided users with tools to run the whole app locally, and they could also check that the open source code was the same as the one running in the browser (a precursor of what became known as deterministic builds).
Of course, we were mocked by the whole security community, with very few exceptions (one being npub1xyd5ja34s4nk0l6urnh69wx9ep6uuxz2ujrkm2f8n6pfhgqa6y5s2xn6n2 ). We didn't care because we had a lot of fun, a reassuring security review from Cure53, and the love of many thousands of users.
With the evolving support of browsers for cryptographic algorithms, the online password manager became faster and more robust.
Clipperz has been running smoothly since 2005, happily serving its loyal and generous users, and it has never suffered a security breach of any sort.