|
Large scale WIFI deployment WEP config
I took a good look at the Wifi-WEP registry configuration based upon the information Dell gave us two days ago. For an individual device, a valid, entered WEP connection is stored in the registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WZCSVC\Param eters\Interfaces\ODIM\TIACXWLN1]
The "ActiveSettings" binary contains a combination of the SSID and an "encrypted" value of the WEP entered for that configuration. The little documentation I have looked at indicates that the use of this key is dictated by the vendors(Dell) of the wifi adapter.
Any restoration of that key almost gets you to where you need to go with deploying that key to multiple devices.
HOWEVER....
The WEP is encrypted in this registry key using OS generated MasterKeys "default.mky" & "System.mky" located in /windows. It both keys are required for the Crypto as some sort of "Public/PrivateKey" decoding of the WEP from the above registry key.
The "default.mky" is OS generated real time when it's needed from the internal crypto api. (The OS also regenerates a NEW(and of course different" key on a soft/hard restart if the default.mky file is deleted or "corrupt"). The "System.mky" is generated by your driver when it saves the WEP information in the WZCSVC entry.
Deletion/corruption of either the "System.mky" or "default.mky" prevents decoding of the registry key containing the WEP for your driver. (This requires the user to re-enter the information from scratch using the Dell WLAN Utility).
So, why don't I just import the registry key, plus copy the "default.mky" & "System.mky" files along to each device....
Well..the best I can discern, is that there is internal Crypto SEED/RNG values or a CRC check used to verify that integrity of the "default.mky" and therefore the "System.mky" when they are used for each device. If they are invalid, the OS will replace the "default.mky" with a new one, invalidating any registry encrypted entries.
Where did I go next? Well..there is a registry entry:
[HKEY_LOCAL_MACHINE\init\BootVars]
"MasterKeysInRegistry"=dword:1
What this does is store the masterkeys into the registry under:
[HKEY_LOCAL_MACHINE\System\DPAPIKeys\default] ....
&
[HKEY_LOCAL_MACHINE\System\DPAPIKeys\System] ...
So, I tried that...I backed up the registry and then imported the required keys to a different device, but the OS saw it with the same SEED/RNG check, and replaced the keys with newly generated keys, thus invalidating the WEP decryption by your driver as before.
Now, I'm stuck. This is where I'd like your help.
Thanks.
__________________
JIM
|