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

Error message 'Filename length exceeds maximum length 146' during upload #11020

Closed
cyberduck opened this issue Apr 6, 2020 · 3 comments
Closed

Error message 'Filename length exceeds maximum length 146' during upload #11020

cyberduck opened this issue Apr 6, 2020 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 6, 2020

ce6d08c created the issue

Hi,

there's a serious bug in Cyberduck's new Cryptomator engine vor vault version 7. I have an online-only vault that has already been migrated to Cryptomator's new vault version and was able to upload / download lots of files already. But for some unknown reason I can't upload the docx file attached to this ticket. I've also included the error log that is shown in the message box.

There's nothing written in the log window so the message box is the only input I can give to you. I've even tried to upload the file to the root of the vault with no success.

Please analyze and fix this accordingly. In case you need any more input, don't hesitate to contact me.

This affects both Windows and Mac versions of Cyberduck 7.3.0.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 18, 2020

ce6d08c commented

Hi,

I've now tested uploading such 'long files' through the Cryptomator app 1.5.0 for iOS which was released yesterday and it worked like a charm. This must have to do something with an incorrect limit inside Cryptomator. I understand that the maximum path length must not exceed a certain value, but no matter in which directory I try to upload certain files - they just don't work.

I think there's something going wrong in the calculation of the full path length value.

The bug is still set to 'New'. Please provide input on an estimated time of completion or at least analysis as this is quite a serious issue.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 20, 2020

@ylangisc commented

I can confirm that this is a bug in the Cryptomator Vault version 7 implementation. We currently do not support long filenames (>146 characters) for v7 vaults but the current implementation checks this threshold on the encrypted filename instead of the cleartest filename.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 21, 2020

@dkocher commented

In 83d1828.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants