Astral VPN v2.2.33 - Final kanit yeniden-probe hotfix
Astral VPN v2.2.33 - Final kanit yeniden-probe hotfix
v2.2.33, v2.2.32 uzerine gelen baglanti kararliligi hotfix'idir. Loglarda gorulen hata, ilk WebProxy hedef kaniti tum secili web hedefleri icin basarili olduktan sonra final asamada ayni hedeflerin tekrar uzun CONNECT sweep'e sokulmasi ve bu ikinci sweep'teki timeout'larin baglantiyi hata durumuna dusurmesiydi.
Degisenler
- Ilk scoped WebProxy proof tum secili web hedef ID'lerini kapsiyorsa final asamada bu proof korunur.
- Final asamada yine PAC/WebProxy kapsaminin aktif oldugu dogrulanir; kapsam bozulduysa baglanti basarili sayilmaz.
- Tam hedef-ID proof eksikse eski guvenlik davranisi korunur ve final proof yeniden calisir.
- App hedefleri icin kanit eksikse Astral
Connecteddemez; web kaniti korunur ve durumTargetActionRequiredolarak kalir. - Bulk secimde 15 hedef icin ikinci gereksiz CONNECT sweep kaldirildigi icin baglanti suresi ve timeout riski azalir.
- Web-only secimlerde WireSock artik
-lacsanal adapter moduyla baslamaz; transparent process modunda yalnizAstral.WebProxy.exetunele alinir. Bu, secili olmayan TCP/443 hedeflerinin normal baglantida kalmasini korur.
Logdan dogrulanan kok neden
2026-06-21 tanilama paketinde:
- 15 hedef seciliydi.
- Ilk
webProxyProof15/15 hedef ID ile basarili oldu. - Azar, IMVU, LiVU ve Tango uygulama surecleri calismadigi icin app proof manual action istedi.
- Tunnel readiness
readyve adapter trafik kaniti vardi. - Final WebProxy proof ayni 15 hedefi yeniden denedi, bazi hostlar timeout oldu ve baglanti Error'a dustu.
v2.2.33 bu son adimi hedef-ID proof reuse kapisiyla daraltir.
Guvenlik
- Tarayici surecleri WireSock
AllowedAppsicine alinmaz. - Web hedefleri PAC +
Astral.WebProxy.exekapsaminda kalir. - Final asamada scoped PAC/WebProxy kapsam dogrulamasi devam eder.
- Web-only hedeflerde sanal adapter acilmaz; app kapsamli hedeflerde
-lackaniti korunur. - HTTPS icerigi cozulmez, sertifika kurulmaz, MITM yapilmaz.
- App proof eksikken tam bagli durumu raporlanmaz.
Dogrulama
Release oncesi su kapilar alinmalidir:
dotnet build Astral.sln --configuration Release
dotnet run --project tests\Astral.Core.Tests --configuration Release
dotnet run --project tests\Astral.Windows.Tests --configuration Release
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\verify.ps1 -ArtifactsPath artifacts\verify-2.2.33
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\build-release.ps1
gitleaks detect --redact --no-banner --verbose
gitleaks dir . --redact --no-banner --verboseElevated live smoke kapilari:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\smoke-live-connect.ps1 -ExePath .\artifacts\publish\win-x64\Astral.exe -TargetIds wattpad -OutputPath .\artifacts\app-live-connect-smoke-v2.2.33-wattpad.txt
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\smoke-live-connect.ps1 -ExePath .\artifacts\publish\win-x64\Astral.exe -TargetIds discord,wattpad -RequireTargetActionRecheck -ManualTargetActionTimeoutSeconds 120 -OutputPath .\artifacts\app-live-connect-smoke-v2.2.33-mixed-target-proof.txt
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\smoke-live-connect.ps1 -ExePath .\artifacts\publish\win-x64\Astral.exe -TargetIds wattpad,bigo-live,blogspot,radio-garden,deutsche-welle,voice-of-america,eksi-sozluk,grok,imgur,pastebin -OutputPath .\artifacts\app-live-connect-smoke-v2.2.33-web-bulk.txtRelease assetleri
Astral-2.2.33-win-x64.zipAstral-2.2.33-win-x64.sha256.txtAstral-win-x64.zipAstral-win-x64.sha256.txt
Son dogrulanan Astral-2.2.33-win-x64.zip SHA-256: C073BEF6E536A80BE01137B0F9F922A33569687048B9874DA46CE29B7160F9C4.
Yayın Asset'leri
- Astral-2.2.33-win-x64.zip
- Astral-2.2.33-win-x64.sha256.txt
- Astral-win-x64.zip
- Astral-win-x64.sha256.txt
- SHA-256: 0316313604230E0972DD2000F456305C27218661D45777506D5DB37817FA1DF3
- Kod imzalama: imzasız paket. Güven sınırı GitHub yayın yetkisi, release yolu, asset digest, SHA-256 dosyası ve manifest doğrulamasıdır.