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 sascha_silbe
Recipients christian.heimes, jcea, mpb, pitrou, r.david.murray, sascha_silbe, underrun
Date 2016-04-01.19:15:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459538106.41.0.0685040416623.issue18293@psf.upfronthosting.co.za>
In-reply-to
Content
Has there been any progress on this? For my application I'd very much like "ssh-like" operation, using the public key itself as identifier rather than requiring some kind of automated CA setup.

Being able to set a custom verification callback would be great, but just being able to cause a dummy callback that accepts any certificate to be used would go a long way. The validation could be done after the connection was established in this case. For some applications, that may even be the best approach, presenting any verification error via the application layer (e.g. HTTP) where they are closer to the problem domain and thus make more sense to the user.
History
Date User Action Args
2016-04-01 19:15:06sascha_silbesetrecipients: + sascha_silbe, jcea, pitrou, christian.heimes, r.david.murray, underrun, mpb
2016-04-01 19:15:06sascha_silbesetmessageid: <1459538106.41.0.0685040416623.issue18293@psf.upfronthosting.co.za>
2016-04-01 19:15:06sascha_silbelinkissue18293 messages
2016-04-01 19:15:06sascha_silbecreate