关于实现sspi [英] About implementing sspi

问题描述

我已经从此页面完成了大多数sspi实现.此代码也有一个vb版本.在其中大多数dll调用来自2个不同的dll. security.dll和secur32.dll.为什么我们不能仅将重点放在一个DLL-secur32.dll上呢?该实现将在所有机器上使用的是什么??

---

我是一堆错误，这些错误与良好的意图交织在一起.

I've done most of my sspi implementation from this page. There was a vb version of this code too. In it most dll calls came from 2 different dlls. security.dll & secur32.dll. Why can't we do the implementation focusing only on one dll - secur32.dll? What all machines would the implementation then work with...?

---

I am a bundle of mistakes intertwined together with good intentions

推荐答案

答案- http://blogs.msdn.com/oldnewthing/archive/2004/07 /02/171769.aspx .

无论如何，似乎security.dll将其所有导出转发到secur32.dll，并且在SDK中有一个用于后者的链接库.因此，我想您都可以(除非您仍然支持Microsoft不再支持的平台).

Here's the answer - http://blogs.msdn.com/oldnewthing/archive/2004/07/02/171769.aspx.

Anyway, looks like security.dll forwards all of its exports to secur32.dll, and there's a link library for the latter in the SDK. So I'd say you're fine either way(unless you're still supporting platforms that Microsoft doesn't any more).

这篇关于关于实现sspi的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！