henkmollema / cryptohelper Goto Github PK

Is there any reason to use net standard 2.0? Yes, we are getting large API set, but lost compatible with all projects <2.0.
Ofcourse, we can still use old version without problem(and without security updates 😫) or upgrade app to new target framework, but I'm really don't understand why use netstandart 2.0 for library project(if it really don't needs).

Hey @henkmollema,

As part of OpenIddict 3.0, I'd like to remove the Microsoft.AspNetCore.Cryptography.KeyDerivation dependency from the OpenIddict core package. I had to lobby hard to convince the ASP.NET team to keep DP compatible with .NET Standard 2.0, which motivated me to get rid of DP in the core stuff.

Do you think it would be possible to copy the key derivation classes you need from Microsoft.AspNetCore.Cryptography.KeyDerivation and ship a version of CryptoHelper with no dependency?

Cheers!

aspnet/Announcements#98

Salts are necessary to protect form rainbow dictionary attacks

@henkmollema Thanks for the handy little tool. 👏 👏

Not exactly an issue. But just wanted let you know that I have created Java version based on your work.
https://github.com/lankaapura/CryptoHelper

• Target RC2 final packages
• Bump version to 1.0.0-rc2-final
• Update build scripts

CryptoHelper is currently targeting dotnet5.4 which is being replaced by netstandard1.3 everywhere, including the ASP.NET Core and aspnet-contrib projects. That would be great if CryptoHelper could be updated to use the new TFM (no hurries, of course, since we can use the imports section to make dotnet5.4 compatible with netstandard1.3).

Pushing a new build would also fix the weird assembly version issues we're seeing with DNX. Here's more context: openiddict/openiddict-core#76 (comment) (it's about IdentityModel, but CryptoHelper is similarly impacted)

https://github.com/henkmollema/CryptoHelper/blob/master/src/CryptoHelper/project.json#L29

Thanks!

/cc @henkmollema