jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-794) generic S3 provider should not provide default endpoint
Date Wed, 04 Feb 2015 21:44:35 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306025#comment-14306025
] 

ASF subversion and git services commented on JCLOUDS-794:
---------------------------------------------------------

Commit 8a2c821e131717b6dc06996886d1393d74b09ff6 in jclouds's branch refs/heads/master from
[~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=8a2c821 ]

JCLOUDS-794: Use bogus URL for generic S3 endpoint

This prevents users from accidentally connecting to AWS.


> generic S3 provider should not provide default endpoint
> -------------------------------------------------------
>
>                 Key: JCLOUDS-794
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-794
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.8.1
>            Reporter: Andrew Gaul
>            Assignee: Andrew Gaul
>            Priority: Minor
>              Labels: s3
>
> The generic S3 provider gives the endpoint for the us-standard region.  This can confuse
users who accidentally use s3 instead of aws-s3 then expect access to other regions.  I do
not believe that this leaks any credentials or exposes users to replay attacks due to inclusion
of the host in the V2 signature, but we should remove this default endpoint to avoid confusion.
> This represents a breaking change to some users; do we need to provide any notice other
than release notes?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message