FlightAware Discussions

Webserver Issue - Stretch Plus PiAware 3.6.3

Using the procedures outlined on https://flightaware.com/adsb/piaware/install (Stretch OS; PiAware 3.6.3), my RasiPi3B+ rig is successfully uploading detected traffic to FlightAware and sudo piaware-status reports all processes running.

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.

Thanks in advance for suggestions

This page is only present for piaware sd-card installs.

You should be able to install it with:

sudo apt install piaware-web
1 Like

wiedehopf,

Thanks for the tip!

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…

Thanks for your help!

I’m not sure what you mean, the map is always available there regardless of installation.
At least it should be.

That’s exactly their reasoning, less chance to break a pre-existing installation of whatever.

How do you save it on a default Raspbian?
Isn’t it just written to /etc/wpa_supplicant/wpa_supplicant.conf?

Yes, it’s always saved as clear text in wpa_supplicant.conf

@NotQuiteJohnGlenn
@keithma

You can generate encrypted password as follows:
(Replace MyWifiNetwork by your actual SSID and s3cr3t99 by your actual WiFI password)

pi@piaware:~ $ wpa_passphrase MyWifiNetwork s3cr3t99

network={
        ssid="MyWifiNetwork"
        #psk="s3cr3t99"
        psk=cede189c01f8c9b7cda72469da38f56a846c06f1179ec2dcb38e3b8b239e5074
}

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

That’s not technically encrypted.

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.

SOURCE: http://www.visiospark.com/password-encryption-tool/

.

Encryption Type Encrypted Password
Original Password: s3cr3t99
DES: $1$rSPEMQM/$CE6avxukGkNKmzc2bgJLD1
MD5: 0212a456c74bdf537e276647c688b66c
sha1: 80034df629bde32d988252defbf5cfe5c4b9fb5d
sha224: 136b01ec0e79a63b8aafc6615c0f8c22d32fe1029133d2dc97611584
sha256: fc529fd738795ad00624f88c73ab2ee9d7a65cc10b2d8225c4275971c4d6bb0b
sha384: ce501c9969fc51845af4775c4fd4aa939eded1a85e1e955b220f484d2ba8039b6de43d1f57e88e29ab8aa915b205ef43
sha512: 92672a075b1f0063fccb14770644f17969ac7f91bd9afdb72e341fd395222a65092b448ec111edaa73c3b2ca358d7093a329e87591bf8999860466f649bfdfc0
ripemd128: 8f22256a9a6c5ae4b21a0af20bc20685
ripemd160: 6d4010171b103fcfdfd5e0a2b67cf3f458c7fafe
ripemd256: 2e133e3e73206b785566d8e6d0e38dec53043dffb13a99763839692756b7ea7c
ripemd320: 0b20d6bda226a7a719fcea471ae88bb2447149bf438dc234b8b586a112685dcbe0c3b534c79d7da8
whirlpool: 4756c64cc5714d5a11511ba5878ab3775536a071fef3d4424fb3d091dc96572acc15b0cab13e61184984deb549402b5b0b8adce619004e1462772dee5b70fc3b
snefru: 218a0e9d81298906ac822a1f0f80e880d30109ed8e24d073e828902af2021344
snefru256: 218a0e9d81298906ac822a1f0f80e880d30109ed8e24d073e828902af2021344
gost: 6ec08b5d41e1465ca8e0bd56f69cc83ffa7bffbea46fadd01182526fcf95507e
crc32: d02322fc
crc32b: 33e3aaff
fnv132: fbe42e53
fnv164: 268533c209af39b3
joaat: 5872cf9e
haval128,3: 211032e10874e641dd86c050030d8d78
haval160,3: be7f8e04ed32fb60b56e3c004951a982b74bae98
haval192,3: ee42821bd0070a1a6be56cb3f53d79b4c327f2b7044f85ad

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.

Fully agree.
Piaware SD card is a covenience (plug n play), else it is same as stretch lite + piaware + dump1090-fa add-on.

EDIT:
Two more convenences of Piaware SD card image:

  1. Easy configuration by sudo piaware-config [parameter] [value] OR sudo nano /boot/piaware-config.txt

  2. Radio page

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?

Of course piaware-config works.
Just no /boot/piaware-config.txt

Even that you might just be able to create and it would read settings from it.

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

I think the only piaware-config command I’ve ever used is for the feeder ID so I’m peachy.

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

1 Like