Re: tag2upload (git-debpush) service architecture - draft

[Sam Hartman <hartmans@debian.org>]

>>>>> "Bastian" == Bastian Blank <waldi@debian.org> writes:

    Bastian> Hi Ian
    Bastian> On Wed, Jul 31, 2019 at 05:08:51PM +0100, Ian Jackson wrote:
    >> Bastian Blank writes ("Re: tag2upload (git-debpush) service
    >> architecture - draft"): > The hypothetical tool creates a
    >> complete .dsc file with the names and > checksums of the
    >> uncompressed files.  The user signed .dsc is put into > the tag.
    >> The point of the tag2upload exercise is to move the .dsc
    >> generation from the uploader's computer to a central service,
    >> because .dsc generation is complicated, slow, and inconvenient.
    >> So generating the .dsc on the user's system defeats the object of
    >> the exercise.

    Bastian> One last time: The user has to certify his upload in a way
    Bastian> the archive can verify.

Let me see if I'm correctly understanding this requirement.  You're
saying that given the dsc presented to dak by the tag2upload service,
dak needs to be able to verify the contents  of the DSC based on the
user's signature and no external data.

So, if the tag2upload service does some transformation to produce the
dsc:

1) dak needs to be able to verify the inputs to that transformation

and
2) confirm those inputs are certified back to a user signature.

Presumably this all needs to be doable using software we'd be
comfortable running as part of dak.

Have I understood your requirement?

--Sam