From 6cee8eb3a13af923bd144e339d19eaa30cdcee73 Mon Sep 17 00:00:00 2001 From: Peter Boy Date: Sep 22 2022 14:59:23 +0000 Subject: Merge #93 `Correct some misspellings` --- diff --git a/docs/modules/ROOT/pages/server-installation-sbc.adoc b/docs/modules/ROOT/pages/server-installation-sbc.adoc index adccead..14b569f 100644 --- a/docs/modules/ROOT/pages/server-installation-sbc.adoc +++ b/docs/modules/ROOT/pages/server-installation-sbc.adoc @@ -180,7 +180,7 @@ Directly at a terminal of the SBC we will make only the minimal, absolutely nece 2. Connect monitor, keyboard and network cable, insert the micro SD card. 3. Connect Raspberry Pi to power and wait. After some time you will be greeted by a very plain configuration screen. 4. If you have a DHCP server on your LAN the only strictly necessary action is to configure root password. Type "4" and enter a suitable password. If you are on a non-US keyboard you should restrict yourself to traditional ASCII and avoid special characters for now. Otherwise, you might later not be able to enter the root password correctly, because a different keyboard mapping applies. In the next stage, with correct mapping, you can set up the password as complex as you like. -5. Ich you don't have a DHCP server on your LAN type "3" and fill in your hostname and your network details. +5. If you don't have a DHCP server on your LAN type "3" and fill in your hostname and your network details. 6. Tap "c" to continue and finalize the configuration. After some waiting, the Fedora Server login prompt appears. + [IMPORTANT] @@ -192,7 +192,7 @@ Always complete this step and close with 'c'. Otherwise this installation routin === Final Configuration -1. On your desktop open a Browser and enter name and port __http://fedora:9090__. Sometimes the internal DNS already work. If not, use the IP address you wrote down, e.g. something like __http://192.168.158.116:9090__. After accepting a warning message due to a missing certificate, voilà, the Cockpit administration interface of the Raspberry Pi appears. +1. On your desktop open a Browser and enter name and port __http://fedora:9090__. Sometimes the internal DNS already works. If not, use the IP address you wrote down, e.g. something like __http://192.168.158.116:9090__. After accepting a warning message due to a missing certificate, voilà, the Cockpit administration interface of the Raspberry Pi appears. + image::serverinstall-sbc-020.png[Cockpit Login Screen] @@ -214,7 +214,7 @@ Select "accounts" in the left navigation column and choose the root account. At + If you chose a simple password during the basic installation, you should replace it with a more complex one at this occasion. -6. If you are non-US you may want to **set your language**. In any case, you should choose the **keyboard layout** correctly. Otherwiese, in case of an emergency you may have to use a directly attached monitor and keyboard again, you need a correct mapping to act efficiently. +6. If you are non-US you may want to **set your language**. In any case, you should choose the **keyboard layout** correctly. Otherwise, in case of an emergency you may have to use a directly attached monitor and keyboard again, you need a correct mapping to act efficiently. + Select "Terminal" in the left navigation menu. You get a terminal access to your device, already logged in as root. + diff --git a/docs/modules/ROOT/pages/service-postgresql-installation.adoc b/docs/modules/ROOT/pages/service-postgresql-installation.adoc index cec69a9..ea639fe 100644 --- a/docs/modules/ROOT/pages/service-postgresql-installation.adoc +++ b/docs/modules/ROOT/pages/service-postgresql-installation.adoc @@ -96,7 +96,7 @@ Fedora preconfigures Postgresql in a way that in any case ensures reliable and m ==== Administrative access -For admin access Fedora postgresql is configured to obtain the host's operating system user name from the kernel and using it as the allowed database user name. Therefore, as soon as someone can authentiate on the host as user __postgres__, that person has administrative priviledges on the postgresql server without any additional password prompt. The only one who can do that by default, is root. Root can configure additional users to be able to su to postgres. In any case, in a whatever emergency, if any then the system administrator is able to quickly access postgresql server unhindered and salvage what can still get salvaged. +For admin access Fedora postgresql is configured to obtain the host's operating system user name from the kernel and using it as the allowed database user name. Therefore, as soon as someone can authentiate on the host as user __postgres__, that person has administrative privileges on the postgresql server without any additional password prompt. The only one who can do that by default, is root. Root can configure additional users to be able to su to postgres. In any case, in a whatever emergency, if any then the system administrator is able to quickly access postgresql server unhindered and salvage what can still get salvaged. If local regulations make it necessary to replace these procedures with a dedicated authentication by postgresql itself, one of the other procedures can be configured later. In general, however, it is not advisable to make any changes. Once root is compromised, there are a lot of completely different problems to get tackled.