1. 14 Nov, 2018 1 commit
  2. 09 Nov, 2018 2 commits
  3. 05 Nov, 2018 3 commits
  4. 02 Nov, 2018 4 commits
  5. 19 Oct, 2018 8 commits
  6. 26 Sep, 2018 8 commits
    • Vincent Pelletier's avatar
    • Vincent Pelletier's avatar
      all: More python3 adaptations. · 8ce08bf9
      Vincent Pelletier authored
      What was not picked up by 2to3.
    • Vincent Pelletier's avatar
      all: Reduce differences with python3. · 7f9e56cf
      Vincent Pelletier authored
      Using only 2to3 conversions which are python2-compatible.
    • Vincent Pelletier's avatar
      wsgi: Become web-friendly · 719959e0
      Vincent Pelletier authored
      Self-describe site structure in application/hal+json format.
      Add Cross-Origin Resource Sharing support: pre-flight request support,
      same-origin-only origin access control minimal html page. Access control
      decision is stored client-side in a signed & time-limited cookie
      supporting multiple concurrent origins. Origins may be pre-allowed (ex:
      when caucase GUI is served from a trusted server).
    • Vincent Pelletier's avatar
      http: Constrain the certificates caucased https CA may sign. · 7ff81404
      Vincent Pelletier authored
      This makes it safer to trust this CA certificate in general-purpose https
      clients, like web browsers, as it prevents such trusted CA certificate
      from issuing rogue certificates.
      Bump pyOpenSSL to latest version (and, as a consequence of pyOpenSSL
      18.0.0 itself requiring cryptography 2.1.1, bump it as well) as it seems to
      fix a bug related to validating NameConstraints - and anyway fixes
      worrying use-after-free errors.
    • Vincent Pelletier's avatar
    • Vincent Pelletier's avatar
      all: Make caucased https certificate independent from CAS. · 17325dc0
      Vincent Pelletier authored
      This is a step in the direction of being browser-friendly: if caucased
      https certificate is issued by CAS CA, then for a browser to trust that
      certificate it would have to trust all certificates emitted by CAS CA
      certificate. This would be very dangerous, as CAS CA does not constrain
      the certificates it may sign, so it exposes users of that caucased to
      rogue certificates.
      Alone, this step is insufficient, as the new internal "http_cas" does not
      constrain certificates yet. This will happen in a separate commit, to
      ease review and regression testing.
      As a consequence of this step, by default client will not check server
      certificate in https. This is consistent with how trust is bootstrapped
      with plain http: maybe client is accessing an unexpected/malicious
      caucased, but in such case issued certificates will be worthless to a
      party which could access the correct caucased. Also, the client
      certificate presented to caucased does not allow that caucased to fake
      being that user, so there is no privilege escalation possible for
    • Vincent Pelletier's avatar
      doc: Add crude overview schema. · bcaebfe7
      Vincent Pelletier authored
  7. 21 Sep, 2018 10 commits
  8. 20 Sep, 2018 4 commits