antiduh
|
1be2b9c7ef
|
Saving work.. working on implementing EncryptMessage. The buffer types and allocation that get passed to the call is really crazy in the sample.
|
2014-06-23 02:34:36 +00:00 |
|
antiduh
|
3142cfff7b
|
Fixed ServerContext to store its final attributes.
|
2014-06-23 02:33:47 +00:00 |
|
antiduh
|
93bdd38729
|
A little cleaner, and we can complete negotiation.
|
2014-06-23 00:13:50 +00:00 |
|
antiduh
|
352e4d18fc
|
Working on implementing the ServerContext and structuring things so that invoking the public interface is a little easier - trying to move out of proof-of-concept code to prototype code. Still need to rework how I deal with the context and credential handles, worried that they're not treated safe. Still need to reorganize a lot of where code lives. Very inconsistent so far.
|
2014-06-22 16:20:10 +00:00 |
|
antiduh
|
a079449f85
|
Changed how internal structures are created for handling SecureBuffers.
|
2014-06-22 03:35:47 +00:00 |
|
antiduh
|
1c5849ba94
|
Moved the secure buffer code to its own folder.
|
2014-06-22 00:43:47 +00:00 |
|
antiduh
|
c64765fbdf
|
I can now successfully call InitializeSecurityContext and get a status of ContinueNeeded.
|
2014-06-21 16:32:34 +00:00 |
|
antiduh
|
0655259f46
|
Rough capture of the options to InitializeSecurityContext (used by clients) and AcceptSecurityContext (used by servers). Some of the options are used only by clients (prefaced by init) and some are only used by servers (prefaced by Accept). It might be worth to either separate the two sets by client options and server options, or unifying the sets in the public interface, and translating to the correct values when actually calling ISC or ASC.
|
2014-06-20 18:06:33 +00:00 |
|
antiduh
|
cfba81cfe2
|
Working on some of the fundamentals of the Context side of things. The Win 32 API is very wonky here though. Going to take some time.
|
2014-06-19 21:53:34 +00:00 |
|