Skip to main content

Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #19302 Force Chromium-based browsers to segment the cache to defend against cache probing
    Infos
    #19302
    Thomas Gerbet (tgerbet)
    2021-02-18 16:14
    2021-02-12 15:52
    20883
    Details
    Force Chromium-based browsers to segment the cache to defend against cache probing

    We should instruct browsers supporting the Fetch Metadata Request Headers (Chromium-based browsers only at this time) to segment their cache according to the origin of the requests in order to defend against a class of cross-site leaks. While Firefox does not support the Fetch Metadata Request Headers since FF85 the cache is partitioned by top-level origin.

    References:

    Other
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2021-02-18
    Attachments
    Empty
    References
    Referenced by request #19302

    Artifact

    rel #18867 12.6

    Other

    gerrit #21773
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2021-02-18 16:14
    Integrated into Tuleap 12.5.99.140
    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2021-02-18
    User avatar
    Thomas Gerbet (tgerbet)2021-02-12 16:02
    See gerrit #21773.
    • Summary
      -Force Chromium-based browsers to segment the cache to to defend against cache probing 
      +Force Chromium-based browsers to segment the cache to defend against cache probing 
    • Status changed from Under implementation to Under review
    User avatar
    Thomas Gerbet (tgerbet)2021-02-12 15:53
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes