Swarm
a clustered load balancer for CC
Why?
- Reliability
- Performance
- Transparancy
How?
- Reliability - multiple nodes, failsafe
- Performance - emulator is in C, API in node.js
- Transparancy - program doesn't even know it was there.
Structure
Use Cases
- High Load Servers
- Protection against internal server DDoS
- Protection against Server Downtime
- Need for fast crypto operations
- Tracking Server Resource usage.
What's been done
Partially swarmc, the emulator used on the workers, is. It has colors implemented, some of OS, a openssl driven aes function, and more.
swarmd has bit implemented as well, that's the middle-man API.
How secure is it?
- Challenge Auth is used for registering a node, then it drops to exchanging pubkeys. Then all traffic is encrypted using generated keys. SSL is also able to be used ontop of it. (sign your keys!)
- Data from bridge to API is challenge auth as well.
Note: Challenge Auth is encrypting data to supposed password, then server tries to dcerypt it. On Success, password is right.
Resources
Swarm
By Jared Allard
