I have old posts/projects that have old C++ security api code in them, but I don't recommend using them.
For example, in this thread:
Quote:
Now for some other comments. The project makes use of the Common code from my project, which I have not made a formal thread on these forums about yet. Boost is required to compile most of the code and I use Visual Studio 2008.
|
However, all the C++ projects pre-date the C# security api, so they're going to most likely have some issues and not offer the same updated API I coded into the C# one.
Basically, you need to custom tailor C++ code for the project you're working on, so after struggling trying to make a generic C++ version anyone could use, I gave up and switched to using C# instead. Nowadays, if I were to do another C++ API, I'd start with the C# API, then port it to C++, and then tailor it to the project at hand. The C# API is known to be stable, well tested, and while it does have performance issues when used under unintended scenarios, you should not have any bugs with it past known limitations.
Those known limitations pretty much come to acting as a proxy between server modules. The encryption/security byte processing doesn't mirror how the server files work, since I wrote the API before server files were released. There's a few posts on the forums mentioning the implications of this. I have an unpublished updated version, but it's not ready for release anytime soon, but seems most people have gotten by without that functionality anyways.
Basically, you'd be better off just porting the C# API to C++, then customizing it as needed. Don't use any of the old code I have posted though, it's all far too old and outdated now.