This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xiang.zhang
Recipients Soon Jeffrey, arp11, xiang.zhang
Date 2017-11-06.07:10:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509952212.47.0.213398074469.issue30434@psf.upfronthosting.co.za>
In-reply-to
Content
I can't reproduce the failure with 2.7.13 but I do encounter the same failure just now, much same as yours, 2.7.5 and 2.7.13.  I'd like to describe my situation.

I have one client process started by 2.7.13(I build it from source) and one server process started by the system Python 2.7.5.  I then get the same error as yours, failing at connect() and the authkey doesn't matter.

The reason I find is that the system Python is patched by the OS vendor, changing the default MD5 algorithm to SHA256.  So they can't communicate.  Patching the source or syncing the version works for me.
History
Date User Action Args
2017-11-06 07:10:12xiang.zhangsetrecipients: + xiang.zhang, arp11, Soon Jeffrey
2017-11-06 07:10:12xiang.zhangsetmessageid: <1509952212.47.0.213398074469.issue30434@psf.upfronthosting.co.za>
2017-11-06 07:10:12xiang.zhanglinkissue30434 messages
2017-11-06 07:10:11xiang.zhangcreate