mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #1029] Amazon to Disable S3 Path-Style Access - Does it Matter to s3fs? #563
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#563
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jamiejackson on GitHub (May 8, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1029
Is s3fs affected by this change? https://www.bleepingcomputer.com/news/security/amazon-to-disable-s3-path-style-access-used-to-bypass-censorship/
@gaul commented on GitHub (May 8, 2019):
s3fs supports both host- and path-style access and defaults to the former. If users opt-in to the latter with AWS they may experience issues.
@jamiejackson commented on GitHub (May 8, 2019):
Ah, right, thanks: https://github.com/s3fs-fuse/s3fs-fuse/blame/master/README.md#L109-L119
Should new versions of s3fs emit some sort of deprecation notice?
@jamiejackson commented on GitHub (May 8, 2019):
Oh, I see that there may be other S3 implementations besides AWS. I hadn't known that. I guess that those could continue to support the path style, so a deprecation notice might not be appropriate (or at least more complicated to implement).