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

Failure opening Cryptomator folder on FTP #13375

Closed
AliveDevil opened this issue May 11, 2022 · 1 comment · Fixed by #13397
Closed

Failure opening Cryptomator folder on FTP #13375

AliveDevil opened this issue May 11, 2022 · 1 comment · Fixed by #13397
Assignees
Labels
bug cryptomator ftp
Milestone

Comments

@AliveDevil
Copy link
Contributor

@AliveDevil AliveDevil commented May 11, 2022

Opening a cryptomator folder on FTP results in Cyberduck failing to list properly, with wrong response:

2022-05-11 14:19:37,021 [background-9] INFO  ch.cyberduck.transcript.request - CWD /work/cryptomator/d/MG/XUU2ZAHKXKYL4TBEAHHPXNTGOUKA2S
2022-05-11 14:19:37,022 [background-9] INFO  ch.cyberduck.transcript.response - 212-Status of /work/cryptomator/d/MG/XUU2ZAHKXKYL4TBEAHHPXNTGOUKA2S:
212-drwxrwsrwx   2 iterate  users           6 May 11 14:13 .
212-drwxrwsrwx   3 iterate  users          44 May 11 14:13 ..
212 End of status

cyberduck.log

@AliveDevil AliveDevil added ftp cryptomator bug labels May 11, 2022
@dkocher dkocher added this to the 8.4.0 milestone May 12, 2022
@dkocher dkocher self-assigned this May 16, 2022
@dkocher
Copy link
Contributor

@dkocher dkocher commented May 16, 2022

Regression from 20d1a7f#diff-7ef9eb1a3108e47e4f733ef933f72eee0d3961aebf307a7bceaee6be3915c830R204 with stream not closed.

dkocher added a commit that referenced this issue May 16, 2022
dkocher added a commit that referenced this issue May 16, 2022
@dkocher dkocher linked a pull request May 16, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug cryptomator ftp
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants