SignedXml using SHA256 on .net framework 4
is there a way to still use SignedXml with sha256 to sign an xml file
SignedXml support for sha2 hashing was added later https://learn.microsoft.com/en-us/dotnet/framework/whats-new/
what is the ideal solution given that
- I cannot targer a recent .net framework version for the web site project
possible options:
- manually creating the signature tag without signed xml
- external call (a console project/ api for example)
What's new in .NET Framework - .NET Framework
See what's new in various versions of .NET Framework. Read a summary of key new features and improvements in each version.
4 Replies
I'd lean towards your second possible option tbh, if you're in cloud there are serverless options you can likely spin up quickly.
nope unfortunately 😔
I figured I'd make an exe and call it or just reconstruct the <Signature> using BouncyCastle along the way
I just want to make sure it's the best option given the current circumstances
I mean you can't upgrade, so really what other choice do you have?
it's one or the other, if you're just doing it inline with a single application, BC will work, but do you have other applications that similarly can't upgrade and need the same services?
on point
exactly
inline no need for code reuse
no cannot upgrade for now but a rework is planned but not for now
guess I'll go for the bc
thanks a lot for your input, much appreciated 💯