I've made a few edits[1] to those steps because the download manager
queues all downloads and the click scope may be dead at the time
downloads are completed. But when starting a download, you can pass a
command line to download manager and it gets run when the download is
completed. So the click scope installs a small script called
"install-helper" that calls packagekit and refreshes the dash with the
new icons when the installation succeeds.
So, to include signatures, it should be the click scope the one
skipping the queue and downloading the detached signature and
verifying its sha-512. And it should pass the path of the signature as
a parameter of the command line for install helper that gets passed to
download manager, and install helper should use it to call packagekit.
On Fri, Jun 27, 2014 at 9:30 AM, Marc Deslauriers /wiki.ubuntu. com/SecurityTea m/Specification s/ClickPackageS igning
<email address hidden> wrote:
> Here's the basic outline of how I think we should do this:
>
> https:/
Hi Marc, thanks for working on this.
I agree with the general approach.
I've made a few edits[1] to those steps because the download manager
queues all downloads and the click scope may be dead at the time
downloads are completed. But when starting a download, you can pass a
command line to download manager and it gets run when the download is
completed. So the click scope installs a small script called
"install-helper" that calls packagekit and refreshes the dash with the
new icons when the installation succeeds.
So, to include signatures, it should be the click scope the one
skipping the queue and downloading the detached signature and
verifying its sha-512. And it should pass the path of the signature as
a parameter of the command line for install helper that gets passed to
download manager, and install helper should use it to call packagekit.
[1] My edits are here: /wiki.ubuntu. com/SecurityTea m/Specification s/ClickPackageS igning? action= diff&rev1= 2&rev2= 3
https:/
cheers,
--
alecu