Comments on: Why Device Lock PIN/Password must be configured with Windows Mobile 6.1 Device Encryption

By: Helmut

Helmut — Thu, 27 Nov 2008 06:05:00 +0000

Thats very bad because we want to use our own LAP and support the builtin encryption. Even Microsofts support will not “let us know” how to do it.

But i am quite sure that a LAP has to set the LAP_CAPABILITIES_MASTER_KEY flag on initialisation and handle the following VeryUser in the correct way ….

If you have any additional information about this, it would be nice you let me know.

Regards …. Helmut

By: dfield

dfield — Wed, 26 Nov 2008 23:31:12 +0000

Hello Helmut,
The device encryptioin feature in WM 6.1 was built to work only with the built-in PIN/Password LAP. I confirmed this with the Microsoft Windows Mobile Product Group. Support for encryption of the user master key by a custom LAP is unsupported. Sorry about that.

By: Helmut

Helmut — Tue, 25 Nov 2008 14:15:45 +0000

For encrypting Mobile 6.1 devices; a LAP (Mirosofts LAP) has to set the logon password to enable the encryption mechanism.

If you replace the original LAP (after encryptins some file) it is not possible to access the encrypted data any longer.

Which functionality must my own LAP implement (which OS function must be called) to tell the entered PIN to the system?

… Helmut

By: csaintamant

csaintamant — Tue, 29 Jul 2008 20:48:32 +0000

Correct, you can now implement encryption of main memory on WM6.1 devices.

By: derek

derek — Tue, 29 Jul 2008 15:14:17 +0000

Does this mean the you can now encrypt files on the main memory of a PDA running WM6.1 ?