X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=pmg-admin-guide.adoc;h=4dfed131729cb3ffaccf44bbf28a91ded08b2391;hb=17a1397250adcb134b0891fce43bd7ab1999494a;hp=f320ce8b0e2eb470908309693a8ab68d2e58615c;hpb=3372775f699852aeacae723257ac8a650e279389;p=pmg-docs.git

diff --git a/pmg-admin-guide.adoc b/pmg-admin-guide.adoc
index f320ce8..4dfed13 100644
--- a/pmg-admin-guide.adoc
+++ b/pmg-admin-guide.adoc
@@ -29,6 +29,8 @@ include::pmgconfig.adoc[]
 
 include::pmg-mail-filter.adoc[]
 
+include::pmg-administration.adoc[]
+
 include::pmgbackup.adoc[]
 
 include::pmgcm.adoc[]
@@ -36,17 +38,6 @@ include::pmgcm.adoc[]
 // Return to normal title levels.
 :leveloffset: 0
 
-TODO
-----
-// FIXME
-
-
-[[mail_server_config]]
-mail_server_config
-
-[[fitering_outgoing_mail]]
-fitering_outgoing_mail
-
 
 Important Service Daemons
 -------------------------
@@ -88,31 +79,13 @@ include::pmgreport.adoc[]
 
 include::pmgupgrade.adoc[]
 
-:leveloffset: 0
-
-
-[[nmap]]
-`nmap` - Port Scans
--------------------
-
-`nmap` is designed to allow system administrators to scan large
-networks to determine which hosts are up and what services they are
-offering. You can use nmap to test your firewall setting, for example
-to see if the required ports are open.
+:leveloffset: 1
 
-.Test Razor port (tcp port 2703):
-----
-# nmap -P0 -sS -p 2703 c301.cloudmark.com
+include::nmap.adoc[]
 
-Starting Nmap 5.00 ( http://nmap.org ) at 2012-07-31 11:10 CEST
-Interesting ports on c301.cloudmark.com (208.83.137.114):
-PORT     STATE SERVICE
-2703/tcp open  unknown
+:leveloffset: 0
 
-Nmap done: 1 IP address (1 host up) scanned in 0.17 seconds
-----
 
-See the manual page (`man nmap`) for more information about nmap.
 
 
 :leveloffset: 1
@@ -122,61 +95,7 @@ include::pmg-bibliography.adoc[]
 :leveloffset: 0
 
 [appendix]
-SSL certificate
----------------
-
-Access to the administration web interface is always done via
-`https`. The default certificate is never valid for your browser and
-you get always warnings.
-
-If you want to get rid of these warnings, you have to generate a valid
-certificate for your server.
-
-Login to your Proxmox via ssh or use the console:
-
-----
-openssl req -newkey rsa:2048 -nodes -keyout key.pem -out req.pem
-----
-
-Follow the instructions on the screen, see this example:
-
-----
-Country Name (2 letter code) [AU]: AT
-State or Province Name (full name) [Some-State]:Vienna
-Locality Name (eg, city) []:Vienna
-Organization Name (eg, company) [Internet Widgits Pty Ltd]: Proxmox GmbH
-Organizational Unit Name (eg, section) []:Proxmox Mail Gateway
-Common Name (eg, YOUR name) []: yourproxmox.yourdomain.com
-Email Address []:support@yourdomain.com
-
-Please enter the following 'extra' attributes to be sent with your certificate request
-A challenge password []: not necessary
-An optional company name []: not necessary
-----
-
-After you finished this certificate request you have to send the file
-`req.pem` to your Certification Authority (CA). The CA will issue the
-certificate (BASE64 encoded) based on your request – save this file as
-`cert.pem` to your Proxmox.
-
-To activate the new certificate, do the following on your Proxmox:
-
-----
-cat key.pem cert.pem >/etc/pmg/pmg-api.pem
-----
-
-The restart the API servers
-
-----
-systemctl restart pmgproxy
-----
-
-Test your new certificate by using your browser.
-
-NOTE: To transfer files from and to your Proxmox, you can use secure
-copy: If you desktop is Linux, you can use the `scp` command line
-tool. If your desktop PC is windows, please use a scp client like
-WinSCP (see http://winscp.net/).
+include::pmg-ssl-certificate.adoc[]
 
 
 [appendix]