entd: move opencryptoki initialization out of entd

entd: move opencryptoki initialization out of entd

Look for a file /home/chronos/.cryptohome-init-pkcs11 and expect cryptohome to initialize the PKCS#11 token, disabling that interface in newer extensions.

Change-Id: I363ec0ef093d58d793a3d75e22dee96b58bdacd3

R=rginda@chromium.org
BUG=chromium-os:12304
TEST=
old extension / new entd (w/ and w/o flag)
new extension / old entd:
new extension / new entd (w/ and w/o flag):

When flag is set with new entd, Initialize button disappears and we wait for cryptohomed to signal the TPM token is ready.

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=3cb4347

[rginda, 2011-04-11 21:29:07]

On 2011/04/09 01:32:22, kmixter1 wrote:

LGTM as long as you wait until cryptohomed actually takes care of this
initialization.  Policy.CallbackError's don't automatically show up in syslog at
the moment, but it probably makes sense to change that.  Juat add an
'entd.syslog.error(data);' call in the definition of Policy.CallbackError.

[kmixter1, 2011-04-15 00:38:30]

PTAL - I updated this to include the corresponding base extension changes to
remove the UI for initializing the token and added UI for showing when the token
has not yet been automatically initialized.

[rginda, 2011-04-15 16:14:17]

On 2011/04/15 00:38:30, kmixter1 wrote:
> PTAL - I updated this to include the corresponding base extension changes to
> remove the UI for initializing the token and added UI for showing when the
token
> has not yet been automatically initialized.

LGTM

[kmixter1, 2011-04-19 02:23:08]

PTAL - pretty big direction shift - now change behavior based on a flag.

[rginda, 2011-04-19 16:39:30]

On 2011/04/19 02:23:08, kmixter1 wrote:
> PTAL - pretty big direction shift - now change behavior based on a flag.

LGTM