Hi. Really don't want this post to go *foom* so I'm reposting Chris' encryption wrapper. Does this thing depend on the windows product key or a specific install of windows? Can I encrypt on 1 machine go to another and decrypt it there or do I need to do something fancy?
Chris Iverson said:
Funny you ask, I literally just finished a personal project of mine yesterday, creating a set of wrapper functions for using the Windows CryptoAPI. I targeted creating SHA256 hashes, 2048-bit RSA asymmetric encryption, and AES-256 symmetric encryption.
That's the set of functions, there's some demo code that demonstrates the final part I wrote(RSA signatures).
I'll create some demo code for those functions for AES-256 encryption.
There's not much documentation at the moment due to it being as much a match as it can to how each function is used in MSDN. Nearly all of the named functions are directly documented on MSDN.
EDIT: The link above now has some easier-to-use functions for AES256 encryption/decryption, as well as key derivation, and demo code showing how to use it.
These wrapper functions are published under the MIT license. Basically, feel free to use the wrappers in any program, but if you distribute it, you have to include my license notice as attribution. (Your project's license does NOT have to match mine; you are only required to retain my copyright notice.)
Last Edit: Apr 4, 2018 16:54:02 GMT -5 by hooshnik
Post by Chris Iverson on Apr 4, 2018 17:14:28 GMT -5
There are no Windows edition restrictions (i.e. Pro vs Home), but part of it would need to be rewritten to work on Windows XP, (as the encryption provider has a different name on XP), and wrapper functions I'm writing for SHA-256 hashing won't work at all(SHA-256 isn't supported on WinXP. Only up to SHA1 is supported, which has already been declared to be crytpographically insecure.)