You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
When trying to use huber for either install or search a package it yields an error message:
huber search k3s
error: authentication required but no callback set; class=Ssh (23); code=Auth (-16)%
After looking at the code for a glance, it seems that the support for SSH key appear only supported RSA key which is denoted by concatenation of path with id_rsa at:
let p = dirs::home_dir().unwrap().join(".ssh").join("id_rsa");
For somebody that does not using RSA for SSH keys, this can lead to the aforementioned issue. For example, I am now, on my current computer only has id_ed25519 and id_ecdsa_sk.
Describe the solution you'd like
What I was thinking for this is that if we could make of use running SSH agent to authenticate the git operations as the agent always carried on the ENVs:
env | grep AGENT
SSH_AGENT_PID=37358
Describe alternatives you've considered
I guess by continuing the previous approach but now we are doing some sort of scanning on known SSH key file name list.
Additional context
No additional context as of now.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
When trying to use
huber
for either install or search a package it yields an error message:After looking at the code for a glance, it seems that the support for SSH key appear only supported RSA key which is denoted by concatenation of path with
id_rsa
at:huber/crates/app/src/component/github.rs
Line 91 in 9850d02
For somebody that does not using RSA for SSH keys, this can lead to the aforementioned issue. For example, I am now, on my current computer only has
id_ed25519
andid_ecdsa_sk
.Describe the solution you'd like
What I was thinking for this is that if we could make of use running SSH agent to authenticate the git operations as the agent always carried on the ENVs:
Describe alternatives you've considered
I guess by continuing the previous approach but now we are doing some sort of scanning on known SSH key file name list.
Additional context
No additional context as of now.
The text was updated successfully, but these errors were encountered: