The concept of being able to refer to a signature with a label isn’t what I’m referring to, it’s how the label is built. Those prefixes are paths in etcd, which doesn’t actually matter to the sign package.

On Apr 23, 2014, at 10:15 AM, Jonathan Boulle <notifications@github.com> wrote:

> In sign/job.go:
> 
> >  	payloadPrefix = "/payload/"
> >  )
> >  
> > -// TagForPayload returns tag used for payload
> > +// TagForJob returns a tag used to identify and store signatures for a Job
> Not strictly true: see func (sc *SignatureCreator) SignJob(j *job.Job). It's used as the "label" of the SignatureSet.
> 
> I agree that it's awkward at the moment, it confused me when I first came across it. Let me mull on it.
> 
> —
> Reply to this email directly or view it on GitHub.
>