This repository has been archived on 2020-03-24. You can view files and clone it, but cannot push or open issues or pull requests.

Matt Jibson b3c2388618 Allow setting of boto's S3 host for SIGv4 ... The problem only happens when a user has configured the new AWS Frankfurt region for their S3 backend. It is the only region to require the new v4 signature. All other regions support both v2 and v4. I'm not sure which version is used by default on US Standard. We could attempt to figure out where the bucket is hosted based on its DNS resolution and auto-populate the host field that way. But I think the amount of effort to have that work correctly outweighs its benefit for such a simple solution. fixes #863 fixes #764		2015-11-18 17:19:33 -05:00
..
directives	Fix typo	2015-11-16 06:21:44 +01:00
pages	Vulnerability UI part 2	2015-11-12 16:59:36 -05:00
services	Merge master into vulnerability-tool	2015-11-12 21:52:47 -05:00
angular-route-builder.js	Move all controllers into page definitions and add support for layout profiles	2015-02-20 18:15:48 -05:00
app.js	Do not redirect on API 404	2015-11-03 12:23:39 -05:00
core-config-setup.js	Allow setting of boto's S3 host for SIGv4	2015-11-18 17:19:33 -05:00
core-ui.js	Delete the old UI!	2015-06-29 12:33:00 +03:00
graphing.js	Never load the full repo image list	2015-11-04 15:53:00 -05:00
tour.js	Tutorial improvements	2015-06-04 14:15:47 -04:00
untar.js	Strip whitespace from ALL the things.	2014-11-24 16:07:38 -05:00