gitignore: ignore certain config and cert files

conf/{grub.cfg,authorized_keys,device.cert.{pem,key}}

these are locally changed config files that should not be
committed

Signed-off-by: Christoph Ostarek <[email protected]>

Author: christoph-zededa

.gitignore

@@ -16,3 +16,7 @@ assets/
 pkg/kernel/build.yml
 pkg/new-kernel/build.yml
 pkg/kernel/certs/*.pem
+conf/authorized_keys
+conf/grub.cfg
+conf/device.cert.pem
+conf/device.key.pem

Makefile

@@ -456,7 +456,9 @@ SWTPM:=SWTPM_$(TPM:%=Y)
 # patch /conf/grub.cfg for developer's builds to enable getty
 GETTY:
 	echo "Enabling GETTY in grub.cfg"
-	grep -qxF 'set_getty' $(CONF_DIR)/grub.cfg || echo 'set_getty' >> $(CONF_DIR)/grub.cfg
+	if [ ! -f $(CONF_DIR)/grub.cfg ]; then\
+	       	cp $(CONF_DIR)/grub.cfg.tmpl $(CONF_DIR)/grub.cfg;\
+	fi
 
 # run-installer
 #

conf/authorized_keys

@@ -1,5 +1,6 @@
-# You can put your GRUB overrides here
+# You can put your GRUB overrides into conf/grub.cfg
 # E.g. to force booting int KVM mode, uncomment the following:
 #   set_global eve_flavor kvm
 # to force booting in Xen mode, uncomment:
 #   set_global eve_flavor xen
+set_getty

conf/grub.cfg renamed to conf/grub.cfg.tmpl

@@ -11,7 +11,7 @@ In general, EVE is trying to make sure that its controller always has the last w
 * `v2tlsbaseroot-certificates.pem` - contains the x509 root certificate to trust for the TLS to the controller when using the V2 API
 * `onboard.cert.pem` - onboarding certificate for the [initial registration](REGISTRATION.md) with the controller
 * `wpa_supplicant.conf` - a legacy way of configuring EVE's WiFi
-* `authorized_keys` - initial authorized SSH keys for accessing EVE's debug console
+* `authorized_keys` - initial authorized SSH keys for accessing EVE's debug console; DO NOT use options, we only accept 'keytype, base64-encoded key, comment' format
 * `bootstrap-config.pb`- initial device configuration used only until device is onboarded (see below for details)
 
 The initial content of these configuration files is stored in the EVE's source tree under [config](../config) folder. From there, these configuration files are baked into the EVE installer images. For the read-write bootable disk installer image these files can further be tweaked by mounting the "EVE" partition and editing those files directly on the installer image. This gives you an ability to take the default installer image and tweak it for your needs without re-building EVE from scratch (obviously this is not an option for a read-only ISO installer image). A typical workflow is to take an installer image from the official EVE build, flash it onto a USB flash drive, insert that USB flash drive into your desktop and edit file on the partition called EVE.