| Type: | Bug | Severity: | Medium | Status: | Closed Fixed | Status Comment: | Fixed in 3.28 | Title: | certificates issue | Version: | 3.27 | Navigate: 1-4
joerg | Re: certificates issue | 20100527 18:49 | | To access sites with invalid certificates you have to disabled the security checks by setting the WEBKIT_IGNORE_SSL_ERRORS environment variable, for example using "SetEnv WEBKIT_IGNORE_SSL_ERRORS 1" in a shell, before starting OWB. | | |
|
Jack | Re: certificates issue | 20100527 22:41 | | @joerg
Other browser do not complain on certificates of the site (checked with seamonkey, cert looks not expired and ok), that the reason I reported it (unless I fail to spot how the cert. is invalid). I am awar eof the WEBKIT_IGNORE_SSL_ERRORS option but I prefer not to use it when it comes to online payments. | | |
|
joerg | Re: certificates issue | 20100529 03:43 | | @Jack
Other browser do not complain on certificates of the site (checked with seamonkey, cert looks not expired and ok), |
| Several do, for example Arora (a simple WebKit based browser), AWeb and WGet (current Linux version, AFAIK the AmigaOS 4.x port of WGet doesn't support https).
that the reason I reported it (unless I fail to spot how the cert. is invalid). |
| I just checked it with FireFox. It's correct, but they use very new certificates (only valid since a few days or weeks). I'll try to export the required ones for this site from FireFox and add it to the libcurl certs. | | |
|
Jack | Re: certificates issue | 20100603 20:32 | | @joerg
Worked as a charm:-) Huge thanks. | | |
| Navigate: 1-4
|
|