Project

General

Profile

Actions
Copy link

Bug #4060

closed

SSL weirdness in redmine

Added by Adam Thompson about 10 years ago. Updated about 10 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Unknown
Target version:
-
Start date:
12/02/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

Pretty much just FYI...

When navigating to https://redmine.pfsense.org/ using Chrome Version 39.0.2171.65 (64-bit) under Linux (Ubuntu 12.04), I get an error NET::ERR_CERT_COMMON_NAME_INVALID complaining about the wildcard cert. See attached screenshot. After manually confirming the cert, Chrome now claims everything is fine.

Firefox v34.0 beta 7 does not have the same issue.

I have no idea what hallucinogen Google has Chrome smoking today...

Files

32.png (94.6 KB) 32.png Adam Thompson, 12/02/2014 12:57 PM
Actions
Copy link
 #1

Updated by Ross Williamson about 10 years ago

That screenshot shows you're trying to connect to redmine.pfsense.com rather than redmine.pfsense.org. The certificate is only valid for the latter...

.com should probably have an HTTP redirect to .org though rather than serving up the same content but with a non matching cert

Actions
Copy link
 #2

Updated by Adam Thompson about 10 years ago

I didn't even notice that! The interesting part is that I followed a link to that... I'll try to retrace my steps, if I can find the link I'll update and re-open.

Actions
Copy link
 #3

Updated by Chris Buechler about 10 years ago

  • Status changed from New to Rejected

I set HTTP on redmine.pfsense.com to redirect to https://redmine.pfsense.org. We don't link to .com anywhere, though either/or worked years back and someone might have pasted a link somewhere.

Actions
Copy link

Also available in: Atom PDF