2toad / rijndael256 Goto Github PK

Hey,

If .NET Core 3.1 still does not support 256 initialization vector why documentation does not reflect that?

Look at this:

//RijndaelManaged
// Legal min key size = 128
// Legal max key size = 256
// Legal min block size = 128
// Legal max block size = 256

Anybody can't get the same result! Why does the documentation is not refleting the truth?

https://docs.microsoft.com/pt-br/dotnet/api/system.security.cryptography.symmetricalgorithm.legalkeysizes?view=netcore-3.1

Originally posted by @dericferreira in #13 (comment)

Currently Rijndael and RijndaelEtM use CBC cipher mode (hard coded).

Acceptance Criteria

1. Settings object contains CipherMode setting
2. Default value is CBC
3. Unit test coverage
4. README.md is updated

Currently the hashes used by Rijndael and RijndaelEtM are computed using 10000 iterations (hard coded).

Acceptance Criteria

1. Value is user configurable
2. Default value is 10000

when using powershell core to add-type like this:

$modulepath= Resolve-Path -path "$PSScriptRoot\lib\netstandard1.3\Rijndael256.dll"

add-type $modulepath

function Encrypt-Rijndael256{
    param(
        $key,
        $plaintext
    )

    return [Rijndael256.Rijndael]::Encrypt($plaintext,$key,256)
}

function Decrypt-Rijndael256{
    param(
        $key,
        $encryptText
        
    )
    return [Rijndael256.Rijndael]::Decrypt($encryptText,$key,256)
}

### i always got error like this.

add-type : (1) : Type or namespace definition, or end-of-file expected
(1) : >>> /home/yoke/Documents/PSPHPIPAM/functions/lib/netstandard1.3/Rijndael256.dll
At /home/yoke/Documents/PSPHPIPAM/functions/Rijndael256.core.ps1:3 char:1
+ add-type $modulepath
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidData: (Microsoft.Power...peCompilerError:AddTypeCompilerError) [Add-Type], Exception
+ FullyQualifiedErrorId : SOURCE_CODE_ERROR,Microsoft.PowerShell.Commands.AddTypeCommand

maybe the below link can show what's wrong there
here

In .net core AES is used which does not support 256 blocksize which is the exact reason why RijindaelManaged doesn't work. Unless I am missing something here, if I am please correct me as I can not get it to work.

Ref: https://github.com/dotnet/corefx/issues/12064

I have done a branch for porting back the project to Visual Studio 2015 and change supported frameworks to .NET Standard 1.3 and .NET Framework 4.5.1.
See any possibility to merge back to the main repo?
This is my fork.

Hello,

It would be interesting to use SecureString instead of String to handle the password

Acceptance Criteria

1. Calling Settings.Reset() restores all settings to their default values
2. Unit test coverage

Acceptance Criteria

1. The Config class is renamed to Settings
2. The ConfigTests class is renamed to SettingsTests
3. Comments and README reference Settings instead of Config

I have a project in vb.net framework version 4.5. I am upgrading my project to ASP.Net Core 1.1 and trying to decry-pt the same encrypted code of framework 4.5 in ASP.Net Core and getting exception

"specified padding mode is not valid for this algorithm"
I have used the Rijndael algorithm for encryption/decryption of data in Asp.Net Framework 4.5 and still using Rijndael in ASP.Net Core for encryption/decryption but getting issue.

Can anyone help me to find-out the reason behind this issue.

Thanks