-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Не работает экспорт из КриптоПро Контейнера ГОСТ 2012 #14
Comments
May be issue is similar to ours: see fixes in this merge commit: https://github.com/garex/nodejs-gost-crypto/tree/561a78fb1a5a9a92f089209002692374bce48d7c There were wrong assumptions that all keys has same length. |
@garex I am still getting "Container is not valid" error. I think something is wrong with key-mac calculation. SignalCom exporting is working now though, thanx again for that. |
@state13 but nobody fixed those )) I just think the issue there is similar — keys size (assumed 256, but actually has 512). |
@state13 fixed in garex@180341f Added cli tool for this.
See
|
Looks Like all Works. Thanks |
@garex Thanks. Actually I have found by myself that E-Z sBox has to be used with new CryptoPro container instead of default E-A. I even thinking to create pull request. But I am not sure though that E-Z could be used with all scope of tc26 algorithms. |
@state13 as I understand, it's a default now by standard. In decompiled cryptocom jar it called DEFAULT constant. |
@garex Seems like it's not working again. When i'm trying to export key i'm getting "Icorrect fp" error. |
Do not work "exportPrivateKey()" on page http://gostcrypto.com/demo-cp-keys.html for ГОСТ 2012
![image](https://user-images.githubusercontent.com/7316441/42586135-0dee4de8-8540-11e8-96e0-f7e52009b3d3.png)
error on line:
if (!equalBuffers(hmac, self.header.hmacKeyContainerContent))
throw new Error("Container is not valid.");
key from https://testca2012.cryptopro.ru/ui/
le-d3bb8.000.zip password qwerty
on pressing "Export Key and Certificate"
The text was updated successfully, but these errors were encountered: