summaryrefslogtreecommitdiffstats
path: root/bower.json
diff options
context:
space:
mode:
authorLukas Reschke <lukas@owncloud.com>2015-11-28 12:19:58 +0100
committerLukas Reschke <lukas@owncloud.com>2015-11-28 12:21:53 +0100
commitf3e9106864421d902cb3751fdd0004f84b369938 (patch)
tree4b95bf59fb688f4628e213fa16b4187ec74e4cec /bower.json
parentd305412a357f31174abff757602b343c24cd91c1 (diff)
downloadnextcloud-server-f3e9106864421d902cb3751fdd0004f84b369938.tar.gz
nextcloud-server-f3e9106864421d902cb3751fdd0004f84b369938.zip
Don't trust update server
In case the update server may deliver malicious content this would allow an adversary to inject arbitrary HTML into the response. So very bad stuff. While signing the response would be better and something we can also do in the future (considering the code signing work), this is already a good first start.
Diffstat (limited to 'bower.json')
0 files changed, 0 insertions, 0 deletions