That said, URL |PiAware server IP| returns the lighttpd “Placeholder page” page rather than the PiAware status page, and URL |PiAware server IP|/dump1090-fa returns 404-Not Found rather than detail live collection.
I scrubbed the discussions and tried some leads, but no luck. Hopefully I didn’t overlook the solution somehow.
It got me to the status page as you indicated. I never suspected the status page would only be available to SD-card installs but iIn retrospect, I suppose there is no knowing what the Stretch host might be doing otherwise, and FlightAware didn’t want to break whatever else might be going on. That said, I think the option to add this step would be a helpful addition to the Stretch how-to.
Is there a similar option for Stretch users that will enable the map page located at http://host IP here/dump1090-fa/ on the SD-card installation?
I’d be happy using the SD-card installation but I’m unwilling to write my wifi pre-shared key to a cleartext config file…
From encrypted password generated, copy-paste line starting with psk= in file in /etc/wpa_supplicant/wpa_supplicant.conf
Remove line psk="s3cr3t99" which contains un-encrypted password
While you can’t calculate the password from the PSK, the PSK is all you need to join the network.
So the only gain of using PSK would exist if you were to use the same password for something else or another WiFi network.
Maybe i’m missing something but i don’t think so.
True, technically it is “masking”, and not “encryption”.
EDIT:
As far as I know, when a WiFi password is entered in a Phone or Tablet in plain text, the device saves it in an encrypted form, and not in plain text.
Hashing is the term you are looking for.
The SSID (wifi name) and password are combined and hashed with SHA1 to generate the PSK.
Every time you really encrypt something you need to decrypt it before using it.
On a phone the best you can do is encrypt it with a key derived from whatever form of access control you use for it.
But that is not really relevant.
If you really wanted to encrypt the password on the sd-card of the RPi you would need to enter some kind of access control on every boot.
I doubt there is any relevant security difference between using stretch or the piaware sd-card image.
But there is no drawback of using stretch with piaware on top.
So the discussion is moot however you view it.
Out of interest, if I build a new receiver using Stretch Lite, install Piaware, Piaware-web and dump1090-fa, do I lose the ability to use sudo piaware-config feeder-id to set my existing feeder ID?
Not ALL configs work in package install.
Following show accepted, but are ineffective: piaware-config rtlsdr-device-index piaware-config rtlsdr-gain piaware-config rtlsdr-ppm
This and lot other piaware-config work in both type of installs (sd image & package install). However dump1090-fa related piaware-config commands are not implemented in package install. In this case edit file /etc/default/dump1090-fa