WireGuard bug when writing config from scratch

Follow

Big Bang

• May 18, 2022 20:23

On a FW Purple, when creating a 3rd party WireGuard VPN Client connection from scratch, there is a bug where the PrivateKey used for the interface is being displayed as a PublicKey once it's created which is a mistake. You need to investigate and correct this.

For example copy and paste this config into the FW app to create a VPN Client config:

[Interface]
Address = 10.0.0.2/24
ListenPort = 51820
PrivateKey = QEwxDMUcSkUsJxTqPIn+Bmkmfl0TgPUTLmFh3DSQiVA=

[Peer]
PublicKey = +zWVFANUEtu0tujtbhS1E/VDlRbl6S0N3LoA1o88KhA=
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = myserver.dyndns.org:51820

You will see that in the iOS firewalla app, the PublicKey of the interface is reported as QEwxDMUcSkUsJxTqPIn+Bmkmfl0TgPUTLmFh3DSQiVA= which is false. It should generate a unique PublicKey so that you can configure it as a peer in my server. 

I believe this is a bug and you should fix it ASAP. Please and thank you.

0

• 

  Firewalla

  • May 20, 2022 04:56

  This is a confirmed display bug, will be fixed in 1.50

  0

  Comment actions Permalink

Please sign in to leave a comment.