E certificate is valid but its commonName does not match hostname
Bug #1518915 reported by
sakis_ser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Epoptes |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
I'm using epoptes-client on a lot of my client machines which are identical. I have successfully received the server certificate. Some of my machines are executing correctly epoptes-client while in other machines I get
"E certificate is valid but its commonName does not match hostname" upon epoptes-client execution. All the machines have almost identical network settings (successive static IPs & hostnames and customized /etc/default/
Revision history for this message
| Fotis Tsamis (ftsamis) wrote | #1 |
| Changed in epoptes: | |
| importance: | Undecided → Medium |
| status: | New → Fix Released |
To post a comment you must log in.
This is an extra certificate check introduced in socat version 1.7.3 which is probably the version installed in the clients showing the error. We take care of this in epoptes-client 0.5.8 and later.
Please add our stable PPA to your sources and upgrade epoptes-client on your clients to 0.5.8
https:/