[Wireguard] Dashboard shows part of public key in table of Endpoint

[anefkens]

Describe the bug
When using the dashboard for Wireguard, it shows the public keys of the endpoint to identify the endpoints. I would have expected to see the name of the endpoint instead.

To Reproduce
Steps to reproduce the behavior:

1. Setup WireGuard VPN Service
2. Add Wireguard to the Dashboard
3. Save the dashboard
4. See part of the public key in the list under endpoints

Expected behavior
The actual name for each VPN client in the column of Endpoint

Screenshots

Environment
OPNsense 21.1-amd64
FreeBSD 12.1-RELEASE-p12-HBSD
OpenSSL 1.1.1i 8 Dec 2020
AMD GX-412TC SOC (4 cores)
PC Engines apu4

[sorano]

There is actually already an old issue for this: #1958

And a PR that's been cooking for a while: #1970

So if you want to you can manually edit the php files with the changes from that PR.

(Offtopic, fellow AFOL eh? 😃 )

[anefkens]

Thanks, I’ll take a look. (Offtopic: yep and proud of it… ;-) Was planning to visit Billund this year, but considering the restrictions do not think it will happen this year… )

…

On 3 Mar 2021, at 14:38, Sorano ***@***.***> wrote: There is actually already an old issue for this: #1958 <#1958> And a PR that's been cooking for a while: #1970 <#1970> So if you want to you can manually edit the php files with the changes from that PR. (Offtopic, fellow AFOL eh? 😃 ) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2217 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALAPGUVEX34KVN4EGA6GXDTBY3V3ANCNFSM4XEZBEUQ>.

[pagong]

You might also consider using
https://github.com/warner/wireguard-vanity-address
for generating public keys that start with a string that has some meaning to you.

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.