Thanks for the info, Moheeb! On 06/15/2012 11:35 AM, [email protected] wrote: > Regarding the TLS bouncing idea. > As the reputation system derives features in part from the submitted > pings, it's important for us to be able to detect abusive reputation > requests. The source IP is a very meaningful feature for detecting > spammy requests. Furthermore, if we get requests from a sufficient > number of users for the same url, we may also attempt to fetch it to > feed the binary into our analysis system. I would like to emphasize that > this data is only kept for two weeks and is subject to strict access controls. > > A trusted proxy run by Mozilla might be an option if it did its own > meaningful spam filtering and additionally provided us at least with > the /24 of the source IP address from the original requester.
So it sounds like a proxy is possible if we send along the first three octets. If we deploy this feature opt-in, I'm not convinced we need to proxy. If we deploy the feature on by default, we might want to consider this. There are a few more open questions, and I know this sounds a bit like an inquisition, but given the lack of a public API or any other feature documentation, I just want to get all the facts on the table: 1. To be explicit, some folks here are curious why we can't just submit a URL hash prefix like for the rest of the safe browsing stuff? I'm assuming it is because of what you say above (if a lot of pings have the same URL, you grab it and do analysis), but can you explain why the whole URL/hash/size are needed? 2. What types of downloads are subject to this filter? Just .exe? (And how do you determine the filetype, extension)? 3. How aggressively are you purging logs of the pings? Some users are concerned about your service being compelled by some legal proceedings to turn over data about their IP address's download habits. 4. Is there any chance we could offer users who want it a "no-ping" option? (This would be a hypothetical client-side whitelist updates but no pings with URL/hash/size.) -Sid _______________________________________________ dev-security mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security
