When using a user password for client side encryption, do I have to store the salt for the user encryption key on the server?

The password of the user shall be used for client side encryption. A PBKDF and salt shall be used to derive a key from the user password.
Do I need to store this salt on the server and deliver it to each new client/device the user authenti… Continue reading When using a user password for client side encryption, do I have to store the salt for the user encryption key on the server?

Would having two identity providers prevent the theoretical possibility of impersonation by an IdP?

I am slowly accepting that OAuth2 is quite amazing, but I’m still worried about the fact that an IdP could theoretically impersonate me as discussed in Can an identity provider impersonate me? (Can Facebook post Stack Overflow questions un… Continue reading Would having two identity providers prevent the theoretical possibility of impersonation by an IdP?

Shamir secret sharing, is security reduced by chunking a secret into smaller blocks?

When using Shamir’s secret sharing algorithm one has to define the size for the finite field over which the secret is split. I came across a few implementations, like secrets.js-lit, and as far as I can see the implementation chunks the se… Continue reading Shamir secret sharing, is security reduced by chunking a secret into smaller blocks?

Is there hardware (like u2f-keys) for passwordless client-side encryption & decryption

I know that u2f keys are designed as authentication factors, but I think it would not be far fetched to also add a protocol that the user can use to encrypt or decrypt data on the client-side. This would relieve the user from remembering a… Continue reading Is there hardware (like u2f-keys) for passwordless client-side encryption & decryption