Block a user
refactor-integrity-check
housekeeping(server): dependencies upgrade
Not using quantum-resistant schemes
Useful top-level research: https://gemini.google.com/share/0d54d7176359
quite focused on blockchain itself. Sadly, not much can be done from our side, aside from migrating our own auth
vault now differentias between expected/unexpected states for commands more granularly
security(server): bind grant revocation state (revoked_at) to integrity hash
mixing concerns: should create a new business-object for signing containing this field
security(server): bind grant revocation state (revoked_at) to integrity hash
We discuseed this: don't mix concerns
security(useragent): validate server cert fingerprint and host instead of accepting all certificates
security(useragent): validate server cert fingerprint and host instead of accepting all certificates
I appreciate the effort, but sadly this is wrong solution. So first of all, we pin based on root CA, not leaf CA. This means that we check if signer that signed presented certificate by server…
suspicious as keywords
I agree. The problem with those is that fucking sqlite dynamically sizes integers. So fucking diesel implement ToSql for sqlite only for i32.
refactor(hashing): introduce Hashable derive macro and migrate server types