Re: Urgent question about possible changes to SecHandle in regards to InitializeSecurityContext

No, there is no small repro at this point. The question remains, "Have any of the recent hot fixes affected the values that might
be returned as context handles?".

Please note that the macro in SSPI.h checks to see if either half (32 bits) of the handle is -1. If so, it indicates an invalid
handle. I am receiving handles that have the upper 32 bits set to -1. It seems to me that the macro is wrong and should be
checking for BOTH halves equal to -1.

On Mon, 29 May 2006 10:31:17 GMT, jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]") wrote:

Hi Roy,

Thanks for your post!

Yes, based on the Schannel InitializeSecurityContext document, we should
get the pointer to a CtxtHandle structure in phNewContext parameter in
first InitializeSecurityContext calling. Then in the following calling, we
should use this first obtained phNewContext parameter as phContext
parameter. We should always pass NULL for phNewContext parameter in 2nd and
following callings.

I am not sure why you got SEC_E_INVALID_HANDLE error after the code running
for more than 2 years. Is it possible for you to provide a little sample
project demonstrate the problem? Then I will continue work with you in the
newsgroup.

Also, I noticed that this issue is urgent for you. based on the newsgroup
support nature, it may not be the most efficient support. If you need a
more efficient support, you may contact Microsoft PSS for an urgency case
support.
You can contact Microsoft Product Support by contacting us at
1-(800)936-5800 or by choosing one of the options listed at
http://www.microsoft.com/services/microsoftservices/srv_support.mspx.

Thanks!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.
http://www.kmsys.com
.

Relevant Pages

  • RE: Urgent question about possible changes to SecHandle in regards to InitializeSecurityContext
    ... first InitializeSecurityContext calling. ... should use this first obtained phNewContext parameter as phContext ... support nature, it may not be the most efficient support. ...
    (microsoft.public.platformsdk.security)
  • Re: Prefectceh?? Was it microsoft who phoned me?
    ... I just had a call from someone claiming to be microsoft getting me to type ... I've talked with many real MS support people over the years, ... calling me back as needed. ... Trust yourself. ...
    (microsoft.public.windowsxp.general)
  • Re: Good Microsoft TV ad!
    ... I wonder who these people are calling Microsoft support ... the vendor is going to start pointing their finger over to Microsoft. ... I thought that OEM pricing was based on providing support. ... Now maybe you can see why people are calling you a liar, ...
    (comp.sys.mac.advocacy)
  • Re: support
    ... > that I need to call Micrsoft direct. ... After calling the ... > support line for Microsoft they explained I cannot get ... > support without paying $35 for phone support. ...
    (microsoft.public.windowsxp.general)
  • *How MSFT *Deliberately, Arrogantly, Egregiously, and Totally* Fails to Support their Products*
    ... this support into the ground. ... Microsoft, particularly developers, as well as those who don't will become ... who adapted MSDE 2000 to Buggy BCM Version 1--aprimitive Beta in a package. ... Support you have ceded to incompetent Convergys. ...
    (microsoft.public.windowsxp.help_and_support)