schnurrito@discuss.tchncs.de to Privacy@lemmy.dbzer0.com · 7 days agoWebsites have a new way to spy on visitors: analyzing their SSD activityarstechnica.comexternal-linkmessage-square39linkfedilinkarrow-up199arrow-down12cross-posted to: security@lemmy.mlprivacy@lemmy.mlpulse_of_truth@infosec.pub
arrow-up197arrow-down1external-linkWebsites have a new way to spy on visitors: analyzing their SSD activityarstechnica.comschnurrito@discuss.tchncs.de to Privacy@lemmy.dbzer0.com · 7 days agomessage-square39linkfedilinkcross-posted to: security@lemmy.mlprivacy@lemmy.mlpulse_of_truth@infosec.pub
minus-squareflambonkscious@sh.itjust.workslinkfedilinkEnglisharrow-up3·6 days agoInteresting ideas in here, particularly the timer precision
minus-squaresp3ctr4l@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up6·6 days agoWaterfox seems to already have a default of 1000 microseconds, if… I think, you go with ‘strict’ privacy settings option? So on the one hand, a very brief perusal of the paper shows that the method needs like, sub 200 timings to work well. On the other hand… I have no idea if the exploit method effectively circumvents the way this timing speed limit actually works. I basically just sped read everything lol.
minus-squarewyldrstallyns@lemmy.dbzer0.comlinkfedilinkarrow-up1·6 days agoSo, you’re saying you only needed one timer?
Interesting ideas in here, particularly the timer precision
Waterfox seems to already have a default of 1000 microseconds, if… I think, you go with ‘strict’ privacy settings option?
So on the one hand, a very brief perusal of the paper shows that the method needs like, sub 200 timings to work well.
On the other hand… I have no idea if the exploit method effectively circumvents the way this timing speed limit actually works.
I basically just sped read everything lol.
So, you’re saying you only needed one timer?