News for hackers. Stuff that matters.

A comment on Bypassing Browser Security Warnings with Pseudo Password Fields. Parent comment

Re:Bypassing Browser Security Warnings with Pseudo Password ... by zAy0LfpBZLC8mAC on Friday November 03, 2017 @12:30AM (#15616703)
Well, yeah, I certainly didn't mean to say that SIP is a great protocol, it is indeed quite terrible--but still in practice if things don't work, that's usually a result of at least one party not following the spec (which is not really surprising , given all the pointless complexity ... but then that's still not really an excuse to not implement SIP when you are claiming that you do).
[ Parent | on HN ]
Re:Bypassing Browser Security Warnings with Pseudo Password ... by MichaelGG on Friday November 03, 2017 @02:33AM (#15617072)
Practically, it is not possible to implement the spec in an interoperable way. Existing implementations are mutually incompatible. Hence the need for config flags per "trunk". What one system requires, another will reject. Sad but true.
[ Parent | on HN ]
Re:Bypassing Browser Security Warnings with Pseudo Password ... by zAy0LfpBZLC8mAC on Friday November 03, 2017 @03:33AM (#15617280)
Well, yes. But still, more often than not, when I encounter interoperability problems, if both sides actually did what the spec says, there wouldn't be a problem. SIP itself is quite sad, but in my experience many implementations are even worse than the spec.
[ Parent | on HN ]