artu-ole

Results 19 comments of artu-ole

@jimmyjamieson @xcuben @beljand @JDuffyCM @Bosper try `import { PushNotificationComponent } from 'ng2-notifications/ng2-notifications';`

Hm, just making sure, do you have WinSCP path configured in the Tabby settings? Having WinSCP in path should not be required, but you need it to be configured in...

Auto-detect didn't function for me either back in the day :(

Interesting, I've now tested the passphrased key and that worked as well. When you say there is nothing in the logs do you mean in the developer tools console there...

Hm, yes, tested with the ssh-keygen generated keypair: `ssh-keygen -t rsa -b 2048` Key is in the settings of the connection: ![Tabby_jrm0MdHKXb](https://user-images.githubusercontent.com/15938416/193743826-90dfe26f-533a-489b-8875-0fdb3a0cc908.png) Key is in the following usual format: Key...

Okay, that might explain it, even though the forge claims to support it ([ED25519](https://github.com/digitalbazaar/forge#ed25519)) something must be failing. I will dig deeper in the evening!

I'm able to reproduce the issue with the ed25519, the source issue is in a node-sshpk library which is used internally by Tabby to handle private keys and at that...

Actually, a correction. The key **is** available as string at that point as well, but node-sshpk is used for its auto parsing mode: https://github.com/TritonDataCenter/node-sshpk#parsekeydata-format--auto-options Then node-forge is used for it's...

Alright, played around with it and indeed now node-sshpk serializes a valid pkcs8 formatted key. But encountered a problem on the other side, the node-forge library is not able to...

@kyuuaria Hey, sorry mate, didn't have time to get into it yet between work and personal life. Since that's still a pressing issue for you and the path forward seems...