Re: CURRENT: bhyve and Kernel SamePage Mergin

2016-06-09 Thread Shawn Webb
Hey David, I'm responding inline. On Thu, Jun 09, 2016 at 09:18:40AM +0100, David Chisnall wrote: > If this paper is the one that I think it is, then I was one of the reviewers. > Their attack is neat, but it depends quite a lot on being able to > deterministically trigger deduplication.

Re: CURRENT: bhyve and Kernel SamePage Mergin

2016-06-09 Thread David Chisnall
If this paper is the one that I think it is, then I was one of the reviewers. Their attack is neat, but it depends quite a lot on being able to deterministically trigger deduplication. Their proof-of-concept exploit was on Windows (and JavaScript attack was really fun) and I’m not convinced

Re: CURRENT: bhyve and Kernel SamePage Mergin

2016-06-08 Thread Pedro Giffuni
Hi oh; Nothing to worry: for good or bad, FreeBSD has no memory deduplication mechanism implemented. Pedro. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

CURRENT: bhyve and Kernel SamePage Mergin

2016-06-08 Thread O. Hartmann
A couple of days I got as a responsible personell for a couple of systems a warning about the vulnerabilities of the mechanism called "Kernel SamePage Mergin". On this year's IEEE symposion there has been submitted a paper by Bosman et al., 2016, describing an attack on KSM. This technique,