Agreed. Regen the cert with the new name. In essence it's not the server complaining, it's the browser complaining that the address in the cert does not match the address it went to, which is true, and is what the browser is supposed to be watching for.
If this is a purchased cert, the vendor might have some discount for a regenned cert, or even do it free. You'd have to check with them. If it's your own self-rolled cert, just re-roll it. --On Thursday, July 29, 2010 9:24 PM -0400 Dave Tisdell <[email protected]> wrote: > I am pretty sure you need to generate a new certificate reflecting the new > name. > > Dave > >>>> Joe Golden <[email protected]> 07/26/10 11:11 PM >>> > Hi All. > > I recently changed the hostname on my development server: a Debian amd64 > stable install. Server used to identify as "oldname.sover.net" and is > now "newname.com". I'm using Apache 2.2.9, Debian kernel 2.6.26-2-amd64 > and running OpenSSL 0.9.8g. The SSL cert is just for my own use. Since I > changed the hostname I keep getting the warning >>> > Accept incorrect security information? > > The site "newname.com" returned security information for > "oldname.sover.net". It is possible that someone is intercepting your > communication to obtain your confidential information. ... >>> > How do I make the system forget its old identity and fully change over > to the new? > > Thanx. > -- > Joe Golden /_\ http://triangul.us /_\ People, Ideas, Connections > > > > > This e-mail may contain information protected under the Family Educational > Rights and Privacy Act (FERPA). If this e-mail contains student information > and you are not entitled to access such information under FERPA, please > notify the sender. Federal regulations require that you destroy this e-mail > without reviewing it and you may not forward it to anyone.
