On Tue, Oct 20, 2009 at 12:47 PM, Mike Ter Louw <mter...@uic.edu> wrote: > The threat model of HistoryModule, as currently defined, seems to be > precisely the threat model that would be addressed by a similar module > implementing a per-origin cache partitioning scheme to defeat history timing > attacks.
Good point. I've added cache timing as an open issue at the bottom of the HistoryModule wiki page. > If these are to be kept as separate modules, then perhaps the threat model > should be more tightly scoped, and directive names should be specific to the > features they enable? It's somewhat unclear when to break things into separate modules, but having one module per threat seems to make sense. The visited link issue and the cache timing issue seem related enough (i.e., both about history stealing) to be in the same module. Adam _______________________________________________ dev-security mailing list dev-security@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security
