Update the meek-amazon fingerprint to B9E7141C594AF25699E0079C1F0146F409495296

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The bridge fingerprint for the meek-amazon bridge has changed. It was: 4EE0CC769EB4B15A872F742EDE27D298A59DCADE but is now: 6DDD1DB8526282837C50E9AB5D14AB50150CD624 People who try using meek-amazon are getting a message like this in their logs: Oct 30 09:18:46.000 [warn] Tried connecting to router at 0.0.2.0:2, but identity key was not as expected: wanted 4EE0CC769EB4B15A872F742EDE27D298A59DCADE but got 6DDD1DB8526282837C50E9AB5D14AB50150CD624.

The bridge changed fingerprint when it was rebooted on 2015-10-09 to renew its TLS certificate: https://lists.torproject.org/pipermail/tor-talk/2015-October/039234.html I neglected to test the bridge using a configured bridge fingerprint. (I only tested it using a configuration that did not specify a fingerprint.) According to the bridge operator, the old identity key is lost.

Please update the bridge's key in bridge_prefs.js. I will attach a patch. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQIcBAEBAgAGBQJWM5u3AAoJEOK5PYFc04jlsRcP/il8KGrD1ORuCmSv0leH20ob NAAsRAAaV12PL9CSKuZS9lQi8InfMvZQSz56MyCkIGkFsgn8TlIq6O8nd1tpC3PM 98S+hwrqbXfs85nGdsYPtWZ4HrKfQkRnxBGErM0ideL6EVLi+fy0B+S83o02ktfl ZB28xs675FjLoEWZhMCDya3hjFQk/vMJXHEOK3GaFzTb6Gj0ELHUCS2ETcCNTSux g/U4xO0Z4Kk42DY00VPJwFjRc2PQ3pEQ/cZECO20D1erhELFzfQScaeWMpH6M2cV gKSxCWpUOpZOuzCriaGveY8Vx1dM0HrmCEdtTwR/U6yN5UtXB06G92u2uuj9UuAQ FAHaqaKpA7nwiNldyGXFsDHFkNb9DHK5O9Y25brTCT7M8MAC1P3gAha0KmLtDUZz gSj/BEs1mGOQN2NozW4kT3OmBj5Ar8TjAIqt0P55zHMREbB7ZYxaFiFtiFxIrGwo HqgIgQu5rU944Ut9SA2nA93onkqdYDp6F+4LgrDfoZUvttRM99nUMPlCrCbtWebn i6R8RhunN1isjpSIv+M1J0rl5s79WXhHY4Bseja5sgX60AkApukaRwBBY1cgS3QZ ADqj1mBttTKJM4DeemPOsA0IHyNY+kBHc7AeNAizU4ULozA+5yYGwKJWiARU3z+w frtlxHT+WoWlswOkq7Xh =ImMV -----END PGP SIGNATURE-----