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 opc-f.netstandard to 1.5.375.443 #98

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 31, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
OPCFoundation.NetStandard.Opc.Ua.Client 1.5.374.168 -> 1.5.375.443 age adoption passing confidence
OPCFoundation.NetStandard.Opc.Ua.Client.ComplexTypes 1.5.374.168 -> 1.5.375.443 age adoption passing confidence
OPCFoundation.NetStandard.Opc.Ua.Gds.Client.Common 1.5.374.168 -> 1.5.375.443 age adoption passing confidence

Release Notes

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

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


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 becomes conflicted, or you tick the rebase/retry checkbox.

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


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

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

@GoetzGoerisch GoetzGoerisch merged commit baf9eda into upstream Feb 11, 2025
31 checks passed
@renovate renovate bot deleted the renovate/opc-f.netstandard branch February 11, 2025 10:07
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.

1 participant