{"action":"created","issue":{"url":"https://api.github.com/repos/opendnssec/SoftHSMv2/issues/399","repository_url":"https://api.github.com/repos/opendnssec/SoftHSMv2","labels_url":"https://api.github.com/repos/opendnssec/SoftHSMv2/issues/399/labels{/name}","comments_url":"https://api.github.com/repos/opendnssec/SoftHSMv2/issues/399/comments","events_url":"https://api.github.com/repos/opendnssec/SoftHSMv2/issues/399/events","html_url":"https://github.com/opendnssec/SoftHSMv2/issues/399","id":328757021,"node_id":"MDU6SXNzdWUzMjg3NTcwMjE=","number":399,"title":"softhsm does not enforce lockout?","user":{"login":"nimbius","id":5444429,"node_id":"MDQ6VXNlcjU0NDQ0Mjk=","avatar_url":"https://avatars0.githubusercontent.com/u/5444429?v=4","gravatar_id":"","url":"https://api.github.com/users/nimbius","html_url":"https://github.com/nimbius","followers_url":"https://api.github.com/users/nimbius/followers","following_url":"https://api.github.com/users/nimbius/following{/other_user}","gists_url":"https://api.github.com/users/nimbius/gists{/gist_id}","starred_url":"https://api.github.com/users/nimbius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nimbius/subscriptions","organizations_url":"https://api.github.com/users/nimbius/orgs","repos_url":"https://api.github.com/users/nimbius/repos","events_url":"https://api.github.com/users/nimbius/events{/privacy}","received_events_url":"https://api.github.com/users/nimbius/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-06-02T16:22:41Z","updated_at":"2018-06-02T22:13:23Z","closed_at":null,"author_association":"NONE","body":"Unlike traditional HSM's, softhsm2 doesnt appear to enforce a lockout.  I can bang away with \r\n` pkcs11-tool --module /usr/lib/softhsm/libsofthsm2.so -l -t -O`\r\nand after numerous incorrect entries can still access the slot and perform an OK authentication against it.  \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/opendnssec/SoftHSMv2/issues/comments/394120815","html_url":"https://github.com/opendnssec/SoftHSMv2/issues/399#issuecomment-394120815","issue_url":"https://api.github.com/repos/opendnssec/SoftHSMv2/issues/399","id":394120815,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NDEyMDgxNQ==","user":{"login":"nimbius","id":5444429,"node_id":"MDQ6VXNlcjU0NDQ0Mjk=","avatar_url":"https://avatars0.githubusercontent.com/u/5444429?v=4","gravatar_id":"","url":"https://api.github.com/users/nimbius","html_url":"https://github.com/nimbius","followers_url":"https://api.github.com/users/nimbius/followers","following_url":"https://api.github.com/users/nimbius/following{/other_user}","gists_url":"https://api.github.com/users/nimbius/gists{/gist_id}","starred_url":"https://api.github.com/users/nimbius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nimbius/subscriptions","organizations_url":"https://api.github.com/users/nimbius/orgs","repos_url":"https://api.github.com/users/nimbius/repos","events_url":"https://api.github.com/users/nimbius/events{/privacy}","received_events_url":"https://api.github.com/users/nimbius/received_events","type":"User","site_admin":false},"created_at":"2018-06-02T22:13:23Z","updated_at":"2018-06-02T22:13:23Z","author_association":"NONE","body":"Understood.  If this is the case, then is there a purpose for the SO pin other than for the user to achieve familiarity with the concept as it applies to a real HSM?  Im having difficulty seeing how softHSM provides meaningful security if it stored, for example, a CA certificate used to sign CSRs.\r\n\r\nThank you for your help"}}
{"actor":{"display_login":"nimbius"}}