getCertificate() gives invalid_argument with newest ID software
aixkalur opened this issue · comments
Why it is now disabled getting certificate with with AUTH filter?
window.hwcrypto.getCertificate({
lang: 'et',
filter: 'AUTH'
})
Example in Linux chrome code i can see, that it's now hard coded response as invalid_argument (similar line in osx and windows):
82d5f5c#diff-fe43588ba7b913eece962fff6f946b5298389c96751d5d86d93c51127cf776deR121
Result for this change is that i cannot create signature with PIN1, so i cannot handle login normally as i can only sign hash with PIN2.
Plugin log:
2021-02-08 16:23:15 [36088] main_block_invoke() [chrome-host.mm:80] Message size: 2
2021-02-08 16:23:15 [36088] main_block_invoke() [chrome-host.mm:95] Message (2): {}
2021-02-08 16:23:15 [36088] write() [chrome-host.mm:38] Response(37) {"result":"invalid_argument","ver":1}
2021-02-08 16:23:20 [36204] main() [chrome-host.mm:54] Starting native host 1.1.3.539
2021-02-08 16:23:20 [36204] main_block_invoke() [chrome-host.mm:80] Message size: 129
2021-02-08 16:23:20 [36204] main_block_invoke() [chrome-host.mm:95] Message (129): {"type":"CERT","lang":"et","filter":"AUTH","nonce":"u3ssh12wj729cx0r","src":"page.js","origin":"https://***","tab":66}
2021-02-08 16:23:20 [36204] write() [chrome-host.mm:38] Response(64) {"result":"invalid_argument","nonce":"u3ssh12wj729cx0r","ver":1}
Related to #192 . Token signing is meant only for signing with Pin2.