On Mon, 15 Jun 2020 14:30:07 +0000 solderpunk <solderpunk at SDF.ORG> wrote: > It's perhaps a little bit tedious for users, but the simplest > solution I can think of for things like this is a convention that all > requests which trigger side-effects (like comments, etc.) must be > made with a client certificate, because that will make it very clear > to the user that something is happening and no surprises are possible. Doesn't this imply that all requests with a client cert will have to be confirmed by the user? > I strongly suspect that completely preventing this kind of thing will > be impossible if we simultaneously insist on a simple protocol and a > frictionless user experience - in which case, everybody knows which > one will be prioritised. :) But if we can somehow pull off both at > once that will be best. Of course, which is why I wrote > But this would require a separator, and we all know where this leads. :) Still, I don't think this is a matter of frictionless user experience, more like... developer ux? Unless we find something simpler than nonces.
---
Previous in thread (5 of 11): 🗣️ Sean Conner (sean (a) conman.org)
Next in thread (7 of 11): 🗣️ Francesco Gazzetta (fgaz (a) fgaz.me)