Welcome to CRUX bug tracking.

FS#1477 - signify: add the pubkey option for the sign command

Attached to Project: CRUX
Opened by Fun (fun) - Saturday, 23 September 2017, 22:03 GMT
Last edited by Tim Biermann (tb) - Thursday, 23 September 2021, 18:15 GMT
Task Type Feature Request
Category tools
Status Closed
Assigned To CRUX Developers (crux)
Operating System CRUX
Severity Low
Priority Normal
Reported Version 3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Using signify with keys from the ~/.ssh/ directory, or having names other than the repository name, will generate a .signature file that must be edited, because the first line is something like:

untrusted comment: verify with /dir/other/than/etc/port/

The attached patch makes it possible to sign ports with

signify -S -p /etc/ports/ -s /home/user/.ssh/y.sec ..

This will allow the use of:

pkgmk -us -sk ... -pk ...

to sign ports with keys from other directories than /etc/ports or avoid editing the .signature files.
This task depends upon

Closed by  Tim Biermann (tb)
Thursday, 23 September 2021, 18:15 GMT
Reason for closing:  Won't implement
Comment by Tim Biermann (tb) - Saturday, 18 September 2021, 15:07 GMT
In sakes of getting things moved one way or the other, I'll try to resolve the ticket.

@Fun: Do you still propose this patch?

Not sure if I'm a fan of the idea, and it hasn't had any response so far, so my uneducated guess is nobody else is.
Comment by Fun (fun) - Wednesday, 22 September 2021, 17:41 GMT
Sure. Drop it, as no one else want it.