Skip to content
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

chore(deps): update dependency opcfoundation.netstandard.opc.ua.configuration to 1.5.375.443 #770

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 24, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
OPCFoundation.NetStandard.Opc.Ua.Configuration 1.5.374.158 -> 1.5.375.443 age adoption passing confidence

Release Notes

OPCFoundation/UA-.NETStandard (OPCFoundation.NetStandard.Opc.Ua.Configuration)

v1.5.375.443: OPC UA 1.05 Maintenance Update

Compare Source

1.05.375 January Release

This release is based on the 1.05.03 Nodeset with generated files from the ModelCompiler.
The focus in this release was to add the support for Elliptic Curve Cryptography (ECC) and keep backward compatibility with existing configurations.

Improvements and bug fixes

  • Various smaller bug fixes.
  • Set corresponding security signature hash and validate ECDSA security signature hash algorithm length for ECC certificates
  • Fix: Return full CertificateChain after Certificate Update
  • Add ECDSA support for importing private key from PEM
  • Allow Subject Name Change of Application Certificate in GDS Push scenario
  • Extend ServerConfiguration & GDS Server for ECC
  • Simplify SetECDsaPublicKey and padd with leading zeros.

ECC support

  • Changes to applications configuration
  • Configuration permits specifying multiple application certificate types details
  • Backward compatibility with existing configurations - meaning no ECC just RSA encryption support
  • Further details can be found here
Known Limitations

Not all curves are supported by all OS platforms and not all .NET implementations offer cryptographic API support for all curve types.
Due to these limitations, the support for ECC profiles is available starting with the following target platforms: .NET 4.8, .NET standard 2.1 and .NET 5 and above.
The supported ECC curve types are the following:

  • NistP256 for ECC certificates with NIST P256 curve
  • NistP384 for ECC certificates with NIST P384 curve
  • BrainpoolP256r1 for ECC certificates with Brainpool P256r1 curve
  • BrainpoolP384r1 for ECC certificates with Brainpool P384r1 curve
Released packages

OPCFoundation.NetStandard.Opc.Ua
OPCFoundation.NetStandard.Opc.Ua.Core
OPCFoundation.NetStandard.Opc.Ua.Security.Certificates
OPCFoundation.NetStandard.Opc.Ua.Configuration
OPCFoundation.NetStandard.Opc.Ua.Server
OPCFoundation.NetStandard.Opc.Ua.Client
OPCFoundation.NetStandard.Opc.Ua.Client.ComplexTypes
OPCFoundation.NetStandard.Opc.Ua.Bindings.Https
OPCFoundation.NetStandard.Opc.Ua.PubSub

What's Changed

Full Changelog: OPCFoundation/UA-.NETStandard@1.5.374.168...1.5.375.443

v1.5.374.168: OPC UA 1.05 Maintenance Update

Compare Source

1.05.374 roll up until Jan 22nd.

This release is based on the 1.05.03 Nodeset with generated files from the ModelCompiler.
The focus in this release was on perf improvements and bug fixes.
This is also the last official release without ECC support...

Server improvements
  • NodeIdDictionary

The underlying dictionary of the commonly used NodeIdDictionary in node managers is now a ConcurrentDictionary. (see CustomNodeManager2 changes)
Perf comparisons with NodeId hashes showed that the lookup of entries is comparable to the previously used Dictionary, but doesn't require locking in the NodeManager. Now all implementations of GetManagerHandle can be accessed without locking the node manager, which should reduce contention between service calls. Still, most calls need to be synchronized with locks, but the GetManagerHandle call is decoupled.

Client improvements
  • A client fast datachange callback gets now access to the MoreNotifications flag, which makes it easier to reshuffle received data changes spread across multiple publish responses. To save the cost of a list translation, the notificationMessage gets a StringCollection for the StringTable instead of a List of strings.
Encoder/Decoder perf improvements
  • Taking advantage of stackalloc and Span ins some areas to reduce allocations and JSON escaping.
.NET 9 lib issues fixed
  • Linking with .NET 8 LTS caused some issues with referenced .NET9 assemblies, now only .NET 8 flavors are referenced.
Known Issues
  • see #​2966, a missing null pointer check may cause NullPointerException
Other bug fixes as below

What's Changed

Full Changelog: OPCFoundation/UA-.NETStandard@1.5.374.158...1.5.374.168


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency opcfoundation.netstandard.opc.ua.configuration to 1.5.374.168 chore(deps): update dependency opcfoundation.netstandard.opc.ua.configuration to 1.5.375.443 Jan 31, 2025
@renovate renovate bot force-pushed the renovate/opcfoundation.netstandard.opc.ua.configuration-1.x branch from cc9e153 to c0b4e19 Compare January 31, 2025 11:43
Copy link
Contributor Author

renovate bot commented Feb 3, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants