#87422Integrate extension meta-manifest
Description
In order to allow that some 3rd party extension is retrieving data from remote sources, this has to be declared in a structured way in a extension manifest.
Idea/Documentation:
Example (this requires more research on standards and how it could be declared better):
{
"remoteSources": {
"script": [
],
"style": [
"type": "font",
"url": "https://use.fontawesome.com/releases/v5.6.3/css/all.css",
"description": "In order to make use of... (description for admin that grants access to this resource)"
]
}
}
Current Draft
- see https://notes.typo3.org/yq1hOL2NSaiqH0jcFREQsA?view
- or markdown file attached to this issue
- consider adding signatures/hashes over content to be embedded (→ someone™ would have to verify the content)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 7
-
Oliver Hader changed subject
Integrate remote resource manifestIntegrate extension meta-manifest <span data-processor="relativetime" data-value="2021-06-16T09:30:35+00:00" > 06/16/21, 09:30 </span> -
Oliver Hader changed description status
NewAccepted TYPO3 Version1011 <span data-processor="relativetime" data-value="2021-06-16T09:31:32+00:00" > 06/16/21, 09:31 </span> -
Oliver Hader changed attached 2021-0616 TYPO3 Extension Meta-Manifest.md <span data-processor="relativetime" data-value="2021-06-16T09:32:07+00:00" > 06/16/21, 09:32 </span>
-
Oliver Hader changed target version <span data-processor="relativetime" data-value="2021-11-17T21:42:20+00:00" > 11/17/21, 21:42 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2023-06-05T09:20:13+00:00" > 06/05/23, 09:20 </span>
-
Oliver Hader changed description <span data-processor="relativetime" data-value="2024-07-08T08:10:09+00:00" > 07/08/24, 08:10 </span>
-
Georg Ringer commented and changed status
AcceptedClosed <span data-processor="relativetime" data-value="2026-11-14T20:08:28+00:00" > 11/14/26, 20:08 </span>
The goal of this issue, declaring in a structured way which remote sources an extension needs, is covered by the Content Security Policy integration in the meantime. Extensions declare the sources they require in
Configuration/ContentSecurityPolicies.php(see for exampleEXT:extensionmanagerandEXT:backend), and integrators can review and adjust them per site, including report-only handling and violation reporting. A second, parallel manifest would hold the same information twice, so I am closing this issue.If a human-readable description per source for administrators, or hashes/signatures for embedded remote content, are still of interest, please open a dedicated issue for them so that it can be discussed on its own.