Re:64-bit Linux Return-Oriented Programming
by runeks on Sunday February 15, 2015 @05:28PM
(#9054410)
How far has development come with the Mill CPU?
This video[1] mentions that "nothing with pins on the bottom" has been made yet.
Re:64-bit Linux Return-Oriented Programming
by Narishma on Sunday February 15, 2015 @05:31PM
(#9054419)
I've been hearing about it for years but it's still vaporware AFAICT.
Re:64-bit Linux Return-Oriented Programming
by reitzensteinm on Sunday February 15, 2015 @10:27PM
(#9055174)
Vaporware is a pretty harsh way to describe it. If everything went perfectly for the Mill team, they'd still not be shipping physical CPUs - it's an outrageously long and complex process. Giving them the benefit of the doubt for now doesn't seem unreasonable.
Re:64-bit Linux Return-Oriented Programming
by renox on Monday February 16, 2015 @04:37AM
(#9056015)
AFAIK they don't have also any FPGA prototype, nor any working backend compiler, so of course no OS working..
Their presentations are full of very nice ideas and I hope that they'll make it, but some are quite skeptical of their 'single address space' feature for example.
Re:64-bit Linux Return-Oriented Programming
by XorNot on Monday February 16, 2015 @05:31AM
(#9056159)
There's a long history of really good ideas on theory and in publications, that when it comes to actual implementation suddenly tear themselves apart due to all the practical compromises that always arise.
Apologies to those suffering Mill fatigue ;)
The Mill CPU is actually immune to these ROP exploits by the simple virtue of having a hardware-managed stack. The return address is not overwriteable.
We are also very firmly in the exploit mitigation camp generally, with our own particular twists to champion when the time comes.
So this article is very nice but very definitely focusing on here-and-now architectures. It'd be throwing the baby out with the bathwater to give up on hardening the architecture when starting over.