Skip to content
This repository has been archived by the owner on Aug 24, 2019. It is now read-only.

The machine readable, verbose index should show signatures. #1

Open
PeterTheOne opened this issue May 5, 2015 · 2 comments
Open

The machine readable, verbose index should show signatures. #1

PeterTheOne opened this issue May 5, 2015 · 2 comments
Assignees
@cmars

Comments

@PeterTheOne
Copy link

The machine readable, verbose index (?op=vindex&options=mr) should show signatures, just like the non machine readable index. I think this is only logical. (I like that you included signatures in the JSONFormat.)

I hope this does not conflict with https://tools.ietf.org/html/draft-shaw-openpgp-hkp-00#section-5.2 that defines Machine Readable Indexes.
@cmars cmars self-assigned this May 5, 2015
@cmars
Copy link
Member

cmars commented May 5, 2015

I think this would be fine. SKS already emits a placeholder uat:::: record[1], which isn't in the draft spec. Clients should ignore record prefixes for those they're not equipped to handle.

How about:
sig:<signing key ID>:<creation date>:<expiration date>:<flags>

[1] http://keyserver.ubuntu.com/pks/lookup?search=0x44a2d1db&op=vindex&options=mr

@PeterTheOne
Copy link
Author

Thanks. What about certification level? Or what do you mean by flags?

emersion added a commit to emersion/go-openpgp-hkp that referenced this issue Sep 13, 2018
@emersion
Ignore unknown line types in indexes
0e76c24 
SKS already emits "uat" placeholders. Other keyservers might emit
other fields such as "sig". See [1].

[1]: hockeypuck/hkp#1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cmars cmars

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cmars @PeterTheOne