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] "Spoofing" tests.
- Previous message (by thread): [atlas] Using Atlas for commercial services
- Next message (by thread): [atlas] "Spoofing" tests.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Warren Kumari
warren at kumari.net
Sat Sep 7 19:24:12 CEST 2013
Apologies if this has already been discussed enlist -- I took a quick look though the archives and didn't see it. I believe that the reason for not allowing things like tests that send spoofed packets is that it might violate the AUP that participants have with their ISPs / be viewed by participants ISPs as an attack. So, what about having a checkbox in the Probe Settings that says something like: "I have no AUP with my ISP or I'm fine to violate my AUP. Run intrusive or dangerous tests on this probe" ? This would create a subset of probes that could be used for more interesting tests, an d would allow for greater visibility into things. W --- It is a mistake to think you can solve any major problem just with potatoes. --Douglas Adams
- Previous message (by thread): [atlas] Using Atlas for commercial services
- Next message (by thread): [atlas] "Spoofing" tests.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]