It's spring time - let's do a little bit of cleanup ...

and merge PS_Firmware branch changes in a first step.

squashed:

FirmwareImage.ps1: intermediate release (#6)

* FirmwareImage.ps1: order of parameters changed for toRSAPrivateKeyFile

* FirmwareImage.ps1: new ability to create new TarMember objects ...
and add them to the firmware image

* FirmwareImage.ps1: unhide setModTime methods for TarMember objects

* re-format code

* signimage: database schema and examples for collecting vendor keys

* signimage: add unique constraint for HWRevision and correct 7390 value

PSScriptAnalyzerSettings.psd1

@@ -0,0 +1,3 @@
+@{
+    ExcludeRules = @('PSAvoidUsingPlainTextForPassword')
+}

autoupdate/README.md

@@ -1,4 +1,4 @@
-## Proof of concept
+# Proof of concept
 
 Add an option for automatic updates during system reboot to '/var/post_install' - this script is called, while a FRITZ!OS based
 device is preparing to restart.
@@ -9,4 +9,4 @@ value in the bootloader environment) may be auto-adjusted to a value supported i
 
 There's a writing (in German) in an IPPF thread regarding the files in this subfolder:
 
-http://www.ip-phone-forum.de/showthread.php?t=286994&p=2186357
+<http://www.ip-phone-forum.de/showthread.php?t=286994&p=2186357>

avm_kernel_config/README.md

@@ -1,6 +1,8 @@
+# Create a `avm_kernel_config` section for own kernels on FRITZ!OS-based devices
+
 This folder contains some utilities to replace/recreate missing parts from AVM's open-source package.
 
-AVM invented a mechanism to initialize some internal structures at kernel startup from a model-specific part and there seems to be 
+AVM invented a mechanism to initialize some internal structures at kernel startup from a model-specific part and there seems to be
 no way to get these sources from vendor - at least an explicit demand to provide them was more or less ignored. The sources pointed
 out in their answer didn't contain any changes regarding these missing parts.
 
@@ -9,7 +11,7 @@ approach to take this way.
 
 You can find further information in an IPPF thread (but it's in German only):
 
-http://www.ip-phone-forum.de/showthread.php?t=287995
+<http://www.ip-phone-forum.de/showthread.php?t=287995>
 
 If you want to compile the contained sources for a specific model, you have to provide a symlink named "linux" to the root of the
 correct kernel sources. The files "include/uapi/linux/avm_kernel_config.h" and the whole directory "scripts/dtc/libfdt" (from the

customconfig/README.md

@@ -1,8 +1,9 @@
-## custom configuration framework
+# custom configuration framework
+
 The scripts in this subdirectory build a solution (based solely on a full-featured BusyBox binary, xz_comp is an optional
 component and may be used to get a better compression rate for the settings archive file) to manage additional settings
-for extension packages in a single archive file, which is unpacked each time the device will be started and where any 
-changes to the settings directory are monitored by inotifyd. If a monitored file has been changed, a countdown will be 
+for extension packages in a single archive file, which is unpacked each time the device will be started and where any
+changes to the settings directory are monitored by inotifyd. If a monitored file has been changed, a countdown will be
 started. If the timeout elapses, the changes recorded so far will be written to a new archive, which will be used for
 unpacking on the next start.