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.

Sign up for GitHub

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

Jump to bottom

PCI/FIPS Compliance #24

Open

schmittjoseph opened this issue Nov 4, 2017 · 2 comments

Labels

bug

schmittjoseph commented Nov 4, 2017 •

edited by Sebastian-Roth

Loading

The AES API relies on RijndaelManaged which has not been certified by NIST. This prevents the client from using that API on PCI compliant machines.

https://forums.fogproject.org/topic/11035/problems-with-fog-client-and-fips-validation

Code reference:
https://github.com/FOGProject/zazzles/blob/master/Zazzles/Data/AES.cs

schmittjoseph added the bug label

schmittjoseph self-assigned this

Author

schmittjoseph commented Nov 4, 2017

Use system.security.cryptography.aesmanaged instead of RijndaelManaged.

Member

Sebastian-Roth commented Feb 22, 2023 •

edited

Loading

Here we have another topic on this in the forums: https://forums.fogproject.org/topic/16706/error-could-not-get-security-token

We should definitely look into #19 as well when working towards PCI/FIPS comliance!!

Sebastian-Roth changed the title ~~PCI Compliance~~ PCI/FIPS Compliance

Sebastian-Roth unassigned schmittjoseph

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment