Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No transcript for SFTP/SCP connections #2944

Closed
cyberduck opened this issue Feb 2, 2009 · 4 comments
Closed

No transcript for SFTP/SCP connections #2944

cyberduck opened this issue Feb 2, 2009 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 2, 2009

aec22a9 created the issue

When connecting to a SFTP host the Log Drawer remains empty.

I reproduced this on 5 servers.

I cannot remember if I ever saw it work in previous versions.

I could not find any existing tickets on this issue.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 27, 2010

@dkocher commented

We never had a transcript for SFTP previously.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 20, 2010

@dkocher commented

#5356 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 15, 2011

3aa8272 commented

I would like to voice my opinion on this bug. I apologize in advance if this is not the most appropriate forum.

This may be arguing semantics, but setting the bug type as an enhancement rather than a defect is wrong in my opinion. This is not a "new feature", but rather unexpected/unintended/unintuitive behavior in its current form. When a user selects "Toggle Log Drawer" and does an SFTP/SCP transfer, and nothing appears there, they think something is wrong - and it is. At the very least, there should be a log entry that pops up there saying that logging is not yet available for SFTP/SCP, otherwise the user is kept completely in the dark about it. They shouldn't need to know in advance that the logging is dependent on which protocol they use to do the transfer.

In my situation, I use Cyberduck almost exclusively with SFTP/SCP now, so this is a critical issue for me. In particular, whenever I use the "synchronize" option, I need to be able to see a transcript of what files were transferred, since it could cause problems if files were overwritten, deleted, etc. without my knowledge. To synchronize a whole directory hierarchy with absolutely no indication of what occurred is playing with fire. It has become such a big issue for me that I had to switch to FileZilla instead until this bug is addressed.

I have a lot of respect for Cyberduck's interface, but this is clearly a bug that should be resolved by now, after being open for two years. I am anxious to see it completed by the 4.0 release.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 15, 2011

@dkocher commented

In f8a912f.

Loading

@cyberduck cyberduck closed this Mar 15, 2011
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants