... then it's true that all said code is owned by Microsoft and they could revoke its license.
Not so! The GPL states in paragraph 4 that the license cannot be revoked as long as the licensee stays in compliance with the GPL. For Microsoft to be able to close up it's GPLed stuff it would need to prove that every licensee in the whole world collectively has violated the GPL (and thereby nullified their license). Not bloody likely!
Does anyone know under what license gnutella is/was distributed? I couldn't find any. The 'gnu' in gnutella suggests a GPL license, in which case the source code should be made available too. Then the entire community can work on it, with or without AOL employees.
Hey, why don't you come to my talk to hear for yourself?:-) The tamper resistance comes from storing keys in an iButton (or other JavaCard) instead of on harddisk. For the RKE stuff you're right: that does change IPSec itself (it's the addition of a new encryption protocol).
As for the export controls, did you follow the recent discussion on the FreeSWAN mailling list on why not to use US code yet? Until things have cleared up more, I won't mess with US crypto code. BTW the new regulations are in in effect only as of January, the SANE2000 paper abstract submission deadline was November 1999.
Some of the stuff seemed overly OS/Implementation dependent. eg: The stuff on tamper-resistant IPSec could be applied to NRL's IPSec code for BSD4.4. The chances are, though, it'll be specific to FreeS/WAN, and won't even apply to NIST's IPSec implementation for Linux.
As co-author of the tamper-resistant IPSec paper I cannot resist to comment on this. The algoritms and methods presented will not be FreeS/WAN specific, they have to be IPSec compliant. For the implementation however we had to choose a platform of course, and we picked FreeS/WAN. You're free to incorporate the stuff into BSD's IPSec code if you want too... the code will probably GPL'ed though, so you can still whine about that. Regarding the NIST's IPSsec implementation: did you bother to check where the authors live? Since we live in Germany and the Netherlands we cannot even get access to NIST's code, so we do not care about it!
Funny thing is that Google supposedly caches the pages it retrieves and that the cached version does not mention Netscape anywhere either. If M$ would be 'cloking' it would show in the cached page.
This is not a Blackdown release! They are at 1.2.2RC4. SUN has released the 'production' version of the SUN/Inprise port, which contains (older) Blackdown code. Not quite the same thing!
Slashdot Mirror
You failed the test for your internet license. Please disconnect and format your hard disk!
Regards,
Your examinator.
PS You flunked your public telephone usage test too.
Not so! The GPL states in paragraph 4 that the license cannot be revoked as long as the licensee stays in compliance with the GPL. For Microsoft to be able to close up it's GPLed stuff it would need to prove that every licensee in the whole world collectively has violated the GPL (and thereby nullified their license). Not bloody likely!
Does anyone know under what license gnutella is/was distributed? I couldn't find any. The 'gnu' in gnutella suggests a GPL license, in which case the source code should be made available too. Then the entire community can work on it, with or without AOL employees.
As for the export controls, did you follow the recent discussion on the FreeSWAN mailling list on why not to use US code yet? Until things have cleared up more, I won't mess with US crypto code.
BTW the new regulations are in in effect only as of January, the SANE2000 paper abstract submission deadline was November 1999.
As co-author of the tamper-resistant IPSec paper I cannot resist to comment on this. The algoritms and methods presented will not be FreeS/WAN specific, they have to be IPSec compliant. For the implementation however we had to choose a platform of course, and we picked FreeS/WAN. You're free to incorporate the stuff into BSD's IPSec code if you want too... the code will probably GPL'ed though, so you can still whine about that.
Regarding the NIST's IPSsec implementation: did you bother to check where the authors live? Since we live in Germany and the Netherlands we cannot even get access to NIST's code, so we do not care about it!
Funny thing is that Google supposedly caches the pages it retrieves and that the cached version does not mention Netscape anywhere either. If M$ would be 'cloking' it would show in the cached page.
FYI, the document mentioned on the Europarliament page (entitled "Development of surveillance technology and risk of abuse of economic information") is dated October 1999. The document itself is not available there however :-( My guess is that the document on the mirror site is a draft version of the same report. If not, it's worth a read anyway!
The best porn image filter you can get! Psst, wanna see some ASCII art naked ladies?
This is not a Blackdown release! They are at 1.2.2RC4. SUN has released the 'production' version of the SUN/Inprise port, which contains (older) Blackdown code. Not quite the same thing!