On Mon, Dec 5, 2022 at 6:15 PM Houman wrote:
>
> Hi Jason,
>
> I was wondering if there are still any plans to focus on the Apple
> development and bring the repo more up-to-date, please.
>
> Since the latest major development on the Wireguard Linux repo seems
> to have finished by 31st October,
Hi Jason,
I was wondering if there are still any plans to focus on the Apple
development and bring the repo more up-to-date, please.
Since the latest major development on the Wireguard Linux repo seems
to have finished by 31st October, I was wondering if Apple dev could
be prioritised next,
Thank you Andrej for explaining the reason. It makes sense.
Kind regards,
Houman
On Thu, 22 Sept 2022 at 10:44, Andrej Mihajlov wrote:
>
> Hi Houman,
>
> I believe that the crash coming from withMemoryRebound is actually assertion
> (assert()). Very often assertions are stripped out from
Hi Houman,
I believe that the crash coming from withMemoryRebound is actually assertion
(assert()). Very often assertions are stripped out from release builds, so I
guess it could be the reason why it just worked in release builds.
Jason has already replied in regards of releasing an update.
Sounds good, thanks, Jason.
On Thu, 22 Sept 2022 at 10:38, Jason A. Donenfeld wrote:
>
> On 9/22/22, Houman wrote:
> > Hi Andrej,
> >
> > It works, well done!
> >
> > A strange thing though, before your patch I was still able to connect
> > to the VPN server, if I changed the schema to Release
On 9/22/22, Houman wrote:
> Hi Andrej,
>
> It works, well done!
>
> A strange thing though, before your patch I was still able to connect
> to the VPN server, if I changed the schema to Release instead of
> Debug. Now with your patch it also works under Debug schema, which is
> fantastic.
> What
Hi Andrej,
It works, well done!
A strange thing though, before your patch I was still able to connect
to the VPN server, if I changed the schema to Release instead of
Debug. Now with your patch it also works under Debug schema, which is
fantastic.
What could be the technical reason that it
Hi,
I think we have a bug. If I am right, basically in both IPv4 and IPv6
extensions, withMemoryRebound takes capacity which is actually a number of
instances of a given type (sockaddr_ variant) and not the byte size of a
struct.
Could you please patch your WireGuardKit with the following
My existing Wireguard iOS implementation stopped working after
upgrading to Xcode 14 today.
When trying to connect to servers that support only IPv4, then it's
fine. But if the server supports both IPv6 and IPv4 then the tunnel
crashes:
This IPv6 extension in
