On Tue, Aug 30, 2005 at 10:08:38AM -0700, Wilkerson, Bryan P wrote: > they're work, I'm not sure I'd trust or use the data unless it was > somehow authenticated.
I doubt many testers would be willing to register on yet another website just for this. So I doubt adding authentication is a good idea. However if you really want to authenticate I could add an email based authentication method similar to the CPUShare authentication method that is already implemented and fully secure. Then I can add a button to hide all not authenticated users from the listing. Things will be substantially more complicated on the server side, so I'd rather prefer that we solve the below points first. > 2. Some of us sit behind corporate firewalls and proxies that have > oppressive rules that would have made Stalin proud. The solution must > be proxy aware and if it used HTTP, even better because it's more likely > to work anywhere. The proxy settings could also be a .config thing. I can easily add a second entry point to the server that can pass through the proxy no problem. > 3. Again security; I haven't cleared this with my corporate superiors > but I'm not sure they'll like the fact that anyone could intercept the > data and compute how many people in the company are running Linux test > kernels. I know this almost sounds anti-open but we're breaking them in > slowly to the model and I don't think they are ready for this one just > yet. :) Sure I understand, KLive wasn't thought in terms of corporate firewalls that must hide anything behind the firewall (I wonder how the proxy prevents the people to search in google though, I bet a few of the cleartext search queries and the syn and tcp timestamp sequence numbers will reveal much more than whatever could ever be sent to klive in cleartext ;). Then I guess all you need is that I use a https instead of http for the secondary entry point discussed above (assuming your proxy lets you do https). Still the routing points of the internet could count the syn packets that you send to klive.cpushare.com and by watching the statistics with many computers coming from the same host md5-sum they may be able to guess which is the "host" that corresponds to the IP that is sending the many syns. So before I add features for your special needs I'd rather make sure that you can live with this worst case condition of the "syn" guessing coming from your proxy and with destination klive.cpushare.com. Thanks a lot! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/