-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in wsl-helper certificates
#6307
Comments
Thanks for the very clear bug report! We're tracking this in #6295 which is (at least partly) the same issue, mostly because that was earlier. Also thanks for the very clear sample — Wikipedia has |
This has been fixed in #6308 and will be included in a 1.12.1 patch release. |
Yeah, freed memory was my assumption too. Thanks for beating me to a fix while I was asleep :) |
Actual Behavior
I'm seeing a very odd issue when trying to start Rancher Desktop. It gets stuck on the "installingCA certificates" step, and in the networking-ca.log file I have the following golang crash:
I've tried running the
wsl-helper.exe certificates
command from a terminal and the same thing happens. Interestingly, when I build and run the wsl-helper program in the debugger it doesn't crash, but the last certificate from each store is corrupted, e.g.i.e. the cert looks fine up until a certain point when it becomes corrupt.
those corrupt bytes decode to 0xEE and 0xFE in a repeating pattern.
What's even stranger is that when I added some debugging code to the certificates_window.go file to examine the final cert in each store, the
block.Bytes
array that's passed to pem.Encode() is seemingly being corrupted during the generation of the base64-encoded data - as in, the array is correct initially, then pem.Encode() is called and after the call the array is then ENTIRELY filled with 0xEE/FE bytes.Steps to Reproduce
Honestly no idea. Other people at my company do not have this problem. Deleting the cert that ends up corrupted just causes another one to end up corrupted instead.
Result
The above crash.
Expected Behavior
No crash, rancher should start up normally with all the root certs installed
Additional Information
No response
Rancher Desktop Version
1.12.0
Rancher Desktop K8s Version
1.28.5
Which container engine are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 11 22H2
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
This happens both with and without a VPN connection. I can't really comment on security software.
The text was updated successfully, but these errors were encountered: