Macfusion 2.0.2 (2.0.1): sshfs favourite: mount times out if new_sshfs_askpass does not interact with keychain within ~5 seconds

[grahamperrin]

Whilst I'm creating a separate ticket for this, it probably explains (could be a duplicate of) ticket:48

1. AFAIR neither Macfusion 2.0.1 nor its agent had been launched

2. downloaded Macfusion 2.0.2 (2.0.1) and overwrote the earlier version

2. launched Macfusion, accepted the invitation to update to 2.0.2

3. re-launched

4. checked for updates again (troubleshooting ticket:65 at the time) but declined the repeat invitations to update to 2.0.2

5. I have just one favourite, an sshfs connection to localhost

6. clicked Mount

7. dialogue (see screen shot attached):

! 
Could not mount filesystem: Mount has timed out.
[[OK]]

8. dialogue (see screen shot attached):

new_sshfs_askpass wants to use your confidential information stored in "localhost" in your keychain. 
Do you want to allow access to this item?
[Always Allow] [Deny] [Allow]

9. clicked Always Allow

10. clicked OK to the earlier dialogue.

[grahamperrin]

Summary line of this ticket changed following what seems to be another manifestation of the same issue.

Now, I'm even more inclined to treat this ticket:66 as a more proper expression of ticket:48.

Reproducing the symptoms

1. create an sshfs favourite and opt to have the password stored in a keychain

2. if the related volume is mounted, unmount it

3. lock the keychain

4. open the favourite

5. wait ~five seconds.

Result: as before,

! 
Could not mount filesystem: Mount has timed out.
[[OK]]

Key points

If the user doesn't grant access to the keychain within ~five seconds, or if (say) the OS is busy and can't present a related dialogue within that time, then a time out is … untimely :)

Solution?

Is it possible for the time-out aspects to be deferred, suppressed, whatever, for as long as interaction with keychain is expected?

Thanks Graham

[lloeki@…]

same kind of issue here, except I authenticate via rsa public key.

[grahamperrin]

To clarify: ideally the countdown/timeout (5 seconds, or whatever is preferred by the user) should begin only after password has been gained from the keychain.

[anonymous]

Milestone 2.0 deleted