-
Notifications
You must be signed in to change notification settings - Fork 373
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
adds security policy Aes128-Sha256-RsaOaep #1032
Conversation
First there are no tests, so we aren't even sure if it works between our client and server. I tired to connect to a server based on Softing SDK and got following error:
|
With the following changes a connection to the server was possible:
|
Hmm, the point of this change is to use aes128, for that the key needs to be 16 bytes |
That is correct, but you need a 32 nounce otherwise the server will rejected it. There for symmetric_key_size is used for the size. |
Ah |
16 is used for "SecurityPolicyBasic128Rsa15" which also states to use aes128. How does handle the issue you described? |
I think it was just a coincidence that symmetric_key_size was equal to the SecureChannelNonceLength. Best way is to add a secure_channel_nonce_length to all security policys. |
Ok, would that be here: opcua-asyncio/asyncua/common/connection.py Line 184 in 4f48eb2
and opcua-asyncio/asyncua/client/client.py Line 336 in b978209
|
Good job. Works with Softing SDK server and i can access a asyncua example server with Aes128-Sha256-RsaOaep, with UAExpert. |
Do I have to add reviewers to the pull request? |
@schroeder- I do not know much the encryption code, so I propose to let you merge that one |
No description provided.