distribution/docs/storage/driver
Stephen J Day 2b4ad94cee Defer case-sensitive support to storage backend
Rather than enforce lowercase paths for all drivers, support for
case-sensitivity has been deferred to the driver. There are a few caveats to
this approach:

1. There are possible security implications for tags that only differ in their
case. For instance, a tag "A" may be equivalent to tag "a" on certain file
system backends.
2. All system paths should not use case-sensitive identifiers where possible.
This might be problematic in a blob store that uses case-sensitive ids. For
now, since digest hex ids are all case-insensitive, this will not be an issue.

The recommend workaround is to not run the registry on a case-insensitive
filesystem driver in security sensitive applications.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-04-07 14:14:45 -07:00
..
azure Merge pull request #294 from fkautz/pr_out_updating_msopentech_azure_sdk_for_go_to_latest_master 2015-03-24 13:27:19 -07:00
base Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
factory Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
filesystem doc: move storage driver readmes into docs 2015-03-05 17:23:33 -08:00
inmemory Avoid crash on invalid Move arguments 2015-04-01 19:03:02 -07:00
ipc Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
middleware Handle cloudFront bucket prefix issue 2015-04-06 19:46:05 -07:00
s3 Handle cloudFront bucket prefix issue 2015-04-06 19:46:05 -07:00
testsuites Defer case-sensitive support to storage backend 2015-04-07 14:14:45 -07:00
fileinfo.go Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
storagedriver.go Defer case-sensitive support to storage backend 2015-04-07 14:14:45 -07:00