3 ms·
Ask HN: How do we fix client auth (My gov. just locked me out)
So, as a supplier to UK gov, I have an account on a UK government website. And I have a password - and it seems they recently upgraded their website. Cos they locked me out. See the imgur here (#)
They checked the form i submitted to login (it was TLS) for funny characters. like "<". So my random password in my password manager worked last month but now it's a potential CSRF attempt. And then they return me a debit page, with my password plain text in it. "There was a potential funny character in this form field - the one labelled 'password'"
S'ok, it's just sent back to me on TLS - not the whole world. Except for the logs for the devs to look at tomorrow.
Look I know the GDS is doing sterling work and i know people make mistakes (I keep the average up here) but I checked the OSWAP cheat sheet for authentication and ... really we should do better. Maybe PKIs are hard. Maybe the friction with anything but a password will stop my startup growing. But browsers have damn good built in crypto stuff nowadays, hell they always have, - why the hell are we still sending passwords over forms?
What is the right way to do this, damn the uptake and friction? What's right? How do we get there? Cos this ain't it.
(#) ok give me a moment i am having trouble logging in there too. I may have used twitter to login or not. See my point.