[login_manager] Use keygen helper to generate owner key

[login_manager] Use keygen helper to generate owner key

Generates the owner key in the session manager, and deprecates SetOwnerKey.  
The change which makes Chrome savvy to this is at http://codereview.chromium.org/6538098/

In the window between landing this and landing the chrome change (which I will try to minimize), ownership will be taken successfully on first login, but the user won't be able to do owner-things (whitelisting, turning off guest mode, etc) until his second login.  Once the chrome change lands as well, this issue will go away. 

BUG=9608
TEST=unit, smoke suite, and also OwnershipTaken and OwnershipNotRetaken autotests

Change-Id: I08504966d9e682f181b317837299cbf6c07c6ecc

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=78fe078

[Chris Masone, 2011-02-20 01:17:46]

PTAL, when you get a chance.  Still have to do the chrome side of this.

[Chris Masone, 2011-02-23 03:04:20]

Ping?

On 2011/02/20 01:17:46, Chris Masone wrote:
> PTAL, when you get a chance.  Still have to do the chrome side of this.

[Will Drewry, 2011-02-23 03:30:16]

LGTM with one question!

This is surprisingly clean :)

http://codereview.chromium.org/6469072/diff/2001/session_manager_service.cc
File session_manager_service.cc (right):

http://codereview.chromium.org/6469072/diff/2001/session_manager_service.cc#n...
session_manager_service.cc:558:
file_util::GetHomeDir().AppendASCII(kTemporaryKeyFilename).value());
I was going to suggest a random location, but since the private key should be in
nss, it seems fine to put the public key in the home dir.  Is this a safe
assumption?

[Chris Masone, 2011-02-23 04:07:49]

On Feb 22, 2011 7:30 PM, <wad@chromium.org> wrote:
>
> LGTM with one question!
>
> This is surprisingly clean :)
>
>
>
http://codereview.chromium.org/6469072/diff/2001/session_manager_service.cc
> File session_manager_service.cc (right):
>
>
http://codereview.chromium.org/6469072/diff/2001/session_manager_service.cc#n...
> session_manager_service.cc:558:
> file_util::GetHomeDir().AppendASCII(kTemporaryKeyFilename).value());
> I was going to suggest a random location, but since the private key
> should be in nss, it seems fine to put the public key in the home dir.
> Is this a safe assumption?
>

That the private key is in nss?  Yes, that's a safe assumption.

And the session manager validates that the public key it got has a
counterpart in the user's nssdb.


>
> http://codereview.chromium.org/6469072/