Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?

To: Spartex who wrote (30242)	2/10/2000 11:14:00 PM
From: ToySoldier	Read Replies (1) \| Respond to of 42771

To clarify, What I was saying was that I dont exactly know what the components of I-Chain are and also, now that I-Chain is so close to public release, it sounds as conceptual as it did when I learned about it last spring. I personally wouldnt have hope that it was announced with a ton more clarity to the industry. I do understand the basis of what I-Chain is suppose to accomplish, but when one dives deeper in the rubber hittin the road, how will it all be accomplished? I made my guesses as to what I think are the components. I still am excited at the I-Chain as a technology concept, I just hope Steve Adam's team has not finished polishing up the CIO message of what I-Chain is. Toy

To: Spartex who wrote (30242)	2/10/2000 11:27:00 PM
From: ToySoldier	Read Replies (3) \| Respond to of 42771

Actually, regarding BorderManager and Denial of Service attacks.... When I went the the vendor pre-release bootcamp of BorderManager, we were told that the beta of BM had a bug in it that Novell discovered when testing on their own WWW.NOVELL.COM production site. Aparently the BM server was hit by a denial of service attack by some hacker (dont remember the location of the related ISP). The problem was that the BM bug made an attempt to respond to the attack and did not just respond with one packet - it absolutely flooded response packets back to the source with as much bandwidth as could fit through the pipe. Now considering that Novell's web site is serviced by at least 1 T3 link (I believe its 2 or 3), it didnt take long for the ISP of the hacker to call Novell and asked why Novell's site was absolutely blowing the ISP out of the water by its own form of "denial of service" response (although completely by accident). Unfortunately since Novell is a member of the Internet Security association (dont recall the exact name), they were forced to report and repair the bug within a very short timeframe (I believe 2 days). But the Novell trainer asked the audience "who here feels that we should leave the bug in the code?" - everyone put up their hands. Dont know how true the story was but it was a good one and quite related to this recent set of events. :)) Cheers! Toy