|
From: SourceForge.net <no...@so...> - 2006-02-12 15:14:13
|
Feature Requests item #1429815, was opened at 2006-02-11 22:19 Message generated for change (Comment added) made by normanr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=1429815&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Norman Rasmussen (normanr) Assigned to: Nobody/Anonymous (nobody) Summary: win32security missing several constants (listed) Initial Comment: Please can you include the following sets of constants: ISC_REQ_* ISC_RET_* ASC_REQ_* ASC_RET_* SECBUFFER_* SECPKG_ATTR_* SECPKG_CONTEXT_* SECPKG_FLAG_* SECPKG_NEGOTIATION_* SECPKG_OPTIONS_* SECURITY_*_DREP SEC_E_OK SEC_I_* SEC_WINNT_* Some are referenced in the help files, but they're not defined. I had to go and dig in sspi.h in the SDK to find the vaules. Some used for AcceptSecurityContext and InitializeSecurityContext are only metioned by wildcard, and should be listed (like PyCtxtHandle.QueryContextAttributes does) (sspi.h attached) ---------------------------------------------------------------------- >Comment By: Norman Rasmussen (normanr) Date: 2006-02-12 17:14 Message: Logged In: YES user_id=336265 what about linking to the search page? e.g. http://search.msdn.microsoft.com/search/results.aspx?qu=AcceptSecurityContext That way the links shouldn't change that often. ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2006-02-12 16:18 Message: Logged In: YES user_id=771074 I added SEC_E_OK to sspicon. It probably got missed since it's in winerror.h rather than sspi.h. Unfortunately, MSDN doesn't keep their URLs constant. It would create a real maintenance headache to keep all those links in synch. Roger ---------------------------------------------------------------------- Comment By: Norman Rasmussen (normanr) Date: 2006-02-12 14:41 Message: Logged In: YES user_id=336265 Shot, those demo's should make my code much simpler. FYI : SEC_E_OK = 0 is missing from the sspicon.py file. I hear you on the 'maybe we shouldn't include all the MSDN docs in the pywin32 ones, because it's just duplication. Maybe provide links to the MSDN pages from the pywin32 ones would assist with that? I generally open my local copy of the MSDN anyways, but I expected the pywin32 docs to include everything. I think a link to the MSDN doc per page would go a long way to remind people that the pywin32 docs only show the _differences_ to the c implementations. ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2006-02-12 12:26 Message: Logged In: YES user_id=771074 These constants are all in sspicon.py. Check out \win32\Demos\security\sspi for some good examples of how the sspi objects work. (also \win32\test\test_sspi.py) They use a couple of classes for client and server auth that abstract away most of the messy details. Generally speaking, individual constants are usually listed in the docs when there are different types of python objects involved depending on what flags are passed. Some of the functions have so many combinations of flags that it would bloat the help file, and most of it would just be a rehash of the MSDN docs. Roger ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=1429815&group_id=78018 |
