Cyberduck
Mountain Duck
CLIChanges between Version 1 and Version 2 of Ticket #10488
- Timestamp:
- Oct 7, 2018 7:38:56 PM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10488 – Description
v1 v2 7 7 The issue: 8 8 9 I have an AWS user with Administrator priv lidges.9 I have an AWS user with Administrator privileges. 10 10 This user can create and upload files at will via either the AWS Web UI or CyberDuck. 11 11 This user is not able to create a new Cryptomator vault, using Cyberduck. … … 56 56 Here's the User policy I am using; this is akin to root level access 57 57 58 ``` 58 {{{ 59 59 { 60 60 "Version": "2012-10-17", … … 67 67 ] 68 68 } 69 ``` 69 }}} 70 70 71 71 72 72 Here's the Log from Cyberduck when connecting to the S3 bookmark with the Admin account detailed above. I am browsing a few directories deep to the location where I would like to create the Cryptomator vault: 73 73 74 ``` 74 {{{ 75 75 GET / HTTP/1.1 76 76 Date: Sun, 07 Oct 2018 19:17:08 GMT … … 233 233 Transfer-Encoding: chunked 234 234 Server: AmazonS3 235 236 ``` 235 }}} 236 237 237 238 238 And here's me trying to create a `test-folder`. This action susceeds. 239 239 240 ``` 240 {{{ 241 241 PUT /MY_BUCKET_PREFIX/test-folder/ HTTP/1.1 242 242 Date: Sun, 07 Oct 2018 19:18:54 GMT … … 291 291 Transfer-Encoding: chunked 292 292 Server: AmazonS3 293 ``` 293 }}} 294 294 295 295 And here's the log from trying to create a `test-vault`. I get this error in Cyberduck: 296 ``` 296 {{{ 297 297 Upload test-vault failed. 298 298 Access Denied. Please contact your web hosting service provider for assistance. 299 ``` 299 }}} 300 300 301 301 And here's the connection log. I clicked `try again` once before clicking cancel: 302 ``` 302 {{{ 303 303 PUT /MY_BUCKET_PREFIX/test-vault/ HTTP/1.1 304 304 Date: Sun, 07 Oct 2018 19:19:38 GMT … … 355 355 Transfer-Encoding: chunked 356 356 Server: AmazonS3 357 ``` 357 }}} 358 358 359 359 360 360 There is nothing particurally useful in `console.app` even after turning Cyberduck debugging mode on: 361 ``` 361 {{{ 362 362 default 12:19:28.792415 -0700 Cyberduck 27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 307 vs 532, 512, <private> 363 363 default 12:20:09.333915 -0700 Cyberduck 27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 309 vs 536, 512, <private> … … 399 399 default 12:20:22.205486 -0700 Cyberduck Discover done 400 400 default 12:20:22.205676 -0700 Cyberduck services: <private> 401 ``` 401 }}} 402 402 403 403 404 404 As soon as i remove the bucket policy, i have no issues creating the vault. 405 405 406 It appears that Cyberduck is ignoring my settings for S3 uploads, under the `Encryption` head ding.406 It appears that Cyberduck is ignoring my settings for S3 uploads, under the `Encryption` heading. 407 407 408 408 Please let me know what else you need from me in order to reproduce & fix.
