Re:Rubygems.org AWS bill for Feb 2014 [pdf]
by sitkack on Wednesday March 05, 2014 @12:42AM
(#7345517)
Mirrors shouldn't be a security concern, the signatures of packages should come from "headquarters", same goes for reliability, clients should be able to, and SHOULD pull from multiple sites simultaneously.
[ Parent
| on HN ]
Re:Rubygems.org AWS bill for Feb 2014 [pdf]
by michaelt on Wednesday March 05, 2014 @03:39AM
(#7345996)
Even if package signing works perfectly, when I connect to a mirror and request a patch for foo, the mirror learns my IP address and the fact I have an as-yet-unpatched version of foo.
Re:Rubygems.org AWS bill for Feb 2014 [pdf]
by evanphx on Wednesday March 05, 2014 @01:08AM
(#7345619)
Very true on the signatures. Using multiple sites isn't necessary though, imho.
Re:Rubygems.org AWS bill for Feb 2014 [pdf]
by sitkack on Thursday March 06, 2014 @03:26AM
(#7352547)
I could be wrong, but it seems like a nice hack to pull for say 3 mirrors at the same time at some offset into the resource using a range get for say, 16k each. The first one to complete does a pipelined request for another 16k slot and this process continues until the entire asset is downloaded. The fast mirrors would dominate, a small percentage of the bandwidth from slow mirrors would assist and truly slow mirrors would be ignored.