[...]
>> # When defining multiple keyids you can choose which of them you want to
>> # use for signing through the -u option on the command line.
>> $CONFIG{'keyid'} = [ qw{DE7AAF6E94C09C7F 62AF4031C82E0039} ];
>>
>> Would it make it?
>
> What about instead it said:
>
> # You can define mul
* Franck Joncourt [2009-05-25 17:22-0400]:
> [...]
> >> Would you consider noting this in the default configuration so that it
> >> will lead someone like myself to read more carefully that man page? :)
> >
> > Ok, I will update the sample configuration to mention it.
>
> # When defining multipl
[...]
>> Would you consider noting this in the default configuration so that it
>> will lead someone like myself to read more carefully that man page? :)
>
> Ok, I will update the sample configuration to mention it.
# When defining multiple keyids you can choose which of them you want to
# use fo
[...]
>> -u yourkeyid, --local-user yourkeyid
>>Select the key that is used for signing, in case you have more than
>>one key. To sign with multiple keys at once, separate multiple keyids
>>by comma. This option requires the key(s) to be defined through the
>>keyid variable in the
* Franck Joncourt [2009-05-25 16:52-0400]:
> Micah Anderson wrote:
> > * Franck Joncourt [2009-04-18 10:26-0400]:
> >> Hi,
> >>
> >> I did another test but no more luck.
> >
> > I think my problem was that I misunderstood that there is a difference
> > between -u and $CONFIG{'keyid'}. I think th
Micah Anderson wrote:
> * Franck Joncourt [2009-04-18 10:26-0400]:
>> Hi,
>>
>> I did another test but no more luck.
>
> I think my problem was that I misunderstood that there is a difference
> between -u and $CONFIG{'keyid'}. I think that your testing has shown
> that and that my issue should be
* Franck Joncourt [2009-04-18 10:26-0400]:
> Hi,
>
> I did another test but no more luck.
I think my problem was that I misunderstood that there is a difference
between -u and $CONFIG{'keyid'}. I think that your testing has shown
that and that my issue should be considered resolved.
I didn't w
Hi,
I did another test but no more luck.
Regards,
--
Franck Joncourt
http://debian.org - http://smhteam.info/wiki/
signature.asc
Description: OpenPGP digital signature
Arne Wichmann wrote:
> begin quotation from Franck Joncourt (in <49de6df1.2060...@dthconnex.com>):
>> I gave a try against 1.1-2 and I am unable to reproduce the problem.
>>
>> $ grep ^$.*keyid /home/thialme/.caffrc
>> $CONFIG{'keyid'} = [ qw{C872DCE08737DFA7 C490534E75C089FE} ];
>
> Hm. Maybe t
begin quotation from Franck Joncourt (in <49de6df1.2060...@dthconnex.com>):
> I gave a try against 1.1-2 and I am unable to reproduce the problem.
>
> $ grep ^$.*keyid /home/thialme/.caffrc
> $CONFIG{'keyid'} = [ qw{C872DCE08737DFA7 C490534E75C089FE} ];
Hm. Maybe the part in the documentation t
Hi,
I have done the same test in a lenny chroot using signing-party 1.0.2,
and I am still unable to reproduce the problem.
I have enclosed my test so you can have a look at it.
For Arne the problem I can see is the fact that caff imports the wrong key
[quote]
(526) a...@anhrefn $ gpg --list-key
Hi,
I gave a try against 1.1-2 and I am unable to reproduce the problem.
$ grep ^$.*keyid /home/thialme/.caffrc
$CONFIG{'keyid'} = [ qw{C872DCE08737DFA7 C490534E75C089FE} ];
$ ./caff -u 75C089FE -R --key-file /home/franck/thialme-test.asc CB777971
[INFO] Importing key C872DCE08737DFA7 from your
Package: signing-party
Version: 1.0-2
Severity: normal
Hi.
caff seems to ignore the key given using -u:
(526) [EMAIL PROTECTED] $ gpg --list-keys --fingerprint 9E783E05
pub 1024D/9E783E05 2006-07-14 [expires: 2013-07-12]
Key fingerprint = C476 70B8 8085 6000 B376 84CA 3325 5FE8 9E78 3E0
13 matches
Mail list logo
