Re: Scheduler fixes for hyperthreading
From: Sam Lawrance (boris_at_brooknet.com.au)
Date: 05/22/05
- Previous message: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- In reply to: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- Next in thread: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- Reply: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Colin Percival <cperciva@freebsd.org> Date: Sun, 22 May 2005 15:10:28 +1000
On Sat, 2005-05-21 at 22:04 -0700, Colin Percival wrote:
> Sam Lawrance wrote:
> > I'm just curious here... would the mac_seeotheruids policy help in
> > obscuring the value of any information collected by a spy process?
>
> Yes. It would mean that the spy could steal an SSL certificate, but
> not know whose SSL certificate it was. :-)
Can the spy be sure that it's not just stealing fortunes though?
I mean for example, can the cache timings shown on page 7 of your paper
be used to reliably identify what the other thread on the CPU is?
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- In reply to: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- Next in thread: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- Reply: Colin Percival: "Re: Scheduler fixes for hyperthreading"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]