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/mat-wg@ripe.net/
[mat-wg] IPv6 extension headers support on RIPE Atlas
- Previous message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
- Next message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jen Linkova
furry13 at gmail.com
Wed Nov 6 16:41:12 CET 2013
On Wed, Nov 6, 2013 at 2:25 AM, Randy Bush <randy at psg.com> wrote: > jen, > > what, if any, is the danger in doing this? I see your point, Randy. I totally agree that allowing users to craft an arbitrary packet(header) might potentially trigger some bugs in software/hardware of intermediate routers or a target system. To ensure that RIPE Atlas is not used (intentionally or not) as a distributed attack system we could consider: - limiting # of probes simultaneously running such measurements to a low number. - requiring explicit permission of the probe owner to run such UDM. In that case I could not not see much difference between UDM and individuals crafting packets on their own. -- SY, Jen Linkova aka Furry
- Previous message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
- Next message (by thread): [mat-wg] IPv6 extension headers support on RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]