[Lunar Linux 0000332]: gpg SOURCE_VFY pubkey method fails for keyservers

[noreply at bugs.lunar-linux.org]

The following bug has been RESOLVED.
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000332
=======================================================================
Reporter:                   elaine
Handler:                    sofar
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000332
Category:                   theedge (core tools)
Reproducibility:            always
Severity:                   major
Priority:                   low
Status:                     resolved
Resolution:                 fixed
=======================================================================
Date Submitted:             2003-08-08 18:27 GMT
Last Modified:              2003-10-05 12:07 GMT
=======================================================================
Summary:                    gpg SOURCE_VFY pubkey method fails for keyservers
Description: 
where a pgp sig/pubkey are intended to be:

gpg:<url-to-detached-sig>:<url-to-public-key>

Most keyservers seem to run on port 11371 where urls like:

gpg:<url-to-detached-sig>:http://server:11371/path 

because the code uses 'cut -d: ...' and the :portnum introduces an
unwanted field. I was unable to find a 
delimiter character which would be not collide with
common urls / shell metacharacters.

Additionally all keyservs I could find are using shell
metas in other parts of their URLs, further complicating
the module-writing process.


=======================================================================

-----------------------------------------------------------------------
 sofar - 2003-10-05 12:07 GMT 
-----------------------------------------------------------------------
for now, the gpg: syntax uses the following setup:

SOURCE_VFY[N]="gpg:[url including :: chars][space][url including ::
chars]"

this solves this issue for now.