Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
34402df316
4 changed files with 53 additions and 0 deletions
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://johan.kiviniemi.name/"
|
||||
nickname="Johan"
|
||||
subject="comment 10"
|
||||
date="2014-05-01T01:33:10Z"
|
||||
content="""
|
||||
Note to self: I experienced this bug with the standalone tarball release (5.20140421) as well, so it’s not caused by something that is different on my system wrt. git-annex’s dependencies etc.
|
||||
"""]]
|
25
doc/bugs/ssh-askpass_locks_me_out_of_x_console.mdwn
Normal file
25
doc/bugs/ssh-askpass_locks_me_out_of_x_console.mdwn
Normal file
|
@ -0,0 +1,25 @@
|
|||
### Please describe the problem.
|
||||
|
||||
Can't access X console after returning to work overnight.
|
||||
|
||||
### What steps will reproduce the problem?
|
||||
|
||||
1. Create git-annex remote repository, with git annex assistance, connected via ssh, using ssh-agent key for authentication.
|
||||
2. "ssh-add -D" to delete the ssh key when not attending computer. Forget to kill git-annex assistant.
|
||||
3. Lock screen with xscreeensaver.
|
||||
4. Return to work. Unlock screen. Find keyboard and mouse not responding. However there are no dialog boxes on screen.
|
||||
5. Open up text console, kill the numerous ssh-askpass processes. Find more ssh-askpass processes. Kill the git-annex processes, then kill the ssh-askpass processes. Find I can access the x console again.
|
||||
|
||||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
Version 5.20140320~bpo70+1 in Debian backports.
|
||||
|
||||
### Please provide any additional information below.
|
||||
|
||||
This isn't git-annex's fault, but it is a serious problem with using git-annex assistant.
|
||||
|
||||
Suspect ssh-askpass isn't displaying dialog properly as it conflicts with xscreensaver, which is running at the time.
|
||||
|
||||
Not really sure what the solution is.
|
||||
|
||||
Unfortunately, Out of time for today, will double check this report makes sense tomorrow.
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="209.250.56.114"
|
||||
subject="comment 1"
|
||||
date="2014-05-01T13:56:32Z"
|
||||
content="""
|
||||
This will be fixed by [[design/assistant/sshpassword]], assuming I make it bypass the OS's IMHO superior ssh-askpass and use its own.
|
||||
|
||||
It would be better to file a bug on the actual program you had problems with though, which is not git-annex.
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="209.250.56.114"
|
||||
subject="comment 2"
|
||||
date="2014-05-01T14:04:12Z"
|
||||
content="""
|
||||
Actually, no, that is only going to handle ssh password prompting the one time needed to set up a passwordless dedicated ssh key.
|
||||
|
||||
It may be that it makes sense to *always* set up such a key, which would bypass the normal key handling, and so avoid this problem. Currently, the assumption is that if you have gone to the bother to already set up a login to a host, without a password being needed, it makes sense for the assistant to use that configuration.
|
||||
"""]]
|
Loading…
Reference in a new issue