UnauthorizedRequest about bingchat

[hswlab]

I finally figured it out. Bing no longer sends the signature in the response content, but in the response header inside X-Sydney-EncryptedConversationSignature. I now use my own solution to communicate with Bing, but the communication principle is more or less the same as with the Bing API here, with the modifications for the signature the Bing API should work again. At least I already could test it successfully in my implementation. :)

[neon-sunset]

@hswlab Thank you, noted this for work once I'll get to next pass of RE and fixes! (currently busy with another project)

[gunpal5]

@neon-sunset I just added a pull request #41

[chinazhaoht]

@hswlab I already know how to obtain a signature, but how should I use it in new communication methods?

[hswlab]

@chinazhaoht For websocket request with ChatHub, this string is currently set in the URL parameter of sec_access_token.
wss://sydney.bing.com/sydney/ChatHub?sec_access_token=TheSignature

If you use the Bing API, you have to wait until the code in the API is customized. @gunpal5 seems to have already an update for this issue. :)

[chinazhaoht]

I used the signature in the X-Sydney-Encryptedconversationsignature header from the create conversation response, URL-encoded it, and passed it as the sec_access_token to the chathub interface, but the chathub still returns "unauthorized request" and "chathub not authorized".

[gunpal5]

@chinazhaoht save your time and use this PR: #41

[chinazhaoht]

@gunpal5 Thank you, I have already solved this problem.