View Issue Details

IDProjectCategoryView StatusLast Update
0004637TalerWeb site(s)public2016-10-11 15:28
ReporterMarcello Stanisci Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityhighSeveritytweakReproducibilityhave not tried
Status closedResolutionfixed 
Product Version0.0 
Target Version0.1Fixed in Version0.1 
Summary0004637: Inline scripts/styles not accepted anymore
DescriptionChromium, maybe jointly with the Taler extension, does not like anymore inline scripts/styles. Apparently it depends from the extension's manifest file, but the page which triggers the complain does not belong to the wallet. That currently prevents us from withdrawing coins, as the form is dynamically generated. Below is the message:

Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-MB/UFUdXxj8tcQU8gPBz4nxUcSjxNb24vq/Wa/Gu9ps='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback.

blog.test.taler.net/:96 Refused to execute inline script because it violates the following Content Security Policy directive: "default-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-zBP1dcmi7VJsAQ4s7yRPrzWSxYmzP5/Xx+iML1zNymc='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Marcello Stanisci

2016-09-02 13:00

reporter   ~0011084

modifying the manifest.json from the wallet did not fix it

Marcello Stanisci

2016-09-05 12:22

reporter   ~0011088

The problem was due to some changes made in nginx config aimed to harden the
Content Security Policy, so starting from commit 7ba48b611e2683e49, web-common has no inline JavaScript/CSS anymore.

Issue History

Date ModifiedUsernameFieldChange
2016-09-02 12:50Marcello StanisciNew Issue
2016-09-02 13:00Marcello StanisciNote Added: 0011084
2016-09-02 14:33Marcello StanisciAssigned To => Marcello Stanisci
2016-09-02 14:33Marcello StanisciStatusnew => assigned
2016-09-05 11:06Christian GrothoffSeveritymajor => tweak
2016-09-05 12:22Marcello StanisciNote Added: 0011088
2016-09-05 12:22Marcello StanisciStatusassigned => informing
2016-09-05 12:22Marcello StanisciResolutionopen => fixed
2016-09-18 22:55Christian GrothoffProduct Versiongit (master) => 0.0
2016-09-18 22:55Christian GrothoffFixed in Version => 0.1
2016-09-18 22:55Christian GrothoffTarget Version => 0.1
2016-10-11 15:28Christian GrothoffStatusinforming => closed