@ivanristic Are there plans to add a HPKP survey to SSL Pulse at some point?
@ivanristic @NullDereference I don't see open bugs in Mozilla's bug tracker that are likely to get fixed anytime soon. What's missing?
-
-
@BRIAN_____@NullDereference Also, why isn’t there a big and loud blog entry about supporting HPKP (from both Chrome and Firefox)? -
@NullDereference@BRIAN_____ That’s only about “built-in public pins”… The post says about HPKP: “… we plan to implement soon." -
@ivanristic@BRIAN_____ Ah, you're right. Links to wiki and then to fixed HPKP bug, but I don't see something saying their "soon" was over.
End of conversation
New conversation -
-
-
@BRIAN_____@NullDereference I might be wrong, but I couldn’t find any UI to observe pins, override them, etc. Prudent to have. -
@ivanristic@NullDereference I agree, but that could be literally years away from being implemented in Fx. Pin enforcement works already. -
@BRIAN_____@NullDereference Why years? (Confused.) -
@ivanristic@NullDereference Because nobody seems to be working on it or interested in it, judging from my bugmail. -
@BRIAN_____@NullDereference Well then, Mozilla should get its priorities in order IMO. -
@ivanristic@BRIAN_____@NullDereference That suggests that the IETF made the right call. We're still working through the implications -
@sleevi_ Sorry, I am not sure what you’re referring to here -- right call about what? -
@ivanristic Including report-uri in the spec when zero implementations of it existed. In theory, simple. In practice, more nuanced issues - 1 more reply
New conversation -
-
-
@BRIAN_____@NullDereference I think report-uri isn't implemented (didn't work in my tests). But I think that shouldn't stop@ivanristic -
@hanno@NullDereference@ivanristic If you wait for report-uri to be implemented, you might be waiting a long while, AFAICT. - 1 more reply
New conversation -
-
-
@BRIAN_____@NullDereference AFAIK, report-uri is not implemented in Chrome.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.