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] Feature request for Validated Timestamps
- Previous message (by thread): [atlas] Feature request for Validated Timestamps
- Next message (by thread): [atlas] Feature request for Validated Timestamps
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Apr 7 11:27:28 CEST 2021
On 2021/04/06 17:04 , Will wrote: > I'm not sure if there's a process for this sort of feature request > beyond this mailing list. Would it help if I propose a more concrete PR > against https://github.com/RIPE-NCC/ripe-atlas-software-probe > <https://github.com/RIPE-NCC/ripe-atlas-software-probe> To the extend that you would like secure geolocation in presence of a malicious probe, it would make sense to me to start with documenting the protocol you would like to use. The current way of geolocating probes works by having to probe report round trip times to a number locations. Obviously, a malicious probe could report any rtt value. I'm sure we can come up with a protocol if we have a sufficient number of trusted servers. However, such a protocol would need to be documented and deployed on those servers. Philip
- Previous message (by thread): [atlas] Feature request for Validated Timestamps
- Next message (by thread): [atlas] Feature request for Validated Timestamps
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]