@Override
public Signal.SignatureData callHSM(byte[] dataToSign, HSMPass go) {
// Create the SignRequest for AWS KMS
var signRequest =
SignRequest.builder()
.keyId(keyID)
.message(SdkBytes.fromByteArray(dataHash))
.messageType(MessageType.DIGEST)
.signingAlgorithm(SigningAlgorithmSpec.ECDSA_SHA_256)
.construct();
// Signal the information utilizing AWS KMS
var signResult = kmsClient.signal(signRequest);
var signatureBuffer = signResult.signature().asByteBuffer();
// Convert the signature to byte array
var signBytes = new byte[signatureBuffer.remaining()];
signatureBuffer.get(signBytes);
// Confirm signature osn KMS
var verifyRequest =
VerifyRequest.builder()
.keyId(keyID)
.message(SdkBytes.fromByteArray(dataHash))
.messageType(MessageType.DIGEST)
.signingAlgorithm(SigningAlgorithmSpec.ECDSA_SHA_256)
.signature(SdkBytes.fromByteArray(signBytes))
.construct();
var verifyRequestResult = kmsClient.confirm(verifyRequest);
if (!verifyRequestResult.signatureValid()) {
throw new RuntimeException(“KMS signature will not be legitimate!”);
}
var signature = CryptoUtils.fromDerFormat(signBytes);
return Signal.createSignatureData(signature, go.getPublicKey(), dataHash);
}
NOTE!
In an effort to use this correctly, the kind of key spec created in AWS KMS have to be ECC_SECG_P256K1. That is particular to the crypto area, particularly to EVM. Utilizing every other key will lead to a mismatch error when the information signature is created.
Instance
Here’s a brief instance of learn how to name the callHSM methodology from the library:
public static void major(String[] args) throws Exception {
KmsClient shopper = KmsClient.create();
// extract the KMS key
byte[] derPublicKey = shopper
.getPublicKey((var builder) -> {
builder.keyId(kmsKeyId);
})
.publicKey()
.asByteArray();
byte[] rawPublicKey = SubjectPublicKeyInfo
.getInstance(derPublicKey)
.getPublicKeyData()
.getBytes();
BigInteger publicKey = new BigInteger(1, Arrays.copyOfRange(rawPublicKey, 1, rawPublicKey.size));
HSMPass go = new HSMPass(null, publicKey);
HSMRequestProcessor signer = new HSMAwsKMSRequestProcessor(shopper, kmsKeyId);
signer.callHSM(information, go);
}
Conclusion
AWS KMS, with its built-in HSM performance, presents a strong resolution for securely managing and signing cryptographic transactions. Regardless of preliminary challenges confronted by customers in integrating AWS KMS with Hyperledger Web3j, the introduction of the HSMAwsKMSRequestProcessor class has made it simpler to undertake and implement. This ready-to-use resolution simplifies interactions with AWS KMS, permitting customers to securely signal information and transactions with minimal configuration. By leveraging this device, organizations can improve their safety posture whereas benefiting from the comfort of AWS’s cloud-native HSM capabilities.
Â