No, actually I meant that they know the 32 bit version is broken because un-wanted code can run in kernel mode:
"... because of all of the unsigned malware that runs in kernel mode can get around content protection..."
I wasn't saying I liked their "solution" of requiring signing, just that they appear to know that the 32-bit version is broken and they don't plan on fixing it (or at least that's what it suggests to me). And the article appears to suggest that the 64-bit version is not (or at least less) broken. Not that I really expect MS to be able to stop people from having their way with the 64-bit version as well. It's just that this seams to imply that they've given up on making the 32-bit version secure.
I wasn't berating their lack of technical ability. But rather the fact that MS appears that they don't even want to try (at least for the 32-bit version).
"This is a decision that the Media Player folks made because there are just too many ways right now for unsigned kernel mode code [to compromise content protection]."
So basically MS knows that the 32-bit version is inherently broken and yet they are putting it out any way? Thanks MS. I'm glad to know exactly how much you value the users of your offerings.
Slashdot Mirror
No, actually I meant that they know the 32 bit version is broken because un-wanted code can run in kernel mode: "... because of all of the unsigned malware that runs in kernel mode can get around content protection..."
I wasn't saying I liked their "solution" of requiring signing, just that they appear to know that the 32-bit version is broken and they don't plan on fixing it (or at least that's what it suggests to me). And the article appears to suggest that the 64-bit version is not (or at least less) broken. Not that I really expect MS to be able to stop people from having their way with the 64-bit version as well. It's just that this seams to imply that they've given up on making the 32-bit version secure.
I wasn't berating their lack of technical ability. But rather the fact that MS appears that they don't even want to try (at least for the 32-bit version).
"This is a decision that the Media Player folks made because there are just too many ways right now for unsigned kernel mode code [to compromise content protection]."
So basically MS knows that the 32-bit version is inherently broken and yet they are putting it out any way? Thanks MS. I'm glad to know exactly how much you value the users of your offerings.
Is upgrading to Netware 6.5 totally out of the question?
If not what about upgrading to 6.5, enabling CIFS and using windows to run a script to map drives?
I mean you could just make a .bat file with a bunch of net use statements to map the drives once CIFS is going.