The Kinguard Project Wiki - User contributions [en]

https://www.kinguardproject.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Pa The Kinguard Project Wiki - User contributions [en] 2026-04-16T10:16:35Z User contributions MediaWiki 1.41.1 https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=126 Downloads 2020-07-19T11:58:11Z

<p>Pa: updated release links.</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 19.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/20.07 Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/20.07/ReleaseNotes_20.07.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> '''For KEEP''', the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> '''For OPI''' write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. When the installation is complete replace the installation SD-card with a blank SD card.<br /> <br /> '''Special OPI note when upgradeing''' from the older OPI software to the newer Kinguard-based version. '''It is not possible to reuse data directly from an old SD-card'''. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI-Legacy/install/ Installation images]<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI-Legacy/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-KEEP-Legacy Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=105 Downloads 2018-12-22T15:55:06Z

<p>Pa: /* Older releases provided by OpenProducts */</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> '''For KEEP''', the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> '''For OPI''' write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. When the installation is complete replace the installation SD-card with a blank SD card.<br /> <br /> '''Special OPI note when upgradeing''' from the older OPI software to the newer Kinguard-based version. '''It is not possible to reuse data directly from an old SD-card'''. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI-Legacy/install/ Installation images]<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI-Legacy/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-KEEP-Legacy Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=103 Downloads 2018-12-22T15:46:03Z

<p>Pa: /* KEEP */</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> '''For KEEP''', the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> '''For OPI''' write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. When the installation is complete replace the installation SD-card with a blank SD card.<br /> <br /> '''Special OPI note when upgradeing''' from the older OPI software to the newer Kinguard-based version. '''It is not possible to reuse data directly from an old SD-card'''. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI/install/ Installation images]<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-KEEP Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=102 Downloads 2018-12-22T15:45:45Z

<p>Pa: /* OPI */</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> '''For KEEP''', the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> '''For OPI''' write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. When the installation is complete replace the installation SD-card with a blank SD card.<br /> <br /> '''Special OPI note when upgradeing''' from the older OPI software to the newer Kinguard-based version. '''It is not possible to reuse data directly from an old SD-card'''. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI/install/ Installation images]<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-OPI/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=101 Downloads 2018-12-22T15:43:39Z

<p>Pa: /* OPI */</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> '''For KEEP''', the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> '''For OPI''' write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. When the installation is complete replace the installation SD-card with a blank SD card.<br /> <br /> '''Special OPI note when upgradeing''' from the older OPI software to the newer Kinguard-based version. '''It is not possible to reuse data directly from an old SD-card'''. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-Legacy/install/ Installation images]<br /> <br /> [https://www.kinguardproject.org/download/releases/OpenProducts-Legacy/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=96 Downloads 2018-12-09T16:27:31Z

<p>Pa: Clairfication on the need for a new/formatted SD card after OPI install.</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> '''For KEEP''', the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> '''For OPI''' write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. When the installation is complete replace the installation SD-card with a blank SD card.<br /> <br /> '''Special OPI note when upgradeing''' from the older OPI software to the newer Kinguard-based version. '''It is not possible to reuse data directly from an old SD-card'''. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=95 Downloads 2018-12-03T12:01:38Z

<p>Pa: /* How to install */</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> For KEEP, the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> For OPI write the image file (.img) to a uSD card (using Etcher or similar tool), insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete. <br /> <br /> '''Special OPI note''' regarding upgrading from the older OPI software to the newer Kinguard-based version. It is currently not possible to reuse data directly from an old SD-card. The default procedure is to perform a backup to USB and then do a complete reinstall with a new/newly formatted SD card.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=93 Downloads 2018-10-08T13:42:00Z

<p>Pa: Update that root-privaliges are needed to edit install parameters.</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> For KEEP, the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters available. Note that you need to be "root" in order to change these parameters.<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=92 Downloads 2018-10-08T10:53:34Z

<p>Pa: Added note about rescue mode.</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> A simple cross platform tool to write .img files to an SD Card or USB Stick is Etcher. https://etcher.io/<br /> <br /> For KEEP, the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact. <br /> <br /> If set to '0', the system will boot into a rescue mode, leaving all data on the system intact, but allowing access to the system using ssh and serial console.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=88 Downloads 2018-10-01T08:59:55Z

<p>Pa: Updated with installation time.</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the img-file to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> For KEEP, the installation takes about 3 minutes. Unfortunately there is currently no visual indication that the installation has completed. A hint though is that when the harddrive spins down, the installation is complete. After the completed installation the unit needs to be power cycled.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> OPI will turn off all LEDs when the installation is complete.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=87 Documentation/sysconfig 2018-08-30T13:26:41Z

<p>Pa: Added example for StringList</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> },<br /> "dns":<br /> {<br /> "availabledomains":["op-i.me","mykeep.net"]<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount<br /> |- vmailbox path to virtual mailbox mapping, relative to filesystem->storagemount<br /> |- vdomains path to virtual domains file (Which domains to accept mail from), relative to filesystem->storagemount<br /> |- saslpasswd path to sasl password store file, relative to filesystem->storagemount<br /> |- oprelayserver URL to OpenProducts smtp-relay<br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- certpath the location where signed certificate are stored<br /> |- customcert full path to custom certificate<br /> |- customkey full path to private key for the custom certificate<br /> |- defaultcert full path to default (fallback) certificate<br /> |- defaultkey full path to private key for the default (fallback) certificate<br /> |- activecert path to symlink for the certificate being used<br /> |- activekey path to symlink for key corresponding to activecert</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=86 Documentation/sysconfig 2018-07-09T07:52:31Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount<br /> |- vmailbox path to virtual mailbox mapping, relative to filesystem->storagemount<br /> |- vdomains path to virtual domains file (Which domains to accept mail from), relative to filesystem->storagemount<br /> |- saslpasswd path to sasl password store file, relative to filesystem->storagemount<br /> |- oprelayserver URL to OpenProducts smtp-relay<br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- certpath the location where signed certificate are stored<br /> |- customcert full path to custom certificate<br /> |- customkey full path to private key for the custom certificate<br /> |- defaultcert full path to default (fallback) certificate<br /> |- defaultkey full path to private key for the default (fallback) certificate<br /> |- activecert path to symlink for the certificate being used<br /> |- activekey path to symlink for key corresponding to activecert</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=81 Documentation/sysconfig 2018-07-04T11:49:39Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- certpath the location where signed certificate are stored<br /> |- customcert full path to custom certificate<br /> |- customkey full path to private key for the custom certificate</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=80 Documentation/sysconfig 2018-07-04T11:24:03Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- certpath the location where signed certificate are stored<br /> |- usercertpath the location where user certificate are stored</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=79 Documentation/sysconfig 2018-07-04T09:57:46Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- customkey complete path to file that holds the private key for the custom certificate (If used)<br /> |- customcert complete path to file that holds the custom certificate (If used)</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=78 Documentation/sysconfig 2018-07-04T09:41:11Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- defaultkey complete path to file that holds the private key for the default certificate (If used)<br /> |- defaultcert complete path to file that holds the default certificate (If used)<br /> |- customkey complete path to file that holds the private key for the custom certificate (If used)<br /> |- customcert complete path to file that holds the custom certificate (If used)</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=77 Documentation/sysconfig 2018-07-04T09:34:27Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- key complete path to file that holds the private key for the default certificate (If used)<br /> |- cert complete path to file that holds the default certificate (If used)<br /> |- customkey complete path to file that holds the private key for the custom certificate (If used)<br /> |- customcert complete path to file that holds the custom certificate (If used)</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=76 Documentation/sysconfig 2018-07-04T08:15:01Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- key complete path to file that holds the private key for the custom certificate (If used)<br /> |- cert complete path to file that holds the custom certificate (If used)</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=75 Documentation/sysconfig 2018-07-04T08:14:38Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey path to the private key used for lower level authentication on service provider backends<br /> |- dnspubkey path to corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - filesystem<br /> |- storagemount mountpoint of storage volume<br /> |- luksdevice luks-created cryptodevice (If used)<br /> |- lvmdevice lvm-created storage pool (If used)<br /> |- lvmvg lvm-created volume group (If used)<br /> |- lvmlv lvm-created logical volume (If used)<br /> <br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - mail<br /> |- localmail configuration file for local mail delivery, relative to filesystem->storagemount<br /> |- virtualalias configuration file for virtual mail aliases, relative to filesystem->storagemount <br /> <br /> - setup<br /> |- conntesthost host used for connectivity tests<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - webapps<br /> |- theme the theme used by webapps<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> |- key complete path to file that holds the private key for the custom certificate<br /> |- cert complete path to file that holds the custom certificate</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=71 Documentation/sysconfig 2018-06-29T06:38:40Z

<p>Pa: /* Config scopes and variables */</p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> Very few of these parameters are mandatory. However default behavior for the applications will vary if an expected parameter is missing.<br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey the key used for lower level authentication on service provider backends<br /> |- dnspubkey corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> <br /> - webapps<br /> |- theme the theme used by webapps</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=70 Documentation/sysconfig 2018-06-29T06:34:49Z

<p>Pa: </p> <hr /> <div>=System configuration file=<br /> <br /> The kinguard system components store all generic none security sensitive configuration in a central configuration file "/etc/kinguard/sysconfig.json".<br /> <br /> This file should however never be manually edited it should always be accessed programatically using either [https://github.com/Kinguard/libkgp libkgp] or any wrapper to this library described further down. <br /> <br /> === File Syntax ===<br /> For reference here is the layout of the sysconfig json file. Please read the file for reference but never ever edit it manually.<br /> <br /> The complete configuration file is one json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> === Native access via libkgp ===<br /> Libkgp is the main library to use when programming locally for the kinguard system it contains c++ objects for managing all kinguard functions. No official documentation exists for this yet but pointers on how it works can be found in the [https://github.com/Kinguard/libkgp/tree/master/test unit tests] and in the applications utilizing them for example [https://github.com/Kinguard/kgp-backend KGP backend] and [https://github.com/Kinguard/kgp-control KGP startup control]<br /> <br /> To access the system configuration the [https://github.com/Kinguard/libkgp/blob/master/SysConfig.h SysConfig class]<br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.<br /> <br /> = Config scopes and variables =<br /> - hostinfo<br /> |- unitid system id to use as account identifier for service provider backends<br /> |- hostname the 'host' part of the [https://en.wikipedia.org/wiki/Fully_qualified_domain_name FQDN]<br /> |- domain the 'domain' part of the FQDN<br /> |- cafile the ca file used to verify service provider backends<br /> |- sysauthkey the key used to access data on service provider backends<br /> |- syspubkey corresponding public key<br /> <br /> - upnp<br /> |- forwardports which ports the device shall try to forward from a UPNP gateway<br /> <br /> - autoupdate<br /> |- enabled turns on and off automatic updates<br /> <br /> - backup<br /> |- backend which storage backend to use for s3ql <br /> |- devicemountpath where to mount local devices, such as usb memories<br /> |- enabled turns on and off the backup service<br /> <br /> - dns<br /> |- dnsauthkey the key used for lower level authentication on service provider backends<br /> |- dnspubkey corresponding public key<br /> |- enabled turns on and off dns updates<br /> |- provider backend provider<br /> <br /> - webcertificate<br /> |- backend backend provider<br /> |- enabled turns on and off generation of web certificates<br /> <br /> - webapps<br /> |- theme the theme used by webapps</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=66 Documentation/sysconfig 2018-06-05T13:13:39Z

<p>Pa: /* Python */</p> <hr /> <div>=System configuration file=<br /> <br /> Runtime parameters should be saved in the file "/etc/kinguard/sysconfig.json".<br /> <br /> Access to the file should be done using [https://github.com/Kinguard/libkgp libkgp (former libopi)], either directly using the shared lib, or by the wrappers for different programming languages.<br /> <br /> === File Syntax ===<br /> The configuration file is a json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> <br /> Example:<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=65 Documentation 2018-06-05T13:10:08Z

<p>Pa: /* Software Components */</p> <hr /> <div>== Manual Source ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.<br /> <br /> In order for this to work, there are separate branches for different products and also a separate branch for a short one-pager.<br /> <br /> == OPI ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> === Schematics ===<br /> The schematics for OPI is available for download [https://download.openproducts.com/opi/documentation/OP-I_1B Rev B .pdf as pdf here]. It is in most aspects a copy of BeageBoneBlack, with the HDMI removed.<br /> <br /> == KEEP ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> === Schematics ===<br /> KEEP is using a SOM (System On Module) from SolidRun, with 2GB DDR RAM and 8GB eMMC. The carrier board is made by [https://www.openproducts.com OpenProducts]. Schematics and component placement for that board is available [https://download.openproducts.com/keep/documentation/KEEP_R1B.pdf as pdf here].<br /> <br /> [https://download.openproducts.com/keep/documentation/KEEP_PCB.step A stp-model] for the PCBA is also available for download (~60MB).<br /> <br /> == SOFTWARE COMPONENTS ==<br /> There are a number of software components available in The Kinguard Project, some of them documented here, but most is by comments in source code and available by running the application with "--help"<br /> * System configuration (sysconfig.json). [[Documentation/sysconfig|Details]]<br /> * System utilities, (kgp-sysinfo, kgp-notifier) [https://github.com/Kinguard/kinguard-utils Details]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=64 Documentation 2018-06-05T13:07:43Z

<p>Pa: /* Software Components */</p> <hr /> <div>== Manual Source ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.<br /> <br /> In order for this to work, there are separate branches for different products and also a separate branch for a short one-pager.<br /> <br /> == OPI ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> === Schematics ===<br /> The schematics for OPI is available for download [https://download.openproducts.com/opi/documentation/OP-I_1B Rev B .pdf as pdf here]. It is in most aspects a copy of BeageBoneBlack, with the HDMI removed.<br /> <br /> == KEEP ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> === Schematics ===<br /> KEEP is using a SOM (System On Module) from SolidRun, with 2GB DDR RAM and 8GB eMMC. The carrier board is made by [https://www.openproducts.com OpenProducts]. Schematics and component placement for that board is available [https://download.openproducts.com/keep/documentation/KEEP_R1B.pdf as pdf here].<br /> <br /> [https://download.openproducts.com/keep/documentation/KEEP_PCB.step A stp-model] for the PCBA is also available for download (~60MB).<br /> <br /> == Software Components ==<br /> There are a number of software components available in The Kinguard Project, some of them documented here, but most is by comments in source code and available by running the application with "--help"<br /> * System configuration (sysconfig.json). [[Documentation/sysconfig|Details]]<br /> * System utilities, (kgp-sysinfo, kgp-notifier) [https://github.com/Kinguard/kinguard-utils Details]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=63 Documentation 2018-06-05T13:05:36Z

<p>Pa: /* Software Components */</p> <hr /> <div>== Manual Source ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.<br /> <br /> In order for this to work, there are separate branches for different products and also a separate branch for a short one-pager.<br /> <br /> == OPI ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> === Schematics ===<br /> The schematics for OPI is available for download [https://download.openproducts.com/opi/documentation/OP-I_1B Rev B .pdf as pdf here]. It is in most aspects a copy of BeageBoneBlack, with the HDMI removed.<br /> <br /> == KEEP ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> === Schematics ===<br /> KEEP is using a SOM (System On Module) from SolidRun, with 2GB DDR RAM and 8GB eMMC. The carrier board is made by [https://www.openproducts.com OpenProducts]. Schematics and component placement for that board is available [https://download.openproducts.com/keep/documentation/KEEP_R1B.pdf as pdf here].<br /> <br /> [https://download.openproducts.com/keep/documentation/KEEP_PCB.step A stp-model] for the PCBA is also available for download (~60MB).<br /> <br /> == Software Components ==<br /> There are a number of software components available in The Kinguard Project, some of them documented here, but most is by comments in source code and available by running the application with "--help"<br /> * System configuration (sysconfig.json). [[Documentation/sysconfig|Details]]<br /> * System utilities, (kgp-sysinfo, kgp-notifier) [[https://github.com/Kinguard/kinguard-utils|Details]]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation/sysconfig&diff=62 Documentation/sysconfig 2018-06-05T13:02:33Z

<p>Pa: Initial 'sysconfig' documentation</p> <hr /> <div>=System configuration file=<br /> <br /> Runtime parameters should be saved in the file "/etc/kinguard/sysconfig.json".<br /> <br /> Access to the file should be done using [https://github.com/Kinguard/libkgp libkgp (former libopi)], either directly using the shared lib, or by the wrappers for different programming languages.<br /> <br /> === File Syntax ===<br /> The configuration file is a json object (note that javascript object syntax is not permitted).<br /> <br /> The file is set up using a "scope" and "key/value" pairs.<br /> <br /> All scope and key identifiers shall be lowercase and written with '''letters and digits only''', no "-" or "_".<br /> <br /> Example:<br /> {<br /> "webapps":<br /> {<br /> "theme":"kgp"<br /> },<br /> "hostinfo":<br /> {<br /> "unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939",<br /> "hostname":"myhost",<br /> "domain":"example.org"<br /> }<br /> }<br /> <br /> <br /> === Wrappers ===<br /> Most wrappers can also be used to access other information provided by libkgp, such as the current running system type, information about system storage etc.<br /> <br /> ===== Shell Scripts =====<br /> For shell scripts, use "[https://github.com/Kinguard/kinguard-utils kgp-sysinfo]". Run kgp-sysinfo --help for options.<br /> <br /> Example:<br /> # kgp-sysinfo -c hostinfo -k unitid -p<br /> c79f425c-9af7-4f38-b1ba-d53277b14939<br /> <br /> # kgp-sysinfo -c hostinfo -k unitid<br /> {"unitid":"c79f425c-9af7-4f38-b1ba-d53277b14939"}<br /> <br /> ===== Python =====<br /> For Python3, use the python library "[https://github.com/Kinguard/kgp-pywrap pylibopi]"<br /> >>> import pylibopi<br /> >>> pylibopi.StorageDevice()<br /> '/dev/disk/by-path/platform-f10a8000.sata-ata-2'<br /> <br /> ===== C =====<br /> For C programs, [https://github.com/Kinguard/libkgp_wrapper libkgp_wrapper] can be used.<br /> <br /> ===== PHP =====<br /> Currently no native PHP wrapper exists, but kgp-sysinfo defaults to output json (see above) that can easily be used in PHP.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=61 Documentation 2018-06-05T12:25:15Z

<p>Pa: </p> <hr /> <div>== Manual Source ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.<br /> <br /> In order for this to work, there are separate branches for different products and also a separate branch for a short one-pager.<br /> <br /> == OPI ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> === Schematics ===<br /> The schematics for OPI is available for download [https://download.openproducts.com/opi/documentation/OP-I_1B Rev B .pdf as pdf here]. It is in most aspects a copy of BeageBoneBlack, with the HDMI removed.<br /> <br /> == KEEP ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> === Schematics ===<br /> KEEP is using a SOM (System On Module) from SolidRun, with 2GB DDR RAM and 8GB eMMC. The carrier board is made by [https://www.openproducts.com OpenProducts]. Schematics and component placement for that board is available [https://download.openproducts.com/keep/documentation/KEEP_R1B.pdf as pdf here].<br /> <br /> [https://download.openproducts.com/keep/documentation/KEEP_PCB.step A stp-model] for the PCBA is also available for download (~60MB).<br /> <br /> == Software Components ==<br /> There are a number of software components available in The Kinguard Project, some of them documented here, but most is by comments in source code and available by running the application with "--help"<br /> * System configuration (sysconfig.json). [[Documentation/sysconfig|Details]]<br /> * System utilities, (kgp-sysinfo, kgp-notifier) [[Documentation/kinguard-utils|Details]]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=60 Downloads 2018-05-30T10:08:19Z

<p>Pa: </p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> === Install images ===<br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the image to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=59 Downloads 2018-05-18T14:14:10Z

<p>Pa: /* How to install */</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the image to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> <br /> If data is to be restored from a backup, the recommended way is to make sure that a backup on USB exists (usually faster than downloading from on-line servers), make a clean shutdown of OPI and then leave the USB memory inserted during the setup. The data set can then be chosen during the "Restore" step of the setup procedure.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=58 Downloads 2018-05-18T13:39:01Z

<p>Pa: </p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> === How to install ===<br /> For KEEP write the image to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> <br /> === Installer Configuration ===<br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=57 Downloads 2018-05-18T13:09:19Z

<p>Pa: 18.06 release</p> <hr /> <div>== Current release ==<br /> The current release for The Kinguard Project is "Kinguard 18.06".<br /> <br /> Install images are provided on the Kinguard [https://www.kinguardproject.org/download/releases/18.06/ Download Area] for both OPI and KEEP.<br /> <br /> Please read the [https://www.kinguardproject.org/download/releases/18.06/ReleaseNotes_18.06.pdf ReleseNotes].<br /> <br /> For KEEP write the image to a USB stick and press and hold the button for 10 seconds while inserting power.<br /> <br /> For OPI write the imate to a uSD card, insert it into OPI and apply power.<br /> <br /> <br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].<br /> <br /> == Older releases provided by OpenProducts ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=56 Documentation 2018-04-19T10:20:24Z

<p>Pa: </p> <hr /> <div>== Manual Source ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.<br /> <br /> In order for this to work, there are separate branches for different products and also a separate branch for a short one-pager.<br /> <br /> == OPI ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> === Schematics ===<br /> The schematics for OPI is available for download [https://download.openproducts.com/opi/documentation/OP-I_1B Rev B .pdf as pdf here]. It is in most aspects a copy of BeageBoneBlack, with the HDMI removed.<br /> <br /> == KEEP ==<br /> <br /> === Manual ===<br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> === Schematics ===<br /> KEEP is using a SOM (System On Module) from SolidRun, with 2GB DDR RAM and 8GB eMMC. The carrier board is made by [https://www.openproducts.com OpenProducts]. Schematics and component placement for that board is available [https://download.openproducts.com/keep/documentation/KEEP_R1B.pdf as pdf here].<br /> <br /> [https://download.openproducts.com/keep/documentation/KEEP_PCB.step A stp-model] for the PCBA is also available for download (~60MB).</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Screenshots&diff=55 Screenshots 2018-04-19T09:59:42Z

<p>Pa: Created page with "== Admin UI == Start/Status page KEEP Status Page User Mangement KEEP User Management Local Mail Mangement F..."</p> <hr /> <div>== Admin UI ==<br /> <br /> Start/Status page<br /> <br /> [[File:Status Page.png|400px|KEEP Status Page]]<br /> <br /> User Mangement<br /> <br /> [[File:UserPage.png|400px|KEEP User Management]]<br /> <br /> Local Mail Mangement<br /> <br /> [[File:LocalMailAccounts.png|400px|Local Mail Mangement]]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=File:LocalMailAccounts.png&diff=54 File:LocalMailAccounts.png 2018-04-19T09:56:54Z

<p>Pa: </p> <hr /> <div>Local Mail Management</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=File:UserPage.png&diff=53 File:UserPage.png 2018-04-19T09:55:12Z

<p>Pa: </p> <hr /> <div>KEEP admin UI user management</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=File:Status_Page.png&diff=52 File:Status Page.png 2018-04-19T09:50:35Z

<p>Pa: </p> <hr /> <div>KEEP Status Page</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Enable_serial_console&diff=51 Enable serial console 2018-04-19T09:45:01Z

<p>Pa: Updated with image of serialport connection</p> <hr /> <div>On both OPI and KEEP, as well as on BeagleBoneBlack, there is a 6-pin header that can be used for debugging the system using a serial cable (not mounted on OPI though), the pinout is compatible with FTDI [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf TTL-232R]<br /> <br /> Setting for the serial port is 115200, 8N1.<br /> <br /> By default, the boot log is displayed on the console, but it can also be enabled for login by reinstalling the unit. Prior to install edit the file "/etc/kgp-install.conf" on the installation media (disk/usb memory/uSD card) and setting the parameter DO_ADDROOT to 1.<br /> <br /> This will make it possible to log into the system with the user "root" and password "op237" on the serial port. Note that this does not enable ssh access, only access using the serial port.<br /> <br /> ==== Serial port connection ====<br /> [[File:KEEP serial connection.jpg|thumb|right|TTL to USB serial cable connection]]<br /> The image shows how to connect the cable mentioned above to KEEP.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=50 Downloads 2018-04-19T09:43:33Z

<p>Pa: </p> <hr /> <div>== Currently available downloads ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]<br /> <br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> How to connect to the serial port is described [[Enable serial console|here]].</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=49 Downloads 2018-04-19T09:41:35Z

<p>Pa: Updated with install parameters</p> <hr /> <div>== Currently available downloads ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]<br /> <br /> In the installer image there is a configuration file that can be used to alter the behavior of the installer image.<br /> <br /> In "/etc/kgp-install.conf" there are few parameters avaialbe:<br /> <br /> DO_INSTALL=1<br /> <br /> By default this parameter is set to "1", which will cause the image to basically do a factory reset by formatting the internal eMMC and reinstalling system software. Any data on the data disk will be left intact.<br /> <br /> DO_ADDROOT=0 <br /> <br /> By default this parameter is set to "0". By changing this to "1", the system will be installed a root account is added with the password "op237".<br /> This is only available on the serial port, ssh is not enabled by default.<br /> <br /> <br /> ==== Serial port connection ====<br /> [[File:KEEP serial connection.jpg|thumb|right|TTL to USB serial cable connection]]<br /> The image shows how to connect a [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf FTDI DS TTL-232R] cable to KEEP.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=File:KEEP_serial_connection.jpg&diff=48 File:KEEP serial connection.jpg 2018-04-19T09:38:30Z

<p>Pa: </p> <hr /> <div>KEEP serial connection using a TTL to USB cable</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Enable_serial_console&diff=47 Enable serial console 2018-04-13T06:50:27Z

<p>Pa: </p> <hr /> <div>On both OPI and KEEP, as well as on BeableBoneBlack, there is a 6-pin header that can be used for debugging the system using a serial cable (not mounted on OPI though), the pinout is compatible with FTDI [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf TTL-232R]<br /> <br /> Setting for the serial port is 115200, 8N1.<br /> <br /> By default, the boot log is displayed on the console, but it can also be enabled for login by reinstalling the unit. Prior to install edit the file "/etc/kgp-install.conf" on the installation media (disk/usb memory/uSD card) and setting the parameter DO_ADDROOT to 1.<br /> <br /> This will make it possible to log into the system with the user "root" and password "op237" on the serial port. Note that this does not enable ssh access, only access using the serial port.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Enable_serial_console&diff=46 Enable serial console 2018-04-13T06:49:43Z

<p>Pa: </p> <hr /> <div>On both OPI and KEEP, as well as on BeableBoneBlack, there is a 6-pin header that can be used for debugging the system using a serial cable, the pinout is compatible with FTDI [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf TTL-232R]<br /> <br /> Setting for the serial port is 115200, 8N1.<br /> <br /> By default, the boot log is displayed on the console, but it can also be enabled for login by reinstalling the unit. Prior to install edit the file "/etc/kgp-install.conf" on the installation media (disk/usb memory/uSD card) and setting the parameter DO_ADDROOT to 1.<br /> <br /> This will make it possible to log into the system with the user "root" and password "op237" on the serial port. Note that this does not enable ssh access, only access using the serial port.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Enable_serial_console&diff=45 Enable serial console 2018-04-13T05:49:32Z

<p>Pa: Created page with "On both OPI and KEEP, as well as on BeableBoneBlack, there is a 6-pin header that can be used for debugging the system using a serial cable, the pinout is compatible with FTDI..."</p> <hr /> <div>On both OPI and KEEP, as well as on BeableBoneBlack, there is a 6-pin header that can be used for debugging the system using a serial cable, the pinout is compatible with FTDI [url=http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf]TTL-232R[/url].<br /> <br /> Setting for the serial port is 115200, 8N1.<br /> <br /> By default, the boot log is displayed on the console, but it can also be enabled for login by reinstalling the unit. Prior to install edit the file "/etc/kgp-install.conf" on the installation media (disk/usb memory/uSD card) and setting the parameter DO_ADDROOT to 1.<br /> <br /> This will make it possible to log into the system with the user "root" and password "op237" on the serial port. Note that this does not enable ssh access, only access using the serial port.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Tutorials_and_How-tos&diff=44 Tutorials and How-tos 2018-04-13T05:40:15Z

<p>Pa: /* Intermediate */</p> <hr /> <div>== Beginner ==<br /> <br /> * [[Access your unit using SSH]]<br /> * [[SSH access using private/public key pair]]<br /> * [[Run a backup manually]]<br /> <br /> == Intermediate ==<br /> * [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=750/ Change to a larger SD card on OPI]<br /> * [[Enable serial console]]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=43 Downloads 2018-03-06T15:13:26Z

<p>Pa: /* OPI */</p> <hr /> <div>== Currently available downloads ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of root/op237. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=42 Downloads 2018-03-06T15:12:58Z

<p>Pa: /* Currently available downloads */</p> <hr /> <div>== Currently available downloads ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> The rescue image is very similar to the install image, only that the image does not re-install the system. The system will be available both on the serial port and on ssh with the user/password of 'root'/'op237'. The root file system can then be accessed and manipulated, but all user data is only available if the encrypted partition in unlocked and mounted by hand.<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=41 Downloads 2018-03-06T15:07:31Z

<p>Pa: Added link to re-install post on forum.</p> <hr /> <div>== Currently available downloads ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> Instructions on how to reinstall is available [https://www.kinguardproject.org/forum/viewtopic.php?f=345&t=466 here]<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Downloads&diff=40 Downloads 2018-03-01T14:31:25Z

<p>Pa: Added KEEP install link</p> <hr /> <div>== Currently available downloads ==<br /> <br /> === OPI ===<br /> <br /> [https://download.openproducts.com/opi/install/ Installation images]<br /> <br /> [https://download.openproducts.com/opi/rescue/ Rescue images]<br /> <br /> === KEEP ===<br /> <br /> [https://download.openproducts.com/keep/install/ Installation images]</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=39 Documentation 2018-01-09T13:11:27Z

<p>Pa: /* SOURCE */</p> <hr /> <div>== OPI ==<br /> <br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> <br /> == KEEP ==<br /> <br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> == SOURCE ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.<br /> <br /> In order for this to work, there are seperate branches for different products and also a separate branch for a short one-pager.</div>

Pa https://www.kinguardproject.org/wiki/index.php?title=Documentation&diff=38 Documentation 2018-01-09T13:10:06Z

<p>Pa: Added link to KEEP documentation</p> <hr /> <div>== OPI ==<br /> <br /> The latest compiled version is available [https://download.openproducts.com/opi/documentation/quickstart.pdf as pdf here]<br /> <br /> == KEEP ==<br /> <br /> The latest compiled version is available [https://download.openproducts.com/keep/documentation/keep-quickstart.pdf as pdf here]<br /> <br /> == SOURCE ==<br /> The manual for the is written in latex and located on [https://github.com/Kinguard/manual github]<br /> Ideally this should be adapted to better suit The Kinguard Project, so feel free to contribute.</div>

Pa