From ff6d1c959b1801d9a6d88a8cd755acc5eff316ad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ole=20Andr=C3=A9=20Vadla=20Ravn=C3=A5s?= Date: Wed, 5 Jun 2024 18:08:58 +0200 Subject: [PATCH] posts: Fix a broken sentence in the 16.3.0 release notes --- _i18n/en/_posts/2024-05-31-frida-16-3-0-released.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_i18n/en/_posts/2024-05-31-frida-16-3-0-released.markdown b/_i18n/en/_posts/2024-05-31-frida-16-3-0-released.markdown index b3bd93b..09ab731 100644 --- a/_i18n/en/_posts/2024-05-31-frida-16-3-0-released.markdown +++ b/_i18n/en/_posts/2024-05-31-frida-16-3-0-released.markdown @@ -119,9 +119,9 @@ Xcode, Console, etc. a lot less useful. It didn't take us long to find private APIs that would allow us to determine the device-side address inside Apple's tunnel, and also create a so-called -“assertion” so that tunnel is kept open for as long as we need it. But the part -we couldn't figure out was how to discover the device-side RSD port inside the -tunnel. +“assertion” so that the tunnel is kept open for as long as we need it. But the +part we couldn't figure out was how to discover the device-side RSD port inside +the tunnel. We knew that `remotepairingd`, running as the local user, knows the RSD port, but we couldn't find a way to get it to tell us what it is. After lots of