Right now, when the plugin sets up the persistent storage location for TUF metadata in the context of a particular repository, it uses this line of code to name the directory:
preg_replace('/[^[:alnum:]\.]/', '-', $repoUrl)
This can be problematic because URLs like site.coop.info/packages and site.coop/info/packages will collide. This is probably something of an edge case, but it's enough of a concern that it should block a 1.0.0 release of this plugin. We need to find a better way to name these directories.
One option is to use a SHA-256 hash of the URL, but that could be quite obscure. Other thoughts welcome...
Right now, when the plugin sets up the persistent storage location for TUF metadata in the context of a particular repository, it uses this line of code to name the directory:
This can be problematic because URLs like
site.coop.info/packagesandsite.coop/info/packageswill collide. This is probably something of an edge case, but it's enough of a concern that it should block a 1.0.0 release of this plugin. We need to find a better way to name these directories.One option is to use a SHA-256 hash of the URL, but that could be quite obscure. Other thoughts welcome...