-
Notifications
You must be signed in to change notification settings - Fork 30
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
TheSafe: config ability to encrypt values using macros and vars #870
Comments
This works, as-is, meaning macro does not need a path to be called: Console.WriteLine("$(::as-string value=\"123456789\" key=\"dodik\"), the value is $(/dont-exist::as-int dflt=\"-456\") OK?".EvaluateVars());
//123456789, the value is -456 OK? we can add Maybe add a "SecurityFlowScope" assertion to check for "AllowEncodedVariables". |
NEED UNIT TESTS!!!!!!!! |
|
DEPLOYED everywhere in G8 |
For example:
We need to add process-wide secret, whihc is NOT "seen" in config context, probably use USER ENV var
SKY_MACHINE_SECRET
by default.The algorithm must NOT rely on Azos.App.SecMan.Cryptography because it needs to configure secman, intead it should be a sinple AES256-based algorithm specifically designed for conf vars protection.
We need to add option to
phash
to cipher config values using a password phrase, e.g.:The text was updated successfully, but these errors were encountered: