-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
SSH RSA Key TagNumberInvalid #10245
Comments
wow... guess I am the only one... WHat I dont get is how is it possible that this long key worked OK till tabby changed to New SSH backend in 1.0.216 and suddenly its picky about the key that worked 100% till now and works everywhere else. I dont think its the key problem although it might be slightly different because of the conversion in PuttyGen to OpenSSH... |
Could you please generate another key with the exact same settings, make sure it is not working in Tabby, and post it here? Thanks |
I have the exact same issue since about 2-3 weeks without any changes from my side. Mac OS: 15.3 (24D60) Error: Keys(Pkcs1(Pkcs8(Asn1(Error { kind: TagUnexpected { expected: Some(Tag(0x30: SEQUENCE)), actual: Tag(0x1a: VisibleString) }, position: None })))) If I enter the exact same ssh login command in a mac os terminal it works using the same key. I'm not about to create a new key since I use this key extensively. |
I just installed tabby 1.0.215 which "resolves" the issue. |
Environment:
Kubuntu 24.10
KDE Plasma
Wayland
Tabby x64 deb installer
Issue:
I went from Tabby 1.0.215 to 1.0.216 and it started there. Also present in 1.0.220. I have a 2 years old RSA key (probably 4096 in strength - not sure atm). Back then it was created with PuttyGen on windows and converted to openssh. Now - this key is working fine with EVERY software out there. Nothing wrong with the key itself it seems. Tabby started throwing error with this key in version 1.0.216 but its all fine in 1.0.215. The error when I try to connect to my VPS:
No idea whats happening and why does it work with other software and succesfully authenticates everywhere except tabby 1.0.216 and newer...
The text was updated successfully, but these errors were encountered: