Block a user
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
Post-quantum crypto and better useragent security
Client key is not integrity-protected
WIP: Post-quantum crypto and better useragent security
Not using quantum-resistant schemes
Bootstrap token comparison is not constant-time
User-agent auth accepts integrity-unavailable state while sealed
User-agent auth accepts integrity-unavailable state while sealed
Currently it's intended behaviour, because vault could be sealed and verification couldn't be performed