Vulnerability Development mailing list archives
Re: distributed.net and seti@home
From: stefan () AESCHBACHER COM (Stefan Aeschbacher)
Date: Tue, 1 Feb 2000 10:44:15 -0800
Sen_Ml Sen_Ml wrote:
what's always bugged me about things like seti@home and distributed.net is the fact that they are in place to conduct massive network sniffing. all these clients on a lot of different networks running software that report some kind of info (who can tell what is sent?) to a central point...scares me. the fact that some of these projects don't release their source code makes it even worse.
even though they don't give you the source code, it's pretty easy to check whether the programm sets your network card in promiscuous mode (on unix ifconfig -a), so I think they wouldn't dare to do such a thing as it would become public pretty fast. There is still the danger of key-grabbing, so they should release the complete source code (and not only the algorithmic section as distributed.net does) EyeMix -- Never trust a runnig system
Current thread:
- Re: distributed.net and seti@home Sen_Ml Sen_Ml (Jan 30)
- Re: distributed.net and seti@home Stefan Aeschbacher (Feb 01)
- <Possible follow-ups>
- Re: distributed.net and seti@home Robert Wojciechowski Jr. (Jan 31)
- Re: distributed.net and seti@home Sebastian (Jan 31)
- Re: distributed.net and seti@home Clifford, Shawn A (Jan 31)
- Re: distributed.net and seti@home Seth R Arnold (Jan 31)
- Re: distributed.net and seti@home CyberPsychotic (Jan 31)
- Re: distributed.net and seti@home Oliver Friedrichs (Feb 01)
- Re: distributed.net and seti@home Iván Arce (Feb 02)
- Re: distributed.net and seti@home Oliver Friedrichs (Feb 01)
- Re: distributed.net and seti@home Sen_Ml Sen_Ml (Feb 01)
- Re: distributed.net and seti@home Kerneels (Feb 02)
- Re: distributed.net and seti@home Sen_Ml Sen_Ml (Feb 01)
(Thread continues...)