Distributed OS: Winter 2011: Difference between revisions
No edit summary |
|||
| Line 35: | Line 35: | ||
===3: Limiting the spread of malware=== | ===3: Limiting the spread of malware=== | ||
Group members: keith, Andrew | Group members: keith, Andrew, David Barrera | ||
===4: Bandwidth hogs=== | ===4: Bandwidth hogs=== | ||
Revision as of 18:33, 19 January 2011
Readings
January 13, 2011: CCR (two papers)
January 18, 2011: OceanStore and Pond
Internet Governance
Problems to Solve
- Attack computers with almost no consequences
- DDoS
- botnets
- capture and analyze private traffic
- distribute malware
- tampering with traffic
- Unauthorized access to data and resources
- Impersonate computers, individuals, applications
- Fraud, theft
- regulate behavior
Design Principles
- subjects of governance: programs and computers
- bind programs and computers to humans & human organizations, but recognize binding is imperfect
- recognize that "bad" behavior is always possible. "good" behavior is enforced through incentives and sanctions.
- rules will change. Even rules for rule changes will change. Need a "living document" governing how rules are chosen and enforced.
Scenarios
1: Stopping DDoS
Group members: Seyyed, Andrew Schoenrock, Thomas McMahon
2: Stopping phishing
Group members: Waheed Ahmed, Nicolas Lessard
3: Limiting the spread of malware
Group members: keith, Andrew, David Barrera
4: Bandwidth hogs
Group members: Mike Preston, Fahim Rahman, Michael Du Plessis
- limit bandwidth for each user
- if user has significant bandwidth demands for a certain period of time
- add them to a watch list
- monitor their behaviour