This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Reasons to celebrate - passed 1K active probes :)
- Previous message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
- Next message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri Dec 23 17:36:41 CET 2011
On 12/23/11 17:27 , Rodolfo kix Garcia wrote: > If some people want to run different code, they need the interface to > communicate with the atlas infrastructure (commands, arguments,...), > and probably this info is in the source code ;-) therefore, you won't > have problems. I'm not worried about people getting their modified firmware to talk to the atlas infrastructure. A lot of that stuff is even documented :-) The problem is, do you trust those results to be correct? And it is not just faking results. That can be done today, to some extent. But more, what if somebody decides to improve traceroute and it works just slightly different and gives also just slightly different results?
- Previous message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
- Next message (by thread): [atlas] Reasons to celebrate - passed 1K active probes :)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]