You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My company is building an open-source filesystem (ceph.newdream.net) that has an S3 emulator gateway, and we'd like to get at least a partial list of S3 clients that will work with it. Unfortunately, best I can tell Cyberduck assumes that all S3 users are connecting to Amazon hosts.
This is something I can look into myself a little bit, but thought I'd check if there was a quick fix available from somebody who had more experience with the Cyberduck code, perhaps by replacing some hardcoded address links with a variable that is read out of the server address? :)
To reproduce:
Set up some non-Amazon S3 interface service.
Run Cyberduck
Click "Open Connection"
Fill in your S3 service's address and port in the "Server:" and "Port:" boxes.
Fill your given key and secret key into the "Username:" and "Password:" boxes.
Click "Connect."
Wait until it fails, and notice a lot of references to "s3.amazonaws.com" in the transcript. ;)
The text was updated successfully, but these errors were encountered:
My company is building an open-source filesystem (ceph.newdream.net) that has an S3 emulator gateway, and we'd like to get at least a partial list of S3 clients that will work with it. Unfortunately, best I can tell Cyberduck assumes that all S3 users are connecting to Amazon hosts.
This is something I can look into myself a little bit, but thought I'd check if there was a quick fix available from somebody who had more experience with the Cyberduck code, perhaps by replacing some hardcoded address links with a variable that is read out of the server address? :)
To reproduce:
The text was updated successfully, but these errors were encountered: