https://bugzilla.gnome.org/show_bug.cgi?id=592836
sysadmin | Other | unspecified
Tobias Mueller <gnome-bugs> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |gnome-b...@auftrags-killer.
| |org
Ever Confirmed|0 |1
--- Comment #4 from Tobias Mueller <[email protected]> 2009-10-29
17:49:20 UTC ---
This is still an issue:
$ openssl s_client -connect jabber.gnome.org:5223
CONNECTED(00000003)
depth=0 /C=Unknown/ST=Unknown/L=Unknown/O=GNOME/OU=Unknown/CN=gnome.org
verify error:num=18:self signed certificate
verify return:1
depth=0 /C=Unknown/ST=Unknown/L=Unknown/O=GNOME/OU=Unknown/CN=gnome.org
verify error:num=10:certificate has expired
notAfter=Oct 7 02:55:21 2006 GMT
verify return:1
depth=0 /C=Unknown/ST=Unknown/L=Unknown/O=GNOME/OU=Unknown/CN=gnome.org
notAfter=Oct 7 02:55:21 2006 GMT
verify return:1
---
Certificate chain
0 s:/C=Unknown/ST=Unknown/L=Unknown/O=GNOME/OU=Unknown/CN=gnome.org
i:/C=Unknown/ST=Unknown/L=Unknown/O=GNOME/OU=Unknown/CN=gnome.org
---
Server certificate
[...]
We have our Bugzilla Certificate signed by StartCom, we could totally have a
signature for a cert for jabber.gnome.org as well.
To set this up, one need access over either {host,post}[email protected] or at
least have a mail quickly forwarded to the person getting the signature from
StartCom.
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact of the bug.
You are watching the assignee of the bug.
_______________________________________________
gnome-infrastructure mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-infrastructure
