|
Bugzilla – Full Text Bug Listing |
| Summary: | Problems with HTTPS since update to Version 1.5 | ||
|---|---|---|---|
| Product: | [Novell Products] MonoTouch | Reporter: | Dirk Seeber <d.seeber> |
| Component: | Runtime | Assignee: | Geoff Norton <gnorton> |
| Status: | RESOLVED FIXED | QA Contact: | Mono Bugs <mono-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | d.seeber |
| Version: | SVN | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X 10.6 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 591516 | ||
| Bug Blocks: | |||
|
Description
Dirk Seeber
2010-03-25 09:53:11 UTC
In MonoTouch 1.5 we added a system that uses the device certificates instead of the previous setup where we basically bailed unless you had manually installed the certificates you trusted or you implicitly trusted all certificates with the callbacks (or you implemented your own validation). Could you please share with me the https endpoint that is causing this problem? As far as I can see in the code, if the iPhone stack determines that the certificate is invalid, it will still invoke your callback with the information and you can still say "This is ok". In our application we use two different URL's. The first one is "https://dev.a3000-filialapotheke.de/mobilecontrolling" and is working although the certificate is invalid. The validation handler gets called and the communication works well. The second URL is "https://www.a3000-filialapotheke.de/MobileControlling" and there we're getting the described exceptions. Although the certificate is valid. Hope that might help you. The first url acts as expected, the second url isn't a regression, but a bug in mono's certificate parsing. I checked in a workaround in r154317 and the real bug has been entered a bug #591516. New bug to track is bug #594110 This is fixed in the next release. |