Closed bestpika closed 1 year ago
Is this actually a problem with WireSock?
WireSock and WireSockUI use distinct APIs to parse configuration files, making it vital to confirm that both can handle multiple identical keys. However, I'm uncertain if this is a top priority right now.
Some service-generated WireGuard configuration files may have contents similar to the following:
If you import the file at this time, you will receive the error message shown in the following image.
I know that as long as I change the content to the following, it will be fine.
But this will not be a problem in the official WireGuard client, so I hope to allow configuration files with this type of content and parse them correctly. Thank you.