... more specifically, right here https://bitbucket.org/actoas/composite-c1/src/9bf3375232d8e7e723879a9988d198f1e6d8197f/CompositeC1/Composite/C1Console/Security/Cryptography/Cryptographer.cs?at=default#cl-60
There are two extension-methods for both Encrypting and Decrypting strings. Unfortunatenly, you can see that the "secretKey" is hardcoded right here https://bitbucket.org/actoas/composite-c1/src/9bf3375232d8e7e723879a9988d198f1e6d8197f/CompositeC1/Composite/C1Console/Security/Cryptography/Cryptographer.cs?at=default#cl-40, and not randomly generated for each C1 instance, so using these methods for truly sensitive data is NOT recommended.
The whole Cryptographer-class should be marked as Obsolete and unsafe to use.
There are two extension-methods for both Encrypting and Decrypting strings. Unfortunatenly, you can see that the "secretKey" is hardcoded right here https://bitbucket.org/actoas/composite-c1/src/9bf3375232d8e7e723879a9988d198f1e6d8197f/CompositeC1/Composite/C1Console/Security/Cryptography/Cryptographer.cs?at=default#cl-40, and not randomly generated for each C1 instance, so using these methods for truly sensitive data is NOT recommended.
The whole Cryptographer-class should be marked as Obsolete and unsafe to use.