Skip to content
Any updates for wireguard support? As other users, we are migrating more and more to wireguard and would love to keep using viscosity in the future...
Any plans to support Wireguard VPN?
Suggestions/comments/criticisms are welcome here
- Posts: 31
- Joined: Sat Feb 23, 2019 12:15 pm
has been over one year now and no comment from sparklabs.....
Mon Jun 28, 2021 10:32 pmmstroiu wrote: I found this tweet about it's implementation in a future version of the application.Any update about this?
Source: https://twitter.com/sparklabs/status/13 ... 2460012544
Hi Jmars,
I'm afraid nothing we can add at this stage. You'll probably find some other past tweets from us talking about waiting on wg-dynamic to be formalised (most commercial VPN Service Providers are doing configuration outside of the VPN connection over custom HTTPS APIs, which isn't ideal), which is still relevant.
Cheers,
James
I'm afraid nothing we can add at this stage. You'll probably find some other past tweets from us talking about waiting on wg-dynamic to be formalised (most commercial VPN Service Providers are doing configuration outside of the VPN connection over custom HTTPS APIs, which isn't ideal), which is still relevant.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 1
- Joined: Thu Jun 30, 2022 1:53 am
I created an account just for this: please add Wireguard support. It has proven itself and it is time to add support to Viscosity.
My goal of buying this product was to have all my VPN config in one app, but all of my servers are switching to Wireguard so I have to use the Official Wireguard app more and more...
My goal of buying this product was to have all my VPN config in one app, but all of my servers are switching to Wireguard so I have to use the Official Wireguard app more and more...
- Posts: 11
- Joined: Wed Jul 19, 2017 7:33 pm
Thu Dec 09, 2021 3:06 pmJames wrote: Hi Jmars,Hi James,
I'm afraid nothing we can add at this stage. You'll probably find some other past tweets from us talking about waiting on wg-dynamic to be formalised (most commercial VPN Service Providers are doing configuration outside of the VPN connection over custom HTTPS APIs, which isn't ideal), which is still relevant.
Cheers,
James
Any updates for wireguard support? As other users, we are migrating more and more to wireguard and would love to keep using viscosity in the future...
Hi User9186,
Feedback is always appreciated, even requests for features we've heard before.
Multi-protocol support is still on the roadmap. We're a small team, and so have to prioritise what we work on. I've commented elsewhere that one of the big projects we've been working on is fully porting Viscosity to Swift (instead of the mix of ObjC/C/C#/C++ we've been working with, which really slows down adding new functionality). We'll be able to speed up adding new features once this is complete, but frustratingly projects like that always end up taking longer than you expect (and Viscosity has 15 years worth of code).
I do want to stress though that this doesn't necessarily mean that we just need to finish off some porting work and multi-protocol support will be the immediate next thing. The security world moves quickly and our priorities are always in flux to ensure that Viscosity and its users are secure. Hopefully we have some good news on the multi-protocol front for you soon, but please don't hold it against us if we need to jump to other things in the meantime to keep Viscosity up-to-speed.
Cheers,
James
Feedback is always appreciated, even requests for features we've heard before.
Multi-protocol support is still on the roadmap. We're a small team, and so have to prioritise what we work on. I've commented elsewhere that one of the big projects we've been working on is fully porting Viscosity to Swift (instead of the mix of ObjC/C/C#/C++ we've been working with, which really slows down adding new functionality). We'll be able to speed up adding new features once this is complete, but frustratingly projects like that always end up taking longer than you expect (and Viscosity has 15 years worth of code).
I do want to stress though that this doesn't necessarily mean that we just need to finish off some porting work and multi-protocol support will be the immediate next thing. The security world moves quickly and our priorities are always in flux to ensure that Viscosity and its users are secure. Hopefully we have some good news on the multi-protocol front for you soon, but please don't hold it against us if we need to jump to other things in the meantime to keep Viscosity up-to-speed.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Sat Nov 25, 2023 9:27 amJames wrote: Hi User9186,Thanks for your response! I can say I was excited to hear that Viscosity is being completely rewritten in SWIFT code! And I look forward to a future implementation of WireGuard.
Feedback is always appreciated, even requests for features we've heard before.
Multi-protocol support is still on the roadmap. We're a small team, and so have to prioritise what we work on. I've commented elsewhere that one of the big projects we've been working on is fully porting Viscosity to Swift (instead of the mix of ObjC/C/C#/C++ we've been working with, which really slows down adding new functionality). We'll be able to speed up adding new features once this is complete, but frustratingly projects like that always end up taking longer than you expect (and Viscosity has 15 years worth of code).
I do want to stress though that this doesn't necessarily mean that we just need to finish off some porting work and multi-protocol support will be the immediate next thing. The security world moves quickly and our priorities are always in flux to ensure that Viscosity and its users are secure. Hopefully we have some good news on the multi-protocol front for you soon, but please don't hold it against us if we need to jump to other things in the meantime to keep Viscosity up-to-speed.
Cheers,
James