In message <[EMAIL PROTECTED]>, Gunnar Peterson writes: >If you do the math on what comes next after the processor >manufacturers' free lunch is over, the implications to concurrency, >security, and privacy are huge: > >http://www.gotw.ca/publications/concurrency-ddj.htm > >How do traditional security mechanisms function in a massively >concurrent world? How relevant are they? What new security designs are >needed? Is it too late to bail and head for academia? > >-gp >
I think this sentence from the essay gives the answer, at least from a security perspective: Probably the greatest cost of concurrency is that concurrency really is hard: The programming model, meaning the model in the programmer?s head that he needs to reason reliably about his program, is much harder than it is for sequential control flow. We all know what hard programming tasks are likely to do to security... --Steve Bellovin, http://www.stevebellovin.com
