+See OEM (Ozzmaker) [[https://ozzmaker.com/berrygps-berrygps-imu-quick-start-guide/][quickstart guide for the BerryGPS-IMU]].
+
+**** Physical Setup
+
+BerryGPS-IMU must be electrically connected to the correct pins on the
+GPIO header of a Raspberry Pi Zero W.
+
+*Optional*: stack together with PiZ Uptime 2.0 module. No GPIO pins
+conflict so a simple stacking and soldering with long header pins is
+possible.
+
+**** Software Setup
+***** Install Executables
+
+Install Raspbian 10 Buster onto an SD card image. See the Raspberry Pi
+Foundation [[https://www.raspberrypi.org/documentation/installation/installing-images/README.md][installation instructions]]. Configure WiFi to permit log
+file transfer. Configure SSH to permit remote administration via the
+command line interface.
+
+Make sure to install the ~unattended-upgrades~ package to make sure
+the latest security patches for packages are installed. See [[https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/][this page]]
+for a description of how ~unattended-upgrades~ works.
+
+Install ~gpsd~, ~gpspipe~, ~git~, and this repository for location
+logging capability.
+
+Install ~syncthing~ for log file transfer capability.
+
+Place ~age~ binary (the one compiled for ARM CPU architecture for
+Linux) in ~$HOME/.local/bin~.
+
+***** Disable Swap File
+Since standard Raspbian 10 install involves copying unencrypted file
+system image to SD card which is mounted by the Raspberry Pi, system
+memory may be written to disk in the form of a Swap file as described
+[[https://ideaheap.com/2013/07/stopping-sd-card-corruption-on-a-raspberry-pi/][here]]. In order to reduce the chance that location log data is ever
+written to disk, swap file functionality must be disabled.
+
+To view the status of the swap file in Raspbian 10, run ~free -m~:
+
+#+BEGIN_EXAMPLE
+pi@ninfacyzga-01:~$ free -m
+ total used free shared buff/cache available
+Mem: 432 86 36 21 309 268
+Swap: 99 0 99
+#+END_EXAMPLE
+
+The swap file may be disabled by:
+
+#+BEGIN_EXAMPLE
+pi@ninfacyzga-01:~$ sudo dphys-swapfile swapoff
+pi@ninfacyzga-01:~$ sudo dphys-swapfile uninstall
+pi@ninfacyzga-01:~$ sudo update-rc.d dphys-swapfile remove
+pi@ninfacyzga-01:~$ free -m
+ total used free shared buff/cache available
+Mem: 432 96 33 22 302 258
+Swap: 0 0 0
+#+END_EXAMPLE
+
+***** Automatic Start Configuration
+
+Edit the user cron job list with ~$ crontab -e~ to add the following
+lines:
+
+#+BEGIN_EXAMPLE
+0 * * * * /bin/bash ~/bkgpslog --output ~/dir
+
+@reboot /bin/bash ~/bkgpslog --output ~/dir
+#+END_EXAMPLE
+
+The first line will run ~bkgpslog~ at the start of every hour and save
+output files to the ~dir~ directory in your home folder.
+
+The second line will run ~bkgpslog~ when the system starts up.
+
+~/bin/bash~ tells ~cron~ to run ~bkgpslog~ with Bash.
+
+If encryption and compression are required, then the appropriate
+options must be added. The lines that must be added via ~$ crontab -e~
+may resemble:
+
+#+BEGIN_EXAMPLE
+0 * * * * /bin/bash ~/bkgpslog -c -e -r age1z2...qkv6p -o ~/dir
+
+@reboot /bin/bash ~/bkgpslog -c -e -r age1z2...qkv6p -o ~/dir
+#+END_EXAMPLE
+
+The ~age1z2...qkv6p~ is an ~age~ public key string. Please see the
+[[*Key Generation][Key Generation]] section for an explanation.
+
+The options are:
+
+: -c : tells bkgpslog to compress output
+: -e : tells bkgpslog log to encrypt output
+: -r : tells bkgpslog to interpret the next argument as a pubkey string
+: -o : tells bkgpslog to write output files to the directory represented
+: by the next argument
+
+***** Log Transfer Configuration
+Log files may be shared to other machines via ~syncthing~. See [[https://docs.syncthing.net/][this]]
+manual for how to set up a shared folder and add Ninfacyzga-01 as a
+device. Syncthing's directory synchronization capability allows a
+remote machine to delete files from Ninfacyzga-01 by deleting from the
+shared folder that they both share.
+
+When log files are removed from Ninfacyzga-01 is not within the scope
+of this document.
+
+***** Key Generation
+An ~age~ encryption key may be generated like so:
+#+BEGIN_EXAMPLE
+$ umask # Gets current umask
+0022 # Note: This is the default umask for Raspbian 10
+$ umask 066 # Sets umask so key.txt will have no permissions except for owner (you)
+$ umask # Confirm umask set to 066
+0066
+$ age-keygen > key.txt
+Public key: age1pu5usxm743sx7rf22985xv2f4s0luzv6r6yx4fa7p8c2zyvp9fvqus2xr5
+$ ls -al key.txt
+-rw------- 1 baltakatei baltakatei 184 Jun 29 18:28 key.txt
+$ umask 0022 # Return umask to default value
+$ umask
+0022
+#+END_EXAMPLE
+
+The resulting public/private keypair data looks like:
+#+BEGIN_EXAMPLE
+$ cat key.txt
+# created: 2020-06-29T18:01:56Z
+# public key: age1pu5usxm743sx7rf22985xv2f4s0luzv6r6yx4fa7p8c2zyvp9fvqus2xr5
+AGE-SECRET-KEY-1NEUU5U2XGZGL9UYWNPU5DL99TGJJHFSN4F2E2WCCSDJJ6L5ZMLESNTVTU0
+#+END_EXAMPLE
+
+The file ~key.txt~ is not password-protected by default and should be
+secured like an SSH public key should. The ~$ umask 066~ command run
+before the ~$ age-keygen > key.txt~ command ensures ~key.txt~ will not
+be readable, writeable, or executable to anyone except the owner
+(you).
+
projects / EVA-2020-02.git / blobdiff