Richard Pospesel authored Oct 17, 2019 and Georg Koppen committed Oct 19, 2019

Torbutton expects all bridges to have a fingerprint when creating
the browser's circuit display. This patch works around the case
when the user provides a bridge without a fingerprint by assuming
it is a bridge, but we cannot determine the other displayed info:
type (obfs4, meek, etc) nor the ip.

In this scenario, the entry node in the circuit display will simply
say "Bridge".

Treat onboarding.properties specially

Add support for meek_lite bridges to bridgeParser. This fixes a
problem where the circuit display broke when a meek_lite bridge
was used.

This reverts commit 676f9b37.

Adding a CSP policy to about:tor to address a failed assertion.