ext Andrew Flegg <and...@bleb.org> writes:

> So the key is the key. All of the entries on my N810 have *two* "key"
> elements per entry, and there's already one for "maemo-extras"
> (although maemo.org Extras for diablo's Release file is not signed).
> Some questions:
>
>   * The name of a domain is only to allow manipulation with
>     hildon-application-manager-config?

That and for naming the files in /var/lib/hildon-application-manager/
that store the list of packages in each domain.

>   * What is the effect of two "key" elements against a domain entry?
>     How would they have got there?

You can use either of the keys to sign the repo.  The idea is that one
of the keys is in use, and the other is in the safe.  Then when the
first key is compromised, you can roll-over to the second one and update
the domain configuration to drop the first key.

>   * Any ideas where the "maemo-extras" one has come from?

The key?  We made them together with the rest of the keys, to be
prepared.  The guys in charge of the repositories on maemo.org should be
able to start signing with it right away, I think.  (I.e., they have the
private half of the first key somewhere ready on the server to be used.)

> Fair enough. I suppose the only outstanding question is whether Nokia
> will push out one last SSU to include the "maemo-community-updates"
> package which correctly sets up the package domain for maemo.org
> Extras.

The only difference between Nokia doing it and the community doing
it[1], is the little <certified/> flag in the nokia-system package
domain: when the community does it, there will be the usual legal
warning to click through, when Nokia does it, the warning wont be shown.
That's the only difference.  I wouldn't plan with Nokia's support.

[1] It always pains me when I have to put Nokia on one side, and the
community on the other.  I was hoping that Nokia would be a member of
the community itself, but doesn't seem to happen.

> Once we've got this sorted, I'm happy to produce and push the various
> packages (assistance always welcome, of course - especially with the
> osso-software-version-rx*).

I can make hildon-application-manager releases, of course, and give out
write access to repos, as far as needed.
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Reply via email to