Content Security Policy

From: Jonas Thelemann <e-mail(at)jonas-thelemann(dot)de>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: Content Security Policy
Date: 2017-01-10 03:21:18
Message-ID: 881a8266-3214-c44d-2fbd-26e1ef5b007d@jonas-thelemann.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Good day pgadmin-hackers,

my name is Jonas Thelemann and I just joined this mailing list. It's my
first mailing list, so I try my best to not make any mistakes.
I joined because I want to contribute some small adjustments to pgadmin.
More precisely to address CSP (Content Security Policy
<https://content-security-policy.com/>) issues.
I wanted to migrate from phppgadmin to pgadmin, because it's the more
contemporary solution, it's possible to influence the development and
because I had problems with my website's CSP restrictions with
phppgadmin. The main problem is just that there is inline JavaScript on
the html page(s) which is considered as insecure by CSP. This issue is
very easy to eliminate though. All occurrences of '<script>foo</script>'
- I counted three so far - have to be replaced with '<script
src="bar"></script>'.
If no one else is currently "working" [that's not serious work, I know]
on this and this can be realized, I'd like to make these small changes
to get to know Git a little bit better.

Greetings from Germany,
Jonas Thelemann

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2017-01-10 04:02:45 Re: Content Security Policy
Previous Message Dave Page 2017-01-09 11:46:42 pgAdmin 4 commit: Fix copyright year on doc page. Fixes #2045