-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14.11.2014 23:27, Darrell Budic wrote: > That’s what I thought too, but... Firefox tells me “This > certificate is already installed as a certificate authority.” > though. It looks like the cert for :6100 is the proper one, too. > Maybe a firefox change with their new signing rules (i’ve disabled > security.use_mozillapkix_verification due to problems with other > internal certs)? I tried removing all the old web site certs and > still had to add the https://<engine>:6100 cert to get the noVNC > console to connect.
also I'm wondering why the certificate should get exchanged during upgrade? is this the "normal" upgrade path? Does upgrade renew/change any previously installed certificates? I guess this should not happen? thanks for any answers in advance Sven -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBAgAGBQJUZ7GHAAoJEAq0kGAWDrqlt8QMAMSy5pw3LE+mYC/kux8DIiQh nbD9xnJj2jZpbg21/wp+aHDGXp99NJl6GGN0ClMnZkPAH1WmCYmxq7zEcqSGnAV7 Nu5+LsmFvyktK+u2INXNi/5Z3NNYCUbGLHOL2d4CprmBOAy/5G+5G4ucBNRmBTIH 8MzLop2sJEtHQ6ZK2VbzpD/5k7K87VwhLSGIXx9R72AEmeuH9p0Q4GNDxhLU99lO 5fMyF63ExECoMGdb/JwSUQ/juZ79K6UnRY63qTdFlMXW7eddf+zetmZrS8eE4lHe HEe+IuMSqqsHovpHn7lCnM27AsQzG6UITqCz9atlO34zlqd2jvaoWhsbYBO0wrUS MKUsMB/abdp/N1Vhs1WigsYkCvv4OoSzabBkrQ+pU9ivzK+zagwi65lqx1nsgfCH UigwWWnb6SWUeGpPu40UYOCAqYWCGCcH3H0kuuGtVsql55Vr++OSHoG9Q9kRYpj3 0d6GfSW9V+6hvhc/jv9C6BAzTY0clNSwiBKBZZyi2w== =VavE -----END PGP SIGNATURE----- _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
