I'm suprised that Microsoft isn't tyring to cloud the issue by talking about the associations of the persons who gave the talk.
Wittfield Diffie is an engineer at Sun Microsystems, one of the only corporations that can be considered a Microsoft competitor. Ron Rivest is a professor as his day job, but gets quite a bit of cash from RSA, and Microsoft isn't using any of the code that RSA provides (BSAFE, etc) in Paladium, so that's a big chunk of change that won't be coming his way.
We here on slashdot may realize that Rivest and Diffie are actually quite excellent individuals in their field, but these kinds of conflicts of interest are frequently what will be pulled out to counter an argument, rather than working from the facts themselves.
Of the "Hacking Exposed" line, there are two good books, Hacking Linux and Hacking Windows 2000. Both of these are able to stay on one OS and cover everything that needs coverage. Hacking Exposed tries to cover everything (come on, who cares about breaking into your PBX and listening to people's voice mail?) and thus can't give any of them the space they actually need. The unix stuff in Hacking exposed is incomplete to say the least. The J2EE book might be good (I haven't read it) but the Web one is definately inferior to the one by Stuart that he did with Addison Wesley. Now why do you think one of the big wig HE authors went to a different publisher to write a book that was also being written under the HE title? I suspect it was to get away from the problems of the HE style. I agree with the reviewer - the risk ratings are not helpful at all, and HE is cluttered with too many pretty icons.
I bet that the Hacking Linux authors were forced to follow the HE format, and in spite of that they wrote a great and readable book.
Also, anyone know why Kurtz is just a "series Consultant" for this one?
Slashdot Mirror
Wittfield Diffie is an engineer at Sun Microsystems, one of the only corporations that can be considered a Microsoft competitor. Ron Rivest is a professor as his day job, but gets quite a bit of cash from RSA, and Microsoft isn't using any of the code that RSA provides (BSAFE, etc) in Paladium, so that's a big chunk of change that won't be coming his way.
We here on slashdot may realize that Rivest and Diffie are actually quite excellent individuals in their field, but these kinds of conflicts of interest are frequently what will be pulled out to counter an argument, rather than working from the facts themselves.
Of the "Hacking Exposed" line, there are two good books,
Hacking Linux and Hacking Windows 2000. Both of these are able to stay on one OS and cover everything that needs coverage.
Hacking Exposed tries to cover everything (come on, who cares about breaking into your PBX and listening to people's voice mail?) and thus can't give any of them the space they actually need. The unix stuff in Hacking exposed is incomplete to say the least.
The J2EE book might be good (I haven't read it) but the Web one is definately inferior to the one by
Stuart that he did with Addison Wesley. Now why do you think one of the big wig HE authors went to a different publisher to write
a book that was also being written under the HE title? I suspect it was to get away from the problems of the HE style. I agree with the reviewer - the risk ratings are not helpful at all, and HE is cluttered with too many pretty icons.
I bet that the Hacking Linux authors were forced to follow the HE format, and in spite of that they wrote a great and readable book.
Also, anyone know why Kurtz is just a "series Consultant" for this one?