Secure Coding mailing list archives
Re: free lunch almost over
From: "Steven M. Bellovin" <bellovin () acm org>
Date: Tue, 01 Feb 2005 21:59:55 +0000
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
Current thread:
- free lunch almost over Gunnar Peterson (Feb 01)
- Re: free lunch almost over Jeff Williams (Feb 01)
- Re: free lunch almost over ljknews (Feb 01)
- Re: free lunch almost over Jeff Williams (Feb 01)
- Re: free lunch almost over ljknews (Feb 02)
- Re: free lunch almost over Jeff Williams (Feb 02)
- Re: free lunch almost over ljknews (Feb 02)
- Re: free lunch almost over ljknews (Feb 01)
- Re: free lunch almost over Jeff Williams (Feb 01)
- <Possible follow-ups>
- Re: free lunch almost over Steven M. Bellovin (Feb 01)
- Re: free lunch almost over Gunnar Peterson (Feb 01)
- Re: free lunch almost over Carl G. Alphonce (Feb 02)
- RE: free lunch almost over Wall, Kevin (Feb 02)