tea accesses ssh-key even when authenticating with token #510

Open
opened 2022-09-20 11:52:26 +00:00 by Emojigit · 2 comments

describe your environment

  • tea version used (tea -v):
    • I also reproduced the issue with the latest master build
    • Version: 0.9.0+2-g6a4ba6a golang: 1.19.1 go-sdk: v0.15.1-0.20220831004139-a0127ed0e7fe
  • Gitea version used:
  • operating system: Arch Linux
  • I make use of...
    • non-standard default branch names (no main,master, or trunk)
    • .ssh/config or .gitconfig host aliases in my git remotes
    • ssh_agent or similar
    • non-standard ports for gitea and/or ssh
    • something else that's likely to interact badly with tea: ...

describe the issue (observed vs expected behaviour)

圖片
I executed ssh-add before all the following commands, but tea still kept asking me for my SSH key password. This is a bug, or at least, should not happen.

I cannot find anything in the bug label. Please notify me if this is a duplicate.

### describe your environment - tea version used (`tea -v`): - [x] I also reproduced the issue [with the latest master build](https://dl.gitea.io/tea/master) - `Version: 0.9.0+2-g6a4ba6a golang: 1.19.1 go-sdk: v0.15.1-0.20220831004139-a0127ed0e7fe` - Gitea version used: - [ ] the issue only occurred after updating gitea recently - I don't know, it is https://git.minetest.land - operating system: Arch Linux - I make use of... - [ ] non-standard default branch names (no `main`,`master`, or `trunk`) - [ ] .ssh/config or .gitconfig host aliases in my git remotes - [x] ssh_agent or similar - [x] non-standard ports for gitea and/or ssh - [ ] something else that's likely to interact badly with tea: ... ### describe the issue (observed vs expected behaviour) ![圖片](/attachments/1d42ddcb-d6b7-4dfd-b296-39c6193fe7c3) I executed `ssh-add` before all the following commands, but tea still kept asking me for my SSH key password. This is a bug, or at least, should not happen. I cannot find anything [in the bug label](https://gitea.com/gitea/tea/issues?q=&type=all&state=open&labels=432&milestone=0&assignee=0&poster=0). Please notify me if this is a duplicate.
Emojigit added the
kind/bug
label 2022-09-20 11:52:26 +00:00
Member

What login method did you configure when adding the login to tea? (ssh-key/cert or token/password?)

  • If you use the ssh-key login method, the key must also be added to ssh-agent when creating the login (tea login add), not only before running tea repo create, otherwise tea won't have selected the ssh-agent key.

  • If you use token or password login method and get this error, this is a bug in tea, as it shouldn't try to decrypt the key for this command.

What login method did you configure when adding the login to tea? (ssh-key/cert or token/password?) - If you use the ssh-key login method, the key must also be added to ssh-agent when creating the login (`tea login add`), not only before running `tea repo create`, otherwise tea won't have selected the ssh-agent key. - If you use token or password login method and get this error, this is a bug in tea, as it shouldn't try to decrypt the key for this command.
Author
  1. I forgot did I run ssh-add before tea login add, but tea repo list use SSH.
  2. I am using a token to login, but I have no idea is gitea using SSH to communicate between the Gitea server.
1. I forgot did I run `ssh-add` before `tea login add`, but `tea repo` list use SSH. 2. I am using a token to login, but I have no idea is gitea using SSH to communicate between the Gitea server.
noerw added this to the v0.9.1 milestone 2022-09-20 14:53:49 +00:00
noerw changed title from Bug: tea is ignoring `ssh-agent` to tea accesses ssh-key even when authenticating with token 2022-09-20 14:56:42 +00:00
6543 modified the milestone from v0.9.1 to v0.9.2 2023-02-15 22:03:55 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#510
No description provided.