3 ms·

This is fantastic news! And they decided to include the Chromium HSTS Preload list too. I've submitted something like ~30 domains to the list, and having them c

This is fantastic news! And they decided to include the Chromium HSTS Preload list too. I've submitted something like ~30 domains to the list, and having them covered in newer versions of IE automatically is a very nice thing.

mikecb 12y ago
How long until that list of yours is just *.gov?
- toomuchtodo 12y ago
  A while. It takes a significant amount of effort to effect change in the IT infrastructure of every organization within the US government. (konklone does mention this in their Reddit post in /r/netsec) Progress is progress.
  - mikecb 12y ago
    Indeed. I was eager to learn more about their specific strategy to achieve it.
    - konklone 12y ago
      There's not a master plan, but there's several promising lines of work happening. Hopefully 2015 will be a fun year. Tomorrow, I'll be on Federal News Radio in the morning, preaching the gospel to DC commuters.
      - mikecb 12y ago
        Link for those interested: http://www.federalnewsradio.com/?nid=1269&sid=3801434 http://www.federalnewsradio.com/?nid=1269&sid=3801434
dmix 12y ago
Is there place where a (current) list of domains are stored by Chrome?
- detaro 12y ago
  List: https://code.google.com/p/chromium/codesearch#chromium/src/net/http/transport_security_state_static.json https://code.google.com/p/chromium/codesearch#chromium/src/n... (there are some surprising domains in there, it's not just a who's who of major sites) Submit your domains: https://hstspreload.appspot.com/ https://hstspreload.appspot.com/
higherpurpose 12y ago
I wonder if they plan to support Curve25519 and BLAKE2 in the browser, so developers can choose non-NIST crypto.
- AlyssaRowan 12y ago
  In terms of Curve25519: it seems so, yes. That is what CFRG's current draft recommends to the TLS Working Group for a 256-bit curve, along with the X25519 key exchange defined with it. There's a slot waiting in WebCrypto for it, too. Not too sure about signatures yet: Ed25519 is definitely one contender, but I don't know where that'll end up.

mikecb 12y ago

How long until that list of yours is just *.gov?

toomuchtodo 12y ago
A while. It takes a significant amount of effort to effect change in the IT infrastructure of every organization within the US government. (konklone does mention this in their Reddit post in /r/netsec) Progress is progress.
- mikecb 12y ago
  Indeed. I was eager to learn more about their specific strategy to achieve it.
  - konklone 12y ago
    There's not a master plan, but there's several promising lines of work happening. Hopefully 2015 will be a fun year. Tomorrow, I'll be on Federal News Radio in the morning, preaching the gospel to DC commuters.
    - mikecb 12y ago
      Link for those interested: http://www.federalnewsradio.com/?nid=1269&sid=3801434 http://www.federalnewsradio.com/?nid=1269&sid=3801434

dmix 12y ago

Is there place where a (current) list of domains are stored by Chrome?

detaro 12y ago
List: https://code.google.com/p/chromium/codesearch#chromium/src/net/http/transport_security_state_static.json https://code.google.com/p/chromium/codesearch#chromium/src/n... (there are some surprising domains in there, it's not just a who's who of major sites) Submit your domains: https://hstspreload.appspot.com/ https://hstspreload.appspot.com/

higherpurpose 12y ago

I wonder if they plan to support Curve25519 and BLAKE2 in the browser, so developers can choose non-NIST crypto.

AlyssaRowan 12y ago
In terms of Curve25519: it seems so, yes. That is what CFRG's current draft recommends to the TLS Working Group for a 256-bit curve, along with the X25519 key exchange defined with it. There's a slot waiting in WebCrypto for it, too. Not too sure about signatures yet: Ed25519 is definitely one contender, but I don't know where that'll end up.