You are not logged in.
I have one physical dedicated server. The name of the server is 'mail.iamghost.tld' which is obviously my Postfix mail server for my users. Now I generated SSL self signed certificates with 'OpenSSL' which is for 'mail.iamghost.tld'. I also have Apache installed on the same server to access my webmail application. I created a pointer record for 'www.iamghost.tld' to point to the same static I.P. as 'mail.iamghost.tld'. So my question is if I also want to encrypt site login's for www.iamghost.tld/webmail, do I need to generate a unique SSL certificate for 'www.iamghost.tld' or can I use my existing SSL certificates that are assigned to 'mail.iamghost.tld'? It's the same server but when people browse to my 'www.iamghost.tld/webmail' site, I don't want there to be an issue with the certificates saying it's for 'mail.iamghost.tld' when they're really communicating with 'www.iamghost.tld'.
Thoughts and or suggestions?
./
Offline
If it's self-signed, just regenerate the certificate/CSR for *.iamghost.tld (ie, wildcard) then the same cert will work for everything in that domain. It's what I do for the archserver.org sites -- saves a lot of overhead in management of certificates.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I didn't know I could do that. Is that not frowned upon when people look at your certificates or is that normal / acceptable practice?
./
Offline
Wildcard's aren't common (they're very expensive from trusted CA's) but they're perfectly valid and normal.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Wildcard's aren't common (they're very expensive from trusted CA's) but they're perfectly valid and normal.
Thank you. As long as it's 'valid' & 'normal' then since it's a self signed certificate with no CA, I think this falls right with in budget.
./
Offline