#1121 Negative values passed to key-find is being accepted as valid output.
Closed: migrated by dmoluguw. Opened by mrniranjan.

When negative values are passed to key-find , it's being accepted and default search is done giving 20 results.

pki -d /opt/rhqa_pki/certs_db -c Secret123 -p 30044 -h dhcp207-176.lab.eng.pnq.redhat.com -n "KRA3_agentV"  key-find --maxResults -5 
-----------------
20 key(s) matched
-----------------
  Key ID: 0x1
  Algorithm: 1.2.840.113549.1.1.1
  Size: 1024
  Owner: UID=mtest1,CN=mytest1
  Key ID: 0x2
  Client ID: a1
  Status: active
  Algorithm: AES
  Size: 128
  Owner: kra3admin
  Key ID: 0x3
  Client ID: mypass
  Status: active
  Algorithm: {1 2 840 113549 3 7}
  Owner: kra3admin
  Key ID: 0x4
  Client ID: temp32278
  Status: active
  Algorithm: AES
  Size: 128
  Owner: KRA3_agentV

Expected Results, When negative values are passed it should return error


Per CS/DS meeting of 08/25/2014: 10.2.3

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog

Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3

NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.

Per Bug Triage of 05/05/2016: 10.4

Metadata Update from @mrniranjan:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field lowhangingfruit adjusted to vakwetu: X
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: FUTURE (was: UNTRIAGED)

Per 10.5.x/10.6 Triage: FUTURE

mharmsen: negative case

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1684

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata