summaryrefslogtreecommitdiff
path: root/lib/nickserver/hkp
AgeCommit message (Collapse)Author
2016-06-15we don't need FetchKeyInfo anymore including in SourceAzul
2016-06-14introduce Hkp::ClientAzul
wraps the hkp protocol
2016-06-14use adapter for FetchKeyInfoAzul
2016-06-11use the adapter not EM in hkp sourceAzul
2016-06-10turn Hkp::FetchKey into Hkp::SourceAzul
The source was really just an empty shell now that we pushed the em specific stuff further down.
2016-06-09refactor: remove EM specific stuff from Hkp::FetchKey interfaceAzul
2016-06-09add Hkp::Source with same interface as CouchDB::SourceAzul
2016-06-09refactor: introduce Hkp::ResponseAzul
2016-05-25simplify KeyInfo. remove unneeded accessorsAzul
2016-05-25copy over all files from rewritten attemptAzul
I started a nickserver from scratch to implement the things that are independent of our choice of stack (eventmachine or other). This commit copies them over and tests both things in parallel.
2016-05-25rubocop: initialize and use ruby 1.9 hash syntaxAzul
2016-04-10minor tweaks to hkp response parsingAzul
Only parse responses that have status code 200 (OK). Simplify status code handling a bit Also profiled it to see if duplicate calculations matter. They don't (2ms for validating 12 keys)
2016-04-10bugfix: 404 if no key matches, fixes #6789Azul
I also separated the parsing of the hkp response from FetchKeyInfo. This way FetchKeyInfo has the EM specific code that has sideeffects and the logic is in a class without sideeffects and (almost) without state. The only state we keep is the KeyInfo array that contains all the information the server returns. This way we avoid parsing the response multiple times.
2013-08-06fix crash when fetched key is rejected (e.g. too short, etc), report errors ↵elijah
in the request, prevent most crashes by catching exceptions.
2013-05-15add CouchDB support.elijah
2013-05-13s/sks_url/hkp_urlelijah
2012-12-24initial commitelijah