2 ms·
Presumably Microsoft would add a salt before losing all that business. Perhaps only if you turn on special NIST-mode, in the way of microsoft and backwards comp
by jrochkind1 10y ago
Presumably Microsoft would add a salt before losing all that business. Perhaps only if you turn on special NIST-mode, in the way of microsoft and backwards compatibility.
It might break some functionality, but probably not as much as moving to an entirely different product if you have things written against MS APIs.
- ckozlowski 10y agoThis is a great example of how smart standards can leverage incredible pressure against vendors to adopt best practices. What will happen is that if the new standard is accepted as is, every single implimentation will have to craft a Plan of Action and Milestones (POAM), and every security officer is going to write in "Waiting for vendor fix". That's a lot of pressure on Microsoft to change this. Will it take time? Certainly. Years in fact. But if you want massive change, this is how you start. I'm a big fan of Active Directory. But I applaud this move. I'm even more excited to see if this will filter down to banks. Probably not as quickly, but one can hope.
- dspillett 10y ago> Perhaps only if you turn on special NIST-mode That is pretty much how they worked the Posix compliance requirement for government/forces use for NT/2000: the API was available through an optional (and IIRC not quite complete) module that very few ever turned on even where it was a contractual requirement that it be present. The option you suggest could be present but no doubt not be in use by many people because extension-X, third-party-app-Y, or internal-automation-subsystem-Z, or some feature of AD itself, would break.