| 183 | | I will quote Javier's howto here just to have all infos in one place: |
| 184 | | |
| 185 | | {{{ |
| 186 | | #!div class=quote style="border: 2pt solid; text-align: left;background-color:#336699" |
| 187 | | - you cannot export your certificate in the CA module because you need a CA certificate to be able to issue other certificates |
| 188 | | |
| 189 | | - to use your certificate as the certificate for web administration, you must: |
| 190 | | 1) put the certificate in the file /var/lib/ebox/conf/ssl.crt/ebox.cert |
| 191 | | 2) put the certficate key file in the file /var/lib/ebox/conf/ssl.key/ebox.key |
| 192 | | 3)create the pem file concatening the two previous files, lke this: |
| 193 | | |
| 194 | | cat /var/lib/ebox/conf/ssl.crt/ebox.cert /var/lib/ebox/conf/ssl.key/ebox.key > /var/lib/ebox/conf/ssl.pem/ebox.pem |
| 195 | | chmod 0400 /var/lib/ebox/conf/ssl.pem/ebox.pem |
| 196 | | |
| 197 | | 4) restart the webserver with: |
| 198 | | /etc/init.d/ebox apache restart |
| 199 | | |
| 200 | | - to use your certficate in the mail server you need to proceed similarly: |
| 201 | | 1) put the certificate in the file /etc/postfix/sasl/smtpd.pem |
| 202 | | 2) put the certficate key file in the file /etc/postfix/sasl/smptd-key.pem |
| 203 | | 3)create the pem file concatenating the two previous files, lke this: |
| 204 | | |
| 205 | | cat /etc/postfix/sasl/smtpd.pem /etc/postfix/sasl/smtpd-key.pem > /etc/postfix/sasl/smtp.pem |
| 206 | | chmod 0400 /etc/postfix/sasl/smtp.pem |
| 207 | | |
| 208 | | 4) restart the mail system with: |
| 209 | | /etc/init.d/ebox mail restart |
| 210 | | |
| 211 | | }}} |
| 212 | | |
| 213 | | |
| 214 | | One remark: if you copy the .pem file created in step 2 to /etc/postfix/sasl/whatever.pem you don't have to repeat the steps later on. |
| 215 | | |
| 216 | | TODO: check whether the certificates are in place after a reboot. |
| 217 | | |
| 218 | | |
| | 183 | I will use Javier's howto here and append my remarks to it:[[BR]] |
| | 184 | [[BR]] |
| | 185 | |
| | 186 | At first, you have to understand, that there are 2 different Apache instances running. One is doing the normal webpages, the other one is serving the web admin pages. These instances have 2 different config files. |
| | 187 | |
| | 188 | Securing webpages (Zarafa's webaccess, Roundcube, etc.):[[BR]] |
| | 189 | 1) put the certificate in the file /etc/apache2/ssl/ssl.cert[[BR]] |
| | 190 | 2) put the certficate key file in the file /etc/apache2/ssl/ssl.key[[BR]] |
| | 191 | 3) create the pem file concatening the two previous files, like this:[[BR]] |
| | 192 | |
| | 193 | {{{ |
| | 194 | #!div class=conf style="border: 2pt solid; text-align: left;background-color:#AAAAAA" |
| | 195 | cat /etc/apache2/ssl/ssl.cert /etc/apache2/ssl/ssl.key > /etc/apache2/ssl/ssl.pem[[BR]] |
| | 196 | chmod 0400 /var/lib/ebox/conf/ssl.pem/ebox.pem |
| | 197 | }}} |
| | 198 | |
| | 199 | here I went over to the /usr/share/<ebox/zentyal>/stubs/webserver and added the following line to default-ssl.mas :[[BR]] |
| | 200 | |
| | 201 | |
| | 202 | {{{ |
| | 203 | #!div class=conf style="border: 2pt solid; text-align: left;background-color:#AAAAAA" |
| | 204 | SSLCertificateChainFile "/etc/apache2/ssl/sub.class1.server.ca.pem" |
| | 205 | }}} |
| | 206 | |
| | 207 | the sub.class1.server.ca.pem is issued by StartSSL, this will tell the browser who is the CA.[[BR]] |
| | 208 | |
| | 209 | Do a [[BR]] |
| | 210 | |
| | 211 | {{{ |
| | 212 | #!div class=conf style="border: 2pt solid; text-align: left;background-color:#AAAAAA" |
| | 213 | /etc/init.d/zentyal webserver restart |
| | 214 | }}} |
| | 215 | and your official certificates should be working.[[BR]] |
| | 216 | |
| | 217 | Securing the admin interface:[[BR]] |
| | 218 | 1) put the certificate in the file /var/lib/ebox|zentyal/conf/ssl/ssl.cert[[BR]] |
| | 219 | 2) put the certficate key file in the file /var/lib/ebox|zentyal/conf/ssl/ssl.key[[BR]] |
| | 220 | 3) create the pem file concatening the two previous files, like this:[[BR]] |
| | 221 | |
| | 222 | {{{ |
| | 223 | #!div class=conf style="border: 2pt solid; text-align: left;background-color:#AAAAAA" |
| | 224 | cat /var/lib/ebox|zentyal/conf/ssl/ssl.cert /var/lib/ebox|zentyal/conf/ssl/ssl.key > /var/lib/ebox|zentyal/conf/ssl/ssl.pem[[BR]] |
| | 225 | chmod 0400 /var/lib/ebox/conf/ssl.pem/ebox.pem |
| | 226 | }}} |
| | 227 | |
| | 228 | TODO: verify inserting official CA[[BR]] |
| | 229 | |
| | 230 | {{{ |
| | 231 | #!div class=conf style="border: 2pt solid; text-align: left;background-color:#AAAAAA" |
| | 232 | /etc/init.d/zentyal apache restart |
| | 233 | }}} |
| | 234 | |
| | 235 | will restart you admin interface, which will have the official certificates as well.[[BR]] |
| | 236 | |
| | 237 | Securing IMAP with an official certificate:[[BR]] |
| | 238 | |
| | 239 | 1) put the certificate in the file /etc/postfix/sasl/smtpd.pem (Zentyal 2.0 or Ebox) or /etc/postfix/sasl/postfix.pem [[BR]] |
| | 240 | Create the .pem file according to above.[[BR]] |
| | 241 | 2) restart the mail system with:[[BR]] |
| | 242 | {{{ |
| | 243 | #!div class=conf style="border: 2pt solid; text-align: left;background-color:#AAAAAA" |
| | 244 | /etc/init.d/zentyal mail restart |
| | 245 | }}} |
| | 246 | |
| | 247 | TODO: check whether the certificates are in place after a reboot. Explain the use of hooks.[[BR]] |
| | 248 | |
| | 249 | |
| | 250 | |