News for hackers. Stuff that matters.
Re:Intel delays chip-making changes by AnimalMuppet on Thursday July 16, 2015 @05:17PM (#9899928)
I don't even want to think about the antivirus implications of running FPGA code.
Re:Intel delays chip-making changes by nickpsecurity on Thursday July 16, 2015 @11:56PM (#9901219)
It could get interesting. Of course, for secure CPU developers, FPGA's have been the solution for stopping malware rather than the problem. Too bad we only have prototypes to work with so far. Remember, though, that there's always anti-fuse (write-once) FPGA's available for a design you don't plan to change.
Re:Intel delays chip-making changes by nickpsecurity on Friday July 17, 2015 @12:24PM (#9903486)
Oh I forgot to give you this to help you sleep better at night:

http://www.cis.upenn.edu/~jms/papers/fpgavirus.pdf

Re:Intel delays chip-making changes by monocasa on Friday July 17, 2015 @01:04PM (#9903710)
Eh, as long as it's on the other side of a hardware based IO-MMU, I'm not super concerned.
Re:Intel delays chip-making changes by nickpsecurity on Friday July 17, 2015 @03:22PM (#9904704)
Those are overhyped so as to be buzzwords. All the IO-MMU really does is make the data come to and go from a certain point of memory. What it does when it hits the system software or applications is a whole, different risk area. See OS process separation vs all the ways it's bypassed with app & kernel-level vulnerabilities.

So, you consider that the FPGA might sabotage data you send through it or what comes from it. Be monitoring or doing validation on both.