'no start line' when running lit auth about lit HOT 4 CLOSED

For clarification for any further users who make it here: openssh's ssh-keygen command defaults to outputting public and private keys in the RFC4716 "SSH Public Key File Format" rather than the older RFC1421 PEM format that lit auth expects.

This can be fixed by passing along the -m PEM flag which will generate the "correct" key format.

Another thing to note is that even with the fall in popularity in RSA keys in favor of ED25519, RSA currently remains as the only way to use lit auth

from lit.

Yeah, I've noticed this issue like a month ago or so, it is not a bug. Here how it goes:

1. Lit only accept PEM body armor.
2. OpenSSH at some point changed the default of keygen.
3. Due to that, in order to make it work with Lit you need to generate it with keygen -t rsa -b 4096 -C "[email protected]" -m PEG (notice the -m PEM).

from lit.

And I can definitely guarantee you it is not abandoned xD

edit: I will be making a change on the Wiki to indicate this nowadays required flag to keygen

from lit.

That worked! Thank you so much!

$ ssh-keygen -t rsa -b 4096 -m PEM -C "lit"
Generating public/private rsa key pair.
Enter file in which to save the key (C:\Users\Julian/.ssh/id_rsa): ./lit
./lit already exists.
Overwrite (y/n)? y
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in ./lit.
Your public key has been saved in ./lit.pub.
$ lit auth notnite
lit version: 3.8.5
luvi version: v2.12.0
command: auth notnite
load config: C:\Users\Julian\AppData\Roaming\litconfig
username: notnite
name: NotNite
email: [email protected]
privateKey: C:\Users\Julian\.ssh\lit
# omitted because i'm not sure if this is private or not lol
update config: C:\Users\Julian\AppData\Roaming\litconfig
done: success
$

Thanks for also changing the wiki, I'm sure it'll save some other tired developers trying to make individual keys.

from lit.