Mail in-toto-run snippet to functionary

[lukpueh]

A user requested a "send in-toto-run snippet to functionary as mail" button on the wrap up page. IMO it would be nice to have but we should first consider fixing #26.

[JustinCappos]

Perhaps it makes sense to ask the functionary to upload their public key at this point too. Or at least we wouldn't email them a private key, right? (Note, I understand this would be a mess to implement and I'm not proposing a login system / state for all of these layouts at this time. I more want us to think through what this could turn into in the future...)

…

On Wed, Sep 13, 2017 at 3:23 PM, lukpueh ***@***.***> wrote: A user requested a *"send in-toto-run snippet to functionary as mail"* button on the wrap up page. IMO it would be nice to have but we should first consider fixing #26 <#26>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#28>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA0XD1VTyRvKxPbIYw-KHg8e-oVkJ2wuks5siCuYgaJpZM4PWmb_> .

[lukpueh]

I'm not sure if I understand. Currently we ask the user to (generate and) upload the public keys so that we can create the layout with the specified authorizations.

This issue talks about something else, namely the in-toto-run snippets, which we provide on the last page as instructions for how functionaries should wrap their supply chain steps.

Also, the tool should never have access to functionary private keys, unless a user inadvertently uploads private keys.